From owner-linux-xfs@oss.sgi.com Sat Sep 1 04:42:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81Bg1j10325 for linux-xfs-outgoing; Sat, 1 Sep 2001 04:42:01 -0700 Received: from st-peter.stw.uni-erlangen.de (IDENT:qmailr@voyager.st-peter.stw.uni-erlangen.de [131.188.24.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81Bfld10300 for ; Sat, 1 Sep 2001 04:41:47 -0700 Received: (qmail 4750 invoked from network); 1 Sep 2001 11:41:46 -0000 Received: from svetljo.st-peter.stw.uni-erlangen.de (HELO st-peter.stw.uni-erlangen.de) (172.17.17.181) by voyager.st-peter.stw.uni-erlangen.de with SMTP; 1 Sep 2001 11:41:46 -0000 Message-ID: <3B90C9A4.3080005@st-peter.stw.uni-erlangen.de> Date: Sat, 01 Sep 2001 13:42:28 +0200 From: svetljo User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010802 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com, raiddev@nuclecu.unam.mx, linux-lvm@sistina.com Subject: Re: [linux-lvm] PBs with LVM over software RAID ( and XFS ? ext2 reiserfs?) References: <3B8E3F0E.8050609@st-peter.stw.uni-erlangen.de> <20010830083546.A20989@sistina.com> <3B8EC633.40202@st-peter.stw.uni-erlangen.de> <3B8F8C5E.7030603@st-peter.stw.uni-erlangen.de> <20010831110512.V541@turbolinux.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi a small adition i've tried to format the LV with ext2 and reiserfs, but it didn't worked : mkfs segfaults a strange one : i'm able to format with IBM JFS , and i can work without a problem with the LV everything just to be fine with JFS i'm currently building: clean 2.4.9-linus with LVM-1.0.1rc1 2.4.9-ac5 with LVM-1.0 ( i couldn't do it with LVM-1.0.1rc1 & rc2) 2.4.10-pre2-xfs-cvs with LVM-1.0.1rc2 to find out what is going on with ext2 reiserfs XFS , is the problem coming from the XFS kernel changes >Hi >i'm having a serios trouble with creating >a LVM over software linear RAID >well i created it, formated it with XFS >but every time i try to mount the LV mount segfaults >and then i can not mount any other file system ( partition, CD, .. >until i reboot, when i try to mount smth mount simple stop to respond >without an error and blocks the console > >i'm using XFS cvs kernel 2.4.9 and LVM-1.0.1rc1 >on ABIT's BP6 2xCelleron 533 512Mb RAM >the drives are on onboard HPT366 controler 2xWD 30Gb 1xMaxtor 40Gb > >the LV is striped over the 3 devices of the VG >the VG is /dev/hdh10 /dev/md6 /dev/md7 >/dev/md6 is linear software RAID /dev/hde6 /dev/hde12 >/dev/md7 is linear software RAID /dev/hdg1 /dev/hdg5 /dev/hdg6 >dev/hdg11 > >i posted to the LVM-lists and there i was told >to try "dmesg | ksymoops" > >and i became the folowing answer > > > >>EIP; e29c0266 <[linear]linear_make_request+36/f0> <===== > > > >> Trace; c023fa12 <__make_request+412/6d0> > >> Trace; c0278dcd > >> Trace; c027fa0f > >> Trace; c023fd89 > > > >OK, so the oops is inside the RAID layer, but it may be that it is > >being fed bogus data from a higher layer. Even so, it should not > >oops in this case. Since XFS changes a lot of the kernel code, I > >would either suggest asking the XFS folks to look at this oops, > >or maybe on the MD RAID mailing list, as they will know more about >it. > >this is the full "dmesg | ksymoops" , i'll try to use other FS to find >out whether it's a problem with XFS, but i wish me not to have to use >other FS, i realy love XFS Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010247 eax: 004ac1ab ebx: 004ac1ab ecx: 00000000 edx: 00000000 esi: d54eb320 edi: c188b928 ebp: 00958357 esp: d4eb3670 ds: 0018 es: 0018 ss: 0018 Process mount (pid: 5536, stackpage=d4eb3000) Stack: d54eb3e0 c023fa12 00000907 d54eb320 00000000 01c02000 c0278dcd dcec43c0 00000000 d54eb320 d54eb320 00000000 01c02000 c027fa0f 00000001 d54eb320 c023fd89 c03a7254 00000000 d54eb320 00000282 00000021 00000000 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: f7 f9 85 d2 74 24 55 51 68 c0 03 9c e2 e8 58 6c 75 dd 6a 00 >>EIP; e29c0266 <[linear]linear_make_request+36/f0> <===== Trace; c023fa12 <__make_request+412/6d0> Trace; c0278dcd Trace; c027fa0f Trace; c023fd89 Trace; c01a6814 <_pagebuf_page_io+1f4/370> Trace; c01a6a85 <_page_buf_page_apply+f5/1c0> Trace; c01a6fc1 Trace; c01a6c47 Trace; c01a6990 <_page_buf_page_apply+0/1c0> Trace; c0105dac <__down+bc/d0> Trace; c0105f1c <__down_failed+8/c> Trace; c02e2140 Trace; c021c10a Trace; c01fe5b8 Trace; c01ff2a4 Trace; c01a553e <_pagebuf_get_object+3e/170> Trace; c01feb6f Trace; c01feed8 Trace; c01fc322 Trace; c0201f40 Trace; c01fb8f3 Trace; c0202fdf Trace; c02026bf Trace; c01a60be Trace; c02026eb Trace; c021e674 Trace; c020b69c Trace; c020b843 Trace; c020b871 Trace; c021cf48 Trace; c01294e0 Trace; c0125f0e Trace; c0125d9d Trace; c013cd72 Trace; c013d01b Trace; c013dafc Trace; c01131e0 Trace; c010724c Trace; c013dd56 Trace; c013dbfc Trace; c013de13 Trace; c010715b Code; e29c0266 <[linear]linear_make_request+36/f0> 00000000 <_EIP>: Code; e29c0266 <[linear]linear_make_request+36/f0> <===== 0: f7 f9 idiv %ecx,%eax <===== Code; e29c0268 <[linear]linear_make_request+38/f0> 2: 85 d2 test %edx,%edx Code; e29c026a <[linear]linear_make_request+3a/f0> 4: 74 24 je 2a <_EIP+0x2a> e29c0290 <[linear]linear_make_request+60/f0> Code; e29c026c <[linear]linear_make_request+3c/f0> 6: 55 push %ebp Code; e29c026d <[linear]linear_make_request+3d/f0> 7: 51 push %ecx Code; e29c026e <[linear]linear_make_request+3e/f0> 8: 68 c0 03 9c e2 push $0xe29c03c0 Code; e29c0273 <[linear]linear_make_request+43/f0> d: e8 58 6c 75 dd call dd756c6a <_EIP+0xdd756c6a> c0116ed0 Code; e29c0278 <[linear]linear_make_request+48/f0> 12: 6a 00 push $0x0 Andreas Dilger wrote: >On Aug 31, 2001 15:08 +0200, svetljo wrote: > >>[root@svetljo mnt]# mount -t xfs /dev/myData/Music music >>Segmentation fault >> > >Generally this is a bad sign. Either mount is segfaulting (unlikely) >or you are getting an oops in the kernel. You need do run something >like "dmesg | ksymoops" in order to get some useful data about where >the problem is (could be xfs, LVM, or elsewhere in the kernel). > >Once you have an oops, you are best off rebooting the system, because >your kernel memory may be corrupted, and cause more oopses which do >not mean anything. If you look in /var/log/messages (or /var/log/kern.log >or some other place, depending on where kernel messages go), you can >decode the FIRST oops in the log with ksymoops. All subsequent ones are >useless. > > >>the LV ( lvcreate -i3 -I4 -L26G -nMusic ) >> >>the VG -> myData /dev/hdh10 /dev/linVG1/linLV1 /dev/linVG2/linLV2 >> >>/dev/hdh10 normal partition 14G >>/dev/linVG1/linLV1 -> linear LV 14G /dev/hde6 /dev/hde12 >>/dev/linVg2/linLV2 -> linear LV 14G /dev/hdg1 /dev/hdg5 /dev/hdg6 /dev/hdg12 >> > >There is absolutely no point in doing this (not that it is possible to do >so anyways). First of all, striping is almost never needed "for performance" >unless you are normally doing very large sequential I/Os, and even so most >disks today have very good sequential I/O rates (e.g. 15-30MB/s). Secondly, >you _should_ be able to just create a single LV that is striped across all >of the PVs above. You would likely need to build it in steps, to ensure >that it is striped across the disks correctly. > >Cheers, Andreas > From owner-linux-xfs@oss.sgi.com Sat Sep 1 07:20:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81EKQY12721 for linux-xfs-outgoing; Sat, 1 Sep 2001 07:20:26 -0700 Received: from st-peter.stw.uni-erlangen.de (IDENT:qmailr@voyager.st-peter.stw.uni-erlangen.de [131.188.24.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81EKDd12701 for ; Sat, 1 Sep 2001 07:20:13 -0700 Received: (qmail 8400 invoked from network); 1 Sep 2001 14:20:11 -0000 Received: from svetljo.st-peter.stw.uni-erlangen.de (HELO st-peter.stw.uni-erlangen.de) (172.17.17.181) by voyager.st-peter.stw.uni-erlangen.de with SMTP; 1 Sep 2001 14:20:11 -0000 Message-ID: <3B90EEC8.3030402@st-peter.stw.uni-erlangen.de> Date: Sat, 01 Sep 2001 16:20:56 +0200 From: svetljo User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010802 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-lvm@sistina.com, linux-xfs@oss.sgi.com, akpm@zip.com.au, neilb@cse.unsw.edu.au Subject: Re: [linux-lvm] PBs with LVM over software RAID ( and XFS ? ext2 reiserfs?) References: <3B8E3F0E.8050609@st-peter.stw.uni-erlangen.de> <20010830083546.A20989@sistina.com> <3B8EC633.40202@st-peter.stw.uni-erlangen.de> <3B8F8C5E.7030603@st-peter.stw.uni-erlangen.de> <20010831110512.V541@turbolinux.com> <3B90C9A4.3080005@st-peter.stw.uni-erlangen.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk and here are the results of mkfs ############################################################### ######### linus-2.4.9 lvm-1.0.1rc1 ################### ############################################################### [root@svetljo root]# mkfs -t reiserfs -f /dev/myData/SRC mkreiserfs, 2001 - reiserfsprogs 3.x.0j =================================================================== LEAF NODE (8211) contains level=1, nr_items=2, free_space=3932 rdkey ------------------------------------------------------------------------------- |###|type|ilen|f/sp| loc|fmt|fsck| key | | | | |e/cn| | |need| | ------------------------------------------------------------------------------- Segmentation fault [root@svetljo root]# mkfs -t ext2 -f /dev/myData/SRC mke2fs 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09 mkfs.ext2: bad fragment size - /dev/myData/SRC ################################################################ ########### linux-2.4.9-ac5 lvm-1.0 ######################## ################################################################ [root@svetljo root]# mkfs -t reiserfs /dev/myData/SRC mkreiserfs, 2001 - reiserfsprogs 3.x.0j =================================================================== LEAF NODE (8211) contains level=1, nr_items=2, free_space=3932 rdkey ------------------------------------------------------------------------------- |###|type|ilen|f/sp| loc|fmt|fsck| key | | | | |e/cn| | |need| | ------------------------------------------------------------------------------- Segmentation fault [root@svetljo root]# mkfs -t reiserfs -f /dev/myData/SRC mkreiserfs, 2001 - reiserfsprogs 3.x.0j =================================================================== LEAF NODE (8211) contains level=1, nr_items=2, free_space=3932 rdkey ------------------------------------------------------------------------------- |###|type|ilen|f/sp| loc|fmt|fsck| key | | | | |e/cn| | |need| | ------------------------------------------------------------------------------- Segmentation fault [root@svetljo root]# mkfs -t ext2 -f /dev/myData/SRC mke2fs 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09 mkfs.ext2: bad fragment size - /dev/myData/SRC [root@svetljo root]# mkfs -t ext2 /dev/myData/SRC mke2fs 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09 Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 786432 inodes, 1572864 blocks 78643 blocks (5.00%) reserved for the super user First data block=0 48 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Writing inode tables: Segmentation fault ##################################################################### ### and linux-2.4.10-pre2-xfs lvm-1.0.1rc2 ####### ##################################################################### [root@svetljo root]# mkfs -t reiserfs /dev/myData/SRC mkreiserfs, 2001 - reiserfsprogs 3.x.0j =================================================================== LEAF NODE (8211) contains level=1, nr_items=2, free_space=3932 rdkey ------------------------------------------------------------------------------- |###|type|ilen|f/sp| loc|fmt|fsck| key | | | | |e/cn| | |need| | ------------------------------------------------------------------------------- Segmentation fault [root@svetljo root]# mkfs -t reiserfs -f /dev/myData/SRC mkreiserfs, 2001 - reiserfsprogs 3.x.0j =================================================================== LEAF NODE (8211) contains level=1, nr_items=2, free_space=3932 rdkey ------------------------------------------------------------------------------- |###|type|ilen|f/sp| loc|fmt|fsck| key | | | | |e/cn| | |need| | ------------------------------------------------------------------------------- Segmentation fault [root@svetljo root]# mkfs -t ext2 /dev/myData/SRC mke2fs 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09 Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 786432 inodes, 1572864 blocks 78643 blocks (5.00%) reserved for the super user First data block=0 48 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Writing inode tables: Segmentation fault [root@svetljo root]# mkfs -t ext2 -f /dev/myData/SRC mke2fs 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09 mkfs.ext2: bad fragment size - /dev/myData/SRC [root@svetljo root]# mkfs -t xfs /dev/myData/SRC meta-data=/dev/myData/SRC isize=256 agcount=8, agsize=196608 blks data = bsize=4096 blocks=1572864, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=0 naming =version 2 bsize=4096 log =internal log bsize=4096 blocks=1200 realtime =none extsz=65536 blocks=0, rtextents=0 [root@svetljo root]# mkfs -t xfs -f /dev/myData/SRC meta-data=/dev/myData/SRC isize=256 agcount=8, agsize=196608 blks data = bsize=4096 blocks=1572864, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=0 naming =version 2 bsize=4096 log =internal log bsize=4096 blocks=1200 realtime =none extsz=65536 blocks=0, rtextents=0 From owner-linux-xfs@oss.sgi.com Sat Sep 1 07:30:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81EUBq13030 for linux-xfs-outgoing; Sat, 1 Sep 2001 07:30:11 -0700 Received: from st-peter.stw.uni-erlangen.de (IDENT:qmailr@voyager.st-peter.stw.uni-erlangen.de [131.188.24.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81ETqd12999 for ; Sat, 1 Sep 2001 07:29:52 -0700 Received: (qmail 5989 invoked from network); 1 Sep 2001 14:10:44 -0000 Received: from svetljo.st-peter.stw.uni-erlangen.de (HELO st-peter.stw.uni-erlangen.de) (172.17.17.181) by voyager.st-peter.stw.uni-erlangen.de with SMTP; 1 Sep 2001 14:10:44 -0000 Message-ID: <3B90EC90.4050606@st-peter.stw.uni-erlangen.de> Date: Sat, 01 Sep 2001 16:11:28 +0200 From: svetljo User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010802 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-lvm@sistina.com, linux-xfs@oss.sgi.com, akpm@zip.com.au, neilb@cse.unsw.edu.au Subject: Re: [linux-lvm] PBs with LVM over software RAID ( and XFS ? ext2 reiserfs?) References: <3B8E3F0E.8050609@st-peter.stw.uni-erlangen.de> <20010830083546.A20989@sistina.com> <3B8EC633.40202@st-peter.stw.uni-erlangen.de> <3B8F8C5E.7030603@st-peter.stw.uni-erlangen.de> <20010831110512.V541@turbolinux.com> <3B90C9A4.3080005@st-peter.stw.uni-erlangen.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk well i did the tests clean Linus kernel-2.4.9 LVM-1.0.1rc1 ext2 and reiserfs segfaults clean linux-2.4.9-ac5 LVM-1.0 ext2 and reiserfs segfaults | linux-2.4.10-pre2-xfs LVM-1.0.1rc2 ext2 and reiserfs segfaults, but xfs seems to work | from SGI's cvs tree linux-2.4-xfs taken today in the early morning i'll try to ad IBM's JFS and try it again and i'll try bonnie on them can you give me ideas how to stres the FS to find out whether it realy works with XFS and JFS what could be wrong with ext2 and reiserfs as it works with JFS-1.0.3 and with the latest cvs XFS svetljo wrote: > Hi > > a small adition i've tried to format the LV with ext2 and reiserfs, > but it didn't worked : mkfs segfaults > a strange one : i'm able to format with IBM JFS , and i can work > without a problem with the LV everything just to be fine with JFS > > i'm currently building: > clean 2.4.9-linus with LVM-1.0.1rc1 > 2.4.9-ac5 with LVM-1.0 ( i couldn't do it with LVM-1.0.1rc1 & rc2) > 2.4.10-pre2-xfs-cvs with LVM-1.0.1rc2 > to find out what is going on with ext2 reiserfs XFS , > is the problem coming from the XFS kernel changes > > >Hi > >i'm having a serios trouble with creating > >a LVM over software linear RAID > >well i created it, formated it with XFS > >but every time i try to mount the LV mount segfaults > >and then i can not mount any other file system ( partition, CD, .. > >until i reboot, when i try to mount smth mount simple stop to respond > >without an error and blocks the console > > > >i'm using XFS cvs kernel 2.4.9 and LVM-1.0.1rc1 > >on ABIT's BP6 2xCelleron 533 512Mb RAM > >the drives are on onboard HPT366 controler 2xWD 30Gb 1xMaxtor 40Gb > > > >the LV is striped over the 3 devices of the VG > >the VG is /dev/hdh10 /dev/md6 /dev/md7 > >/dev/md6 is linear software RAID /dev/hde6 /dev/hde12 > >/dev/md7 is linear software RAID /dev/hdg1 /dev/hdg5 /dev/hdg6 > >dev/hdg11 > > > >i posted to the LVM-lists and there i was told > >to try "dmesg | ksymoops" > > > >and i became the folowing answer > > > > > >>EIP; e29c0266 <[linear]linear_make_request+36/f0> <===== > > > > > >> Trace; c023fa12 <__make_request+412/6d0> > > >> Trace; c0278dcd > > >> Trace; c027fa0f > > >> Trace; c023fd89 > > > > > >OK, so the oops is inside the RAID layer, but it may be that it is > > >being fed bogus data from a higher layer. Even so, it should not > > >oops in this case. Since XFS changes a lot of the kernel code, I > > >would either suggest asking the XFS folks to look at this oops, > > >or maybe on the MD RAID mailing list, as they will know more about > >it. > > > >this is the full "dmesg | ksymoops" , i'll try to use other FS to find > >out whether it's a problem with XFS, but i wish me not to have to use > >other FS, i realy love XFS > > > Using defaults from ksymoops -t elf32-i386 -a i386 > EFLAGS: 00010247 > eax: 004ac1ab ebx: 004ac1ab ecx: 00000000 edx: 00000000 > esi: d54eb320 edi: c188b928 ebp: 00958357 esp: d4eb3670 > ds: 0018 es: 0018 ss: 0018 > Process mount (pid: 5536, stackpage=d4eb3000) > Stack: d54eb3e0 c023fa12 00000907 d54eb320 00000000 01c02000 c0278dcd > dcec43c0 > 00000000 d54eb320 d54eb320 00000000 01c02000 c027fa0f 00000001 > d54eb320 > c023fd89 c03a7254 00000000 d54eb320 00000282 00000021 00000000 > 00000000 > Call Trace: [] [] [] [] > [] > [] [] [] [] [] > [] > [] [] [] [] [] > [] > [] [] [] [] [] > [] > [] [] [] [] [] > [] > [] [] [] [] [] > [] > [] [] [] [] [] > [] > [] > Code: f7 f9 85 d2 74 24 55 51 68 c0 03 9c e2 e8 58 6c 75 dd 6a 00 > > >>EIP; e29c0266 <[linear]linear_make_request+36/f0> <===== > Trace; c023fa12 <__make_request+412/6d0> > Trace; c0278dcd > Trace; c027fa0f > Trace; c023fd89 > Trace; c01a6814 <_pagebuf_page_io+1f4/370> > Trace; c01a6a85 <_page_buf_page_apply+f5/1c0> > Trace; c01a6fc1 > Trace; c01a6c47 > Trace; c01a6990 <_page_buf_page_apply+0/1c0> > Trace; c0105dac <__down+bc/d0> > Trace; c0105f1c <__down_failed+8/c> > Trace; c02e2140 > Trace; c021c10a > Trace; c01fe5b8 > Trace; c01ff2a4 > Trace; c01a553e <_pagebuf_get_object+3e/170> > Trace; c01feb6f > Trace; c01feed8 > Trace; c01fc322 > Trace; c0201f40 > Trace; c01fb8f3 > Trace; c0202fdf > Trace; c02026bf > Trace; c01a60be > Trace; c02026eb > Trace; c021e674 > Trace; c020b69c > Trace; c020b843 > Trace; c020b871 > Trace; c021cf48 > Trace; c01294e0 > Trace; c0125f0e > Trace; c0125d9d > Trace; c013cd72 > Trace; c013d01b > Trace; c013dafc > Trace; c01131e0 > Trace; c010724c > Trace; c013dd56 > Trace; c013dbfc > Trace; c013de13 > Trace; c010715b > Code; e29c0266 <[linear]linear_make_request+36/f0> > 00000000 <_EIP>: > Code; e29c0266 <[linear]linear_make_request+36/f0> <===== > 0: f7 f9 idiv %ecx,%eax <===== > Code; e29c0268 <[linear]linear_make_request+38/f0> > 2: 85 d2 test %edx,%edx > Code; e29c026a <[linear]linear_make_request+3a/f0> > 4: 74 24 je 2a <_EIP+0x2a> e29c0290 > <[linear]linear_make_request+60/f0> > Code; e29c026c <[linear]linear_make_request+3c/f0> > 6: 55 push %ebp > Code; e29c026d <[linear]linear_make_request+3d/f0> > 7: 51 push %ecx > Code; e29c026e <[linear]linear_make_request+3e/f0> > 8: 68 c0 03 9c e2 push $0xe29c03c0 > Code; e29c0273 <[linear]linear_make_request+43/f0> > d: e8 58 6c 75 dd call dd756c6a <_EIP+0xdd756c6a> > c0116ed0 > Code; e29c0278 <[linear]linear_make_request+48/f0> > 12: 6a 00 push $0x0 > > Andreas Dilger wrote: > > >On Aug 31, 2001 15:08 +0200, svetljo wrote: > > > >>[root@svetljo mnt]# mount -t xfs /dev/myData/Music music > >>Segmentation fault > >> > > > >Generally this is a bad sign. Either mount is segfaulting (unlikely) > >or you are getting an oops in the kernel. You need do run something > >like "dmesg | ksymoops" in order to get some useful data about where > >the problem is (could be xfs, LVM, or elsewhere in the kernel). > > > >Once you have an oops, you are best off rebooting the system, because > >your kernel memory may be corrupted, and cause more oopses which do > >not mean anything. If you look in /var/log/messages (or > /var/log/kern.log > >or some other place, depending on where kernel messages go), you can > >decode the FIRST oops in the log with ksymoops. All subsequent ones > are > >useless. > > > > > >>the LV ( lvcreate -i3 -I4 -L26G -nMusic ) > >> > >>the VG -> myData /dev/hdh10 /dev/linVG1/linLV1 /dev/linVG2/linLV2 > >> > >>/dev/hdh10 normal partition 14G > >>/dev/linVG1/linLV1 -> linear LV 14G /dev/hde6 /dev/hde12 > >>/dev/linVg2/linLV2 -> linear LV 14G /dev/hdg1 /dev/hdg5 /dev/hdg6 > /dev/hdg12 > >> > > > >There is absolutely no point in doing this (not that it is possible > to do > >so anyways). First of all, striping is almost never needed "for > performance" > >unless you are normally doing very large sequential I/Os, and even > so most > >disks today have very good sequential I/O rates (e.g. 15-30MB/s). > Secondly, > >you _should_ be able to just create a single LV that is striped > across all > >of the PVs above. You would likely need to build it in steps, to > ensure > >that it is striped across the disks correctly. > > > >Cheers, Andreas > > > > > > > From owner-linux-xfs@oss.sgi.com Sat Sep 1 09:11:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81GBnn14749 for linux-xfs-outgoing; Sat, 1 Sep 2001 09:11:49 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81GBad14730 for ; Sat, 1 Sep 2001 09:11:36 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id 4EBB467040; Sat, 1 Sep 2001 18:11:30 +0200 (CEST) To: Seth Mos Cc: linux-xfs@oss.sgi.com, Michael Wahlbrink Subject: Re: Kernel Oops ..... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Sat, 1 Sep 2001 18:11:28 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 18:11:32, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 18:11:32, Serialize complete at 01.09.2001 18:11:32, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 18:11:33, S/MIME Sign complete at 01.09.2001 18:11:33, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 18:11:33, Serialize complete at 01.09.2001 18:11:33, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 01.09.2001 18:11:30, Serialize complete at 01.09.2001 18:11:30 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z44518_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z44518_boundary_sign Content-Type: text/plain; charset="us-ascii" On 31.08.2001 23:57:07 Seth Mos wrote: >On Fri, 31 Aug 2001, Michael Wahlbrink wrote: > >> On 31.08.2001 23:12:22 Seth Mos wrote: >> >On Fri, 31 Aug 2001, Eric Sandeen wrote: >> > >> >> Michael Wahlbrink wrote: >> >> >> >> > Hi eric, >> >> > I've read this, but where I can get this egs for the suse 7.2 >which >> >I have >> >> > to use (company standard..... I would prefer debian.......)?? >> >> > >> >> > So I hope you can help me.... >> >> >> >> Hi Michael - >> >> >> >> I _think_ you could use Red Hat's compat-egcs and compat-glibc RPMs >> >on a >> >> SuSE system, to get this compiler - can any of the SuSE-users >verify >> >> that this is OK? >> > >> >I have seen reports that it can succesfully be used on SuSE. I >believe >> >this is what most people are doing right now. >> > >> >Cheers >> Ok I've downloaded and installed these rpms, now my stupid question: >what >> I've to do, that these other Compiler will be used (change the >'cc-link' >> to the kgcc??)???? I'm now so far with xfs so I want also a running >system >> ;-) so please give me a little hint, that I can bring my first >xfs-box up! > >In the top level Makefile for the kernel is one that is especially for >kgcc. > >You can find it including comments. Just remove the # sign from that >line. > >Cheers >Seth Hi, Bad news..... Ok, the Kernel compiled fine with kgcc ;-) and it runs longer under load then the other old kernel but i get an oops again...... :-( here it is! cu micha ksymoops 2.4.1 on i686 2.4.10-pre2-xfs. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.10-pre2-xfs/ (default) -m /boot/System.map-2.4.10-pre2-xfs (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. No modules in ksyms, skipping objects Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file? Sep 1 19:01:03 swan kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000152 Sep 1 19:01:03 swan kernel: c01b3e95 Sep 1 19:01:03 swan kernel: *pde = 00000000 Sep 1 19:01:03 swan kernel: Oops: 0000 Sep 1 19:01:03 swan kernel: CPU: 0 Sep 1 19:01:03 swan kernel: EIP: 0010:[xlog_recover_do_inode_trans+1461/1600] Sep 1 19:01:03 swan kernel: EFLAGS: 00010246 Sep 1 19:01:03 swan kernel: eax: 00000000 ebx: ffffffe8 ecx: c1461b18 edx: c02bc7e0 Sep 1 19:01:03 swan kernel: esi: cf75a18c edi: cf5e0c00 ebp: 00000000 esp: c9a75e0c Sep 1 19:01:03 swan kernel: ds: 0018 es: 0018 ss: 0018 Sep 1 19:01:03 swan kernel: Process rm (pid: 2996, stackpage=c9a75000) Sep 1 19:01:03 swan kernel: Stack: 0000006c 00000000 cf5e0c00 00000008 c01cac0c cf5e0c00 00000000 030a3225 Sep 1 19:01:03 swan kernel: 00000000 00000000 c9a75ec4 00000000 00000000 c2172614 c21725fc 00000008 Sep 1 19:01:03 swan kernel: ce957640 c8498050 c8498042 00000084 00000000 c01d21a0 c8498000 cf5e0c00 Sep 1 19:01:03 swan kernel: Call Trace: [xfs_ioctl+3388/4528] [uiomove+192/320] [xfs_dir2_sf_toino8+704/1056] [_lsn_cmp+167/224] [_lsn_cmp+16/224] Sep 1 19:01:03 swan kernel: Code: 66 83 bb 6a 01 00 00 00 75 10 80 a3 50 01 00 00 f7 53 e8 54 Using defaults from ksymoops -t elf32-i386 -a i386 Code; 00000000 Before first symbol 00000000 <_EIP>: Code; 00000000 Before first symbol 0: 66 83 bb 6a 01 00 00 cmpw $0x0,0x16a(%ebx) Code; 00000007 Before first symbol 7: 00 Code; 00000008 Before first symbol 8: 75 10 jne 1a <_EIP+0x1a> 0000001a Before first symbol Code; 0000000a Before first symbol a: 80 a3 50 01 00 00 f7 andb $0xf7,0x150(%ebx) Code; 00000011 Before first symbol 11: 53 push %ebx Code; 00000012 Before first symbol 12: e8 54 00 00 00 call 6b <_EIP+0x6b> 0000006b Before first symbol 2 warnings issued. Results may not be reliable. ---------z44518_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwMTE2MTEzM1owIwYJKoZIhvcNAQkEMRYEFJRGiFvt3VYwK6XF wgUVHGLdd3LPMEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGAUxkzEYvy1gY9xGG0mHw8AgHF4rrzR/zMR9NeUKW0VYUuCBl/1ZlI WOPA4/Qo5+IMFX8qjZKPiB6jbnRjSq2i4xn/uOqIqY7yCKX5CaF+b9P05WbAz1VZ 7d7wBDsTk87jQv9EvvrfW/HDfQO4iErEG51y2hmYTTib93GXP5TrWoQAAAAAAAAA AA== ---------z44518_boundary_sign-- From owner-linux-xfs@oss.sgi.com Sat Sep 1 09:35:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81GZpV15201 for linux-xfs-outgoing; Sat, 1 Sep 2001 09:35:51 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81GZmd15182 for ; Sat, 1 Sep 2001 09:35:48 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id SAA10195; Sat, 1 Sep 2001 18:35:47 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id SAA22040; Sat, 1 Sep 2001 18:35:47 +0200 (CEST) Date: Sat, 1 Sep 2001 18:35:46 +0200 (CEST) From: Seth Mos To: Michael Wahlbrink cc: linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 1 Sep 2001, Michael Wahlbrink wrote: > On 31.08.2001 23:57:07 Seth Mos wrote: > >On Fri, 31 Aug 2001, Michael Wahlbrink wrote: > > Hi, > Bad news..... > Ok, the Kernel compiled fine with kgcc ;-) and it runs longer under load > then the other old kernel but i get an oops again...... :-( > here it is! I see you are using part of the syslog messages. Can you find the syslog initscript and add the -x option to it? By adding -x to syslog it will not try to interpret the oops. This might give better results in running ksymoops. I am suspecting hardware problems. Could you find and run memtest86 to test your memory? I am updating my tree here to -pre2 as well and see if it gives me problems. Cheers Seth From owner-linux-xfs@oss.sgi.com Sat Sep 1 11:14:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81IEpT16682 for linux-xfs-outgoing; Sat, 1 Sep 2001 11:14:51 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81IEld16660 for ; Sat, 1 Sep 2001 11:14:47 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f81IEe507252 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Sat, 1 Sep 2001 11:14:40 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id UAA797770 for ; Sat, 1 Sep 2001 20:14:39 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA1957513; Sat, 1 Sep 2001 13:13:21 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA95154; Sat, 1 Sep 2001 13:13:15 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f81IBbO23125; Sat, 1 Sep 2001 13:11:37 -0500 Message-Id: <200109011811.f81IBbO23125@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: David Lloyd cc: linux-xfs@oss.sgi.com Subject: Re: Pingpong-Journaling? In-Reply-To: Message from David Lloyd of "Fri, 31 Aug 2001 11:59:30 +0930." <3B8EF68A.C3FC5FCA@rebel.net.au> Content-Transfer-Encoding: 8bit Date: Sat, 01 Sep 2001 13:11:37 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Anyone got any comments on this with respect to XFS? Well, XFS transactions do not have 'invalidation blocks' they work differently than the scheme this seems to describe. The XFS journal is also very compact since it only logs the changes to blocks rather than the whole block. Right now we do not have any plans for changing the journalling in XFS - except for getting rid of the synchronous transactions in the delete path. Steve > > DSL > > -------- Original Message -------- > Subject: [reiserfs-list] Pingpong-Journaling in reiser4? > Date: Thu, 30 Aug 2001 23:30:16 +0200 > From: Xuan Baldauf > Organization: Medium.net > To: Hans Reiser > CC: reiserfs-list@namesys.com > > Hello Hans, > > are you considering pingpong-journaling for reiser4? > > Ping-Pong journaling is that, in the case you are able to > know that the blocks you are writing to will be overwritten > due to outstanding requests|future transactions, you do not > write the invalidation block of the old transaction until > the affected blocks are overwritten by the new transaction. > Doing journaling in that way, you are bringing the count of > required writes for journaling to the count of required > writes for non-journaling (1 changed block, 1 write instead > of 1 changed block, 1 write to the journal and 1 write to > the real location), and thus saving half the > journal-related writes in the ideal case. The superblock is > a good candidate for this feature. > > I think that heavily loaded servers with parallel disk > writes will be able to see a considerable speedup. > > Xubn. From owner-linux-xfs@oss.sgi.com Sat Sep 1 11:18:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81IIrB16855 for linux-xfs-outgoing; Sat, 1 Sep 2001 11:18:53 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81IIid16833 for ; Sat, 1 Sep 2001 11:18:44 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id E202E67040; Sat, 1 Sep 2001 20:18:37 +0200 (CEST) To: Seth Mos Cc: linux-xfs@oss.sgi.com, Michael Wahlbrink Subject: Re: Kernel Oops ..... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Sat, 1 Sep 2001 20:18:36 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 20:18:41, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 20:18:41, Serialize complete at 01.09.2001 20:18:41, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 20:18:41, S/MIME Sign complete at 01.09.2001 20:18:41, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 01.09.2001 20:18:38, Serialize complete at 01.09.2001 20:18:38 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z63867_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z63867_boundary_sign Content-Type: text/plain; charset="us-ascii" On 01.09.2001 18:35:46 Seth Mos wrote: >On Sat, 1 Sep 2001, Michael Wahlbrink wrote: > >> On 31.08.2001 23:57:07 Seth Mos wrote: >> >On Fri, 31 Aug 2001, Michael Wahlbrink wrote: >> >> Hi, >> Bad news..... >> Ok, the Kernel compiled fine with kgcc ;-) and it runs longer under >load >> then the other old kernel but i get an oops again...... :-( >> here it is! > >I see you are using part of the syslog messages. Can you find the syslog >initscript and add the -x option to it? By adding -x to syslog it will >not >try to interpret the oops. Ok its done! > >This might give better results in running ksymoops. > >I am suspecting hardware problems. Could you find and run memtest86 to >test your memory? No problem, as standard Suse Installs an Memtest Bootimage...... ..... I let run memtest for 1pass with no errors so it seems, that the 256mb infineon module works correct. Perhaps it is a problem, that i chose in the kernel athlon/duron as processor type, i'll build a kernel with only pentium.... maybe it will help? And will try the things also on another old pII mashine with only 2 30gig hdds....... (takes some time) > >I am updating my tree here to -pre2 as well and see if it gives me >problems. > >Cheers >Seth cu micha -- Michael Wahlbrink IT Services Propack Data GmbH Karlsruhe miw@propack-data.com 0721/9650-851 ---------z63867_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwMTE4MTg0MVowIwYJKoZIhvcNAQkEMRYEFEPXPs3Dzq/in1dp 4OMp49ZOFzuxMEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGAkVkLtD0KWtRhiTlgPW/FfQSUVypMlXt7IarqIEEHADdVEJTvCOYW au+dxXEFkMYi15o4WBh62cd5SS+LkBxhjcrU+GB8zFZaOTh1JU7uFc3AfITrwA4w 7cGVT26eiuma5OiyzkJInIfro/jTUBO2cngxOh8Xuf0zEphFbru9CpwAAAAAAAAA AA== ---------z63867_boundary_sign-- From owner-linux-xfs@oss.sgi.com Sat Sep 1 11:35:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81IZYF17329 for linux-xfs-outgoing; Sat, 1 Sep 2001 11:35:34 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81IZUd17310 for ; Sat, 1 Sep 2001 11:35:30 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA24229; Sat, 1 Sep 2001 20:35:29 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id UAA26065; Sat, 1 Sep 2001 20:35:29 +0200 (CEST) Date: Sat, 1 Sep 2001 20:35:28 +0200 (CEST) From: Seth Mos To: Michael Wahlbrink cc: linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 1 Sep 2001, Michael Wahlbrink wrote: > On 01.09.2001 18:35:46 Seth Mos wrote: > >On Sat, 1 Sep 2001, Michael Wahlbrink wrote: > > > >> On 31.08.2001 23:57:07 Seth Mos wrote: > >> >On Fri, 31 Aug 2001, Michael Wahlbrink wrote: > >> > >> Hi, > >> Bad news..... > >> Ok, the Kernel compiled fine with kgcc ;-) and it runs longer under > >load > >> then the other old kernel but i get an oops again...... :-( > >> here it is! > > > >I see you are using part of the syslog messages. Can you find the syslog > >initscript and add the -x option to it? By adding -x to syslog it will > >not > >try to interpret the oops. > > Ok its done! > > > > >This might give better results in running ksymoops. > > > >I am suspecting hardware problems. Could you find and run memtest86 to > >test your memory? > > No problem, as standard Suse Installs an Memtest Bootimage...... Nice. > ..... I let run memtest for 1pass with no errors so it seems, that the > 256mb infineon module works correct. > Perhaps it is a problem, that i chose in the kernel athlon/duron as > processor type, i'll build a kernel with only pentium.... maybe it will > help? It could affect, compiling for i386 will always work, but compiling for athlon/duron will make it faster. I compile my kernel for athlon systems and I don't have problems. Do you have the latest bios for your system, that is asuming you have a motherboard with a VIA chipset. > And will try the things also on another old pII mashine with only 2 30gig > hdds....... (takes some time) If can try it on another machine we can see if it is purely a software or hardware problem. Cheers Seth From owner-linux-xfs@oss.sgi.com Sat Sep 1 11:38:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81IcDG17479 for linux-xfs-outgoing; Sat, 1 Sep 2001 11:38:13 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81Ic5d17460; Sat, 1 Sep 2001 11:38:05 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id C751B67040; Sat, 1 Sep 2001 20:37:58 +0200 (CEST) To: "Michael Wahlbrink" Cc: Seth Mos , linux-xfs@oss.sgi.com, Michael Wahlbrink , owner-linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Sat, 1 Sep 2001 20:37:58 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 20:38:02, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 20:38:02, Serialize complete at 01.09.2001 20:38:02, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 20:38:02, S/MIME Sign complete at 01.09.2001 20:38:02, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 01.09.2001 20:37:59, Serialize complete at 01.09.2001 20:37:59 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z61674_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z61674_boundary_sign Content-Type: text/plain; charset="us-ascii" On 01.09.2001 20:18:36 "Michael Wahlbrink" wrote: >On 01.09.2001 18:35:46 Seth Mos wrote: [...] >>I see you are using part of the syslog messages. Can you find the >syslog >>initscript and add the -x option to it? By adding -x to syslog it will >>not >>try to interpret the oops. > >Ok its done! But no my syslog doesnt start anymore its complainig about an unknown option -x ;-( > >> cu micha ---------z61674_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwMTE4MzgwMlowIwYJKoZIhvcNAQkEMRYEFGu8kOB6bjK7RFZh Xs4qFnq+9KQRMEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGAhPZWDhB436a+KDuFEMk6/jL4NYjMZcMsj3csywhZEAxlYjnudg1i vz1K/TI8z8ILDyf7dTgC1FbuI9Z+L209dFy5xn6iFtPsrld7MqzRyXM7elrFzZHc Khs3vXOtAPf36ByqFZF/bFk95c60vOWj8g9UAd9niCLInHRpYZoLdsAAAAAAAAAA AA== ---------z61674_boundary_sign-- From owner-linux-xfs@oss.sgi.com Sat Sep 1 11:44:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81Iise17658 for linux-xfs-outgoing; Sat, 1 Sep 2001 11:44:54 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81Iind17638; Sat, 1 Sep 2001 11:44:50 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA25063; Sat, 1 Sep 2001 20:44:48 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id UAA26355; Sat, 1 Sep 2001 20:44:48 +0200 (CEST) Date: Sat, 1 Sep 2001 20:44:48 +0200 (CEST) From: Seth Mos To: Michael Wahlbrink cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 1 Sep 2001, Michael Wahlbrink wrote: > On 01.09.2001 20:18:36 "Michael Wahlbrink" wrote: > >On 01.09.2001 18:35:46 Seth Mos wrote: > [...] > >>I see you are using part of the syslog messages. Can you find the > >syslog > >>initscript and add the -x option to it? By adding -x to syslog it will > >>not > >>try to interpret the oops. > > > >Ok its done! > > But no my syslog doesnt start anymore its complainig about an unknown > option -x ;-( Oops! It seems that this is not supported under SuSE. It might be that SuSE uses another deamon for syslog. Ok skip that part. From owner-linux-xfs@oss.sgi.com Sat Sep 1 11:45:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81Ij6B17740 for linux-xfs-outgoing; Sat, 1 Sep 2001 11:45:06 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81Iixd17711 for ; Sat, 1 Sep 2001 11:44:59 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id BB49F67040; Sat, 1 Sep 2001 20:44:52 +0200 (CEST) To: Seth Mos Cc: linux-xfs@oss.sgi.com, Michael Wahlbrink Subject: Re: Kernel Oops ..... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Sat, 1 Sep 2001 20:44:51 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 20:44:56, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 20:44:56, Serialize complete at 01.09.2001 20:44:56, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 20:44:56, S/MIME Sign complete at 01.09.2001 20:44:56, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 01.09.2001 20:44:53, Serialize complete at 01.09.2001 20:44:53 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z49578_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z49578_boundary_sign Content-Type: text/plain; charset="us-ascii" On 01.09.2001 20:35:28 Seth Mos wrote: > >It could affect, compiling for i386 will always work, but compiling for >athlon/duron will make it faster. I compile my kernel for athlon systems >and I don't have problems. Do you have the latest bios for your system, >that is asuming you have a motherboard with a VIA chipset. > No, Its one with the new SiS735 (ECS K7S5A)....... But I'll see if there is a new bios..... >> And will try the things also on another old pII mashine with only 2 >30gig >> hdds....... (takes some time) > >If can try it on another machine we can see if it is purely a software >or >hardware problem. It's on the way cu michael ---------z49578_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwMTE4NDQ1NlowIwYJKoZIhvcNAQkEMRYEFAkQswJRS3UlXij/ vX0Mav4oTYdBMEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGAl1d4L7sJID4ImOcD+Wc7UhU1D9c0LndFToS8VEtpbpRrsmWS4ndu atHS+VckrVHW6EH5Ut6dOoVueTVvfL1/wON4KsGfTf2oN8FxK7/qg8zoVs6C09xf 5mFd7+5bMe4AXd7/629bUgEu8BPwv86q7VtPLsrDxddKY4sD7w5Tx9oAAAAAAAAA AA== ---------z49578_boundary_sign-- From owner-linux-xfs@oss.sgi.com Sat Sep 1 12:24:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81JOCH18428 for linux-xfs-outgoing; Sat, 1 Sep 2001 12:24:12 -0700 Received: from monkeyiq.dnsalias.org (CPE-203-45-215-234.qld.bigpond.net.au [203.45.215.234]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81JO9d18409 for ; Sat, 1 Sep 2001 12:24:09 -0700 Received: by monkeyiq.dnsalias.org id f81IrdM31005 ; Sun, 2 Sep 2001 04:53:39 +1000 Date: Sun, 2 Sep 2001 04:53:39 +1000 Message-Id: <200109011853.f81IrdM31005@monkeyiq.dnsalias.org> To: linux-xfs@oss.sgi.com Cc: monkeyiq@users.sourceforge.net Subject: Preallocation of space From: monkeyiq MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I was reading over this again: http://www.osnews.com/story.php?news_id=69 And decided that the next feature for ferris to pick on was: It's an extent-based filesystem, has features like delayed allocation, space preallocation and space coallescing on deletion, and goes to great lengths in attempting to layout files using the largest extents possible (an "extent" being an offset and a length within a file). So I was reading xfs_mkfile.c line 188 of 277 flck.l_whence = SEEK_SET; flck.l_start = 0LL; flck.l_len = size; #if 0 (void)ioctl(fd, XFS_IOC_RESVSP64, &flck); I presume that this XFS_IOC_RESVSP64 tells XFS to reserve off a chunk of space for future use by the file. Are the ioctl() calls for XFS documented anywhere? /usr/include/xfs/xfs_fs.h and the tool src is all I am using at the moment. It just struck me as odd that in xfsprogs-1.2.8 the call was preprocessed out. ----------------------------------------------------- http://witme.sourceforge.net/libferris.web/index.html From owner-linux-xfs@oss.sgi.com Sat Sep 1 12:53:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81JrDK18903 for linux-xfs-outgoing; Sat, 1 Sep 2001 12:53:13 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81JrAd18882 for ; Sat, 1 Sep 2001 12:53:11 -0700 Received: (qmail 5747 invoked from network); 1 Sep 2001 19:53:06 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 1 Sep 2001 19:53:06 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: "Michael Wahlbrink" cc: Seth Mos , linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... In-reply-to: Your message of "Sat, 01 Sep 2001 20:37:58 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Sep 2001 05:53:06 +1000 Message-ID: <22084.999373986@ocs3.ocs-net> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 1 Sep 2001 20:37:58 +0200, "Michael Wahlbrink" wrote: >But no my syslog doesnt start anymore its complainig about an unknown >option -x ;-( klogd -x, not syslog -x. From owner-linux-xfs@oss.sgi.com Sat Sep 1 13:08:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81K8N819208 for linux-xfs-outgoing; Sat, 1 Sep 2001 13:08:23 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81K8Gd19186 for ; Sat, 1 Sep 2001 13:08:17 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id 941CB67040; Sat, 1 Sep 2001 22:08:10 +0200 (CEST) To: Keith Owens Cc: Seth Mos , linux-xfs@oss.sgi.com, "Michael Wahlbrink" Subject: Re: Kernel Oops ..... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Sat, 1 Sep 2001 22:08:08 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 22:08:13, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 22:08:13, Serialize complete at 01.09.2001 22:08:13, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 22:08:13, S/MIME Sign complete at 01.09.2001 22:08:13, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 01.09.2001 22:08:10, Serialize complete at 01.09.2001 22:08:10 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z116_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z116_boundary_sign Content-Type: text/plain; charset="us-ascii" On 01.09.2001 21:53:06 Keith Owens wrote: >On Sat, 1 Sep 2001 20:37:58 +0200, >"Michael Wahlbrink" wrote: >>But no my syslog doesnt start anymore its complainig about an unknown >>option -x ;-( > >klogd -x, not syslog -x. Thanks, that works ;-) cu micha ---------z116_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwMTIwMDgxM1owIwYJKoZIhvcNAQkEMRYEFCkxcyOx1GqBi8G0 qdleSTALTe3CMEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGAr2gxXO5u9lQu0xGEdQxVdv6veR/xyZ4Ck9M1hGfSTj9c9lXhSKrr Wqv+ZEoX7VcBlUWNKEdXP9gTJQ+PIWkYKNobct0/ibtyOCyM/St0mK+mNMa0oFQz z11ekluWQpvYIEPsWLS5TCnvR8CvYcB0b+SkfQGEVPjiUXMlOEJ0Y78AAAAAAAAA AA== ---------z116_boundary_sign-- From owner-linux-xfs@oss.sgi.com Sat Sep 1 14:36:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81La4820509 for linux-xfs-outgoing; Sat, 1 Sep 2001 14:36:04 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81LZxd20490; Sat, 1 Sep 2001 14:36:00 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA10572; Sat, 1 Sep 2001 23:35:57 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id XAA03063; Sat, 1 Sep 2001 23:35:57 +0200 (CEST) Date: Sat, 1 Sep 2001 23:35:57 +0200 (CEST) From: Seth Mos To: Keith Owens cc: Michael Wahlbrink , linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... In-Reply-To: <22084.999373986@ocs3.ocs-net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 2 Sep 2001, Keith Owens wrote: > On Sat, 1 Sep 2001 20:37:58 +0200, > "Michael Wahlbrink" wrote: > >But no my syslog doesnt start anymore its complainig about an unknown > >option -x ;-( > > klogd -x, not syslog -x. Uhm, yes ... does almost right count ? From owner-linux-xfs@oss.sgi.com Sat Sep 1 14:42:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81LgLu20691 for linux-xfs-outgoing; Sat, 1 Sep 2001 14:42:21 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81Lg9d20669; Sat, 1 Sep 2001 14:42:09 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id 872D667040; Sat, 1 Sep 2001 23:42:01 +0200 (CEST) To: "Michael Wahlbrink" Cc: Keith Owens , Seth Mos , linux-xfs@oss.sgi.com, "Michael Wahlbrink" , owner-linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Sat, 1 Sep 2001 23:42:00 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 23:42:05, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 23:42:05, Serialize complete at 01.09.2001 23:42:05, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 01.09.2001 23:42:05, S/MIME Sign complete at 01.09.2001 23:42:05, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 01.09.2001 23:42:02, Serialize complete at 01.09.2001 23:42:02 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z31063_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z31063_boundary_sign Content-Type: text/plain; charset="us-ascii" On 01.09.2001 22:08:08 "Michael Wahlbrink" wrote: >On 01.09.2001 21:53:06 Keith Owens wrote: >>On Sat, 1 Sep 2001 20:37:58 +0200, >>"Michael Wahlbrink" wrote: >>>But no my syslog doesnt start anymore its complainig about an unknown >>>option -x ;-( >> >>klogd -x, not syslog -x. > >Thanks, that works ;-) And here comes the next oops with newest bios and -x for klogd :-( cu michael ksymoops 2.4.1 on i686 2.4.10-pre2-xfs. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.10-pre2-xfs/ (default) -m /boot/System.map-2.4.10-pre2-xfs (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. No modules in ksyms, skipping objects Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file? Sep 2 00:29:43 swan kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000152 Sep 2 00:29:43 swan kernel: c01b3e95 Sep 2 00:29:43 swan kernel: *pde = 00000000 Sep 2 00:29:43 swan kernel: Oops: 0000 Sep 2 00:29:43 swan kernel: CPU: 0 Sep 2 00:29:43 swan kernel: EIP: 0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 Sep 2 00:29:43 swan kernel: EFLAGS: 00010246 Sep 2 00:29:43 swan kernel: eax: 00000000 ebx: ffffffe8 ecx: c147cc50 edx: c02bc7e0 Sep 2 00:29:43 swan kernel: esi: c8858ecc edi: cf5f7c00 ebp: 00000000 esp: cf4f7e0c Sep 2 00:29:43 swan kernel: ds: 0018 es: 0018 ss: 0018 Sep 2 00:29:43 swan kernel: Process rm (pid: 1019, stackpage=cf4f7000) Sep 2 00:29:43 swan kernel: Stack: 00000000 00000000 cf5f7c00 00000008 c01cac0c cf5f7c00 00000000 0a0ac689 Sep 2 00:29:43 swan kernel: 00000000 00000000 cf4f7ec4 00000000 00000000 cacd426c cacd4254 00000008 Sep 2 00:29:43 swan kernel: cc4f66c0 cf5fc078 cf5fc06a 0000002a 00000000 c01d21a0 cf5fc000 cf5f7c00 Sep 2 00:29:43 swan kernel: Call Trace: [] [] [] [] [] Sep 2 00:29:43 swan kernel: [] [] [] [] [] [] Sep 2 00:29:43 swan kernel: [] [] [] Sep 2 00:29:43 swan kernel: Code: 66 83 bb 6a 01 00 00 00 75 10 80 a3 50 01 00 00 f7 53 e8 54 >>EIP; c01b3e95 <===== Trace; c01cac0c Trace; c01d21a0 Trace; c019f090 Trace; c01cf6c7 Trace; c01cf630 Trace; c01cf630 Trace; c01d8f7d Trace; c01416cc Trace; c01cf630 Trace; c01396b3 Trace; c0139d5b Trace; c013a33c <__user_walk+3c/60> Trace; c0137486 Trace; c0106cab Code; c01b3e95 00000000 <_EIP>: Code; c01b3e95 <===== 0: 66 83 bb 6a 01 00 00 cmpw $0x0,0x16a(%ebx) <===== Code; c01b3e9c 7: 00 Code; c01b3e9d 8: 75 10 jne 1a <_EIP+0x1a> c01b3eaf Code; c01b3e9f a: 80 a3 50 01 00 00 f7 andb $0xf7,0x150(%ebx) Code; c01b3ea6 11: 53 push %ebx Code; c01b3ea7 12: e8 54 00 00 00 call 6b <_EIP+0x6b> c01b3f00 2 warnings issued. Results may not be reliable. ---------z31063_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwMTIxNDIwNVowIwYJKoZIhvcNAQkEMRYEFAeiH2LnHkD5n9OC 2LgjhS/yQ0DSMEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGAsHpuAAA+sbcHZH1XQ4nojNIfQzg4pt+e1BzG2a/Ne8zxGQyLAZdm KLYFw5NUQPgxsJLQ7oSM1u7manVHWnzoe83dHT11b7yx+ng4hqSpt+Tb3f9kGQVI g/fT+pwq8YFuLDsrOUARFSEjymFOo61fxLISNci8U0gbIg0BMzmPFf4AAAAAAAAA AA== ---------z31063_boundary_sign-- From owner-linux-xfs@oss.sgi.com Sat Sep 1 14:50:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81LoWf20926 for linux-xfs-outgoing; Sat, 1 Sep 2001 14:50:32 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81LoRd20904; Sat, 1 Sep 2001 14:50:28 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA11957; Sat, 1 Sep 2001 23:50:26 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id XAA03721; Sat, 1 Sep 2001 23:50:26 +0200 (CEST) Date: Sat, 1 Sep 2001 23:50:26 +0200 (CEST) From: Seth Mos To: Michael Wahlbrink cc: Keith Owens , linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 1 Sep 2001, Michael Wahlbrink wrote: > On 01.09.2001 22:08:08 "Michael Wahlbrink" wrote: > >On 01.09.2001 21:53:06 Keith Owens wrote: > >>On Sat, 1 Sep 2001 20:37:58 +0200, > >>"Michael Wahlbrink" wrote: > >>>But no my syslog doesnt start anymore its complainig about an unknown > >>>option -x ;-( > >> > >>klogd -x, not syslog -x. > > > >Thanks, that works ;-) > > And here comes the next oops with newest bios and -x for klogd :-( You are first that I see with a SiS 735 based motherboard so I have no clue how well it works within Linux. The performance and stability of this board is reported to be good. So I am assuming it works decently under linux as well. Do you have problems with a normal ext2 filesystem or a linus kernel? You will have to wait for a guru te repond to the Oops and do something with it, which is something I can't Cheers Seth From owner-linux-xfs@oss.sgi.com Sat Sep 1 15:07:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f81M7xk21304 for linux-xfs-outgoing; Sat, 1 Sep 2001 15:07:59 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f81M7pd21281 for ; Sat, 1 Sep 2001 15:07:51 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id B26BF67040; Sun, 2 Sep 2001 00:07:43 +0200 (CEST) To: Seth Mos Cc: Keith Owens , linux-xfs@oss.sgi.com, Michael Wahlbrink Subject: Re: Kernel Oops ..... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Sun, 2 Sep 2001 00:07:42 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 02.09.2001 00:07:47, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 02.09.2001 00:07:47, Serialize complete at 02.09.2001 00:07:47, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 02.09.2001 00:07:48, S/MIME Sign complete at 02.09.2001 00:07:48, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 02.09.2001 00:07:48, Serialize complete at 02.09.2001 00:07:48, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 02.09.2001 00:07:44, Serialize complete at 02.09.2001 00:07:44 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z43558_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z43558_boundary_sign Content-Type: text/plain; charset="us-ascii" On 01.09.2001 23:50:26 Seth Mos wrote: >On Sat, 1 Sep 2001, Michael Wahlbrink wrote: > >> On 01.09.2001 22:08:08 "Michael Wahlbrink" wrote: >> >On 01.09.2001 21:53:06 Keith Owens wrote: >> >>On Sat, 1 Sep 2001 20:37:58 +0200, >> >>"Michael Wahlbrink" wrote: >> >>>But no my syslog doesnt start anymore its complainig about an >unknown >> >>>option -x ;-( >> >> >> >>klogd -x, not syslog -x. >> > >> >Thanks, that works ;-) >> >> And here comes the next oops with newest bios and -x for klogd :-( > >You are first that I see with a SiS 735 based motherboard so I have no >clue how well it works within Linux. The performance and stability of >this >board is reported to be good. So I am assuming it works decently under >linux as well. Do you have problems with a normal ext2 filesystem or a >linus kernel? > >You will have to wait for a guru te repond to the Oops and do something >with it, which is something I can't > Ok, no problem ;-) I'll make my tests with ext2 to see if the kernel 'oopses' too......... And the PII is still compiling th xfs kernel.... cu michael ---------z43558_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwMTIyMDc0N1owIwYJKoZIhvcNAQkEMRYEFGQHBFLafrPL9m2L yBjCg9rQ1esCMEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGAeJTk4ngP9C3gjFCpQp/hxJUk+04IFrS9hYufDrMv11a/XI1ntrnq qdY8eP3SBHVj+YqCP205WBUhDoBGfb5i/JDhH/ZVVR3ES4NSbwG/0x59sb0umKA9 udL+MRiyQkJCHlTPaSAWn3padqJiTLhrSb2KS1gXmVe4Y5tZhBQUfSUAAAAAAAAA AA== ---------z43558_boundary_sign-- From owner-linux-xfs@oss.sgi.com Sun Sep 2 13:11:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f82KBcZ08645 for linux-xfs-outgoing; Sun, 2 Sep 2001 13:11:38 -0700 Received: from kendy.up.ac.za (kendy.up.ac.za [137.215.101.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f82KBOd08626 for ; Sun, 2 Sep 2001 13:11:34 -0700 Received: from [137.215.145.210] (helo=it.up.ac.za) by kendy.up.ac.za with esmtp (Exim 3.15 #1) id 15ddZ8-0000FK-00; Sun, 02 Sep 2001 22:09:58 +0200 Message-ID: <3B929216.B2D4AC60@it.up.ac.za> Date: Sun, 02 Sep 2001 22:09:58 +0200 From: Paul Schutte X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.9-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: "Theo E. Schlossnagle" CC: exim-users@exim.org, linux-xfs@oss.sgi.com Subject: Re: Exim and XFS filesystem References: <3B8BB7C7.4020808@omniti.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Scanner: exiscan *15ddZ8-0000FK-00*dXniCV7KWOg* http://duncanthrax.net/exiscan/ Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk What mount options did you use ? Paul "Theo E. Schlossnagle" wrote: > Hello all, > > We have been running exim for a while and we run it on over 75 machines > (Linux, BSDs Solaris). We recently started using SGI's xfs filesystem for > most of our operations because of its speed and stability -- we are _very_ > happy with it. I have never had any problems with it ... until now. > > Exim v3.14,v3.22,v3.33 and Linux 2.4.2-xfs. The xfs parition in question is > running atop a RAID-1 md device on two 9GB scsi drives. > > After running Exim with its spool directory on an xfs partition and under low > load (100 messages/minute) I would soon get an Exim process spinning CPU bound > and I could not kill it [kill -9 did nothing]. The system was stuck on disk > writes (so any process that calls fsync or friends would get stuck in the run > queue never to come out again.) No modified files were writted to disk (by > any process) after this point. A reboot was required and restore "normal" > operation. > > We tried many things to fix this with no success, but as soon as we configured > exim to use a non xfs (ext2 in this case) mounted spool directory, the problem > instantly disappeared. > > It looked as if the kernel had a thread stuck writing to or reading from the > filesystem journal. If anyone knows a solution to this problem, I am all > ears. Otherwise, steer clear of running you Exim spools on xfs. > > -- > Theo Schlossnagle > 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 Sun Sep 2 13:43:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f82Kh6V09268 for linux-xfs-outgoing; Sun, 2 Sep 2001 13:43:06 -0700 Received: from kendy.up.ac.za (kendy.up.ac.za [137.215.101.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f82Kh0d09246 for ; Sun, 2 Sep 2001 13:43:01 -0700 Received: from [137.215.145.210] (helo=it.up.ac.za) by kendy.up.ac.za with esmtp (Exim 3.15 #1) id 15de46-0000jQ-00; Sun, 02 Sep 2001 22:41:58 +0200 Message-ID: <3B929996.FFC809B9@it.up.ac.za> Date: Sun, 02 Sep 2001 22:41:58 +0200 From: Paul Schutte X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.9-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Seth Mos CC: Eric Sandeen , XFS mailing list Subject: Re: Kernel hangs with mongo.pl benchmark. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Scanner: exiscan *15de46-0000jQ-00*RAJGVXPGfF6* http://duncanthrax.net/exiscan/ Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > On Fri, 31 Aug 2001, Eric Sandeen wrote: > > > Paul Schutte wrote: > > > > > > Hi, > > > > > > I found a problem while doing benchmarks with mongo.pl > > > > > > The sympthom is that the machine just hangs. No error messages. > > > > Ok, I see this too.... looks like bdflush is the only thing that's > > running. > > > > If I try a sync, then that's what hangs, both of these get lost in > > write_some_buffers - looks like a deadlock? > > Then it is specific to scsi perhaps. AFAIk the scsi layer was never > considered "elegant". I Think this is a SCSI thing. I just ran it on a BusLogic card. I saw the same sympthoms: only bdflush running. Thus far I could'nt reproduce this on any IDE system. > > > Hm.... you think Hans did this on purpose? ;-) > > > > I'll see if I can find anything next week... time for my weekend now, > > I'm afraid. > > Mine started 8 hours ago :-) > > > Thanks for pointing this out! > > > > -Eric > > > > p.s. fwiw, this is on adaptec hardware as well. > > I am not seeing it on my Athlon and IDE home box. Is this thus only > reproducable on adaptec/scsi hardware? > > I'll scavenge the room for my spare 4.5GB scsi disk and see if I can get > my homebox to hang. My controller however is a sym53c8xx. > > I have tried 1,5 and 10 processes but it just won't hang :-) > > Cheers > > Seth Paul From owner-linux-xfs@oss.sgi.com Sun Sep 2 16:17:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f82NHit11349 for linux-xfs-outgoing; Sun, 2 Sep 2001 16:17:44 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f82NHfd11330 for ; Sun, 2 Sep 2001 16:17:41 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id ; Sun, 2 Sep 2001 18:16:53 -0500 Message-ID: <85063BBE668FD411944400D0B744267A88851B@AUSMAIL> From: "Gonyou, Austin" To: XFS mailing list Subject: System lock while accessing files causes file corruption Date: Sun, 2 Sep 2001 18:16:48 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Why is this? If I open a file, text/otherwise and the power actually fails, (i turn it off), once in a while I get a corrupt file. Why is this? What would happen if I was writing to some Oracle filesystems and this situation occurred? Please advise. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Sun Sep 2 16:51:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f82Np1811916 for linux-xfs-outgoing; Sun, 2 Sep 2001 16:51:01 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f82Nowd11897 for ; Sun, 2 Sep 2001 16:50:58 -0700 Received: from rattle.melbourne.sgi.com (rattle.melbourne.sgi.com [134.14.55.145]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id QAA05403 for ; Sun, 2 Sep 2001 16:49:18 -0700 (PDT) mail_from (kenmcd@melbourne.sgi.com) Received: from localhost (kenmcd@localhost) by rattle.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id KAA91626; Mon, 3 Sep 2001 10:48:23 +1100 (AEDT) X-Authentication-Warning: rattle.melbourne.sgi.com: kenmcd owned process doing -bs Date: Mon, 3 Sep 2001 10:48:23 +1100 From: Ken McDonell Reply-To: To: "Gonyou, Austin" cc: XFS mailing list Subject: Re: System lock while accessing files causes file corruption In-Reply-To: <85063BBE668FD411944400D0B744267A88851B@AUSMAIL> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I think this has been done to death on the list and FAQ. XFS journals metadata, not file data. In the case of Oracle, that's what the transaction log is for, and that is why the transaction log for a DBMS requires synchronous or guaranteed writes. On Sun, 2 Sep 2001, Gonyou, Austin wrote: > Why is this? If I open a file, text/otherwise and the power actually fails, > (i turn it off), once in a while I get a corrupt file. Why is this? What > would happen if I was writing to some Oracle filesystems and this situation > occurred? Please advise. > > -- > Austin Gonyou > Systems Architect, CCNA > Coremetrics, Inc. > Phone: 512-796-9023 > email: austin@coremetrics.com > From owner-linux-xfs@oss.sgi.com Sun Sep 2 17:18:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f830IfD12373 for linux-xfs-outgoing; Sun, 2 Sep 2001 17:18:41 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f830Icd12350 for ; Sun, 2 Sep 2001 17:18:39 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id CAA20477; Mon, 3 Sep 2001 02:18:34 +0200 (CEST) Message-Id: <4.3.2.7.2.20010903021638.034ee5e0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 03 Sep 2001 02:17:53 +0200 To: "Gonyou, Austin" , XFS mailing list From: Seth Mos Subject: Re: System lock while accessing files causes file corruption In-Reply-To: <85063BBE668FD411944400D0B744267A88851B@AUSMAIL> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 18:16 2-9-2001 -0500, Gonyou, Austin wrote: >Why is this? If I open a file, text/otherwise and the power actually fails, >(i turn it off), once in a while I get a corrupt file. Why is this? What >would happen if I was writing to some Oracle filesystems and this situation >occurred? Please advise. See the http://oss.sgi.com/projects/xfs/faq.html#nulls A database would survive since most have their own buffering and transaction scheme. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Sep 2 19:03:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8323A313791 for linux-xfs-outgoing; Sun, 2 Sep 2001 19:03:10 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83233d13772 for ; Sun, 2 Sep 2001 19:03:03 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA00214 for ; Sun, 2 Sep 2001 19:01:22 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id MAA30179; Mon, 3 Sep 2001 12:02:13 +1000 Date: Mon, 3 Sep 2001 12:02:13 +1000 From: Keith Owens Message-Id: <200109030202.MAA30179@sherman.melbourne.sgi.com> Subject: TAKE - Update to 2.4.10-pre4 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Update to 2.4.10-pre4 Date: Sun Sep 2 18:59:58 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102058a linux/scripts/ver_linux - 1.9 linux/mm/vmscan.c - 1.72 linux/mm/swapfile.c - 1.35 linux/mm/swap_state.c - 1.28 linux/mm/memory.c - 1.57 linux/mm/filemap.c - 1.84 linux/kernel/sched.c - 1.39 linux/kernel/ksyms.c - 1.103 linux/kernel/fork.c - 1.34 linux/include/linux/sysv_fs.h - 1.11 linux/include/linux/skbuff.h - 1.21 linux/include/linux/sched.h - 1.42 linux/include/linux/pagemap.h - 1.28 linux/include/linux/fs.h - 1.114 linux/include/asm-ppc/machdep.h - 1.18 linux/include/asm-ppc/keyboard.h - 1.10 linux/include/asm-i386/timex.h - 1.4 linux/include/asm-i386/system.h - 1.19 linux/include/asm-i386/msr.h - 1.9 linux/fs/umsdos/rdir.c - 1.13 linux/fs/umsdos/namei.c - 1.11 linux/fs/umsdos/inode.c - 1.17 linux/fs/umsdos/emd.c - 1.9 linux/fs/umsdos/dir.c - 1.17 linux/fs/umsdos/README-WIP.txt - 1.4 linux/fs/sysv/symlink.c - 1.7 linux/fs/sysv/inode.c - 1.23 linux/fs/sysv/balloc.c - 1.6 linux/fs/sysv/Makefile - 1.6 linux/fs/namei.c - 1.35 linux/fs/binfmt_elf.c - 1.30 linux/fs/Makefile - 1.34 linux/drivers/usb/Makefile - 1.41 linux/drivers/usb/Config.in - 1.45 linux/drivers/scsi/sd.c - 1.40 linux/drivers/pci/pci.c - 1.42 linux/drivers/net/Makefile - 1.45 linux/drivers/macintosh/via-pmu.c - 1.15 linux/drivers/macintosh/Makefile - 1.10 linux/drivers/char/Makefile - 1.47 linux/drivers/block/ps2esdi.c - 1.18 linux/drivers/block/loop.c - 1.34 linux/arch/sparc64/kernel/ioctl32.c - 1.40 linux/arch/ppc/kernel/prep_setup.c - 1.23 linux/arch/ppc/kernel/pmac_setup.c - 1.24 linux/arch/ppc/kernel/chrp_setup.c - 1.25 linux/arch/ppc/8xx_io/fec.c - 1.14 linux/arch/ppc/8xx_io/enet.c - 1.14 linux/arch/i386/kernel/setup.c - 1.50 linux/arch/i386/kernel/mtrr.c - 1.27 linux/arch/i386/defconfig - 1.65 linux/Makefile - 1.117 linux/Documentation/Configure.help - 1.96 linux/drivers/video/vga16fb.c - 1.10 linux/drivers/usb/printer.c - 1.39 linux/drivers/block/blkpg.c - 1.9 linux/drivers/block/cpqarray.c - 1.25 linux/drivers/net/macsonic.c - 1.8 linux/include/asm-i386/hw_irq.h - 1.19 linux/arch/ppc/kernel/head_8xx.S - 1.13 linux/drivers/block/DAC960.c - 1.33 linux/arch/i386/kernel/pci-pc.c - 1.25 linux/include/linux/pmu.h - 1.4 linux/drivers/pcmcia/yenta.c - 1.27 linux/drivers/net/8139too.c - 1.25 linux/drivers/usb/plusb.c - 1.13 linux/drivers/ide/ide.c - 1.26 linux/arch/mips64/kernel/ioctl32.c - 1.8 linux/arch/i386/kdb/kdbasupport.c - 1.16 linux/drivers/usb/storage/transport.c - 1.11 linux/include/asm-sparc/kmap_types.h - 1.3 linux/drivers/usb/storage/sddr09.c - 1.8 linux/drivers/md/raid1.c - 1.12 linux/arch/i386/kernel/bluesmoke.c - 1.11 linux/drivers/block/cciss.c - 1.12 linux/drivers/md/md.c - 1.19 linux/include/asm-ppc/kmap_types.h - 1.5 linux/fs/reiserfs/stree.c - 1.6 linux/fs/reiserfs/super.c - 1.6 linux/fs/reiserfs/journal.c - 1.6 linux/fs/reiserfs/inode.c - 1.8 linux/fs/reiserfs/bitmap.c - 1.3 linux/drivers/usb/storage/unusual_devs.h - 1.5 linux/drivers/net/wan/dscc4.c - 1.3 linux/fs/freevxfs/vxfs_super.c - 1.3 linux/fs/freevxfs/vxfs_olt.c - 1.2 linux/fs/freevxfs/vxfs_inode.c - 1.4 linux/fs/freevxfs/vxfs_fshead.c - 1.2 linux/fs/freevxfs/vxfs_extern.h - 1.2 linux/drivers/acpi/ospm/busmgr/Makefile - 1.2 linux/drivers/acpi/include/platform/acgcc.h - 1.2 linux/fs/sysv/super.c - 1.2 From owner-linux-xfs@oss.sgi.com Sun Sep 2 21:46:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f834k1d15686 for linux-xfs-outgoing; Sun, 2 Sep 2001 21:46:01 -0700 Received: from home.smithconcepts.com (ubr-35.28.151.oviedo.cfl.rr.com [65.35.28.151]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f834jvd15667 for ; Sun, 2 Sep 2001 21:45:57 -0700 Received: from ieee.org (IDENT:bjsmith@bitman.oviedo.smithconcepts.com [172.24.24.192]) by home.smithconcepts.com (8.9.3/8.9.3) with ESMTP id AAA12948; Mon, 3 Sep 2001 00:38:12 -0400 Message-ID: <3B930B7F.372CB436@ieee.org> Date: Mon, 03 Sep 2001 00:47:59 -0400 From: Bryan-TheBS-Smith Organization: SmithConcepts, Inc. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: XFS mailing list Subject: Best CVS tags to build from ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've probably asked this before, but I'm having trouble finding the answer in my old E-mails, the archives or in a downloaded CVS tree myself. Q: Is there a moving CVS tag or series of tags that is/are "STABLE" or otherwise that are used to mark potential patch or other potential points of release? Alt-Q: If not, would someone let me know whenever they feel there is a good tag and/or date-timestamp of the tree when it would be good to build RPMs from? Thanx in advance ... -- TheBS P.S. The reason why I ask is because I'm going to try to start releasing kernel RPMs again. My current job function (wireless LAN development) will require me to do kernel modifications and releases for various distros anyway, so I figure I might as well release an XFS version (since it is currently my preferred 2.4 kernel JFS after exhausted use of it, ReiserFS and Ext3 over the past year). P.S.S. I'm working hard to find a SDSL provider for here in Central Florida so I can serve out more than my current 256Kbps site. I know the lines are capable, but only ADSL seems to be offered by the relatively ignorant salespeople I can get ahold of. Does anyone know of one offering SDSL? I'm willing to pay several hundred $$$/month for a 768Kbps - 1.5Mbps SDSL line with high or unlimited transfers to a residential (or commercial if I have to) area. Thanx again. -- Bryan "TheBS" Smith mailto:b.j.smith@ieee.org chat:thebs413 Engineer AbsoluteValue Systems, Inc. http://www.linux-wlan.org President SmithConcepts, Inc. http://www.SmithConcepts.com From owner-linux-xfs@oss.sgi.com Sun Sep 2 22:13:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f835Djs16102 for linux-xfs-outgoing; Sun, 2 Sep 2001 22:13:45 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f835Dhd16082 for ; Sun, 2 Sep 2001 22:13:43 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id WAA04023 for ; Sun, 2 Sep 2001 22:12:03 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id QAA43483; Mon, 3 Sep 2001 16:10:47 +1100 (EDT) Date: Mon, 3 Sep 2001 16:10:47 +1100 From: Timothy Shimmin To: Andrew Klaassen Cc: linux-xfs@oss.sgi.com Subject: Re: Problems with DAT tape.... Message-ID: <20010903161046.O135568@boing.melbourne.sgi.com> References: <002501c12fea$b1091620$50824e40@iboats.com> <20010829103705.H114864@boing.melbourne.sgi.com> <20010829102702.B7083@dkp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20010829102702.B7083@dkp.com>; from ak@dkp.com on Wed, Aug 29, 2001 at 10:27:02AM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Aug 29, 2001 at 10:27:02AM -0400, Andrew Klaassen wrote: > On Wed, Aug 29, 2001 at 10:37:05AM +1100, > Timothy Shimmin wrote: > > > I would recommend just putting the scsi tape driver into > > variable block sized mode. > > > > # mt -f /dev/st0 setblk 0 > > We've found that doing this on certain tape drives - especially > when you're trying to read the data back - can lead to pretty > significant slowdowns. So you might want to do a little testing > in your particular environment before you go ahead and do > this... > Thanks for the tip. --Tim From owner-linux-xfs@oss.sgi.com Sun Sep 2 22:42:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f835gJj16636 for linux-xfs-outgoing; Sun, 2 Sep 2001 22:42:19 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f835gHd16617 for ; Sun, 2 Sep 2001 22:42:17 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f835gB507550 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Sun, 2 Sep 2001 22:42:11 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id HAA821574 for ; Mon, 3 Sep 2001 07:42:08 +0200 (CEST) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id PAA05707; Mon, 3 Sep 2001 15:42:02 +1000 Date: Mon, 3 Sep 2001 15:42:02 +1000 From: Keith Owens Message-Id: <200109030542.PAA05707@sherman.melbourne.sgi.com> Subject: TAKE - Correct 2.4.10-pre4 for UP APIC Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk 2.4.10-pre4 has a partial copy of the UP APIC code from the -ac tree, but not all of it. NOTE: kdb for Linus's tree and for XFS will not work on Athlon with CONFIG_X86_UP_IOAPIC. The full fix for Athlon UP is only in the -ac tree. Do not use CONFIG_X86_UP_IOAPIC on Athlon UP in XFS. Date: Sun Sep 2 22:39:03 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102063a linux/arch/i386/kernel/apic.c - 1.18 From owner-linux-xfs@oss.sgi.com Sun Sep 2 23:30:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f836UgH17480 for linux-xfs-outgoing; Sun, 2 Sep 2001 23:30:42 -0700 Received: from rebel.net.au (IDENT:root@mail.rebel.net.au [203.20.69.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f836Udd17461 for ; Sun, 2 Sep 2001 23:30:39 -0700 Received: from rebel.net.au (dialup-6.rebel.net.au [203.20.69.76]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id QAA31222 for ; Mon, 3 Sep 2001 16:00:32 +0930 Message-ID: <3B93250B.79CE6C23@rebel.net.au> Date: Mon, 03 Sep 2001 16:06:59 +0930 From: David Lloyd X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.5-xfs-1.0.1 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS Minus the Journal Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Weird question, and I could probably just "try", but is there any way to use XFS without the journal? DSL -- Pussy's good for six at the most (Mrs. Lovett, Sweeney Todd) From owner-linux-xfs@oss.sgi.com Mon Sep 3 00:23:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f837NRN18177 for linux-xfs-outgoing; Mon, 3 Sep 2001 00:23:27 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f837NOd18158 for ; Mon, 3 Sep 2001 00:23:24 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f837NI511152 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Mon, 3 Sep 2001 00:23:18 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id JAA818794 for ; Mon, 3 Sep 2001 09:23:18 +0200 (CEST) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id RAA20654 for linux-xfs@oss.sgi.com; Mon, 3 Sep 2001 17:21:57 +1000 (EST) Date: Mon, 3 Sep 2001 17:21:57 +1000 (EST) From: Nathan Scott Message-Id: <200109030721.RAA20654@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsprogs Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Couple of minor fixes for recently reported issues. Date: Mon Sep 3 00:18:05 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102065a cmd/xfsprogs/db/freesp.c - 1.2 - do the same thing as db/check.c in the situation where we can't read a block in a btree - warn, then continue, don't segv. cmd/xfsprogs/mkfile/xfs_mkfile.c - 1.5 - looks like the prealloc ioctl is all there in the kernel, but this bit of user code was not updated to use it (conditional via -p). fix that. cmd/xfsprogs/doc/CHANGES - 1.35 - update with a couple of minor changes. From owner-linux-xfs@oss.sgi.com Mon Sep 3 00:25:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f837Puf18309 for linux-xfs-outgoing; Mon, 3 Sep 2001 00:25:56 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f837Pld18290 for ; Mon, 3 Sep 2001 00:25:48 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f837Pg511314 for ; Mon, 3 Sep 2001 00:25:42 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id SAA22597; Mon, 3 Sep 2001 18:24:25 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA18315; Mon, 3 Sep 2001 18:24:24 +1100 (AEDT) Date: Mon, 3 Sep 2001 18:24:24 +1100 From: Nathan Scott To: Fran?ois Dupoux Cc: linux-xfs@oss.sgi.com Subject: Re: segfault in xfsprogs/xfs_db Message-ID: <20010903182424.D15451@wobbly.melbourne.sgi.com> References: <01082721164700.00907@duron750.fdupoux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01082721164700.00907@duron750.fdupoux.org>; from fdupoux@free.fr on Mon, Aug 27, 2001 at 09:16:47PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, I just put a fix in for the core dump here - db/freesp.c now does the same thing as db/check.c when it can't read one of the blocks in a btree. as to why it can't, I'm not sure yet, but at least now we'll be able to see which block and which allocation group the problem is, and it will attempt to keep going instead of dying. thanks. On Mon, Aug 27, 2001 at 09:16:47PM +0200, Fran?ois Dupoux wrote: > Hi, > > I had a segfault with xfs_db compiled from xfsprogs-1.3.5.src.tar.gz. > Kernel 2.4.9, Redhat-7.1 > > The segfault happens when I run the command "freesp -d -s" with "xfs_db -x > /dev/hdc5". > This partition was formatted by mkfs.xfs. This is a 14.16 GB partition, > with 5.34 GB used. > > duron750:/home/dupoux# xfs_db -x /dev/hdc5 > xfs_db: freesp -d -s > 0 43730 1 > 0 43731 1 > 0 43732 1 > 0 43733 1 > 0 43734 1 > 0 43735 1 > Segmentation fault (core dumped) > > --------------- gdb /sbin/xfs_db core ------------------- > GNU gdb 5.0rh-5 Red Hat Linux 7.1 > Copyright 2001 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-redhat-linux"... > Core was generated by `xfs_db -x /dev/hdc5'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /lib/i686/libc.so.6...done. > Loaded symbols for /lib/i686/libc.so.6 > Reading symbols from /lib/ld-linux.so.2...done. > Loaded symbols for /lib/ld-linux.so.2 > #0 scanfunc_bno (ablock=0x0, typ=TYP_BNOBT, level=0, agf=0x80ab5e0) at > /usr/include/linux/byteorder/swab.h:132 > 132 { > -------------------------------------------------------- > > ------------ informations about /dev/hdc5 ------------- > Block size....................4096 bytes > Total blocks count............3710999 > Used blocks count.............1400933 > Free blocks count.............2310066 > Space usage:..................37 % > Total space:..................14.16 GB > Used space....................5.34 GB > Free space....................8.81 GB > Bitmap size...................453.00 KB > Allocation Group count:.......15 > Blocks per Allocation Group...262144 > Allocation Group size:........1.00 GB > -------------------------------------------------------- > > You can download the core file from http://www.partimage.org/misc/core.gz > It seems that the "freelist" is working, and it segfault at beginning of > reading > the btree (the BNO one). > > Here is the beginning of the result I d'like to obtain: > --------------------------------------------------------- > addToHist: 0 43730 1 > addToHist: 0 43731 1 > addToHist: 0 43732 1 > addToHist: 0 43733 1 > addToHist: 0 43734 1 > addToHist: 0 43735 1 > addToHist: 0 12 1 > addToHist: 0 54 247 > addToHist: 0 325 89 > addToHist: 0 566 25 > addToHist: 0 628 821 > addToHist: 0 1465 11 > addToHist: 0 1813 159 > addToHist: 0 1976 1 > ...... > --------------------------------------------------------- > > The partition was very fragmented. There is no problem when reading files > from the mount point. (I am using the patch XFS-2001-08-19 for 2.4.9). Here > is how > I made this 14 GB partition: > mkfs.xfs /dev/hdc5 > mount /dev/hdc5 /mnt/ess > cd /mnt/ess > createdata -d6 . > mv a r > mv b s > createdata -d6 . > umount /mnt/ess > > createdata is a small program which creates a lot of files of a random size, > with random data. It > fills the partition. When there is no space left, it erases a lot of files > (it keeps 1 file for 6 files > when the option -d6 is used). It's very useful to make a fragmented file > system. You can download the source > code on http://www.partimage.org/misc/createdata.cpp. > > I already had the same problem, after formatting and filling this partition > with the same method (other random files) > > thanks > -- Nathan From owner-linux-xfs@oss.sgi.com Mon Sep 3 00:28:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f837SsL18471 for linux-xfs-outgoing; Mon, 3 Sep 2001 00:28:54 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f837Spd18452 for ; Mon, 3 Sep 2001 00:28:51 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f837SjJ07368 for ; Mon, 3 Sep 2001 00:28:45 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id SAA22617; Mon, 3 Sep 2001 18:27:23 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA94602; Mon, 3 Sep 2001 18:27:23 +1100 (AEDT) Date: Mon, 3 Sep 2001 18:27:23 +1100 From: Nathan Scott To: monkeyiq Cc: linux-xfs@oss.sgi.com Subject: Re: Standard EA names Message-ID: <20010903182723.E15451@wobbly.melbourne.sgi.com> References: <200109010420.f814KhY32589@monkeyiq.dnsalias.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109010420.f814KhY32589@monkeyiq.dnsalias.org>; from monkeyiq@users.sourceforge.net on Sat, Sep 01, 2001 at 02:20:43PM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Sat, Sep 01, 2001 at 02:20:43PM +1000, monkeyiq wrote: > > Hi, > I am creating a VFS solution that relies on EA to a heavy degree. > I am wondering if there is a EA naming convention forum out there? Not that I know of. For the extended attributes that XFS uses itself (ie. in the "root" namespace, not the "user" namespace), the naming convention is to use "SGI_" as the name prefix. This is used for things like ACLs, MAC labels, DMAPI attributes, and several others. > For example, the GPG guys might decide what the attr name of a sig > block should be? I will probably make up names myself using something > like the emacs-naming-scheme that I have been using for read only > generated EA so far in ferris. Just thought I'd ask incase there was > already an effort in place for shared naming of handy attributes. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Sep 3 00:36:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f837aQa18727 for linux-xfs-outgoing; Mon, 3 Sep 2001 00:36:26 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f837aMd18707 for ; Mon, 3 Sep 2001 00:36:22 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id AAA01356 for ; Mon, 3 Sep 2001 00:36:17 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id SAA22655; Mon, 3 Sep 2001 18:34:57 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA68177; Mon, 3 Sep 2001 18:34:56 +1100 (AEDT) Date: Mon, 3 Sep 2001 18:34:55 +1100 From: Nathan Scott To: monkeyiq Cc: linux-xfs@oss.sgi.com Subject: Re: Preallocation of space Message-ID: <20010903183455.F15451@wobbly.melbourne.sgi.com> References: <200109011853.f81IrdM31005@monkeyiq.dnsalias.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109011853.f81IrdM31005@monkeyiq.dnsalias.org>; from monkeyiq@users.sourceforge.net on Sun, Sep 02, 2001 at 04:53:39AM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Sun, Sep 02, 2001 at 04:53:39AM +1000, monkeyiq wrote: > > I was reading over this again: > http://www.osnews.com/story.php?news_id=69 > ... > It's an extent-based filesystem, has features like delayed allocation, > space preallocation and space coallescing on deletion, and goes to > great lengths in attempting to layout files using the largest extents > possible (an "extent" being an offset and a length within a file). Pfft - don't listen to that guy! > > So I was reading xfs_mkfile.c line 188 of 277 > flck.l_whence = SEEK_SET; > flck.l_start = 0LL; > flck.l_len = size; > #if 0 > (void)ioctl(fd, XFS_IOC_RESVSP64, &flck); > Hmm.... well I see the kernel code is all there. I'm guessing this was just overlooked during porting, so I've pushed in the change (mkfile does prealloc conditionally only, via the -p option). > I presume that this XFS_IOC_RESVSP64 tells XFS to reserve off a chunk of > space for future use by the file. Yes, pretty much. > Are the ioctl() calls for XFS documented anywhere? No, but they should be. Some of the documentation exists in the IRIX syssgi man page - I'll probably slap that into xfs(5) at some point. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Sep 3 00:54:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f837spQ19234 for linux-xfs-outgoing; Mon, 3 Sep 2001 00:54:51 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f837smd19215 for ; Mon, 3 Sep 2001 00:54:48 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id AAA07199 for ; Mon, 3 Sep 2001 00:53:09 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id SAA22741; Mon, 3 Sep 2001 18:52:05 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA90876; Mon, 3 Sep 2001 18:52:05 +1100 (AEDT) Date: Mon, 3 Sep 2001 18:52:05 +1100 From: Nathan Scott To: David Lloyd Cc: linux-xfs@oss.sgi.com Subject: Re: XFS Minus the Journal Message-ID: <20010903185205.G15451@wobbly.melbourne.sgi.com> References: <3B93250B.79CE6C23@rebel.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B93250B.79CE6C23@rebel.net.au>; from lloy0076@rebel.net.au on Mon, Sep 03, 2001 at 04:06:59PM +0930 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Mon, Sep 03, 2001 at 04:06:59PM +0930, David Lloyd wrote: > > Weird question, and I could probably just "try", but is there any way to > use XFS without the journal? No. There was a plan to do this (via a new mount option, IIRC) awhile ago to compare performance to non-journaled filesystems, but noone ever got around to it. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Sep 3 02:08:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8398Xh20943 for linux-xfs-outgoing; Mon, 3 Sep 2001 02:08:33 -0700 Received: from monkeyiq.dnsalias.org (CPE-203-45-215-234.qld.bigpond.net.au [203.45.215.234]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8398Sd20924 for ; Mon, 3 Sep 2001 02:08:28 -0700 Received: by monkeyiq.dnsalias.org id f83988S26342 ; Mon, 3 Sep 2001 19:08:08 +1000 Date: Mon, 3 Sep 2001 19:08:08 +1000 Message-Id: <200109030908.f83988S26342@monkeyiq.dnsalias.org> To: Nathan Scott Cc: monkeyiq , linux-xfs@oss.sgi.com Subject: Re: Preallocation of space From: monkeyiq MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nathan Scott writes: > hi, > > On Sun, Sep 02, 2001 at 04:53:39AM +1000, monkeyiq wrote: > > > > So I was reading xfs_mkfile.c line 188 of 277 > > flck.l_whence = SEEK_SET; > > flck.l_start = 0LL; > > flck.l_len = size; > > #if 0 > > (void)ioctl(fd, XFS_IOC_RESVSP64, &flck); > > > > Hmm.... well I see the kernel code is all there. I'm > guessing this was just overlooked during porting, so I've > pushed in the change (mkfile does prealloc conditionally > only, via the -p option). > > > I presume that this XFS_IOC_RESVSP64 tells XFS to reserve off a chunk of > > space for future use by the file. > > Yes, pretty much. > > > Are the ioctl() calls for XFS documented anywhere? > > No, but they should be. Some of the documentation exists in > the IRIX syssgi man page - I'll probably slap that into xfs(5) > at some point. I've found this page which I'll use as my reference to syssgi() unless there is a better online version. http://reality.sgi.com/cgi-bin/getman?syssgi-2#toc1 One interesting question about this call, if I have a file (potentially with holes in it) that is, for example, 4Mb large and issue a SEEK_SET, start=0, len=10Mb should this ioctl work? Or is reserving space only valid from the end of file? From the above interface it would seem that one can reserve space from anywhere, eg, SEEK_CUR, start=1Mb, len=4Mb to reserve a 4 meg chunk one meg down the pipe. I would like to know when its best for this call to be made, I am thinking as a extra param to file creation in ferris, though I might also allow one to perform it at any time so that a file can be extended with preallocation when a new chunk of data is known to be coming and will be put into that file. ----------------------------------------------------- A new world order: http://witme.sourceforge.net/libferris.web/ From owner-linux-xfs@oss.sgi.com Mon Sep 3 05:02:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83C2Sx23964 for linux-xfs-outgoing; Mon, 3 Sep 2001 05:02:28 -0700 Received: from wingate.merck.de (wingate.merck.de [155.250.128.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83C2Nd23944 for ; Mon, 3 Sep 2001 05:02:24 -0700 Received: from dedamsg4.merck.de (mail4.merck.de [155.250.249.26]) by wingate.merck.de (8.9.3 (PHNE_18546)/8.9.3) with ESMTP id OAA07908 for ; Mon, 3 Sep 2001 14:02:21 +0200 (METDST) From: Oliver.Karch@merck.de Received: from admin.bci.merck.de ([155.250.217.66]) by dedamsg4.merck.de (Lotus Domino Release 5.0.8) with ESMTP id 2001090314022028:47457 ; Mon, 3 Sep 2001 14:02:20 +0200 Received: from mailserver.bci.merck.de (gate-ranseti.bci.merck.de [155.250.217.8]) by admin.bci.merck.de (8.8.5/8.7.1) with ESMTP id OAA7929505; Mon, 3 Sep 2001 14:02:19 +0200 (MDT) Message-ID: <3B93714A.55B0A38D@mailserver.bci.merck.de> Date: Mon, 03 Sep 2001 14:02:19 +0200 Organization: Merck KGaA X-Mailer: Mozilla 4.61C-SGI [en] (X11; I; IRIX 6.5 IP32) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Cc: BCIHelp@admin.bci.merck.de.sgi.com X-MIMETrack: Itemize by SMTP Server on DEDAMSG4/EMD/Merck(Release 5.0.8 |June 18, 2001) at 03.09.2001 14:02:20, Serialize by Router on DEDAMSG4/EMD/Merck(Release 5.0.8 |June 18, 2001) at 03.09.2001 14:02:21, Serialize complete at 03.09.2001 14:02:21 Subject: Value too large for defined data type Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, we are successfully using xfs on SGI linux workstation / servers (330L and 1450). However if I try to stat a file larger than 2 GB, which is eventually done by a networker backup, I get an error: Value too large for defined data type Do we need an update of glibc or an "xfs aware" version of stat ? We are using XFS 1.0.1 on Linux sumba 2.4.3-SGI_XFS_1.0.1smp #1 SMP Mon Jul 9 14:03:40 CDT 2001 i686 unknown Any help would be appreciated. Thanks. Best regards Oliver Karch -- __________________________________________________________ Dr. Oliver Karch Frankfurter Str. 250 MERCK KGaA 64271 Darmstadt, Germany Medicinal Chemistry +49 6151 723825 (phone) Research Department +49 6151 723329 (fax) Bio- and Chemoinformatics http://www.merck.de From owner-linux-xfs@oss.sgi.com Mon Sep 3 07:32:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83EWcs18212 for linux-xfs-outgoing; Mon, 3 Sep 2001 07:32:38 -0700 Received: from zeta.qmw.ac.uk (zeta.qmw.ac.uk [138.37.6.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83EWYd18170 for ; Mon, 3 Sep 2001 07:32:34 -0700 Received: from heppcl.ph.qmw.ac.uk ([138.37.50.187]) by zeta.qmw.ac.uk with esmtp (Exim 3.16 #1) id 15dum9-0005iF-00 for linux-xfs@oss.sgi.com; Mon, 03 Sep 2001 15:32:33 +0100 Received: from heppct.ph.qmw.ac.uk (heppct.ph.qmw.ac.uk [138.37.50.246]) by heppcl.ph.qmw.ac.uk (8.9.3/8.9.3) with ESMTP id PAA29892 for ; Mon, 3 Sep 2001 15:32:33 +0100 Received: from localhost (pd@localhost) by heppct.ph.qmw.ac.uk (8.11.2/8.9.3) with ESMTP id f83EWXR22748 for ; Mon, 3 Sep 2001 15:32:33 +0100 X-Authentication-Warning: heppct.ph.qmw.ac.uk: pd owned process doing -bs Date: Mon, 3 Sep 2001 15:32:33 +0100 (BST) From: "P.Dixon" To: Subject: about to try RAID.... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, We're about to try xfs and software raid. We've done this in the past using 3x Promise Ultra ATA 100TX2 controllers. However, I've seen on this list a few bad comments about Promise, so I was wondering if there are any alternatives that people think would be a better option. This is what we plan to do: Using a standard motherboad/CPU in a large tower case, we want to use 8x IBM 61.5 GB hard disks in a software RAID 5 configuration (using XFS of course). Any hints/tips would be greatly appreciated. Cheerio, Paul ------------------------------------------------------------------------------- Paul Dixon Email: P.Dixon@qmw.ac.uk Department of Physics Phone: (020) 7882 5054 Queen Mary, University of London Fax : (020) 7882 5054 Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd ------------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Mon Sep 3 07:36:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83Ea5e19656 for linux-xfs-outgoing; Mon, 3 Sep 2001 07:36:05 -0700 Received: from zeta.qmw.ac.uk (zeta.qmw.ac.uk [138.37.6.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83Ea3d19624 for ; Mon, 3 Sep 2001 07:36:03 -0700 Received: from heppcl.ph.qmw.ac.uk ([138.37.50.187]) by zeta.qmw.ac.uk with esmtp (Exim 3.16 #1) id 15dupW-0005km-00 for linux-xfs@oss.sgi.com; Mon, 03 Sep 2001 15:36:02 +0100 Received: from heppct.ph.qmw.ac.uk (heppct.ph.qmw.ac.uk [138.37.50.246]) by heppcl.ph.qmw.ac.uk (8.9.3/8.9.3) with ESMTP id PAA29922 for ; Mon, 3 Sep 2001 15:36:02 +0100 Received: from localhost (pd@localhost) by heppct.ph.qmw.ac.uk (8.11.2/8.9.3) with ESMTP id f83Ea2L22775 for ; Mon, 3 Sep 2001 15:36:02 +0100 X-Authentication-Warning: heppct.ph.qmw.ac.uk: pd owned process doing -bs Date: Mon, 3 Sep 2001 15:36:02 +0100 (BST) From: "P.Dixon" To: Subject: Re: about to try RAID.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > We're about to try xfs and software raid. We've done this in the past > using ext2 I should add! Paul From owner-linux-xfs@oss.sgi.com Mon Sep 3 07:53:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83ErGN26428 for linux-xfs-outgoing; Mon, 3 Sep 2001 07:53:16 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83ErAd26350 for ; Mon, 3 Sep 2001 07:53:10 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id QAA04130; Mon, 3 Sep 2001 16:53:07 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id QAA05495; Mon, 3 Sep 2001 16:53:07 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 1032457306; Mon, 3 Sep 2001 16:52:16 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id F18A125835; Mon, 3 Sep 2001 16:52:11 +0200 (CEST) Message-ID: <3B93991B.24B2798F@ch.sauter-bc.com> Date: Mon, 03 Sep 2001 16:52:11 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: "P.Dixon" Cc: linux-xfs@oss.sgi.com Subject: Re: about to try RAID.... References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "P.Dixon" schrieb: > > Hi, > > We're about to try xfs and software raid. We've done this in the past > using 3x Promise Ultra ATA 100TX2 controllers. However, I've seen on this > list a few bad comments about Promise, so I was wondering if there are any > alternatives that people think would be a better option. > > This is what we plan to do: > > Using a standard motherboad/CPU in a large tower case, we want to use 8x > IBM 61.5 GB hard disks in a software RAID 5 configuration (using XFS of > course). > > Any hints/tips would be greatly appreciated. I was trying something similar but without success due to the following reasons: 1) The 8 IBM drives IC35L060AVER07-0 (made in thailand, march 2001) where in fact unusable for what I planned to do. Six of them started to produce 'bad sectors' whithin two days of operation. Using the IBM Drive Fittness Test tool 'repaired' the disk but new errors came after some more hours of activity. It was even so bad that the RAID5 never synced because it always reached a bad sector while syncing. I will send all of the disks back to IBM but I'm not sure for what - to receive another 8 failing disks? 2) The Promise Ultra ATA 100TX2 has produced corrupt data in two Computers from DELL. One was Precision 220, the other PowerEdge 1400SC. This error occured only when accessing more than one disk simultaneously - be it on the onboard IDE controller or the Promise. It looks like we have a general problem here because the same was reported from VIA based motherboards. However, I'm using the Ultra ATA 100TX2 in my home server with four Quantum Fireball 15G on a AMD-K6-2 and it work absolutely stable! My advice is that you just check whether the Promise is stable in your system and you make sure the 8 drives are okay. Performance of the Promise controllers is very good. Simon > > Cheerio, > Paul > > ------------------------------------------------------------------------------- > Paul Dixon Email: P.Dixon@qmw.ac.uk > Department of Physics Phone: (020) 7882 5054 > Queen Mary, University of London Fax : (020) 7882 5054 > Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd > ------------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Mon Sep 3 09:16:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83GGFm30599 for linux-xfs-outgoing; Mon, 3 Sep 2001 09:16:15 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83GG7d30579 for ; Mon, 3 Sep 2001 09:16:07 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id 5FE856703E for ; Mon, 3 Sep 2001 18:16:00 +0200 (CEST) Cc: linux-xfs@oss.sgi.com Subject: Re: about to try RAID.... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 3 Sep 2001 18:15:59 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 03.09.2001 18:16:08, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 03.09.2001 18:16:08, Serialize complete at 03.09.2001 18:16:08, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 03.09.2001 18:16:09, S/MIME Sign complete at 03.09.2001 18:16:09, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 03.09.2001 18:16:01, Serialize complete at 03.09.2001 18:16:01 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z12334_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z12334_boundary_sign Content-Type: text/plain; charset="us-ascii" On 03.09.2001 16:32:33 "P.Dixon" wrote: >Hi, > >We're about to try xfs and software raid. We've done this in the past >using 3x Promise Ultra ATA 100TX2 controllers. However, I've seen on >this >list a few bad comments about Promise, so I was wondering if there are >any >alternatives that people think would be a better option. > >This is what we plan to do: > >Using a standard motherboad/CPU in a large tower case, we want to use 8x >IBM 61.5 GB hard disks in a software RAID 5 configuration (using XFS of >course). > >Any hints/tips would be greatly appreciated. > >Cheerio, > Paul We use the 3ware IDE-Raidcontrollers for real Raid, so we don't have to care about the software-raid layer.......(And they are fast) cu michael ---------z12334_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwMzE2MTYwOVowIwYJKoZIhvcNAQkEMRYEFDq0eHeI3p47UoaJ c/cJLx5WvzvRMEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGAEsrYwPa3S9ppCwg1mmT5eN6naMiHS01+jW1R9TcancdsokfRTa9D WeaOakGvJywPIxr19JUJTMmu75SiFSUb1l7IUnyydeXL3rH7jN7MZZuo1aWnMvRz tN6sRkVs5/nwZqTTdYf0EGBjFnuuLRh1vxw6q+rA37wbv22qWq84wToAAAAAAAAA AA== ---------z12334_boundary_sign-- From owner-linux-xfs@oss.sgi.com Mon Sep 3 09:23:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83GN8v30836 for linux-xfs-outgoing; Mon, 3 Sep 2001 09:23:08 -0700 Received: from zeta.qmw.ac.uk (zeta.qmw.ac.uk [138.37.6.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83GN6d30817 for ; Mon, 3 Sep 2001 09:23:06 -0700 Received: from heppcl.ph.qmw.ac.uk ([138.37.50.187]) by zeta.qmw.ac.uk with esmtp (Exim 3.16 #1) id 15dwV5-00076o-00 for linux-xfs@oss.sgi.com; Mon, 03 Sep 2001 17:23:03 +0100 Received: from heppct.ph.qmw.ac.uk (heppct.ph.qmw.ac.uk [138.37.50.246]) by heppcl.ph.qmw.ac.uk (8.9.3/8.9.3) with ESMTP id RAA31455 for ; Mon, 3 Sep 2001 17:23:04 +0100 Received: from localhost (pd@localhost) by heppct.ph.qmw.ac.uk (8.11.2/8.9.3) with ESMTP id f83GN4V23447 for ; Mon, 3 Sep 2001 17:23:04 +0100 X-Authentication-Warning: heppct.ph.qmw.ac.uk: pd owned process doing -bs Date: Mon, 3 Sep 2001 17:23:04 +0100 (BST) From: "P.Dixon" To: Subject: Re: about to try RAID.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > We use the 3ware IDE-Raidcontrollers for real Raid, so we don't have to > care about the software-raid layer.......(And they are fast) > Lots of good comments about 3ware stuff - but can't actually find anyone selling these things in Britain! Cheerio, Paul From owner-linux-xfs@oss.sgi.com Mon Sep 3 09:54:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83Gs5P31271 for linux-xfs-outgoing; Mon, 3 Sep 2001 09:54:05 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83Gs1d31252 for ; Mon, 3 Sep 2001 09:54:01 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id PAA02483; Mon, 3 Sep 2001 15:59:26 +0200 (CEST) Message-Id: <4.3.2.7.2.20010903155822.03f95a40@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 03 Sep 2001 15:58:43 +0200 To: Oliver.Karch@merck.de, linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Value too large for defined data type Cc: BCIHelp@admin.bci.merck.de.sgi.com In-Reply-To: <3B93714A.55B0A38D@mailserver.bci.merck.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 14:02 3-9-2001 +0200, Oliver.Karch@merck.de wrote: >Hi, > >we are successfully using xfs on SGI linux workstation / servers (330L >and 1450). However if I try to stat a file larger than 2 GB, which is >eventually done by a networker backup, I get an error: > >Value too large for defined data type > >Do we need an update of glibc or an "xfs aware" version of stat ? We are >using XFS 1.0.1 on It's in the FAQ. Cheers >Linux sumba 2.4.3-SGI_XFS_1.0.1smp #1 SMP Mon Jul 9 14:03:40 CDT 2001 >i686 unknown > >Any help would be appreciated. Thanks. > >Best regards > >Oliver Karch > >-- >__________________________________________________________ >Dr. Oliver Karch Frankfurter Str. 250 >MERCK KGaA 64271 Darmstadt, Germany >Medicinal Chemistry +49 6151 723825 (phone) >Research Department +49 6151 723329 (fax) >Bio- and Chemoinformatics http://www.merck.de -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Sep 3 09:55:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83GtYW31402 for linux-xfs-outgoing; Mon, 3 Sep 2001 09:55:34 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83GtRd31383 for ; Mon, 3 Sep 2001 09:55:27 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id 3716B6703E; Mon, 3 Sep 2001 18:55:21 +0200 (CEST) To: "P.Dixon" Cc: linux-xfs@oss.sgi.com Subject: Re: about to try RAID.... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 3 Sep 2001 18:55:20 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 03.09.2001 18:55:29, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 03.09.2001 18:55:29, Serialize complete at 03.09.2001 18:55:29, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 03.09.2001 18:55:29, S/MIME Sign complete at 03.09.2001 18:55:29, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 03.09.2001 18:55:21, Serialize complete at 03.09.2001 18:55:21 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z1706_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z1706_boundary_sign Content-Type: text/plain; charset="us-ascii" On 03.09.2001 18:23:04 "P.Dixon" wrote: >> We use the 3ware IDE-Raidcontrollers for real Raid, so we don't have >to >> care about the software-raid layer.......(And they are fast) >> >Lots of good comments about 3ware stuff - but can't actually find anyone >selling these things in Britain! > >Cheerio, > Paul Hi Paul, >From the 3ware homepage (www.3ware.com): United Kingdom: Distributor TMC Technology Ltd Caxton Place, Caxton Way, Stevenage, Hertfordshire. SG1 2UQ United Kingdom Tel. +44 1438 842 300 Fax. +44 1438 842 333 www.tmc-uk.com Contact: James Low email:sales@tmc-uk.com Tel. +44 1438 842 300 x317 ask them for resellers or direct buy ;-) cu micha ---------z1706_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwMzE2NTUyOVowIwYJKoZIhvcNAQkEMRYEFEwvikmijBIdaYo2 ciPnBNMp3yo1MEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGAEN2jkkMHFdIzUX83nfOoXiaC9SiKUI9vOqQZEIgVbZyK61my47Qx Ip8LL1hzeWcJMJcbSQ0q89mI2dcx66fdX20oW5lHU6aLFPH3kcMG7rf8OTWA9vP9 VEKmYj07EeoLv7NxCkBFYWLRd7/TCLLx9tWK8MPAqlPWb/RSWSPtScQAAAAAAAAA AA== ---------z1706_boundary_sign-- From owner-linux-xfs@oss.sgi.com Mon Sep 3 10:41:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83Hfu432013 for linux-xfs-outgoing; Mon, 3 Sep 2001 10:41:56 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83Hfqd31994 for ; Mon, 3 Sep 2001 10:41:52 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id ; Mon, 3 Sep 2001 12:41:23 -0500 Message-ID: <85063BBE668FD411944400D0B744267A888526@AUSMAIL> From: "Gonyou, Austin" To: "'Seth Mos'" , "Gonyou, Austin" , XFS mailing list Subject: RE: System lock while accessing files causes file corruption Date: Mon, 3 Sep 2001 12:41:19 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk That's all well and good..but what about the configuration files? They are text and are not redundant in the same way. I know it's been done to death..and I've read a lot of this stuff, but even after making thanges, etc, especially if I use logbufs > 2, I can make this happen at will. That's why I've got concerns. I know about the points Keith made, and very valid in this case especially, but my major concern is deploying a TB size db only to get taken down that my configs are messed up. (yes, I know that's what backups and CVS are for) but that's not acceptable when talking about my primary FS. I'm going to go through as many iterations of this as I can to see if I can narrow down exactly what and where, what hardware, etc. We're about to do a major deployment and I'm just trying to do due dilligence, beyond the FAQ and random mails. Thanks for listening, and this can certainly come off-list if you feel that's best. I really don't want to beat a dead horse anymore than I have to. Assurance of success in this respect is very important. We don't have a lot of storage to throw around. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Seth Mos [mailto:knuffie@xs4all.nl] > Sent: Sunday, September 02, 2001 7:18 PM > To: Gonyou, Austin; XFS mailing list > Subject: Re: System lock while accessing files causes file corruption > > > At 18:16 2-9-2001 -0500, Gonyou, Austin wrote: > >Why is this? If I open a file, text/otherwise and the power > actually fails, > >(i turn it off), once in a while I get a corrupt file. Why > is this? What > >would happen if I was writing to some Oracle filesystems and > this situation > >occurred? Please advise. > > See the http://oss.sgi.com/projects/xfs/faq.html#nulls > > A database would survive since most have their own buffering and > transaction scheme. > > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. > From owner-linux-xfs@oss.sgi.com Mon Sep 3 11:03:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83I3i332464 for linux-xfs-outgoing; Mon, 3 Sep 2001 11:03:44 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83I3fd32445 for ; Mon, 3 Sep 2001 11:03:41 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f83I3Z324911 for linux-xfs@oss.sgi.com; Mon, 3 Sep 2001 14:03:35 -0400 Date: Mon, 3 Sep 2001 14:03:35 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: in xfsdump CVS:STREAM_MAX?? Message-ID: <20010903140335.A24744@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Last couple of days... gcc -O1 -g -DDEBUG -funsigned-char -Wall -DDUMP -DRMT -DBASED -DDOSOCKS -DINVCONVFIX -DSIZEEST -DPIPEINVFIX -DEXTATTR -DDMEXTATTR -I/usr/include/xfs -I/usr/include/attr '-DVERSION="1.1.3"' -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DXFS_BIG_FILES=1 -DXFS_BIG_FILESYSTEMS=1 -I/usr/include/xfs -I/usr/include/attr -c -o cldmgr.o cldmgr.c cldmgr.c:65: STREAM_MAX' undeclared here (not in a function) cldmgr.c:65: size of array cld' has non-integer type cldmgr.c: In function cldmgr_create': cldmgr.c:109: STREAM_MAX' undeclared (first use in this function) cldmgr.c:109: (Each undeclared identifier is reported only once cldmgr.c:109: for each function it appears in.) make[1]: *** [cldmgr.o] Error 1 make: *** [default] Error 2 error: Bad exit status from /home/alane/rpm/tmp/rpm-tmp.16124 (%build) xfs-adventure> take STREAM_MAX I see no STREAM_MAX here. xfs-adventure> explain [alane@wwweasel idutils]$ (cd usr; aid STREAM_MAX);(cd kernel; aid STREAM_MAX) _POSIX_STREAM_MAX /usr/include/bits/posix1_lim.h _SC_STREAM_MAX /usr/include/bits/confname.h [alane@wwweasel idutils]$ -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Mon Sep 3 11:21:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83IL5w32754 for linux-xfs-outgoing; Mon, 3 Sep 2001 11:21:05 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83IKxd32735 for ; Mon, 3 Sep 2001 11:20:59 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id LAA04810 for ; Mon, 3 Sep 2001 11:20:59 -0700 (PDT) mail_from (austin@coremetrics.com) Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id ; Mon, 3 Sep 2001 13:18:54 -0500 Message-ID: <85063BBE668FD411944400D0B744267A888527@AUSMAIL> From: "Gonyou, Austin" To: "Gonyou, Austin" , "'Seth Mos'" , "'XFS mailing list'" Subject: RE: System lock while accessing files causes file corruption Date: Mon, 3 Sep 2001 13:18:51 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk One quick not on this, is there anything I can do kernel wise to prevent this without striking a crapload of overhead on the system? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Gonyou, Austin > Sent: Monday, September 03, 2001 12:41 PM > To: 'Seth Mos'; Gonyou, Austin; XFS mailing list > Subject: RE: System lock while accessing files causes file corruption > > > That's all well and good..but what about the configuration > files? They are text and are not redundant in the same way. I > know it's been done to death..and I've read a lot of this > stuff, but even after making thanges, etc, especially if I > use logbufs > 2, I can make this happen at will. That's why > I've got concerns. I know about the points Keith made, and > very valid in this case especially, but my major concern is > deploying a TB size db only to get taken down that my configs > are messed up. (yes, I know that's what backups and CVS are > for) but that's not acceptable when talking about my primary > FS. I'm going to go through as many iterations of this as I > can to see if I can narrow down exactly what and where, what > hardware, etc. We're about to do a major deployment and I'm > just trying to do due dilligence, beyond the FAQ and random > mails. Thanks for listening, and this can certainly come > off-list if you feel that's best. I really don't want to beat > a dead horse anymore than I have to. Assurance of success in > this respect is very important. We don't have a lot of > storage to throw around. > > -- > Austin Gonyou > Systems Architect, CCNA > Coremetrics, Inc. > Phone: 512-796-9023 > email: austin@coremetrics.com > > > -----Original Message----- > > From: Seth Mos [mailto:knuffie@xs4all.nl] > > Sent: Sunday, September 02, 2001 7:18 PM > > To: Gonyou, Austin; XFS mailing list > > Subject: Re: System lock while accessing files causes file > corruption > > > > > > At 18:16 2-9-2001 -0500, Gonyou, Austin wrote: > > >Why is this? If I open a file, text/otherwise and the power > > actually fails, > > >(i turn it off), once in a while I get a corrupt file. Why > > is this? What > > >would happen if I was writing to some Oracle filesystems and > > this situation > > >occurred? Please advise. > > > > See the http://oss.sgi.com/projects/xfs/faq.html#nulls > > > > A database would survive since most have their own buffering and > > transaction scheme. > > > > > > -- > > Seth > > Every program has two purposes one for which > > it was written and another for which it wasn't > > I use the last kind. > > > From owner-linux-xfs@oss.sgi.com Mon Sep 3 13:50:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83Koe501847 for linux-xfs-outgoing; Mon, 3 Sep 2001 13:50:40 -0700 Received: from msg.ecetra.com (dollar.ecetra.com [193.164.224.209]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83KoWd01828 for ; Mon, 3 Sep 2001 13:50:32 -0700 Received: from vie-ac.office.ecetra.com (vie-ac.office.ecetra.com [10.251.148.147] (may be forged)) by msg.ecetra.com (8.9.3/8.9.3) with ESMTP id WAA07799; Mon, 3 Sep 2001 22:50:25 +0200 Received: from localhost (localhost [127.0.0.1]) by vie-ac.office.ecetra.com (8.11.4/8.11.3) with ESMTP id f83KoOx31451; Mon, 3 Sep 2001 22:50:24 +0200 Date: Mon, 3 Sep 2001 22:50:24 +0200 (CEST) From: Adam Cioccarelli To: "Gonyou, Austin" cc: Subject: RE: System lock while accessing files causes file corruption In-Reply-To: <85063BBE668FD411944400D0B744267A888527@AUSMAIL> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Just one point... Oracle just has one configuration file, initxxx.ora and this only read by the database at startup, it never writes to this file. If you ever lose it you can easily recreate it by taking a look in the alert logs which show all non default parameters taken from the init file. Anyway I think that the point is that where you might end up with a file that is just garbage on an xfs filesystem, you wouldn't have any file at all on ext2, or at least that is my undersatnding... ------------------------------------------------------------------------------- Adam Cioccarelli (B.E Mechanical) Adam.Cioccarelli@ecetra.com Database Administrator Phone: +43 1 536 89 7725 Fax: +43 1 536 89 7719 ecetra Central European e-Finance AG Mobile:+43 664 181 4195 ------------------------------------------------------------------------------- On Mon, 3 Sep 2001, Gonyou, Austin wrote: > One quick not on this, is there anything I can do kernel wise to prevent > this without striking a crapload of overhead on the system? > > -- > Austin Gonyou > Systems Architect, CCNA > Coremetrics, Inc. > Phone: 512-796-9023 > email: austin@coremetrics.com > > > -----Original Message----- > > From: Gonyou, Austin > > Sent: Monday, September 03, 2001 12:41 PM > > To: 'Seth Mos'; Gonyou, Austin; XFS mailing list > > Subject: RE: System lock while accessing files causes file corruption > > > > > > That's all well and good..but what about the configuration > > files? They are text and are not redundant in the same way. I > > know it's been done to death..and I've read a lot of this > > stuff, but even after making thanges, etc, especially if I > > use logbufs > 2, I can make this happen at will. That's why > > I've got concerns. I know about the points Keith made, and > > very valid in this case especially, but my major concern is > > deploying a TB size db only to get taken down that my configs > > are messed up. (yes, I know that's what backups and CVS are > > for) but that's not acceptable when talking about my primary > > FS. I'm going to go through as many iterations of this as I > > can to see if I can narrow down exactly what and where, what > > hardware, etc. We're about to do a major deployment and I'm > > just trying to do due dilligence, beyond the FAQ and random > > mails. Thanks for listening, and this can certainly come > > off-list if you feel that's best. I really don't want to beat > > a dead horse anymore than I have to. Assurance of success in > > this respect is very important. We don't have a lot of > > storage to throw around. > > > > -- > > Austin Gonyou > > Systems Architect, CCNA > > Coremetrics, Inc. > > Phone: 512-796-9023 > > email: austin@coremetrics.com > > > > > -----Original Message----- > > > From: Seth Mos [mailto:knuffie@xs4all.nl] > > > Sent: Sunday, September 02, 2001 7:18 PM > > > To: Gonyou, Austin; XFS mailing list > > > Subject: Re: System lock while accessing files causes file > > corruption > > > > > > > > > At 18:16 2-9-2001 -0500, Gonyou, Austin wrote: > > > >Why is this? If I open a file, text/otherwise and the power > > > actually fails, > > > >(i turn it off), once in a while I get a corrupt file. Why > > > is this? What > > > >would happen if I was writing to some Oracle filesystems and > > > this situation > > > >occurred? Please advise. > > > > > > See the http://oss.sgi.com/projects/xfs/faq.html#nulls > > > > > > A database would survive since most have their own buffering and > > > transaction scheme. > > > > > > > > > -- > > > Seth > > > Every program has two purposes one for which > > > it was written and another for which it wasn't > > > I use the last kind. > > > > > > From owner-linux-xfs@oss.sgi.com Mon Sep 3 13:56:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83KuR902017 for linux-xfs-outgoing; Mon, 3 Sep 2001 13:56:27 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83KuLd01998 for ; Mon, 3 Sep 2001 13:56:21 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA17374; Mon, 3 Sep 2001 22:56:20 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id WAA16805; Mon, 3 Sep 2001 22:56:19 +0200 (CEST) Date: Mon, 3 Sep 2001 22:56:19 +0200 (CEST) From: Seth Mos To: "Gonyou, Austin" cc: "'XFS mailing list'" Subject: RE: System lock while accessing files causes file corruption In-Reply-To: <85063BBE668FD411944400D0B744267A888527@AUSMAIL> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 3 Sep 2001, Gonyou, Austin wrote: > One quick not on this, is there anything I can do kernel wise to prevent > this without striking a crapload of overhead on the system? No, all metadata journaling filesystems have this. ReiserFS has it and I suspect that JFS can do this as well. If I ever get the NCR MP-RAS box to be out of production I could test this with Veritas as well. I hate to say it but this a general metadata jfs problem/feature. It needs a smarter kernel to make it go to disk faster when the box is not loaded. > > -----Original Message----- > > From: Gonyou, Austin > > Sent: Monday, September 03, 2001 12:41 PM > > To: 'Seth Mos'; Gonyou, Austin; XFS mailing list > > Subject: RE: System lock while accessing files causes file corruption > > > > > > That's all well and good..but what about the configuration > > files? They are text and are not redundant in the same way. I > > know it's been done to death..and I've read a lot of this > > stuff, but even after making thanges, etc, especially if I > > use logbufs > 2, I can make this happen at will. That's why > > I've got concerns. I know about the points Keith made, and > > very valid in this case especially, but my major concern is > > deploying a TB size db only to get taken down that my configs > > are messed up. (yes, I know that's what backups and CVS are > > for) but that's not acceptable when talking about my primary > > FS. I'm going to go through as many iterations of this as I > > can to see if I can narrow down exactly what and where, what > > hardware, etc. We're about to do a major deployment and I'm > > just trying to do due dilligence, beyond the FAQ and random > > mails. Thanks for listening, and this can certainly come > > off-list if you feel that's best. I really don't want to beat > > a dead horse anymore than I have to. Assurance of success in > > this respect is very important. We don't have a lot of > > storage to throw around. > > > > -- > > Austin Gonyou > > Systems Architect, CCNA > > Coremetrics, Inc. > > Phone: 512-796-9023 > > email: austin@coremetrics.com > > > > > -----Original Message----- > > > From: Seth Mos [mailto:knuffie@xs4all.nl] > > > Sent: Sunday, September 02, 2001 7:18 PM > > > To: Gonyou, Austin; XFS mailing list > > > Subject: Re: System lock while accessing files causes file > > corruption > > > > > > > > > At 18:16 2-9-2001 -0500, Gonyou, Austin wrote: > > > >Why is this? If I open a file, text/otherwise and the power > > > actually fails, > > > >(i turn it off), once in a while I get a corrupt file. Why > > > is this? What > > > >would happen if I was writing to some Oracle filesystems and > > > this situation > > > >occurred? Please advise. > > > > > > See the http://oss.sgi.com/projects/xfs/faq.html#nulls > > > > > > A database would survive since most have their own buffering and > > > transaction scheme. > > > > > > > > > -- > > > Seth > > > Every program has two purposes one for which > > > it was written and another for which it wasn't > > > I use the last kind. > > > > > > > From owner-linux-xfs@oss.sgi.com Mon Sep 3 14:10:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83LAoA02444 for linux-xfs-outgoing; Mon, 3 Sep 2001 14:10:50 -0700 Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83LAmd02425 for ; Mon, 3 Sep 2001 14:10:48 -0700 Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 15e0zS-000NVP-0Y for linux-xfs@oss.sgi.com; Mon, 3 Sep 2001 22:10:44 +0100 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id 02FA027F0 for ; Mon, 3 Sep 2001 22:10:40 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id 10E04125E6; Mon, 3 Sep 2001 22:10:40 +0100 (BST) Date: Mon, 3 Sep 2001 22:10:39 +0100 (BST) From: Keith Matthews Subject: Re[2]: System lock while accessing files causes file corruption To: linux-xfs@oss.sgi.com In-Reply-To: References: X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010903211040.10E04125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f83LAmd02426 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 3 Sep 2001 22:50:24 +0200 (CEST) Adam Cioccarelli > wrote: > > Just one point... Oracle just has one configuration file, initxxx.ora and > this only read by the database at startup, it never writes to this file. > If you ever lose it you can easily recreate it by taking a look in the > alert logs which show all non default parameters taken from the init file From owner-linux-xfs@oss.sgi.com Mon Sep 3 14:18:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83LIjq02643 for linux-xfs-outgoing; Mon, 3 Sep 2001 14:18:45 -0700 Received: from quasar.sif.it (IDENT:root@quasar.sif.it [131.154.110.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83LIed02617 for ; Mon, 3 Sep 2001 14:18:40 -0700 Received: from localhost (matteo@localhost) by quasar.sif.it (8.11.2/8.11.2) with ESMTP id f83LIqT18811; Mon, 3 Sep 2001 23:18:52 +0200 Date: Mon, 3 Sep 2001 23:18:52 +0200 (CEST) From: Matteo Centonza To: "P.Dixon" cc: Subject: Re: about to try RAID.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, we actually use a Promise Ultra ATA 100 and an on board controller with 4 IBM DTLA hd with LVM on top of soft RAID5 (Athlon 1.33 Ghz). This setup is in production, updating the kernel cvs every once in a while, since early june, it's rock solid, and recently saved our ass when our server keep on crashing hergodically (10 times per day due to a power supply defect, avoiding the consequent 140 Gb fs check). Thanks to XFS(primarily) and LVM, we have extremely valid HA solution for linux. Thanks a lot guys. Ciao, -m On Mon, 3 Sep 2001, P.Dixon wrote: > Hi, > > We're about to try xfs and software raid. We've done this in the past > using 3x Promise Ultra ATA 100TX2 controllers. However, I've seen on this > list a few bad comments about Promise, so I was wondering if there are any > alternatives that people think would be a better option. > > This is what we plan to do: > > Using a standard motherboad/CPU in a large tower case, we want to use 8x > IBM 61.5 GB hard disks in a software RAID 5 configuration (using XFS of > course). > > Any hints/tips would be greatly appreciated. > > Cheerio, > Paul > > ------------------------------------------------------------------------------- > Paul Dixon Email: P.Dixon@qmw.ac.uk > Department of Physics Phone: (020) 7882 5054 > Queen Mary, University of London Fax : (020) 7882 5054 > Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd > ------------------------------------------------------------------------------- > From owner-linux-xfs@oss.sgi.com Mon Sep 3 14:23:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83LNNb02788 for linux-xfs-outgoing; Mon, 3 Sep 2001 14:23:23 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83LN2d02768; Mon, 3 Sep 2001 14:23:02 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id EF44D6703F; Mon, 3 Sep 2001 23:22:55 +0200 (CEST) To: "Michael Wahlbrink" Cc: Keith Owens , Seth Mos , linux-xfs@oss.sgi.com, Michael Wahlbrink , owner-linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 3 Sep 2001 23:22:54 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 03.09.2001 23:23:04, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 03.09.2001 23:23:04, Serialize complete at 03.09.2001 23:23:04, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 03.09.2001 23:23:04, S/MIME Sign complete at 03.09.2001 23:23:04, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 03.09.2001 23:22:56, Serialize complete at 03.09.2001 23:22:56 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z18235_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z18235_boundary_sign Content-Type: text/plain; charset="us-ascii" On 02.09.2001 00:07:42 "Michael Wahlbrink" wrote: >Ok, no problem ;-) > >I'll make my tests with ext2 to see if the kernel 'oopses' too......... >And the PII is still compiling th xfs kernel.... > >cu >michael > Ok, I think I've found the error! :-)) I've made the tests also with ext2 and run into IO errors...... I checked the drives and burned my fingers...... The drives are getting to hot :-( So I installed a additional cooler and all was nearly fine... Because of all the compilation tries and tests my system was unusuable and i get more and more strange errors (also from xfs)...... So i installed a new clean system (2.4.10-pre4-xfs), and now its working.......! On the PII its also working fine..... But there is one thing, why does ext2 says that it have IO Problems when writing to disk and xfs simply dies with an oops when you try to acess the corrupt data ???? cu michael ---------z18235_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwMzIxMjMwNFowIwYJKoZIhvcNAQkEMRYEFPV8P2EO6q2OrzhK Hx+Co7FjxjmLMEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGAALTQDaK8fkNJKSCcFDDhRFOmU1qMQ2pYgqbXhVXF0BbnjMknk+Jz dbKSf6uChjIJZKtmlvolrOqAzEKqi7jq4AVf2q/im13WEEfEAMCUUoC39ne/0Ysl GpTvdadchaOT0I1qYzArkOHOWb4YHBjOFeE15fEgIy6RwnT7xliINW4AAAAAAAAA AA== ---------z18235_boundary_sign-- From owner-linux-xfs@oss.sgi.com Mon Sep 3 14:33:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83LX4V03124 for linux-xfs-outgoing; Mon, 3 Sep 2001 14:33:04 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83LWvd03104 for ; Mon, 3 Sep 2001 14:32:57 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id ; Mon, 3 Sep 2001 16:32:25 -0500 Message-ID: <85063BBE668FD411944400D0B744267A88852A@AUSMAIL> From: "Gonyou, Austin" To: "'XFS mailing list'" Subject: RE: System lock while accessing files causes file corruption Date: Mon, 3 Sep 2001 16:32:23 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk All, Thanks so much for your input on this and not flaming the living daylights out of me. The info I've gathered here from everyone's feedback is sure enough to be good armament should I run into problems helping people understand things. Knowing the reality of things vs. "facts" is very important. Thank you all again for your help. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Seth Mos [mailto:knuffie@xs4all.nl] > Sent: Monday, September 03, 2001 3:56 PM > To: Gonyou, Austin > Cc: 'XFS mailing list' > Subject: RE: System lock while accessing files causes file corruption > > > On Mon, 3 Sep 2001, Gonyou, Austin wrote: > > > One quick not on this, is there anything I can do kernel > wise to prevent > > this without striking a crapload of overhead on the system? > > No, all metadata journaling filesystems have this. ReiserFS > has it and I > suspect that JFS can do this as well. If I ever get the NCR > MP-RAS box to > be out of production I could test this with Veritas as well. > > I hate to say it but this a general metadata jfs > problem/feature. It needs > a smarter kernel to make it go to disk faster when the box is > not loaded. > > > > -----Original Message----- > > > From: Gonyou, Austin > > > Sent: Monday, September 03, 2001 12:41 PM > > > To: 'Seth Mos'; Gonyou, Austin; XFS mailing list > > > Subject: RE: System lock while accessing files causes > file corruption > > > > > > > > > That's all well and good..but what about the configuration > > > files? They are text and are not redundant in the same way. I > > > know it's been done to death..and I've read a lot of this > > > stuff, but even after making thanges, etc, especially if I > > > use logbufs > 2, I can make this happen at will. That's why > > > I've got concerns. I know about the points Keith made, and > > > very valid in this case especially, but my major concern is > > > deploying a TB size db only to get taken down that my configs > > > are messed up. (yes, I know that's what backups and CVS are > > > for) but that's not acceptable when talking about my primary > > > FS. I'm going to go through as many iterations of this as I > > > can to see if I can narrow down exactly what and where, what > > > hardware, etc. We're about to do a major deployment and I'm > > > just trying to do due dilligence, beyond the FAQ and random > > > mails. Thanks for listening, and this can certainly come > > > off-list if you feel that's best. I really don't want to beat > > > a dead horse anymore than I have to. Assurance of success in > > > this respect is very important. We don't have a lot of > > > storage to throw around. > > > > > > -- > > > Austin Gonyou > > > Systems Architect, CCNA > > > Coremetrics, Inc. > > > Phone: 512-796-9023 > > > email: austin@coremetrics.com > > > > > > > -----Original Message----- > > > > From: Seth Mos [mailto:knuffie@xs4all.nl] > > > > Sent: Sunday, September 02, 2001 7:18 PM > > > > To: Gonyou, Austin; XFS mailing list > > > > Subject: Re: System lock while accessing files causes file > > > corruption > > > > > > > > > > > > At 18:16 2-9-2001 -0500, Gonyou, Austin wrote: > > > > >Why is this? If I open a file, text/otherwise and the power > > > > actually fails, > > > > >(i turn it off), once in a while I get a corrupt file. Why > > > > is this? What > > > > >would happen if I was writing to some Oracle filesystems and > > > > this situation > > > > >occurred? Please advise. > > > > > > > > See the http://oss.sgi.com/projects/xfs/faq.html#nulls > > > > > > > > A database would survive since most have their own > buffering and > > > > transaction scheme. > > > > > > > > > > > > -- > > > > Seth > > > > Every program has two purposes one for which > > > > it was written and another for which it wasn't > > > > I use the last kind. > > > > > > > > > > > > From owner-linux-xfs@oss.sgi.com Mon Sep 3 14:48:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83LmbL03452 for linux-xfs-outgoing; Mon, 3 Sep 2001 14:48:37 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83LmTd03433 for ; Mon, 3 Sep 2001 14:48:29 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA01658; Mon, 3 Sep 2001 23:48:27 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id XAA27542; Mon, 3 Sep 2001 23:48:27 +0200 (CEST) Date: Mon, 3 Sep 2001 23:48:27 +0200 (CEST) From: Seth Mos To: "Gonyou, Austin" cc: "'XFS mailing list'" Subject: RE: System lock while accessing files causes file corruption In-Reply-To: <85063BBE668FD411944400D0B744267A88852A@AUSMAIL> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 3 Sep 2001, Gonyou, Austin wrote: > All, > Thanks so much for your input on this and not flaming the living > daylights out of me. The info I've gathered here from everyone's feedback is You have to give me a good reason first. Since my new laptop arived I don't really care ;-) > sure enough to be good armament should I run into problems helping people > understand things. Knowing the reality of things vs. "facts" is very > important. Thank you all again for your help. You're welcome > > -- > Austin Gonyou > Systems Architect, CCNA > Coremetrics, Inc. > Phone: 512-796-9023 > email: austin@coremetrics.com > > > -----Original Message----- > > From: Seth Mos [mailto:knuffie@xs4all.nl] > > Sent: Monday, September 03, 2001 3:56 PM > > To: Gonyou, Austin > > Cc: 'XFS mailing list' > > Subject: RE: System lock while accessing files causes file corruption > > > > > > On Mon, 3 Sep 2001, Gonyou, Austin wrote: > > > > > One quick not on this, is there anything I can do kernel > > wise to prevent > > > this without striking a crapload of overhead on the system? > > > > No, all metadata journaling filesystems have this. ReiserFS > > has it and I > > suspect that JFS can do this as well. If I ever get the NCR > > MP-RAS box to > > be out of production I could test this with Veritas as well. > > > > I hate to say it but this a general metadata jfs > > problem/feature. It needs > > a smarter kernel to make it go to disk faster when the box is > > not loaded. > > > > > > -----Original Message----- > > > > From: Gonyou, Austin > > > > Sent: Monday, September 03, 2001 12:41 PM > > > > To: 'Seth Mos'; Gonyou, Austin; XFS mailing list > > > > Subject: RE: System lock while accessing files causes > > file corruption > > > > > > > > > > > > That's all well and good..but what about the configuration > > > > files? They are text and are not redundant in the same way. I > > > > know it's been done to death..and I've read a lot of this > > > > stuff, but even after making thanges, etc, especially if I > > > > use logbufs > 2, I can make this happen at will. That's why > > > > I've got concerns. I know about the points Keith made, and > > > > very valid in this case especially, but my major concern is > > > > deploying a TB size db only to get taken down that my configs > > > > are messed up. (yes, I know that's what backups and CVS are > > > > for) but that's not acceptable when talking about my primary > > > > FS. I'm going to go through as many iterations of this as I > > > > can to see if I can narrow down exactly what and where, what > > > > hardware, etc. We're about to do a major deployment and I'm > > > > just trying to do due dilligence, beyond the FAQ and random > > > > mails. Thanks for listening, and this can certainly come > > > > off-list if you feel that's best. I really don't want to beat > > > > a dead horse anymore than I have to. Assurance of success in > > > > this respect is very important. We don't have a lot of > > > > storage to throw around. > > > > > > > > -- > > > > Austin Gonyou > > > > Systems Architect, CCNA > > > > Coremetrics, Inc. > > > > Phone: 512-796-9023 > > > > email: austin@coremetrics.com > > > > > > > > > -----Original Message----- > > > > > From: Seth Mos [mailto:knuffie@xs4all.nl] > > > > > Sent: Sunday, September 02, 2001 7:18 PM > > > > > To: Gonyou, Austin; XFS mailing list > > > > > Subject: Re: System lock while accessing files causes file > > > > corruption > > > > > > > > > > > > > > > At 18:16 2-9-2001 -0500, Gonyou, Austin wrote: > > > > > >Why is this? If I open a file, text/otherwise and the power > > > > > actually fails, > > > > > >(i turn it off), once in a while I get a corrupt file. Why > > > > > is this? What > > > > > >would happen if I was writing to some Oracle filesystems and > > > > > this situation > > > > > >occurred? Please advise. > > > > > > > > > > See the http://oss.sgi.com/projects/xfs/faq.html#nulls > > > > > > > > > > A database would survive since most have their own > > buffering and > > > > > transaction scheme. > > > > > > > > > > > > > > > -- > > > > > Seth > > > > > Every program has two purposes one for which > > > > > it was written and another for which it wasn't > > > > > I use the last kind. > > > > > > > > > > > > > > > > > > > From owner-linux-xfs@oss.sgi.com Mon Sep 3 16:57:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f83NvnJ05162 for linux-xfs-outgoing; Mon, 3 Sep 2001 16:57:49 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f83Nvld05143 for ; Mon, 3 Sep 2001 16:57:47 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id QAA02726 for ; Mon, 3 Sep 2001 16:57:34 -0700 (PDT) mail_from (ajag@snort.melbourne.sgi.com) Received: (from ajag@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id JAA92509 for linux-xfs@oss.sgi.com; Tue, 4 Sep 2001 09:56:09 +1000 (EST) Date: Tue, 4 Sep 2001 09:56:09 +1000 (EST) From: Andrew Gildfind Message-Id: <200109032356.JAA92509@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - Fix xfsdump build Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Un-STREAM_MAXify... undo mod 2.4.x-xfs:slinx:101997a and fix the remaining STREAM_MAX's.. Date: Mon Sep 3 16:53:47 PDT 2001 Workarea: snort.melbourne.sgi.com:/home/ajag/isms/slinx Undoes mod: 2.4.x-xfs:slinx:101997a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102075a cmd/xfsdump/dump/content.c - 1.10 cmd/xfsdump/common/stream.c - 1.4 cmd/xfsdump/common/mlog.c - 1.3 cmd/xfsdump/common/main.c - 1.9 cmd/xfsdump/common/cldmgr.c - 1.4 cmd/xfsdump/restore/content.c - 1.14 From owner-linux-xfs@oss.sgi.com Mon Sep 3 17:24:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f840ONo05634 for linux-xfs-outgoing; Mon, 3 Sep 2001 17:24:23 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f840OKd05614 for ; Mon, 3 Sep 2001 17:24:20 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f840OE524643 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Mon, 3 Sep 2001 17:24:14 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id CAA860667 for ; Tue, 4 Sep 2001 02:24:13 +0200 (CEST) mail_from (ajag@snort.melbourne.sgi.com) Received: (from ajag@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA49510 for linux-xfs@oss.sgi.com; Tue, 4 Sep 2001 10:22:51 +1000 (EST) Date: Tue, 4 Sep 2001 10:22:51 +1000 (EST) From: Andrew Gildfind Message-Id: <200109040022.KAA49510@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - Fix xfsdump build Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sync with IRIX, remove warnings... Date: Mon Sep 3 17:21:28 PDT 2001 Workarea: snort.melbourne.sgi.com:/home/ajag/isms/slinx The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102078a cmd/xfsdump/common/mlog.c - 1.4 cmd/xfsdump/common/main.c - 1.10 - Remove warnings From owner-linux-xfs@oss.sgi.com Mon Sep 3 19:03:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8423a707148 for linux-xfs-outgoing; Mon, 3 Sep 2001 19:03:36 -0700 Received: from longsword.omniti.com (IDENT:exim@longsword.omniti.com [216.0.51.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8423Xd07129 for ; Mon, 3 Sep 2001 19:03:33 -0700 Received: from warhammer.omniti.com ([216.0.51.145] helo=omniti.com) by longsword.omniti.com with esmtp (Exim 3.22 #2) id 15e5Yo-0003fz-00; Mon, 03 Sep 2001 22:03:30 -0400 Message-ID: <3B943672.4040302@omniti.com> Date: Mon, 03 Sep 2001 22:03:30 -0400 From: "Theo E. Schlossnagle" Organization: OmniTI, Inc. -- Computer Consulting User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010802 X-Accept-Language: en-us MIME-Version: 1.0 To: Paul Schutte CC: exim-users@exim.org, linux-xfs@oss.sgi.com Subject: Re: [Exim] Re: Exim and XFS filesystem References: <3B8BB7C7.4020808@omniti.com> <3B929216.B2D4AC60@it.up.ac.za> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Paul Schutte wrote: > What mount options did you use ? Mounting xfs for /var/spool with options: logbufs=8,logbsize=32768 Mounting xfs for /var with options: defaults. My install of exim writes everything but logs into /var/spool, logs it writes into /var. -- Theo Schlossnagle 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 Mon Sep 3 20:54:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f843s3d09079 for linux-xfs-outgoing; Mon, 3 Sep 2001 20:54:03 -0700 Received: from webber.adilger.int (h24-64-71-161.cg.shawcable.net [24.64.71.161]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f843s0d09060 for ; Mon, 3 Sep 2001 20:54:00 -0700 Received: from webber.adilger.int (adilger@localhost [127.0.0.1]) by localhost (8.12.0.Beta10/8.12.0.Beta10/Debian 8.12.0.Beta10) with ESMTP id f843r14h032579; Mon, 3 Sep 2001 21:53:02 -0600 Received: (from adilger@localhost) by webber.adilger.int (8.12.0.Beta10/8.12.0.Beta10/Debian 8.12.0.Beta10) id f843r0wN032577; Mon, 3 Sep 2001 21:53:00 -0600 From: Andreas Dilger Date: Mon, 3 Sep 2001 21:53:00 -0600 To: linux-lvm@sistina.com Cc: linux-xfs@oss.sgi.com, akpm@zip.com.au, neilb@cse.unsw.edu.au Subject: Re: [linux-lvm] PBs with LVM over software RAID ( and XFS ? ext2 reiserfs?) Message-ID: <20010903215300.B32553@turbolinux.com> Mail-Followup-To: linux-lvm@sistina.com, linux-xfs@oss.sgi.com, akpm@zip.com.au, neilb@cse.unsw.edu.au References: <3B8E3F0E.8050609@st-peter.stw.uni-erlangen.de> <20010830083546.A20989@sistina.com> <3B8EC633.40202@st-peter.stw.uni-erlangen.de> <3B8F8C5E.7030603@st-peter.stw.uni-erlangen.de> <20010831110512.V541@turbolinux.com> <3B90C9A4.3080005@st-peter.stw.uni-erlangen.de> <3B90EC90.4050606@st-peter.stw.uni-erlangen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B90EC90.4050606@st-peter.stw.uni-erlangen.de> User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sep 01, 2001 16:11 +0200, svetljo wrote: > clean Linus kernel-2.4.9 LVM-1.0.1rc1 ext2 and > reiserfs segfaults > clean linux-2.4.9-ac5 LVM-1.0 ext2 and > reiserfs segfaults > | linux-2.4.10-pre2-xfs LVM-1.0.1rc2 ext2 and > reiserfs segfaults, but xfs seems to work > | from SGI's cvs tree linux-2.4-xfs taken today in > the early morning Is it possible that you are having memory problems? Did this work with earlier kernels and it now only fails with 2.4.9? Have you tried running with memtest86 to check your RAM? It seems like you are having too many problems with different filesystems. Cheers, Andreas -- Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry?" http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert From owner-linux-xfs@oss.sgi.com Mon Sep 3 20:59:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f843x9Q09254 for linux-xfs-outgoing; Mon, 3 Sep 2001 20:59:09 -0700 Received: from alaska.net (kitsune.nwc.alaska.net [209.112.130.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f843x4d09235 for ; Mon, 3 Sep 2001 20:59:04 -0700 Received: from erbenson.alaska.net (34-pm21.nwc.alaska.net [209.112.143.34]) by alaska.net (8.9.1/8.9.1) with ESMTP id TAA10597 for ; Mon, 3 Sep 2001 19:58:54 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 07583397B for ; Mon, 3 Sep 2001 19:45:37 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id B091110246; Mon, 3 Sep 2001 19:45:37 -0800 (AKDT) Date: Mon, 3 Sep 2001 19:45:37 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: kernel spam when mounting xfs Message-ID: <20010903194537.G14519@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Sw7tCqrGA+HQ0/zt" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --Sw7tCqrGA+HQ0/zt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, i just recently converted a machine to use xfs on all partitions sans /boot. =20 the only thing i really dislike about it is all the spam from the kernel when the filesystems are mounted: Start mounting filesystem: ide0(3,5) Ending clean XFS mount for filesystem: ide0(3,5) =2E... and so on .... when you have several filesystems (i prefer to keep / /var /home and /usr split) this is rather messy. I also prefer the old axiom of `No news is good news' that is, if the filesystem mounts without errors, and was clean, i don't need to be told that.=20 so my suggestion is to eliminate the `Start mounting filesystem...' message altogether (its useless IMHO) and eliminate the `Ending clean mount' instead only display a (single) message if filesystem recovery was required. perhaps make a mount option, verbose, if some people prefer to see all these messages on filesystem mount. =20 note i have debug mode turned off in my kernel config. =20 thanks --=20 Ethan Benson http://www.alaska.net/~erbenson/ --Sw7tCqrGA+HQ0/zt 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 iEYEARECAAYFAjuUTmEACgkQJKx7GixEevyvbACghnIDBAUcGgIdB3KFJUzXF89B u1AAnRysvJpwqpOOpbMKQhFu63OvdM1U =zBjU -----END PGP SIGNATURE----- --Sw7tCqrGA+HQ0/zt-- From owner-linux-xfs@oss.sgi.com Mon Sep 3 23:54:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f846shB11840 for linux-xfs-outgoing; Mon, 3 Sep 2001 23:54:43 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f846sbd11817 for ; Mon, 3 Sep 2001 23:54:37 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA04960; Tue, 4 Sep 2001 08:54:35 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA28435; Tue, 4 Sep 2001 08:54:34 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 9EBF157306; Tue, 4 Sep 2001 08:53:23 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 4B95125835; Tue, 4 Sep 2001 08:53:23 +0200 (CEST) Message-ID: <3B947A63.F08A1245@ch.sauter-bc.com> Date: Tue, 04 Sep 2001 08:53:23 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Ethan Benson Cc: linux-xfs@oss.sgi.com Subject: Re: kernel spam when mounting xfs References: <20010903194537.G14519@plato.local.lan> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ethan Benson schrieb: > > Hi, > > i just recently converted a machine to use xfs on all partitions sans > /boot. > > the only thing i really dislike about it is all the spam from the > kernel when the filesystems are mounted: Is this spam? Did you ever use ReiserFS? Checking ReiserFS transaction log (device 03:06) ... Using r5 hash to sort names Primary Sponsor thresholdnetworks.com Raid Tuning sponsored by emusic.com HSM sponsored by bigstorage.com Alpha port and SMP sponsored by alpha-processor.com, alpha port by www.innovative-software.com and www.quant-x.com. ReiserFS version 3.5.29 VFS: Mounted root (reiserfs filesystem) readonly. change_root: old root has d_count=1 Trying to unmount old root ... okay Freeing unused kernel memory: 128k freed Adding Swap: 506008k swap-space (priority -1) Checking ReiserFS transaction log (device 03:01) ... Using r5 hash to sort names ReiserFS version 3.5.29 Checking ReiserFS transaction log (device 03:08) ... Using r5 hash to sort names ReiserFS version 3.5.29 Checking ReiserFS transaction log (device 03:07) ... Using r5 hash to sort names ReiserFS version 3.5.29 > > Start mounting filesystem: ide0(3,5) > Ending clean XFS mount for filesystem: ide0(3,5) > .... and so on .... > > when you have several filesystems (i prefer to keep / /var /home and > /usr split) this is rather messy. I also prefer the old axiom of `No > news is good news' that is, if the filesystem mounts without errors, > and was clean, i don't need to be told that. > > so my suggestion is to eliminate the `Start mounting filesystem...' > message altogether (its useless IMHO) and eliminate the `Ending clean > mount' instead only display a (single) message if filesystem recovery > was required. > > perhaps make a mount option, verbose, if some people prefer to see all > these messages on filesystem mount. > > note i have debug mode turned off in my kernel config. > > thanks > > -- > Ethan Benson > http://www.alaska.net/~erbenson/ > > ------------------------------------------------------------------------ > Part 1.2Type: application/pgp-signature From owner-linux-xfs@oss.sgi.com Tue Sep 4 00:03:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8473N012106 for linux-xfs-outgoing; Tue, 4 Sep 2001 00:03:23 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8473Gd12087; Tue, 4 Sep 2001 00:03:16 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id JAA06610; Tue, 4 Sep 2001 09:03:14 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id JAA29065; Tue, 4 Sep 2001 09:03:13 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id B2A7357306; Tue, 4 Sep 2001 09:02:20 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 4A34825835; Tue, 4 Sep 2001 09:02:20 +0200 (CEST) Message-ID: <3B947C7C.7E44DC92@ch.sauter-bc.com> Date: Tue, 04 Sep 2001 09:02:20 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Michael Wahlbrink Cc: Keith Owens , Seth Mos , linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Michael Wahlbrink schrieb: > > On 02.09.2001 00:07:42 "Michael Wahlbrink" wrote: > >Ok, no problem ;-) > > > >I'll make my tests with ext2 to see if the kernel 'oopses' too......... > >And the PII is still compiling th xfs kernel.... > > > >cu > >michael > > > Ok, I think I've found the error! :-)) > I've made the tests also with ext2 and run into IO errors...... I checked > the drives and burned my fingers...... The drives are getting to hot :-( > So I installed a additional cooler and all was nearly fine... > Because of all the compilation tries and tests my system was unusuable and > i get more and more strange errors (also from xfs)...... So i installed a > new clean system (2.4.10-pre4-xfs), and now its working.......! > On the PII its also working fine..... > > But there is one thing, why does ext2 says that it have IO Problems when > writing to disk and xfs simply dies with an oops when you try to acess the > corrupt data ???? Just imagine you have bad memory, it is flipping bits sometimes. Now can you ask why does it crash when using this or another filesystem? No, I mean the filesystems just expect properly working hardware. If there is a problem with corruption, you can not expect reproducable effects. My own experience with corruption was that most time xfs survived without oopsing. But anyway such a system is unusable. 1 must be 1, and 0 must be 0. Simon > > cu > michael -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Tue Sep 4 00:04:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8474mC12256 for linux-xfs-outgoing; Tue, 4 Sep 2001 00:04:48 -0700 Received: from rebel.net.au (IDENT:root@rebel.rebel.net.au [203.20.69.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8474id12237 for ; Tue, 4 Sep 2001 00:04:44 -0700 Received: from rebel.net.au (dialup-6.rebel.net.au [203.20.69.76]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id QAA32157; Tue, 4 Sep 2001 16:34:09 +0930 Message-ID: <3B947E6F.A45A65D2@rebel.net.au> Date: Tue, 04 Sep 2001 16:40:39 +0930 From: David Lloyd X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.5-xfs-1.0.1 i586) X-Accept-Language: en MIME-Version: 1.0 To: Simon Matter CC: Ethan Benson , linux-xfs@oss.sgi.com Subject: Re: kernel spam when mounting xfs References: <20010903194537.G14519@plato.local.lan> <3B947A63.F08A1245@ch.sauter-bc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Heh! > Is this spam? Did you ever use ReiserFS? > > Checking ReiserFS transaction log (device 03:06) ... > Using r5 hash to sort names > Primary Sponsor thresholdnetworks.com > Raid Tuning sponsored by emusic.com > HSM sponsored by bigstorage.com > Alpha port and SMP sponsored by alpha-processor.com, alpha port by > www.innovative-software.com and www.quant-x.com. If you search the ReiserFS mailing list there was an absolute flame war about this very matter ;-P DSL -- Pussy's good for six at the most (Mrs. Lovett, Sweeney Todd) From owner-linux-xfs@oss.sgi.com Tue Sep 4 01:19:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f848JmP13582 for linux-xfs-outgoing; Tue, 4 Sep 2001 01:19:48 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f848IMd13544; Tue, 4 Sep 2001 01:18:22 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id E7E9767040; Tue, 4 Sep 2001 10:18:10 +0200 (CEST) To: Simon Matter Cc: Keith Owens , Seth Mos , linux-xfs@oss.sgi.com, Michael Wahlbrink , owner-linux-xfs@oss.sgi.com Subject: Re: Kernel Oops ..... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Tue, 4 Sep 2001 10:18:09 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 04.09.2001 10:18:20, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 04.09.2001 10:18:20, Serialize complete at 04.09.2001 10:18:20, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 04.09.2001 10:18:20, S/MIME Sign complete at 04.09.2001 10:18:20, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 04.09.2001 10:18:11, Serialize complete at 04.09.2001 10:18:11 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z46341_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z46341_boundary_sign Content-Type: text/plain; charset="us-ascii" On 04.09.2001 09:02:20 Simon Matter wrote: >Michael Wahlbrink schrieb: >> >> On 02.09.2001 00:07:42 "Michael Wahlbrink" wrote: >> >Ok, no problem ;-) >> > >> >I'll make my tests with ext2 to see if the kernel 'oopses' >too......... >> >And the PII is still compiling th xfs kernel.... >> > >> >cu >> >michael >> > >> Ok, I think I've found the error! :-)) >> I've made the tests also with ext2 and run into IO errors...... I >checked >> the drives and burned my fingers...... The drives are getting to hot >:-( >> So I installed a additional cooler and all was nearly fine... >> Because of all the compilation tries and tests my system was >unusuable and >> i get more and more strange errors (also from xfs)...... So i >installed a >> new clean system (2.4.10-pre4-xfs), and now its working.......! >> On the PII its also working fine..... >> >> But there is one thing, why does ext2 says that it have IO Problems >when >> writing to disk and xfs simply dies with an oops when you try to >acess the >> corrupt data ???? > >Just imagine you have bad memory, it is flipping bits sometimes. Now can >you ask why does it crash when using this or another filesystem? No, I >mean the filesystems just expect properly working hardware. If there is >a problem with corruption, you can not expect reproducable effects. My >own experience with corruption was that most time xfs survived without >oopsing. But anyway such a system is unusable. 1 must be 1, and 0 must >be 0. I think it was the temperature, cause the SDRAM was checked one night long with memtest86 without errors, and also for a test replaced with other DIMMs which worked fine in another Mashine and are also correct........ cu micha ---------z46341_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM1MIICHaADAgECAgQ68WMUMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYDVQQLExdDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNz IDIgQ0EwHhcNMDEwNTAzMDAwMDAwWhcNMDIwNTAzMjM1OTAwWjCBnTELMAkGA1UE BhMCREUxEDAOBgNVBAgTB0dlcm1hbnkxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgG A1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEaMBgGA1UEAxMR TWljaGFlbCBXYWhsYnJpbmsxIjAgBgkqhkiG9w0BCQEWE21pd0Bwcm9wYWNrLWRh dGEuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALIOckqT1A9Rhsfgt4Y0 A98B9yUW0jztpCFpnti1cj5hkjaB7bTj029ki6cVXwlmv/MzqrIB0AfqOhILTDOo OilUqAjydR5D88jKnLPT1JyIKOaMjjFWa26vmSB2lTp4RdPmbtkiQoUZ9cBvglMV FYL/b9gC6mEpLAAyAfV8pIrNAgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAEZhuNN2 nawO0zgdlUS379E2LP1Y1UkqRvbs+JJt4o/9iICT9QtC1Xqfb2S1AUldHSrT83PW TUoNjpL+n/SYeDrq6UPkfCMrbO4XhwRcOy5b+xJG+5GfshrL0ENzBVF2SsSYWcoz cp6y0GAVI74Wf7W91QCPz4cyhr3AP7ASal15XjlXLyoNL+59AqD2elGWsU6OUCg8 qw2xG/2IYAcpMGgHpmab9OBtF4R8+2b9qnFDqWUPK+L6KjJpwPFvkYpgW4ESsW5L jQgfog9+/gB8GxFU1FXvcbnuaJFwudaq9wMyKiLWJIK0jVH5fUIUzEPOemOz8fhn zUNVTnhZVI/sF6wwggO6MIICoqADAgECAgQ5Td9zMA0GCSqGSIb3DQEBBAUAMIGe MQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYD VQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMSAwHgYD VQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBE YXRhIENsYXNzIDIgQ0EwHhcNMDAwNjE4MDAwMDAwWhcNMDIwNjE4MjM1OTAwWjCB njELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVtYmVyZzESMBAG A1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEgR21iSDEgMB4G A1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sg RGF0YSBDbGFzcyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA 4sC9VaqHbKulz8+2vUwsODP7NAtBFxlehMYd6zHoYgD67GKnTlQj0EKK+TtHfZvI VtPKBXo4xuwePOx34pS+yeg4Wu2Yt984UFvy5WGhaSOox5OTfQ040go0QP+GPcz/ 02q8sy/UKdEFH1Q7l4AMQoewr6mi12mSii2HudcA4oWBqshHrZG64TFbZ539M4Au DxFqxGISuozATaMw4UVzR4Jju7KUH+chhj7eTYxGr1a8Ov8xapOuSxwrR0Nm9qKl h1/b9tspuLC3wNP2SExBccmOOX1QPHI9uVOegkQX0kSFmL0kONzUIa9d9TAYyP5H /OazPHpKcb7evqyJh5gmNwIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQBMrCrpoVIi mshBQdBdtPVCBex75s8sb/qmPFwxTn8IHASc3AWtfBPmoEf1c5FcVUERLQFr6uQV RU5ejmJewyzzf+iKlGLjWPvWLghEibWm+GTm1rLJpe+YwgR6/5y874RhaUj3KFi7 yCJsUaF2qKgEv39Lq4VgdRihhB++ZF3zgj/dv7dwOwC2jgk8mAZf1Cp3jG8yhLnI ZIRbYOuZdUCpBzCRj1qfD+P4izFarG4sHo3k7kfkCzpsyDrCJojmXzzoF3diAm5Q PHWlYYhNA0i09m8hW9YpxhfBp7qmIIYd5tCOqjZVgiyA9RLb68a2PnS30LzIIsQH OtubyM8KT7WqAAAxgDCCAfgCAQEwgacwgZ4xCzAJBgNVBAYTAmRlMRswGQYDVQQI ExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEaMBgGA1UE ChMRUHJvcGFjayBEYXRhIEdtYkgxIDAeBgNVBAsTF0NlcnRpZmljYXRpb24gQXV0 aG9yaXR5MSAwHgYDVQQDExdQcm9wYWNrIERhdGEgQ2xhc3MgMiBDQQIEOvFjFDAJ BgUrDgMCGgUAoIGrMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN AQkFMQ8XDTAxMDkwNDA4MTgyMFowIwYJKoZIhvcNAQkEMRYEFBt+fAfpe7NDJFJu lcjDwz7RKtwXMEwGCSqGSIb3DQEJDzE/MD0wBwYFKw4DAh0wDgYIKoZIhvcNAwIC AgCAMAoGCCqGSIb3DQMHMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3 DQEBAQUABIGACysK+7ZUbvvpcfNiqAMykEqTmnYwMNYvWHfCtgLG+KrGUkGDlYb+ N6vRE+RLCQ5ZvYcYN0HCWoLedd3TByHoxtqQnBQjqtyalytIVDJ3ZOvK91l7rrt3 aC2bDv1Skw8Rf3CVekVI+pXMJeZAvZ1/nsHTeEaDzv36KRzCM2byh5wAAAAAAAAA AA== ---------z46341_boundary_sign-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 02:06:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8496ww14370 for linux-xfs-outgoing; Tue, 4 Sep 2001 02:06:58 -0700 Received: from trna.ximian.com (trna.ximian.com [141.154.95.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8496ud14344 for ; Tue, 4 Sep 2001 02:06:56 -0700 Received: (from vladimir@localhost) by trna.ximian.com (8.9.3/8.9.3) id FAA17013; Tue, 4 Sep 2001 05:06:37 -0400 Date: Tue, 4 Sep 2001 05:06:37 -0400 From: Vladimir Vukicevic To: David Lloyd Cc: Simon Matter , Ethan Benson , linux-xfs@oss.sgi.com Subject: Re: kernel spam when mounting xfs Message-ID: <20010904050637.A16701@ximian.com> References: <20010903194537.G14519@plato.local.lan> <3B947A63.F08A1245@ch.sauter-bc.com> <3B947E6F.A45A65D2@rebel.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B947E6F.A45A65D2@rebel.net.au>; from lloy0076@rebel.net.au on Tue, Sep 04, 2001 at 04:40:39PM +0930 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 04, 2001 at 04:40:39PM +0930, David Lloyd wrote: > > Checking ReiserFS transaction log (device 03:06) ... > > Using r5 hash to sort names > > Primary Sponsor thresholdnetworks.com > > Raid Tuning sponsored by emusic.com > > HSM sponsored by bigstorage.com > > Alpha port and SMP sponsored by alpha-processor.com, alpha port by > > www.innovative-software.com and www.quant-x.com. > > If you search the ReiserFS mailing list there was an absolute flame war > about this very matter ;-P Isn't everything on the ReiserFS mailing list a flame of some form or another? :-) :-) :-) - Vlad From owner-linux-xfs@oss.sgi.com Tue Sep 4 02:15:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f849Fdt14625 for linux-xfs-outgoing; Tue, 4 Sep 2001 02:15:39 -0700 Received: from alaska.net (sephiroth.nwc.alaska.net [209.112.130.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f849FYd14606 for ; Tue, 4 Sep 2001 02:15:34 -0700 Received: from erbenson.alaska.net (34-pm21.nwc.alaska.net [209.112.143.34]) by alaska.net (8.11.5/8.11.5) with ESMTP id f849FVP03311 for ; Tue, 4 Sep 2001 01:15:32 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 79DD7397B for ; Tue, 4 Sep 2001 01:15:30 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 47BC110246; Tue, 4 Sep 2001 01:15:30 -0800 (AKDT) Date: Tue, 4 Sep 2001 01:15:30 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: kernel spam when mounting xfs Message-ID: <20010904011530.I14519@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010903194537.G14519@plato.local.lan> <3B947A63.F08A1245@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/GPgYEyhnw15BExa" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B947A63.F08A1245@ch.sauter-bc.com>; from simon.matter@ch.sauter-bc.com on Tue, Sep 04, 2001 at 08:53:23AM +0200 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --/GPgYEyhnw15BExa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 04, 2001 at 08:53:23AM +0200, Simon Matter wrote: > Ethan Benson schrieb: > >=20 > > Hi, > >=20 > > i just recently converted a machine to use xfs on all partitions sans > > /boot. > >=20 > > the only thing i really dislike about it is all the spam from the > > kernel when the filesystems are mounted: >=20 > Is this spam? Did you ever use ReiserFS? no i prefer to use filesystems that runs on archetectures other then i386 ;-) > Checking ReiserFS transaction log (device 03:06) ... > Using r5 hash to sort names > Primary Sponsor thresholdnetworks.com > Raid Tuning sponsored by emusic.com > HSM sponsored by bigstorage.com > Alpha port and SMP sponsored by alpha-processor.com, alpha port by > www.innovative-software.com and www.quant-x.com. > ReiserFS version 3.5.29 > VFS: Mounted root (reiserfs filesystem) readonly. > change_root: old root has d_count=3D1 > Trying to unmount old root ... okay > Freeing unused kernel memory: 128k freed > Adding Swap: 506008k swap-space (priority -1) > Checking ReiserFS transaction log (device 03:01) ... > Using r5 hash to sort names > ReiserFS version 3.5.29 > Checking ReiserFS transaction log (device 03:08) ... > Using r5 hash to sort names > ReiserFS version 3.5.29 > Checking ReiserFS transaction log (device 03:07) ... > Using r5 hash to sort names > ReiserFS version 3.5.29 ok thats bad (ya reason not to use reiserfs...). but still my request stands. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --/GPgYEyhnw15BExa 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 iEYEARECAAYFAjuUm7IACgkQJKx7GixEevxWGwCeMc4U3A6fIS6V5oxtNLNWFwR8 IcoAn1A/AyuRGl4DH37RCNd6jOzmgze2 =Cwo7 -----END PGP SIGNATURE----- --/GPgYEyhnw15BExa-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 04:41:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84BfCM17200 for linux-xfs-outgoing; Tue, 4 Sep 2001 04:41:12 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Bf9d17181 for ; Tue, 4 Sep 2001 04:41:09 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f84Bf3523571 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 4 Sep 2001 04:41:03 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id NAA861257 for ; Tue, 4 Sep 2001 13:41:03 +0200 (CEST) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id VAA08035 for linux-xfs@oss.sgi.com; Tue, 4 Sep 2001 21:39:42 +1000 (EST) Date: Tue, 4 Sep 2001 21:39:42 +1000 (EST) From: Nathan Scott Message-Id: <200109041139.VAA08035@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - mount msgs Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Consensus seems to be less chatty on mount - this should do the trick. Can still get at these messages with a debug build (as is the case for the nightly QA runs) where these messages are still quite useful. cheers. Date: Tue Sep 4 04:36:44 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/attr-linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102087a linux/fs/xfs/xfs_log.c - 1.240 linux/fs/xfs/xfs_log_recover.c - 1.209 - only report clean log mounts in debug mode. linux/fs/xfs_support/debug.c - 1.3 - make debug mode cmn_err only print out messages in debug kernels. From owner-linux-xfs@oss.sgi.com Tue Sep 4 04:44:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Biv117371 for linux-xfs-outgoing; Tue, 4 Sep 2001 04:44:57 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Bisd17352 for ; Tue, 4 Sep 2001 04:44:54 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id A46D51E11C; Tue, 4 Sep 2001 13:44:48 +0200 (MEST) Date: Tue, 4 Sep 2001 13:44:37 +0200 From: Andi Kleen To: Nathan Scott Cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010904134437.A28205@gruyere.muc.suse.de> References: <200109041139.VAA08035@snort.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109041139.VAA08035@snort.melbourne.sgi.com>; from nathans@snort.melbourne.sgi.com on Tue, Sep 04, 2001 at 09:39:42PM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 04, 2001 at 09:39:42PM +1000, Nathan Scott wrote: > Consensus seems to be less chatty on mount - this should do the trick. > Can still get at these messages with a debug build (as is the case for > the nightly QA runs) where these messages are still quite useful. I think it would be better to keep them; as it makes debugging even on production machines easier. -Andi From owner-linux-xfs@oss.sgi.com Tue Sep 4 04:53:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Br5117614 for linux-xfs-outgoing; Tue, 4 Sep 2001 04:53:05 -0700 Received: from ender.capfed1.sinectis.com.ar (IDENT:root@ender.capfed1.sinectis.com.ar [216.244.211.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Br0d17594 for ; Tue, 4 Sep 2001 04:53:00 -0700 Received: from sinectis.com (ix.sinectis.com.ar [216.244.192.24]) by ender.capfed1.sinectis.com.ar (8.9.3/8.9.3) with ESMTP id IAA25261 for ; Tue, 4 Sep 2001 08:52:58 -0300 Message-ID: <3B94BFD9.83E09CEE@sinectis.com> Date: Tue, 04 Sep 2001 08:49:45 -0300 From: Dario Brignardello Organization: Sinectis S.A. X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.4.7 i686) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: Block size. Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms3AAA66B764624A336696086E" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a cryptographically signed message in MIME format. --------------ms3AAA66B764624A336696086E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all: Sorry for bother with a newbie question, but I didn't find the answer in the FAQ:-). I would like to now the reasons (technically speaking) for the max block size to be fixed at 4K in linux, since, as stated in the white papers, XFS is designed to support larger block sizes, and it was one of the reasons that made it the difference when I had to choose a journaling filesystem. Thanks a lot for your time. Regards! Dario Brignardello --------------ms3AAA66B764624A336696086E Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIHKAYJKoZIhvcNAQcCoIIHGTCCBxUCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BXEwggJAMIIBqaADAgECAgMEPIQwDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMTAyMjExNzA3MjZaFw0wMjAyMjExNzA3MjZa MEcxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxJDAiBgkqhkiG9w0BCQEWFWRi cmlnbmFyQHNpbmVjdGlzLmNvbTBcMA0GCSqGSIb3DQEBAQUAA0sAMEgCQQCn/IthgAlkAIa6 +dZyjp+6U06kxrHJKPfRAJM/1YJeiTY5vjHq4fMdrUaF/tkd90V4H10aO7FK2B0+KV5odlRJ AgMBAAGjMjAwMCAGA1UdEQQZMBeBFWRicmlnbmFyQHNpbmVjdGlzLmNvbTAMBgNVHRMBAf8E AjAAMA0GCSqGSIb3DQEBBAUAA4GBABaZqSGHw4VZbOeZRUKqPbPqTNv3f5D6OX0x3kJX0nZq 2gLRExP7rhWGTxjtIoLr7+PvOyt2E/p4CQpy/zjHtoqATT4Nl5DM6Oz0ywsi2TW6Zxvog0gO G+AVS+UBdIvqO8Bat/bX633X10ibTH41Yh1pQ0T5SnLD1i/bis2EqbQIMIIDKTCCApKgAwIB AgIBDDANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4g Q2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEo MCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhh d3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVl bWFpbEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTAyMDgyOTIzNTk1OVowgZIxCzAJ BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEP MA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UE AxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/ +TRxoKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENC UFGHgzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwx GjAYBgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0P BAQDAgEGMA0GCSqGSIb3DQEBBAUAA4GBAHMbbyZli/8VNEtZYortRL5Jx+gNu4+5DWomKmKE H7iHY3QcbbfPGlORS+HN5jjZ7VD0Omw0kqzmkpxuwSMBwgmn70uuct0GZ/VQby5YuLYLwVBX tewc1+8XttWIm7eiiBrtOVs5fTT8tpYYJU1q9J3Fw5EvqZa4BTxS/N3pYgNIMYIBfzCCAXsC AQEwgZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcT CUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2 aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBDyEMAkG BSsOAwIaBQCgfTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0w MTA5MDQxMTQ5NDZaMB4GCSqGSIb3DQEJDzERMA8wDQYIKoZIhvcNAwICASgwIwYJKoZIhvcN AQkEMRYEFOdTigqqhhe10klBwEZBBCVfN674MA0GCSqGSIb3DQEBAQUABEChZnqjeGBBM4rt GbS3swQTXFRLJsqqfL5Fz4n/Vh4+wBhyG5Wy5NWWAGzw8v8IZaSgOVACjVRsHyJWkh3l+irV --------------ms3AAA66B764624A336696086E-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 04:54:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84BsrY17763 for linux-xfs-outgoing; Tue, 4 Sep 2001 04:54:53 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Bsod17744 for ; Tue, 4 Sep 2001 04:54:50 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f84Bsi524529 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 4 Sep 2001 04:54:44 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id NAA875744 for ; Tue, 4 Sep 2001 13:54:44 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id WAA29632; Tue, 4 Sep 2001 22:53:24 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id WAA63648; Tue, 4 Sep 2001 22:53:23 +1100 (AEDT) Date: Tue, 4 Sep 2001 22:53:23 +1100 From: Nathan Scott To: Andi Kleen Cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010904225323.A344731@wobbly.melbourne.sgi.com> References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010904134437.A28205@gruyere.muc.suse.de>; from ak@suse.de on Tue, Sep 04, 2001 at 01:44:37PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Andi, On Tue, Sep 04, 2001 at 01:44:37PM +0200, Andi Kleen wrote: > On Tue, Sep 04, 2001 at 09:39:42PM +1000, Nathan Scott wrote: > > Consensus seems to be less chatty on mount - this should do the trick. > > Can still get at these messages with a debug build (as is the case for > > the nightly QA runs) where these messages are still quite useful. > > I think it would be better to keep them; as it makes debugging even on > production machines easier. > _Now_ you pipe up! Well, I don't think the "finished clean mount" message is particularly useful, but I'll put the initial message back in at the start of a mount, I think, so that in the normal case its just one message per mount. If anyone else really wants the message at the end of a clean mount, I guess I can put that back too... cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 4 05:26:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84CQKt18450 for linux-xfs-outgoing; Tue, 4 Sep 2001 05:26:20 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84CQFd18429 for ; Tue, 4 Sep 2001 05:26:15 -0700 Received: (qmail 28738 invoked from network); 4 Sep 2001 12:26:11 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 4 Sep 2001 12:26:11 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 2ECE8300090; Tue, 4 Sep 2001 22:25:29 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id D0EA39E; Tue, 4 Sep 2001 22:25:29 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Dario Brignardello Cc: "linux-xfs@oss.sgi.com" Subject: Re: Block size. In-reply-to: Your message of "Tue, 04 Sep 2001 08:49:45 -0300." <3B94BFD9.83E09CEE@sinectis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Sep 2001 22:25:24 +1000 Message-ID: <11089.999606324@ocs3.intra.ocs.com.au> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 04 Sep 2001 08:49:45 -0300, Dario Brignardello wrote: > Sorry for bother with a newbie question, but I didn't find the >answer in the FAQ:-). I would like to now the reasons (technically >speaking) for the max block size to be fixed at 4K in linux It is a restriction of the Linux VM subsystem, at the moment file block size must equal hardware page size. There is work in progress to remove the restriction, but it is kernel 2.5 code. From owner-linux-xfs@oss.sgi.com Tue Sep 4 05:32:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84CWPR18661 for linux-xfs-outgoing; Tue, 4 Sep 2001 05:32:25 -0700 Received: from alaska.net (sephiroth.nwc.alaska.net [209.112.130.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84CWLd18640 for ; Tue, 4 Sep 2001 05:32:21 -0700 Received: from erbenson.alaska.net (34-pm21.nwc.alaska.net [209.112.143.34]) by alaska.net (8.11.5/8.11.5) with ESMTP id f84CWIP17773 for ; Tue, 4 Sep 2001 04:32:19 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 4E574397B for ; Tue, 4 Sep 2001 04:32:17 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 7411C10246; Tue, 4 Sep 2001 04:32:17 -0800 (AKDT) Date: Tue, 4 Sep 2001 04:32:17 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010904043217.U14519@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Zd8I2GZVcdxtyaG/" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010904225323.A344731@wobbly.melbourne.sgi.com>; from nathans@sgi.com on Tue, Sep 04, 2001 at 10:53:23PM +1100 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --Zd8I2GZVcdxtyaG/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 04, 2001 at 10:53:23PM +1100, Nathan Scott wrote: > hi Andi, >=20 > On Tue, Sep 04, 2001 at 01:44:37PM +0200, Andi Kleen wrote: > > On Tue, Sep 04, 2001 at 09:39:42PM +1000, Nathan Scott wrote: > > > Consensus seems to be less chatty on mount - this should do the trick. > > > Can still get at these messages with a debug build (as is the case for > > > the nightly QA runs) where these messages are still quite useful. > >=20 > > I think it would be better to keep them; as it makes debugging even on > > production machines easier. > >=20 >=20 > _Now_ you pipe up! Well, I don't think the "finished clean mount" > message is particularly useful, but I'll put the initial message > back in at the start of a mount, I think, so that in the normal case > its just one message per mount. please don't, or make it a compile time option. it makes an ugly mess of boot messages and clutters the logs with really useless data. > If anyone else really wants the message at the end of a clean mount, > I guess I can put that back too... make it a compile time option if some people want it. =20 CONFIG_VERBOSE_MOUNT or something. =20 no news is good news. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --Zd8I2GZVcdxtyaG/ 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 iEYEARECAAYFAjuUydEACgkQJKx7GixEevyG4ACcDH9s1dShiMpC2JTs+w2HPIcC wz8AoJhahpiIdsvbnF9qJvWZ2ZBxTSUO =UPrn -----END PGP SIGNATURE----- --Zd8I2GZVcdxtyaG/-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 05:39:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Cdx218987 for linux-xfs-outgoing; Tue, 4 Sep 2001 05:39:59 -0700 Received: from alaska.net (sephiroth.nwc.alaska.net [209.112.130.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Cdtd18968 for ; Tue, 4 Sep 2001 05:39:56 -0700 Received: from erbenson.alaska.net (34-pm21.nwc.alaska.net [209.112.143.34]) by alaska.net (8.11.5/8.11.5) with ESMTP id f84CdrP18274 for ; Tue, 4 Sep 2001 04:39:54 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 7AB6E397B for ; Tue, 4 Sep 2001 04:39:52 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id BD6FD10246; Tue, 4 Sep 2001 04:39:52 -0800 (AKDT) Date: Tue, 4 Sep 2001 04:39:52 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: smaller mkfs.xfs Message-ID: <20010904043952.V14519@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JaUdphvQ2+4F/M7k" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --JaUdphvQ2+4F/M7k Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Is there any possible ways to reduce the size of the mkfs.xfs binary? =20 I am working on adding support for direct XFS installation to the Debian boot-floppies, but the size of mkfs.xfs is proving to be a real problem (we are already very tight on space as it is). =20 from what i can tell by briefly looking at it, libuuid appears to be statically linked into this binary? is this correct? making this dynamic would help a little (probably not much but i can use every kbyte i can get). also its built with -O1 optimization, is there any reason for this? would -Os be potentially problematic? --=20 Ethan Benson http://www.alaska.net/~erbenson/ --JaUdphvQ2+4F/M7k 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 iEYEARECAAYFAjuUy5gACgkQJKx7GixEevz6swCeJtCYhPgXs6bazyJ3Oe+rYmai uNAAoI70TsNkyOa9epWSB0KzKxo4xaQc =eAD2 -----END PGP SIGNATURE----- --JaUdphvQ2+4F/M7k-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 05:43:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Chh119156 for linux-xfs-outgoing; Tue, 4 Sep 2001 05:43:43 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Chdd19137 for ; Tue, 4 Sep 2001 05:43:40 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 316871E102; Tue, 4 Sep 2001 14:43:34 +0200 (MEST) Date: Tue, 4 Sep 2001 14:43:23 +0200 From: Andi Kleen To: Nathan Scott Cc: Andi Kleen , linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010904144323.B29262@gruyere.muc.suse.de> References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010904225323.A344731@wobbly.melbourne.sgi.com>; from nathans@sgi.com on Tue, Sep 04, 2001 at 10:53:23PM +1100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 04, 2001 at 10:53:23PM +1100, Nathan Scott wrote: > hi Andi, > > On Tue, Sep 04, 2001 at 01:44:37PM +0200, Andi Kleen wrote: > > On Tue, Sep 04, 2001 at 09:39:42PM +1000, Nathan Scott wrote: > > > Consensus seems to be less chatty on mount - this should do the trick. > > > Can still get at these messages with a debug build (as is the case for > > > the nightly QA runs) where these messages are still quite useful. > > > > I think it would be better to keep them; as it makes debugging even on > > production machines easier. > > > > _Now_ you pipe up! Well, I don't think the "finished clean mount" > message is particularly useful, but I'll put the initial message > back in at the start of a mount, I think, so that in the normal case > its just one message per mount. Keeping the initial message only would be fine for me. -Andi From owner-linux-xfs@oss.sgi.com Tue Sep 4 05:46:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Ckd519332 for linux-xfs-outgoing; Tue, 4 Sep 2001 05:46:39 -0700 Received: from mailin3.email.bigpond.com (juicer24.bigpond.com [139.134.6.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84CkZd19310 for ; Tue, 4 Sep 2001 05:46:35 -0700 Received: from HERCULES ([144.135.24.87]) by mailin3.email.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GJ52FP00.IUG for ; Tue, 4 Sep 2001 22:52:37 +1000 Received: from CPE-61-9-143-213.vic.bigpond.net.au ([61.9.143.213]) by bwmam07.mailsvc.email.bigpond.com(MailRouter V2.9i 8347/3792041); 04 Sep 2001 22:52:37 Content-Type: text/plain; charset="iso-8859-1" From: AKH To: linux-xfs@oss.sgi.com Subject: Re: about to try RAID.... Date: Tue, 4 Sep 2001 22:46:25 +1000 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01090422462501.03514@HERCULES> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk If you think getting 3ware controllers are hard in the UK - try getting them in Australia. The only way I got mine was to get it at the Asian distributor in Singapore when I was there on business. I'm in the process of doing exactly the same thing as you. At the moment at work I have 2 server machines running stress/benchmark tests - mongo.pl & bonie++. The tests have only been running for a day but so far the 3ware controller has died on all 3 attempts at mongo.pl (but passes bonnie++), whereas the machine running the 2 Promise TX2 controllers has not missed a beat. I still have quite a few more tests before I put either of them into service but so far it looks good for the Promise controllers. The machine's specs: Machine #1 Athlon 1.333 ASUS A7V-133-C 256M SDRAM 5 IBM 20G (IC35L020AVER07-0 from both Thailand & Philippines from May onwards) 2 Promise TX2 IDE controllers Machine #2 Same as above except the 3ware controller (4 port 6000 series) I did have problems with the Promise TX2 controllers before Kernel 2.4.7 I had to use -ac patches to get the things to run at all. Now I'm using 2.4.9 without -ac patches. However, I have noticed a couple of lines of code difference between the vanilla 2.4.9 and the 2.4.9-ac5 with regards to the Promise driver. (Not sure what the differences really does yet). It appears these days you really have to test your hardware well yourself to be able to sleep soundly at night. Adrian Head From owner-linux-xfs@oss.sgi.com Tue Sep 4 05:48:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84CmBc19496 for linux-xfs-outgoing; Tue, 4 Sep 2001 05:48:11 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Cm8d19477 for ; Tue, 4 Sep 2001 05:48:09 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 463601E101; Tue, 4 Sep 2001 14:48:03 +0200 (MEST) Date: Tue, 4 Sep 2001 14:47:31 +0200 From: Andi Kleen To: Keith Owens Cc: Dario Brignardello , "linux-xfs@oss.sgi.com" Subject: Re: Block size. Message-ID: <20010904144731.A29342@gruyere.muc.suse.de> References: <3B94BFD9.83E09CEE@sinectis.com> <11089.999606324@ocs3.intra.ocs.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <11089.999606324@ocs3.intra.ocs.com.au>; from kaos@melbourne.sgi.com on Tue, Sep 04, 2001 at 10:25:24PM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 04, 2001 at 10:25:24PM +1000, Keith Owens wrote: > On Tue, 04 Sep 2001 08:49:45 -0300, > Dario Brignardello wrote: > > Sorry for bother with a newbie question, but I didn't find the > >answer in the FAQ:-). I would like to now the reasons (technically > >speaking) for the max block size to be fixed at 4K in linux > > It is a restriction of the Linux VM subsystem, at the moment file block > size must equal hardware page size. There is work in progress to > remove the restriction, but it is kernel 2.5 code. Minor correction: it must be smaller or equal hardware block size. -Andi From owner-linux-xfs@oss.sgi.com Tue Sep 4 06:21:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84DLLV20172 for linux-xfs-outgoing; Tue, 4 Sep 2001 06:21:21 -0700 Received: from alaska.net (kitsune.nwc.alaska.net [209.112.130.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84DLId20153 for ; Tue, 4 Sep 2001 06:21:18 -0700 Received: from erbenson.alaska.net (34-pm21.nwc.alaska.net [209.112.143.34]) by alaska.net (8.9.1/8.9.1) with ESMTP id FAA22070 for ; Tue, 4 Sep 2001 05:21:16 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id C6BA1397B for ; Tue, 4 Sep 2001 05:21:13 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id C116610246; Tue, 4 Sep 2001 05:21:13 -0800 (AKDT) Date: Tue, 4 Sep 2001 05:21:13 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010904052113.X14519@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <20010904144323.B29262@gruyere.muc.suse.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PxDrs/Fpf4pPiewX" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010904144323.B29262@gruyere.muc.suse.de>; from ak@suse.de on Tue, Sep 04, 2001 at 02:43:23PM +0200 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --PxDrs/Fpf4pPiewX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 04, 2001 at 02:43:23PM +0200, Andi Kleen wrote: > Keeping the initial message only would be fine for me. why? at least on debian mount is called with -v which prints its own (more informative) mounting message --=20 Ethan Benson http://www.alaska.net/~erbenson/ --PxDrs/Fpf4pPiewX 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 iEYEARECAAYFAjuU1UkACgkQJKx7GixEevyAcACbBujc1WR9O1tSpkhnd8yGE9m0 PGsAniE9YFqEXkMzy7UswHQjZcnhxol7 =RJfH -----END PGP SIGNATURE----- --PxDrs/Fpf4pPiewX-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 06:23:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84DNBV20327 for linux-xfs-outgoing; Tue, 4 Sep 2001 06:23:11 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84DN6d20308 for ; Tue, 4 Sep 2001 06:23:06 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id PAA10370; Tue, 4 Sep 2001 15:23:00 +0200 (CEST) Message-Id: <4.3.2.7.2.20010904152044.035d3b48@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 04 Sep 2001 15:23:12 +0200 To: Ethan Benson , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: TAKE - mount msgs In-Reply-To: <20010904043217.U14519@plato.local.lan> References: <20010904225323.A344731@wobbly.melbourne.sgi.com> <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 04:32 4-9-2001 -0800, Ethan Benson wrote: >On Tue, Sep 04, 2001 at 10:53:23PM +1100, Nathan Scott wrote: > > hi Andi, > >=20 > > On Tue, Sep 04, 2001 at 01:44:37PM +0200, Andi Kleen wrote: > > > On Tue, Sep 04, 2001 at 09:39:42PM +1000, Nathan Scott wrote: > > > > Consensus seems to be less chatty on mount - this should do the trick. > > > > Can still get at these messages with a debug build (as is the case for > > > > the nightly QA runs) where these messages are still quite useful. > > >=20 > > > I think it would be better to keep them; as it makes debugging even on > > > production machines easier. > > >=20 > >=20 > > _Now_ you pipe up! Well, I don't think the "finished clean mount" > > message is particularly useful, but I'll put the initial message > > back in at the start of a mount, I think, so that in the normal case > > its just one message per mount. > >please don't, or make it a compile time option. it makes an ugly mess >of boot messages and clutters the logs with really useless data. > > > If anyone else really wants the message at the end of a clean mount, > > I guess I can put that back too... > >make it a compile time option if some people want it. =20 > >CONFIG_VERBOSE_MOUNT or something. =20 > >no news is good news. I like having at least one message that it mounted a certain fs. I can then use dmesg to see if it actually worked, and if it needs to recover or if it fails I like to see it as well. One line is enough. What I don't know is if you could stick these messages on one line. So the first mounting message without a \n and the succes or fail message after it. Don't know if it lets us do that. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Sep 4 06:31:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84DVQp20589 for linux-xfs-outgoing; Tue, 4 Sep 2001 06:31:26 -0700 Received: from alaska.net (sephiroth.nwc.alaska.net [209.112.130.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84DVLd20569 for ; Tue, 4 Sep 2001 06:31:21 -0700 Received: from erbenson.alaska.net (75-pm18.nwc.alaska.net [209.112.142.75]) by alaska.net (8.11.5/8.11.5) with ESMTP id f84DVJP22019 for ; Tue, 4 Sep 2001 05:31:19 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 083D3397B for ; Tue, 4 Sep 2001 05:31:17 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id B873C10246; Tue, 4 Sep 2001 05:31:17 -0800 (AKDT) Date: Tue, 4 Sep 2001 05:31:17 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010904053117.Y14519@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010904225323.A344731@wobbly.melbourne.sgi.com> <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <20010904043217.U14519@plato.local.lan> <4.3.2.7.2.20010904152044.035d3b48@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SzQ167Kp6Zo0TWVn" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4.3.2.7.2.20010904152044.035d3b48@pop.xs4all.nl>; from knuffie@xs4all.nl on Tue, Sep 04, 2001 at 03:23:12PM +0200 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --SzQ167Kp6Zo0TWVn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 04, 2001 at 03:23:12PM +0200, Seth Mos wrote: > >no news is good news. >=20 > I like having at least one message that it mounted a certain fs. I can th= en=20 > use dmesg to see if it actually worked, and if it needs to recover or if = it=20 > fails I like to see it as well. running mount will also tell you that it worked. =20 as for recovery, i have always said leave the message mentioning that recovery was needed, i want to know that. but if no recovery was needed, and nothing went wrong then nothing should be printed at all. the lack of news is telling me everything was fine. =20 just like rm does not say `Sucessfully unlinked file: /blah' for everything it removes, it only prints something if there was a problem, eg: permission denied, readonly filesystem, or whatever. or in this case: rm: Starting unlink of file: /blah rm: Successfully unlinked file: /blah > One line is enough. What I don't know is if you could stick these message= s=20 zero lines is enough on clean sucessful mounts ;-) > on one line. So the first mounting message without a \n and the succes or= =20 > fail message after it. >=20 > Don't know if it lets us do that. dunno maybe, but i still prefer not to see anything if all went well. so again, a compile time option perhaps? --=20 Ethan Benson http://www.alaska.net/~erbenson/ --SzQ167Kp6Zo0TWVn 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 iEYEARECAAYFAjuU16UACgkQJKx7GixEevyXQQCgodICl1EAEMqo7kWd+67KGFnj ab4An0HA0BV8Isqs2cCf70T2UAJJxJ+v =yKq3 -----END PGP SIGNATURE----- --SzQ167Kp6Zo0TWVn-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 06:53:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84DrLi21075 for linux-xfs-outgoing; Tue, 4 Sep 2001 06:53:21 -0700 Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.133]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84DrGd21055 for ; Tue, 4 Sep 2001 06:53:17 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp7.xs4all.nl (8.9.3/8.9.3) with ESMTP id PAA10778 for ; Tue, 4 Sep 2001 15:53:15 +0200 (CEST) Message-Id: <4.3.2.7.2.20010904155327.035d2a00@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 04 Sep 2001 15:53:33 +0200 To: linux XFS Mailing List From: Seth Mos Subject: Fwd: Re: TAKE - mount msgs Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >X-XS4ALL-To: >X-Sender: blizbor@mail.ima.pl >X-Mailer: QUALCOMM Windows Eudora Version 5.1 >Date: Tue, 04 Sep 2001 15:50:10 +0200 >To: Seth Mos >From: Blizbor >Subject: Re: TAKE - mount msgs > >At 9/4/01 03:23 PM, you wrote: >One line is enough. What I don't know is if you could stick these messages >on one line. So the first mounting message without a \n and the succes or >fail message after it. > > >Don't know if it lets us do that. > >Sep 5 08:52:20 blizbor kernel: Start mounting filesystem: ide0(3,5) >Sep 5 08:55:38 blizbor kernel: Ending clean XFS mount for filesystem: >ide0(3,5) > >hmm ... what you can tell about such a system ? :>>> >Two lines are giving you two timestamps. It gives you chance >to a) measure performance of bad mounts, b) detect any problems. > >Really, I can't find any reason for cutting these lines out. >When you have one, central logs collecting server you have >no reason to login and check if filesystems are mounted. > >I don't know how to translate polish idiom "bicie piany" >but this thread is a big waste of time. >Please leave these lines. Everyone who doesnt like it can >remove them manually when compiling kernel. What a problem ? > >Regards, >Blizbor > >-- > > -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Sep 4 06:56:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84DuBf21277 for linux-xfs-outgoing; Tue, 4 Sep 2001 06:56:11 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Du8d21257 for ; Tue, 4 Sep 2001 06:56:08 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 217731E135; Tue, 4 Sep 2001 15:56:03 +0200 (MEST) Date: Tue, 4 Sep 2001 15:55:55 +0200 From: Andi Kleen To: Ethan Benson Cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010904155555.A30796@gruyere.muc.suse.de> References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <20010904144323.B29262@gruyere.muc.suse.de> <20010904052113.X14519@plato.local.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010904052113.X14519@plato.local.lan>; from erbenson@alaska.net on Tue, Sep 04, 2001 at 05:21:13AM -0800 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 04, 2001 at 05:21:13AM -0800, Ethan Benson wrote: > On Tue, Sep 04, 2001 at 02:43:23PM +0200, Andi Kleen wrote: > > > Keeping the initial message only would be fine for me. > > why? at least on debian mount is called with -v which prints its own > (more informative) mounting message Doesn't help for the root fs. -Andi From owner-linux-xfs@oss.sgi.com Tue Sep 4 07:01:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84E1bO21521 for linux-xfs-outgoing; Tue, 4 Sep 2001 07:01:37 -0700 Received: from alaska.net (kitsune.nwc.alaska.net [209.112.130.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84E1Xd21502 for ; Tue, 4 Sep 2001 07:01:33 -0700 Received: from erbenson.alaska.net (75-pm18.nwc.alaska.net [209.112.142.75]) by alaska.net (8.9.1/8.9.1) with ESMTP id GAA29336 for ; Tue, 4 Sep 2001 06:01:32 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 4D676397B for ; Tue, 4 Sep 2001 06:01:29 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 6C8AF10246; Tue, 4 Sep 2001 06:01:29 -0800 (AKDT) Date: Tue, 4 Sep 2001 06:01:29 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010904060129.A14519@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <20010904144323.B29262@gruyere.muc.suse.de> <20010904052113.X14519@plato.local.lan> <20010904155555.A30796@gruyere.muc.suse.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XeHo0rFSNt4mQX/E" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010904155555.A30796@gruyere.muc.suse.de>; from ak@suse.de on Tue, Sep 04, 2001 at 03:55:55PM +0200 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --XeHo0rFSNt4mQX/E Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 04, 2001 at 03:55:55PM +0200, Andi Kleen wrote: > On Tue, Sep 04, 2001 at 05:21:13AM -0800, Ethan Benson wrote: > > On Tue, Sep 04, 2001 at 02:43:23PM +0200, Andi Kleen wrote: > >=20 > > > Keeping the initial message only would be fine for me. > >=20 > > why? at least on debian mount is called with -v which prints its own > > (more informative) mounting message >=20 > Doesn't help for the root fs. um... if the root filesystem doesn't mount i think your going to notice ;-) --=20 Ethan Benson http://www.alaska.net/~erbenson/ --XeHo0rFSNt4mQX/E 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 iEYEARECAAYFAjuU3rkACgkQJKx7GixEevzN4wCgn9ZivLYBlRWegur5tb43n6zf uAMAnAtCvRbAdPGsmN07G0il2CGFXKPI =7IMG -----END PGP SIGNATURE----- --XeHo0rFSNt4mQX/E-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 07:23:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84ENQZ22128 for linux-xfs-outgoing; Tue, 4 Sep 2001 07:23:26 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84ENNd22107 for ; Tue, 4 Sep 2001 07:23:23 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 148821E140; Tue, 4 Sep 2001 16:23:18 +0200 (MEST) Date: Tue, 4 Sep 2001 16:23:02 +0200 From: Andi Kleen To: Ethan Benson Cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010904162302.A31393@gruyere.muc.suse.de> References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <20010904144323.B29262@gruyere.muc.suse.de> <20010904052113.X14519@plato.local.lan> <20010904155555.A30796@gruyere.muc.suse.de> <20010904060129.A14519@plato.local.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010904060129.A14519@plato.local.lan>; from erbenson@alaska.net on Tue, Sep 04, 2001 at 06:01:29AM -0800 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 04, 2001 at 06:01:29AM -0800, Ethan Benson wrote: > On Tue, Sep 04, 2001 at 03:55:55PM +0200, Andi Kleen wrote: > > On Tue, Sep 04, 2001 at 05:21:13AM -0800, Ethan Benson wrote: > > > On Tue, Sep 04, 2001 at 02:43:23PM +0200, Andi Kleen wrote: > > > > > > > Keeping the initial message only would be fine for me. > > > > > > why? at least on debian mount is called with -v which prints its own > > > (more informative) mounting message > > > > Doesn't help for the root fs. > > um... if the root filesystem doesn't mount i think your going to > notice ;-) The point is that you can quickly blame XFS for it ("it crashed in XFS log replay"). With no message it is a lot harder to find which subsystem to debug. -Andi From owner-linux-xfs@oss.sgi.com Tue Sep 4 07:24:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84EO3f22267 for linux-xfs-outgoing; Tue, 4 Sep 2001 07:24:03 -0700 Received: from cwpads02.ud.com ([207.8.4.212]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84EO1d22248 for ; Tue, 4 Sep 2001 07:24:01 -0700 content-class: urn:content-classes:message Subject: root mount mislabled.. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 4 Sep 2001 09:24:00 -0500 Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: root mount mislabled.. Thread-Index: AcE1TT28Xz+54kXVT+a9RB31pIN72g== From: "Joseph Southwell" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f84EO1d22249 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I am trying to use xfs as my root partition and it is being mislabeled. for instance I installed on /dev/hda3. I setup a smaller partition on dev/hda1 with xfs and booted to that partition. The data and the size of the root partition indicate that /dev/hda1 is mounted as root. however df indicates that /dev/hda3 is mounted as root. Because of this /dev/hda3 is transparent, in other words I can't mount it. This is the second time I have gone through this last time hda3 and hda1 were in opposite corners. I tried deleting the ext2 (at the time /dev/hda1) partition and then I got a bunch of read only filesystem errors during boot to the xfs partition. So this time I removed the read-only from the xfs boot partitions boot clause. It still mislabels them and I am reluctant to take risk destroying my system as it is used for other things and I already had to reinstall it once over this. So, short of trying to delete the existing ext2 partition any ideas on how to get the operating system to see this correctly? Joseph Southwell Solutions Engineer United Devices 512-692-4146 From owner-linux-xfs@oss.sgi.com Tue Sep 4 07:39:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84EdVd22751 for linux-xfs-outgoing; Tue, 4 Sep 2001 07:39:31 -0700 Received: from alaska.net (kitsune.nwc.alaska.net [209.112.130.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84EdRd22732 for ; Tue, 4 Sep 2001 07:39:27 -0700 Received: from erbenson.alaska.net (75-pm18.nwc.alaska.net [209.112.142.75]) by alaska.net (8.9.1/8.9.1) with ESMTP id GAA07575 for ; Tue, 4 Sep 2001 06:39:25 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 33A343924 for ; Tue, 4 Sep 2001 06:39:23 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 1399710246; Tue, 4 Sep 2001 06:39:22 -0800 (AKDT) Date: Tue, 4 Sep 2001 06:39:22 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010904063922.C14519@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <20010904144323.B29262@gruyere.muc.suse.de> <20010904052113.X14519@plato.local.lan> <20010904155555.A30796@gruyere.muc.suse.de> <20010904060129.A14519@plato.local.lan> <20010904162302.A31393@gruyere.muc.suse.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="o5hfEDzsoqw8wJwC" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010904162302.A31393@gruyere.muc.suse.de>; from ak@suse.de on Tue, Sep 04, 2001 at 04:23:02PM +0200 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --o5hfEDzsoqw8wJwC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 04, 2001 at 04:23:02PM +0200, Andi Kleen wrote: >=20 > The point is that you can quickly blame XFS for it ("it crashed in XFS log > replay"). With no message it is a lot harder to find which subsystem to= =20 > debug. so print the messages in debug mode, but not otherwise. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --o5hfEDzsoqw8wJwC 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 iEYEARECAAYFAjuU55oACgkQJKx7GixEevwsqwCdFHirrNenCoVt1rvXyZFN17io EwYAoInxIGOuurHzhmQxhEkfuneWeD5o =JX3A -----END PGP SIGNATURE----- --o5hfEDzsoqw8wJwC-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 08:35:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84FZTA24347 for linux-xfs-outgoing; Tue, 4 Sep 2001 08:35:29 -0700 Received: from ns.caldera.de (ns.caldera.de [212.34.180.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84FZPd24326 for ; Tue, 4 Sep 2001 08:35:26 -0700 Received: (from hch@localhost) by ns.caldera.de (8.11.1/8.11.1) id f84FZD330808; Tue, 4 Sep 2001 17:35:13 +0200 Date: Tue, 4 Sep 2001 17:35:12 +0200 From: Christoph Hellwig To: Simon Matter Cc: Ethan Benson , linux-xfs@oss.sgi.com Subject: Re: kernel spam when mounting xfs Message-ID: <20010904173512.A30319@caldera.de> References: <20010903194537.G14519@plato.local.lan> <3B947A63.F08A1245@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B947A63.F08A1245@ch.sauter-bc.com>; from simon.matter@ch.sauter-bc.com on Tue, Sep 04, 2001 at 08:53:23AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 04, 2001 at 08:53:23AM +0200, Simon Matter wrote: > Is this spam? Did you ever use ReiserFS? At least the sponsorship crap is ripped out in the kernel versions. There are more than enough (technical) reasons not to use reiserfs, though.. Christoph -- Of course it doesn't work. We've performed a software upgrade. From owner-linux-xfs@oss.sgi.com Tue Sep 4 08:38:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Fcjd24555 for linux-xfs-outgoing; Tue, 4 Sep 2001 08:38:45 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Fcbd24535; Tue, 4 Sep 2001 08:38:37 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id 8FF4E6703F; Tue, 4 Sep 2001 17:38:30 +0200 (CEST) To: AKH Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com Subject: Re: about to try RAID.... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Tue, 4 Sep 2001 17:38:30 +0200 X-MIMETrack: S/MIME Sign by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 04.09.2001 17:38:41, Serialize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 04.09.2001 17:38:41, Serialize complete at 04.09.2001 17:38:41, Itemize by Notes Client on Michael Wahlbrink/ITS/Propack Data GmbH(Release 5.0.7 |March 21, 2001) at 04.09.2001 17:38:41, S/MIME Sign complete at 04.09.2001 17:38:41, Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 04.09.2001 17:38:30, Serialize complete at 04.09.2001 17:38:30 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary=-------z14971_boundary_sign Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is an S/MIME signed message. ---------z14971_boundary_sign Content-Type: text/plain; charset="us-ascii" On 04.09.2001 14:46:25 AKH wrote: >If you think getting 3ware controllers are hard in the UK - try getting >them >in Australia. The only way I got mine was to get it at the Asian >distributor >in Singapore when I was there on business. > >I'm in the process of doing exactly the same thing as you. At the >moment at >work I have 2 server machines running stress/benchmark tests - mongo.pl how do you get mongo.pl working with xfs? >& >bonie++. The tests have only been running for a day but so far the >3ware >controller has died on all 3 attempts at mongo.pl (but passes bonnie++), >whereas the machine running the 2 Promise TX2 controllers has not >missed a >beat. I still have quite a few more tests before I put either of them >into >service but so far it looks good for the Promise controllers. > cu micha ---------z14971_boundary_sign Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAA oIAwggM/MIICJ6ADAgECAgQ7lLsBMA0GCSqGSIb3DQEBBAUAMIGcMQswCQYDVQQG EwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1iZXJnMRIwEAYDVQQHEwlLYXJs c3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBHbWJIMR4wHAYDVQQLExVDZXJ0 aWZpY2F0ZSBBdXRob3JpdHkxIDAeBgNVBAMTF1Byb3BhY2sgRGF0YSBDbGFzcyAx IENBMB4XDTAxMDkwMzAwMDAwMFoXDTAyMDYxODIzNTkwMFowgakxCzAJBgNVBAYT AkRFMRswGQYDVQQIExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxz cnVoZTEaMBgGA1UEChMRUHJvcGFjayBEYXRhIEdtYkgxDDAKBgNVBAsTA0lUUzEa MBgGA1UEAxMRTWljaGFlbCBXYWhsYnJpbmsxIzAhBgkqhkiG9w0BCQEWFG1pd0Bw cm9wYWNrLWRhdGEuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDRl70z rpIxvQtPawUDEEnQAEzkk8bad/BK6SQf1H5T8yujxbJb/f8edTx4rnAWE2r0RsNy NpQAdgAOBkJ2P599bb+iuGXDxncqQUx47AzLj7RV6Kph8iVWOFb+5yuLDsPcU03w T7eAHWU9qWj9NOR/vNT3Rt7vff85eNwFLWetNQIDAQABMA0GCSqGSIb3DQEBBAUA A4IBAQBUgk869M22A4nFoZ2FP4VktmkMH8FddO5pjdjQuRl1gGQb/ds4dsz82Q2f B9YRqFlQg1kZ6nEExxONyL7UUqbTJm/s17KONrae6jxktm2N55r7CRGbhRCJMLFE II3sa3Ttn1rK1UU/Cg0SVIcdQPVHcVTZwH93Zib/wQdaztfLJEa/6TUR/HU7Gc6z n9t4wDZaAWOEHnHtDfHLfH9COJxqljtBd8vJb8oQGu2mQ3YzvT292AQ6YjF4GAt/ cXFteP/zqjqLT0w81p/oOdyBhJZ+YGRavEpy8fKszzKU/AExqa4LKYJGDnATGVCO qtHOFs6eICDSu6ZpfDI5c/EhNxMOMIIDtjCCAp6gAwIBAgIEOU3ehzANBgkqhkiG 9w0BAQQFADCBnDELMAkGA1UEBhMCZGUxGzAZBgNVBAgTEkJhZGVuLVd1ZXJ0dGVt YmVyZzESMBAGA1UEBxMJS2FybHNydWhlMRowGAYDVQQKExFQcm9wYWNrIERhdGEg R21iSDEeMBwGA1UECxMVQ2VydGlmaWNhdGUgQXV0aG9yaXR5MSAwHgYDVQQDExdQ cm9wYWNrIERhdGEgQ2xhc3MgMSBDQTAeFw0wMDA2MTgwMDAwMDBaFw0wMjA2MTgy MzU5MDBaMIGcMQswCQYDVQQGEwJkZTEbMBkGA1UECBMSQmFkZW4tV3VlcnR0ZW1i ZXJnMRIwEAYDVQQHEwlLYXJsc3J1aGUxGjAYBgNVBAoTEVByb3BhY2sgRGF0YSBH bWJIMR4wHAYDVQQLExVDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxIDAeBgNVBAMTF1By b3BhY2sgRGF0YSBDbGFzcyAxIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB CgKCAQEApHbliMdXSZ4eYlfV+EE7A0e1htSUHt+wLFfFUXAoYA7Bp1A6FkYLI1Vl JBNE4fpXYtrFg9CP3LPrB1aXCxX2YYWza2joyW1DOvkPoE9uTSvyYbXMkENtz/5L Csn5xeJAihd6BoTSzWPUJnzbWSEuuV7O+6fP88E6Y01hVbEUCD9W6GeB3kCJbVD4 FP42ZicaksYLp7IctzoaDzHWRXL5oiqtPT6ujwMCrICNRnh4/qOe+tDHAdwI1+xq eDRjyp97gEG7XmkRs/JwSU5ABM1EQ6kAdNItVmO1w79UKL3KvcRreQiXSMKPCRVX VLAtntixr828a3s2uHW6HZ3Tq7Xb3QIDAQABMA0GCSqGSIb3DQEBBAUAA4IBAQB2 L3hFYcBp8Q+m5K1YtuEsDCQ6t3SZtu0nx+Wh2jXGYO1h23ABIWa60HK7tEVD5VdZ kdEZM1k84nHF9IS2vsf1JwQqY8dnUrDkVIGZcas3DxClqvx5iH2QMT8+lqSY9Kgq CtitD8ATsVncTm7QuC/9MPQybHPR1nDG3kqn4MGnmFIIEj+oDen1w8F9usqvK+1Q V/5WYmBBkEiOHhJsxovK6z6zzKFca9qF0/FO2WnvwGDdDgfQAdqz300C1vxHnmLW N8tWvkW63wRXuQrngc69m4dgAgwQR0Uh8aEh///0bkxFi6CvJD0k/p+sPOSATIB2 cIm/tERxeKmxPqAQuTKXAAAxgDCCAfYCAQEwgaUwgZwxCzAJBgNVBAYTAmRlMRsw GQYDVQQIExJCYWRlbi1XdWVydHRlbWJlcmcxEjAQBgNVBAcTCUthcmxzcnVoZTEa MBgGA1UEChMRUHJvcGFjayBEYXRhIEdtYkgxHjAcBgNVBAsTFUNlcnRpZmljYXRl IEF1dGhvcml0eTEgMB4GA1UEAxMXUHJvcGFjayBEYXRhIENsYXNzIDEgQ0ECBDuU uwEwCQYFKw4DAhoFAKCBqzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqG SIb3DQEJBTEPFw0wMTA5MDQxNTM4NDFaMCMGCSqGSIb3DQEJBDEWBBQjmtiGSlsT 9LsfoyIyB06y/r3ssTBMBgkqhkiG9w0BCQ8xPzA9MAcGBSsOAwIdMA4GCCqGSIb3 DQMCAgIAgDAKBggqhkiG9w0DBzAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkq hkiG9w0BAQEFAASBgMa8DnXtWtHOt0D4c5aHcld9Y0ioAwtbRVWjkdPiscGhxhwv 5jr2LX6BCA2NFMQ0L1SxuSlcQIY4KXT++ejPRyYNK4B7NcNM3ECluAkUJHCVbf1j 7KCJyvWJj/QckOJ5PGAG3Cf2ihzjvR8ZFfJ7a7jn6+Sk+HmXPKFFooQL6TRlAAAA AAAAAAA= ---------z14971_boundary_sign-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 08:39:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Fdo124714 for linux-xfs-outgoing; Tue, 4 Sep 2001 08:39:50 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Fdld24671 for ; Tue, 4 Sep 2001 08:39:47 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id IAA09266 for ; Tue, 4 Sep 2001 08:38:10 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id KAA54315; Tue, 4 Sep 2001 10:38:29 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.32 #1 (Debian)) id 15eIHV-0000RR-00; Tue, 04 Sep 2001 10:38:29 -0500 Date: Tue, 4 Sep 2001 10:38:29 -0500 From: Nathan Straz To: Joseph Southwell Cc: linux-xfs@oss.sgi.com Subject: Re: root mount mislabled.. Message-ID: <20010904103828.A726@sgi.com> Mail-Followup-To: Joseph Southwell , linux-xfs@oss.sgi.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 04, 2001 at 09:24:00AM -0500, Joseph Southwell wrote: > I am trying to use xfs as my root partition and it is being > mislabeled. for instance I installed on /dev/hda3. I setup a smaller > partition on dev/hda1 with xfs and booted to that partition. The data > and the size of the root partition indicate that /dev/hda1 is mounted as > root. however df indicates that /dev/hda3 is mounted as root. There are two mounted partitions tables, /etc/mtab and /proc/mounts. /proc/mounts is what the kernel uses and is always correct. /etc/mtab is the user space table and can be wrong. This usually happens if you pass a "root=" option to the kernel that differs from what's in /etc/fstab. If /proc/mounts has /dev/root use /usr/sbin/rdev to find out what your real root partition is. Sometimes is do a `cat /proc/mounts > /etc/mtab` if the differences get in my way, but I don't know how safe that is. -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Tue Sep 4 08:39:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84FdqZ24734 for linux-xfs-outgoing; Tue, 4 Sep 2001 08:39:52 -0700 Received: from mailfast.internal.ima.pl (ip222ds.ima.pl [62.89.65.222]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Fdhd24668 for ; Tue, 4 Sep 2001 08:39:44 -0700 Received: from mailhub.internal.ima.pl by mailfast.internal.ima.pl with ESMTP id f84FdUh12914 for ; Tue, 4 Sep 2001 17:39:30 +0200 Received: from mail.ima.pl by mailhub.internal.ima.pl with ESMTP id f84FdTR12909 for ; Tue, 4 Sep 2001 17:39:29 +0200 Received: from blizbor.ima.pl (jurek.primark.gdansk.tpnet.pl [195.117.150.37]) by mail.ima.pl with ESMTP id f84FdTV00685 for ; Tue, 4 Sep 2001 17:39:29 +0200 Message-Id: <5.1.0.14.0.20010904173732.01f17cc0@mail.ima.pl> X-Sender: blizbor@mail.ima.pl X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 04 Sep 2001 17:43:57 +0200 To: linux-xfs@oss.sgi.com From: Blizbor Subject: Re: TAKE - mount msgs In-Reply-To: <20010904063922.C14519@plato.local.lan> References: <20010904162302.A31393@gruyere.muc.suse.de> <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <20010904144323.B29262@gruyere.muc.suse.de> <20010904052113.X14519@plato.local.lan> <20010904155555.A30796@gruyere.muc.suse.de> <20010904060129.A14519@plato.local.lan> <20010904162302.A31393@gruyere.muc.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 9/4/01 04:39 PM, Ethan Benson wrote: >On Tue, Sep 04, 2001 at 04:23:02PM +0200, Andi Kleen wrote: >> >> The point is that you can quickly blame XFS for it ("it crashed in XFS log >> replay"). With no message it is a lot harder to find which subsystem to >> debug. > >so print the messages in debug mode, but not otherwise. Ethan, so what next ? pppd authors ? ethernet drivers authors ? maybe guys doing scsi ? What should be changed next to produce less initial output ? Please, don't be silly. When you are managing network you NEED those messages. Two lines less or more when you are taking megabytes of logs daily really doesn't matter. There are grep, sed or so other more or less advanced tools to cut something from logs, but none of them could add something in the case of problems. If they are not necessary for you, remove them itself for your own usage. It's the OpenSource power - change to feet your needs. Regards, Blizbor From owner-linux-xfs@oss.sgi.com Tue Sep 4 08:42:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Fgsf25027 for linux-xfs-outgoing; Tue, 4 Sep 2001 08:42:54 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Fgqd25008 for ; Tue, 4 Sep 2001 08:42:52 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f84Fgk515792 for ; Tue, 4 Sep 2001 08:42:46 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2884109; Tue, 4 Sep 2001 10:41:31 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA92168; Tue, 4 Sep 2001 10:41:30 -0500 (CDT) Message-ID: <3B94F5D7.C4E4CD75@sgi.com> Date: Tue, 04 Sep 2001 10:40:07 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: monkeyiq CC: Nathan Scott , linux-xfs@oss.sgi.com Subject: Re: Preallocation of space References: <200109030908.f83988S26342@monkeyiq.dnsalias.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk monkeyiq wrote: > I've found this page which I'll use as my reference to syssgi() > unless there is a better online version. > http://reality.sgi.com/cgi-bin/getman?syssgi-2#toc1 If you want to use it as a reference, save it locally... reality *might* going away... :( -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Tue Sep 4 08:44:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84FiDf25170 for linux-xfs-outgoing; Tue, 4 Sep 2001 08:44:13 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Fi9d25151 for ; Tue, 4 Sep 2001 08:44:09 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id RAA10170; Tue, 4 Sep 2001 17:44:07 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id RAA12071; Tue, 4 Sep 2001 17:44:06 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 82B6057306; Tue, 4 Sep 2001 17:43:42 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 4183A25835; Tue, 4 Sep 2001 17:43:42 +0200 (CEST) Message-ID: <3B94F6AE.F516522@ch.sauter-bc.com> Date: Tue, 04 Sep 2001 17:43:42 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Andi Kleen Cc: Ethan Benson , linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <20010904144323.B29262@gruyere.muc.suse.de> <20010904052113.X14519@plato.local.lan> <20010904155555.A30796@gruyere.muc.suse.de> <20010904060129.A14519@plato.local.lan> <20010904162302.A31393@gruyere.muc.suse.de> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Andi Kleen schrieb: > > On Tue, Sep 04, 2001 at 06:01:29AM -0800, Ethan Benson wrote: > > On Tue, Sep 04, 2001 at 03:55:55PM +0200, Andi Kleen wrote: > > > On Tue, Sep 04, 2001 at 05:21:13AM -0800, Ethan Benson wrote: > > > > On Tue, Sep 04, 2001 at 02:43:23PM +0200, Andi Kleen wrote: > > > > > > > > > Keeping the initial message only would be fine for me. > > > > > > > > why? at least on debian mount is called with -v which prints its own > > > > (more informative) mounting message > > > > > > Doesn't help for the root fs. > > > > um... if the root filesystem doesn't mount i think your going to > > notice ;-) > > The point is that you can quickly blame XFS for it ("it crashed in XFS log > replay"). With no message it is a lot harder to find which subsystem to > debug. I agree with this. Anyway it's a really good sign for XFS. If we don't have more important stuff to discuss here it means that XFS is _really_ good. I know it is very good but... -Simon From owner-linux-xfs@oss.sgi.com Tue Sep 4 08:48:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84FmUk25424 for linux-xfs-outgoing; Tue, 4 Sep 2001 08:48:30 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84FmRd25403 for ; Tue, 4 Sep 2001 08:48:27 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f84FmLJ08531 for ; Tue, 4 Sep 2001 08:48:21 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2885324; Tue, 4 Sep 2001 10:47:06 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA03924; Tue, 4 Sep 2001 10:47:05 -0500 (CDT) Message-ID: <3B94F726.E978C299@sgi.com> Date: Tue, 04 Sep 2001 10:45:42 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: "Gonyou, Austin" CC: "'Seth Mos'" , XFS mailing list Subject: Re: System lock while accessing files causes file corruption References: <85063BBE668FD411944400D0B744267A888526@AUSMAIL> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Gonyou, Austin" wrote: > > That's all well and good..but what about the configuration files? They are > text and are not redundant in the same way. In my spare time (!) I'm working on characterizing how long it takes a write to get out to disk on average, it seem to be on the order of 30 seconds, with normal mount options (this should be ~ the same as with ext2, for example). This is what I would expect based on bdflush, etc, but some people's experience suggests that it's taking longer, this is really something I want to feel sure of. But in any case, it occurred to me that you could make /etc on it's own partition, and mount that O_SYNC - I don't think that would be too much overhead, /etc doesn't get written that much on a normal system (?). If Oracle puts config files elsewhere, you could simlink them onto this filesystem. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Tue Sep 4 08:58:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84FwcW25783 for linux-xfs-outgoing; Tue, 4 Sep 2001 08:58:38 -0700 Received: from zeta.qmw.ac.uk (zeta.qmw.ac.uk [138.37.6.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Fwad25764 for ; Tue, 4 Sep 2001 08:58:36 -0700 Received: from heppcl.ph.qmw.ac.uk ([138.37.50.187]) by zeta.qmw.ac.uk with esmtp (Exim 3.16 #1) id 15eIaw-0000Mr-00; Tue, 04 Sep 2001 16:58:34 +0100 Received: from heppct.ph.qmw.ac.uk (heppct.ph.qmw.ac.uk [138.37.50.246]) by heppcl.ph.qmw.ac.uk (8.9.3/8.9.3) with ESMTP id QAA08704; Tue, 4 Sep 2001 16:58:34 +0100 Received: from localhost (pd@localhost) by heppct.ph.qmw.ac.uk (8.11.2/8.9.3) with ESMTP id f84FwYj27352; Tue, 4 Sep 2001 16:58:34 +0100 X-Authentication-Warning: heppct.ph.qmw.ac.uk: pd owned process doing -bs Date: Tue, 4 Sep 2001 16:58:34 +0100 (BST) From: "P.Dixon" To: Michael Wahlbrink cc: Subject: Re: about to try RAID.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > If you think getting 3ware controllers are hard in the UK - try > getting them in Australia. The only way I got mine was to get it at > the Asian distributor in Singapore when I was there on business. > For anyone who's interested, I just ordered the 3Ware Escalade 6800 (8 port) card and 8 24" cables for the grand total of 400 UK pounds from TMC-UK - www.tmc-uk.com (sent them an email and got a reply back within minutes). This is approx $640(US) - if I bought from www.hypermicro.com, it would cost me just $309(US) or 193 UK pounds. Another example off Rip Off Britain. Right, I need to read up on LVM... Cheerio, Paul From owner-linux-xfs@oss.sgi.com Tue Sep 4 09:22:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84GMmh26348 for linux-xfs-outgoing; Tue, 4 Sep 2001 09:22:48 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84GMjd26329 for ; Tue, 4 Sep 2001 09:22:45 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id JAA00204 for ; Tue, 4 Sep 2001 09:21:08 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2634880; Tue, 4 Sep 2001 11:20:14 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA23283; Tue, 4 Sep 2001 11:20:12 -0500 (CDT) Message-ID: <3B94FEE8.F29DA88B@sgi.com> Date: Tue, 04 Sep 2001 11:18:48 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Paul Schutte CC: Seth Mos , XFS mailing list Subject: Re: Kernel hangs with mongo.pl benchmark. References: <3B929996.FFC809B9@it.up.ac.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Paul Schutte wrote: > > > > > > > > Hi, > > > > > > > > I found a problem while doing benchmarks with mongo.pl > I Think this is a SCSI thing. > I just ran it on a BusLogic card. > I saw the same sympthoms: only bdflush running. Hm, apparently the "reserved buffer head pool" change I put in is possibly the culprit.... you guys could either try backing that out or wait for me to figure out what went wrong... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Tue Sep 4 09:33:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84GXgn26665 for linux-xfs-outgoing; Tue, 4 Sep 2001 09:33:42 -0700 Received: from moutvdom01.kundenserver.de (moutvdom01.kundenserver.de [195.20.224.200]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84GXdd26612 for ; Tue, 4 Sep 2001 09:33:39 -0700 Received: from [195.20.224.208] (helo=mrvdom01.schlund.de) by moutvdom01.kundenserver.de with esmtp (Exim 2.12 #2) id 15eJ8r-00003M-00; Tue, 4 Sep 2001 18:33:37 +0200 Received: from pd901e253.dip.t-dialin.net ([217.1.226.83] helo=kernelpanix.aura.of.mankind) by mrvdom01.schlund.de with esmtp (Exim 2.12 #2) id 15eJ8r-0002m1-00; Tue, 4 Sep 2001 18:33:37 +0200 Received: (from utz@localhost) by kernelpanix.aura.of.mankind (8.11.2/8.11.2) id f84FvsN14161; Tue, 4 Sep 2001 17:57:54 +0200 X-Authentication-Warning: kernelpanix.aura.of.mankind: utz set sender to xfs@s2y4n2c.de using -f Date: Tue, 4 Sep 2001 17:57:54 +0200 From: utz lehmann To: Eric Sandeen Cc: "Gonyou, Austin" , "'Seth Mos'" , XFS mailing list Subject: Re: System lock while accessing files causes file corruption Message-ID: <20010904175754.A14064@s2y4n2c.de> References: <85063BBE668FD411944400D0B744267A888526@AUSMAIL> <3B94F726.E978C299@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: <3B94F726.E978C299@sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Eric Eric Sandeen [sandeen@sgi.com] wrote: > But in any case, it occurred to me that you could make /etc on it's own > partition, and mount that O_SYNC - I don't think that would be too much > overhead, /etc doesn't get written that much on a normal system (?). If > Oracle puts config files elsewhere, you could simlink them onto this > filesystem. You can't make /etc on a different partition than /. /etc, /sbin, /dev (without devfs) must on the / partition otherwise your system will not boot. utz From owner-linux-xfs@oss.sgi.com Tue Sep 4 09:33:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84GXdh26601 for linux-xfs-outgoing; Tue, 4 Sep 2001 09:33:39 -0700 Received: from cwpads02.ud.com ([207.8.4.212]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84GXZd26581 for ; Tue, 4 Sep 2001 09:33:35 -0700 content-class: urn:content-classes:message Subject: RE: root mount mislabled.. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 4 Sep 2001 11:33:35 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: root mount mislabled.. Thread-Index: AcE1XbgTt0SMQRyWThO9J3pvJQaYXwAARYkA From: "Joseph Southwell" To: "Nathan Straz" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f84GXad26582 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk mtab is being populated by calling mount -f. Root is set to LABEL=/ in /etc/fstab, if I change it to /dev/hda1 I get stopped during boot up because fsck tries to run and determines that the partition isn't ext2. I went into the single user shell it gave me there and df/mount are still disagreeing with rdev so that broke something and didn't solve the problem. Any other ideas? -----Original Message----- From: Nathan Straz [mailto:nstraz@sgi.com] Sent: Tuesday, September 04, 2001 11:22 AM To: Joseph Southwell Subject: Re: root mount mislabled.. On Tue, Sep 04, 2001 at 11:09:07AM -0500, Joseph Southwell wrote: > /proc/mounts says /dev/root > rdev says /dev/hda1. which is what I expected because I can tell that > one is mounted. > root=/dev/hda1 in the lilo.conf file for this boot image. > I tried correcting the mtab as you suggested, that change does not > survive a boot. Any other thoughts? Update your /etc/fstab to use /dev/hda1 as your root since that's what you're doing anyway. I think most of the rc.sysinit scripts I've seen rewrite /etc/mtab using /etc/fstab during boot. It has to do with mount wanting to update /etc/mtab while / is still read-only, so rc.sysinit fakes it after / is mounted read-write. -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Tue Sep 4 09:37:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Gb2G26882 for linux-xfs-outgoing; Tue, 4 Sep 2001 09:37:02 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Gb0d26863 for ; Tue, 4 Sep 2001 09:37:00 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id JAA09394 for ; Tue, 4 Sep 2001 09:35:23 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id LAA57267; Tue, 4 Sep 2001 11:35:42 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.32 #1 (Debian)) id 15eJAs-0000Zf-00; Tue, 04 Sep 2001 11:35:42 -0500 Date: Tue, 4 Sep 2001 11:35:42 -0500 From: Nathan Straz To: Joseph Southwell Cc: linux-xfs@oss.sgi.com Subject: Re: root mount mislabled.. Message-ID: <20010904113541.C726@sgi.com> Mail-Followup-To: Joseph Southwell , linux-xfs@oss.sgi.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 04, 2001 at 11:33:35AM -0500, Joseph Southwell wrote: > mtab is being populated by calling mount -f. Root is set to LABEL=/ in > /etc/fstab, if I change it to /dev/hda1 I get stopped during boot up > because fsck tries to run and determines that the partition isn't ext2. > I went into the single user shell it gave me there and df/mount are > still disagreeing with rdev so that broke something and didn't solve the > problem. Any other ideas? Did you change the file system type in /etc/fstab? Maybe we need to see a copy of your /etc/fstab, just two double check. -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Tue Sep 4 09:41:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Gfr427070 for linux-xfs-outgoing; Tue, 4 Sep 2001 09:41:53 -0700 Received: from cwpads02.ud.com ([207.8.4.212]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Gfod27050 for ; Tue, 4 Sep 2001 09:41:50 -0700 content-class: urn:content-classes:message Subject: RE: root mount mislabled.. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 4 Sep 2001 11:41:50 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: root mount mislabled.. Thread-Index: AcE1X6UYyut/Ldu/QkqAXyoWb3acLwAAMBxw From: "Joseph Southwell" To: "Nathan Straz" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f84Gfpd27051 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The filesystem type was the problem. Thank for your patience. -----Original Message----- From: Nathan Straz [mailto:nstraz@sgi.com] Sent: Tuesday, September 04, 2001 11:36 AM To: Joseph Southwell Cc: linux-xfs@oss.sgi.com Subject: Re: root mount mislabled.. On Tue, Sep 04, 2001 at 11:33:35AM -0500, Joseph Southwell wrote: > mtab is being populated by calling mount -f. Root is set to LABEL=/ in > /etc/fstab, if I change it to /dev/hda1 I get stopped during boot up > because fsck tries to run and determines that the partition isn't ext2. > I went into the single user shell it gave me there and df/mount are > still disagreeing with rdev so that broke something and didn't solve the > problem. Any other ideas? Did you change the file system type in /etc/fstab? Maybe we need to see a copy of your /etc/fstab, just two double check. -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Tue Sep 4 10:34:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84HYBt28053 for linux-xfs-outgoing; Tue, 4 Sep 2001 10:34:11 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84HY7d28034 for ; Tue, 4 Sep 2001 10:34:07 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id TAA20627; Tue, 4 Sep 2001 19:33:32 +0200 (CEST) Message-Id: <4.3.2.7.2.20010904193203.032499a0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 04 Sep 2001 19:33:49 +0200 To: utz lehmann , Eric Sandeen From: Seth Mos Subject: Re: System lock while accessing files causes file corruption Cc: "Gonyou, Austin" , XFS mailing list In-Reply-To: <20010904175754.A14064@s2y4n2c.de> References: <3B94F726.E978C299@sgi.com> <85063BBE668FD411944400D0B744267A888526@AUSMAIL> <3B94F726.E978C299@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:57 4-9-2001 +0200, utz lehmann wrote: >Hi Eric > >Eric Sandeen [sandeen@sgi.com] wrote: > > But in any case, it occurred to me that you could make /etc on it's own > > partition, and mount that O_SYNC - I don't think that would be too much > > overhead, /etc doesn't get written that much on a normal system (?). If > > Oracle puts config files elsewhere, you could simlink them onto this > > filesystem. > >You can't make /etc on a different partition than /. >/etc, /sbin, /dev (without devfs) must on the / partition otherwise your >system will not boot. If you use a decent layout fopr your data it does not matter. If you have a separate /usr /var /tmp /home like most servers do you could just mount your / fs O_SYNC since it would only have a _very_ slight performance loss since you almost never write to the root fs. :-) Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Sep 4 10:53:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84HrXo28606 for linux-xfs-outgoing; Tue, 4 Sep 2001 10:53:33 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84HrUd28587 for ; Tue, 4 Sep 2001 10:53:30 -0700 Received: from scare ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta16/8.12.0.Beta16) with ESMTP id f84HrLXi091451; Tue, 4 Sep 2001 12:53:22 -0500 (CDT) Subject: Re: TAKE - mount msgs From: Russell Cattelan To: Andi Kleen Cc: Ethan Benson , linux-xfs@oss.sgi.com In-Reply-To: <20010904162302.A31393@gruyere.muc.suse.de> References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <20010904144323.B29262@gruyere.muc.suse.de> <20010904052113.X14519@plato.local.lan> <20010904155555.A30796@gruyere.muc.suse.de> <20010904060129.A14519@plato.local.lan> <20010904162302.A31393@gruyere.muc.suse.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 04 Sep 2001 12:46:33 -0500 Message-Id: <999625595.30969.4.camel@scare> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 04 Sep 2001 16:23:02 +0200, Andi Kleen wrote: > On Tue, Sep 04, 2001 at 06:01:29AM -0800, Ethan Benson wrote: > > On Tue, Sep 04, 2001 at 03:55:55PM +0200, Andi Kleen wrote: > > > On Tue, Sep 04, 2001 at 05:21:13AM -0800, Ethan Benson wrote: > > > > On Tue, Sep 04, 2001 at 02:43:23PM +0200, Andi Kleen wrote: > > > > > > > > > Keeping the initial message only would be fine for me. > > > > > > > > why? at least on debian mount is called with -v which prints its own > > > > (more informative) mounting message > > > > > > Doesn't help for the root fs. > > > > um... if the root filesystem doesn't mount i think your going to > > notice ;-) > > The point is that you can quickly blame XFS for it ("it crashed in XFS log > replay"). With no message it is a lot harder to find which subsystem to > debug. Yes... I agree, having a the mount message is very helpful especially when loading xfs as a module... I vote for leaving the message in ... maybe shrink it to one line if people really thinks it's "cluttering" up the log to much. > > > -Andi From owner-linux-xfs@oss.sgi.com Tue Sep 4 10:56:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84Huwu28802 for linux-xfs-outgoing; Tue, 4 Sep 2001 10:56:58 -0700 Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84Husd28782 for ; Tue, 4 Sep 2001 10:56:54 -0700 Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 15eKRP-000Jl8-0W for linux-xfs@oss.sgi.com; Tue, 4 Sep 2001 18:56:51 +0100 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id 8E4D027EF for ; Tue, 4 Sep 2001 18:56:49 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id BBF8B125E6; Tue, 4 Sep 2001 18:56:46 +0100 (BST) Date: Tue, 4 Sep 2001 18:56:46 +0100 (BST) From: Keith Matthews Subject: Re[2]: System lock while accessing files causes file corruption To: linux-xfs@oss.sgi.com In-Reply-To: <4.3.2.7.2.20010904193203.032499a0@pop.xs4all.nl> References: <3B94F726.E978C299@sgi.com> <85063BBE668FD411944400D0B744267A888526@AUSMAIL> <3B94F726.E978C299@sgi.com>, <4.3.2.7.2.20010904193203.032499a0@pop.xs4all.nl> X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010904175646.BBF8B125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f84Hutd28783 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 04 Sep 2001 19:33:49 +0200 Seth Mos > wrote: > At 17:57 4-9-2001 +0200, utz lehmann wrote: > >Hi Eric > > > >Eric Sandeen [sandeen@sgi.com] wrote: > > > But in any case, it occurred to me that you could make /etc on it's own > > > partition, and mount that O_SYNC - I don't think that would be too much > > > overhead, /etc doesn't get written that much on a normal system (?). If > > > Oracle puts config files elsewhere, you could simlink them onto this > > > filesystem. > > > >You can't make /etc on a different partition than /. > >/etc, /sbin, /dev (without devfs) must on the / partition otherwise your > >system will not boot. > If you use a decent layout fopr your data it does not matter. > If you have a separate /usr /var /tmp /home like most servers do you could > just mount your / fs O_SYNC since it would only have a _very_ slight > performance loss since you almost never write to the root fs. :-) If you use Oracle's recommended layout you have (at least ) 4 top level mount points. It does not use OS config directories for its config for good reasons - you may want to have more than one database instance on a host. Well designed layouts for database files should have no problems with special control. Its better to have synced writes for the data files anyway as the DBMS does its own caching. -- Keith Matthews Spam trap - my real account at this node is keith_m Frequentous Consultants - Linux Services, Oracle development & database administration From owner-linux-xfs@oss.sgi.com Tue Sep 4 12:27:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84JRbs30434 for linux-xfs-outgoing; Tue, 4 Sep 2001 12:27:37 -0700 Received: from adriano.agestado.com.br (avantesma.oesp.com.br [200.196.192.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84JRQd30406 for ; Tue, 4 Sep 2001 12:27:27 -0700 Received: (qmail 1606 invoked by uid 666); 4 Sep 2001 19:27:14 -0000 Date: Tue, 4 Sep 2001 16:27:14 -0300 From: Adriano Nagelschmidt Rodrigues To: linux-xfs@oss.sgi.com Subject: Re: kernel spam when mounting xfs Message-ID: <20010904162714.A1567@agestado.com.br> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Christoph Hellwig writes: > At least the sponsorship crap is ripped out in the kernel versions. > There are more than enough (technical) reasons not to use reiserfs, > though.. Ok, I'll bite, I use ReiserFS and I'm new to this list. What are the technical reasons not to use ReiserFS? Thanks, -- Adriano From owner-linux-xfs@oss.sgi.com Tue Sep 4 13:41:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84KfJ232023 for linux-xfs-outgoing; Tue, 4 Sep 2001 13:41:19 -0700 Received: from imapserverb.fnal.gov (imapserverb.fnal.gov [131.225.9.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84KfDd32003 for ; Tue, 4 Sep 2001 13:41:14 -0700 Received: from imapserverb.fnal.gov ([131.225.9.17]) by imapserverb.fnal.gov (Netscape Messaging Server 4.15) with SMTP id GJ5O4O00.402 for ; Tue, 4 Sep 2001 15:41:12 -0500 Received: from fnal.gov ([131.225.7.82]) by imapserverb.fnal.gov (NAVIEG 2.1 bld 63) with SMTP id M2001090415411115294 ; Tue, 04 Sep 2001 15:41:11 -0500 Message-ID: <3B953C69.BBACF47@fnal.gov> Date: Tue, 04 Sep 2001 15:41:13 -0500 From: yocum@fnal.gov X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Federico Sevilla III CC: "Philippine Linux Users' Group Mailing List" , Linux XFS Mailing List Subject: Re: Playing around with NFS+XFS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jijo, Federico Sevilla III wrote: > Version 1.01d ------Sequential Output------ --Sequential Input---Rando > -Per Chr- --Block-- -Rewrite- -Per Chr- --Block----Seeks > Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec % > Gusi-NFS-XFS 1G 4200 82 5937 7 1988 4 4037 76 10512 9 120.3 >>-------------------------------^^^^ That's the best you'll get out of your 3ware 6400 card under RAID5, so your bottleneck is the card, not the network, here. :-( If you want good performance out of a 3ware card, use RAID 1 or 10 (if you have a 6x00 card) or get a 7x10, which will do about 17MB/s in RAID5. It's still not great, but a lot better than 6MB/s. RAID1/10 on the 7810 is >>100MB/s for writes, and about 180MB/s reads. So, here's what I get for performance on NFSv3 over gigabit ethernet to XFS (I didn't tweak the r/wmem_default values, only the r/wmem_max. r/wsize is set to 32k. Version 1.01c ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP dp9nfsdp8 2000M:64k 10918 96 25679 23 8436 14 10731 99 42655 34 100.8 5 dp9nfsdp8 2000M:64k 10992 98 25247 23 9225 15 10749 99 48310 44 121.7 6 dp9nfsdp8 2000M:64k 11022 98 24388 21 8503 14 10729 99 45993 39 113.1 6 dp9nfsdp8 2000M:64k 11027 98 25949 23 8467 15 10752 99 41494 32 101.4 6 dp9nfsdp8 2000M:64k 10968 98 26145 24 8760 15 10751 99 43958 36 98.0 6 dp9nfsdp8 2000M:64k 11037 98 28687 27 8533 15 10747 99 43546 36 101.7 6 dp9nfsdp8 2000M:64k 11053 98 24593 21 8513 14 10751 99 41769 33 102.2 5 The XFS volume is RAID50, hw RAID5, then sw RAID0 (striped), hence the reason I can get >17MB/s. I used a 512kb chunksize for the sw RAID0, but I think I might be able to get better performance if I used 448kb. *and* no data/inode corruption now that '-i size=512' now. Cheers, Dan -- Dan Yocum Sloan Digital Sky Survey, Fermilab 630.840.6509 yocum@fnal.gov, http://www.sdss.org SDSS. Mapping the Universe. From owner-linux-xfs@oss.sgi.com Tue Sep 4 15:25:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84MP8X02075 for linux-xfs-outgoing; Tue, 4 Sep 2001 15:25:08 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84MP5d02052 for ; Tue, 4 Sep 2001 15:25:05 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f84MOr521866 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 4 Sep 2001 15:24:53 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id AAA912528 for ; Wed, 5 Sep 2001 00:24:56 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id JAA02802; Wed, 5 Sep 2001 09:23:33 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id JAA63859; Wed, 5 Sep 2001 09:23:21 +1100 (AEDT) Date: Wed, 5 Sep 2001 09:23:21 +1100 From: Nathan Scott To: Russell Cattelan Cc: Andi Kleen , Ethan Benson , linux-xfs@oss.sgi.com Subject: Re: TAKE - mount msgs Message-ID: <20010905092321.A324361@wobbly.melbourne.sgi.com> References: <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <20010904144323.B29262@gruyere.muc.suse.de> <20010904052113.X14519@plato.local.lan> <20010904155555.A30796@gruyere.muc.suse.de> <20010904060129.A14519@plato.local.lan> <20010904162302.A31393@gruyere.muc.suse.de> <999625595.30969.4.camel@scare> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <999625595.30969.4.camel@scare>; from cattelan@thebarn.com on Tue, Sep 04, 2001 at 12:46:33PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Russell, On Tue, Sep 04, 2001 at 12:46:33PM -0500, Russell Cattelan wrote: > On 04 Sep 2001 16:23:02 +0200, Andi Kleen wrote: > > > > The point is that you can quickly blame XFS for it ("it crashed in XFS log > > replay"). With no message it is a lot harder to find which subsystem to > > debug. > Yes... I agree, having a the mount message is very helpful especially > when loading xfs as a module... > > I vote for leaving the message in ... maybe shrink it to one line if > people really thinks it's "cluttering" up the log to much. > Yup, thanks - thats what I ended up doing - leaving in just one line for the normal (clean log) case, more if anything unusual is happening, and more for debug kernels. And now back to doing some real work... cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 4 15:24:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84MOAB02010 for linux-xfs-outgoing; Tue, 4 Sep 2001 15:24:10 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84MO8d01991 for ; Tue, 4 Sep 2001 15:24:08 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f84MO2521800 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 4 Sep 2001 15:24:02 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id AAA911730 for ; Wed, 5 Sep 2001 00:24:06 +0200 (CEST) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id PAA71446 for ; Tue, 4 Sep 2001 15:28:59 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id A51E915A213 for ; Tue, 4 Sep 2001 15:22:32 -0700 (PDT) Subject: Re: TAKE - mount msgs From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <4.3.2.7.2.20010904152044.035d3b48@pop.xs4all.nl> References: <20010904225323.A344731@wobbly.melbourne.sgi.com> <200109041139.VAA08035@snort.melbourne.sgi.com> <20010904134437.A28205@gruyere.muc.suse.de> <20010904225323.A344731@wobbly.melbourne.sgi.com> <4.3.2.7.2.20010904152044.035d3b48@pop.xs4all.nl> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 04 Sep 2001 15:22:32 -0700 Message-Id: <999642152.29244.153.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 04 Sep 2001 15:23:12 +0200, Seth Mos wrote: > > I like having at least one message that it mounted a certain fs. I can then > use dmesg to see if it actually worked, and if it needs to recover or if it > fails I like to see it as well. One line per partition seems to be the best tradeoff: "filesystem /dev/blahblah failed" or "filesystem /dev/foobar succeeded" or something. And maybe just one more line when the module is loaded up (if XFS is a module). -- Florin Andrei "Our kernel does have source control: its name is Linus Torvalds, CVS with a brain." - Nicholas Knight From owner-linux-xfs@oss.sgi.com Tue Sep 4 15:28:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84MSR302349 for linux-xfs-outgoing; Tue, 4 Sep 2001 15:28:27 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84MSPd02329 for ; Tue, 4 Sep 2001 15:28:25 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f84MSJ522094 for ; Tue, 4 Sep 2001 15:28:19 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id JAA02823; Wed, 5 Sep 2001 09:27:02 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id JAA33508; Wed, 5 Sep 2001 09:27:02 +1100 (AEDT) Date: Wed, 5 Sep 2001 09:27:01 +1100 From: Nathan Scott To: Joseph Southwell Cc: Nathan Straz , linux-xfs@oss.sgi.com Subject: Re: root mount mislabled.. Message-ID: <20010905092701.B324361@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 joseph@ud.com on Tue, Sep 04, 2001 at 11:33:35AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Tue, Sep 04, 2001 at 11:33:35AM -0500, Joseph Southwell wrote: > mtab is being populated by calling mount -f. Root is set to LABEL=/ in > /etc/fstab, if I change it to /dev/hda1 I get stopped during boot up > because fsck tries to run and determines that the partition isn't ext2. This particular problem, ie. the fsck frontend not understanding "LABEL=" and "UUID=" for XFS filesystems, has now been fixed in the current e2fsprogs release (http://e2fsprogs.sourceforge.net/) - version 1.24 is the first with the fix, I believe. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 4 15:49:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84MnWi02816 for linux-xfs-outgoing; Tue, 4 Sep 2001 15:49:32 -0700 Received: from commsrvr.projectdesign.com ([63.98.246.130]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84MnSd02794 for ; Tue, 4 Sep 2001 15:49:29 -0700 Received: by commsrvr.projectdesign.com with Internet Mail Service (5.5.2653.19) id ; Tue, 4 Sep 2001 15:49:22 -0700 Message-ID: <58FE74F275AFD411900800508B556525943AD3@commsrvr.projectdesign.com> From: Joshua Penix To: linux-xfs@oss.sgi.com Subject: RE: TAKE - mount msgs Date: Tue, 4 Sep 2001 15:49:22 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Linus himself seems to want to eliminate "good status" messages from kernel boot... http://marc.theaimsgroup.com/?l=linux-kernel&m=99374815219617&w=2 --Josh > -----Original Message----- > From: Blizbor [mailto:tb670725@ima.pl] > Sent: Tuesday, September 04, 2001 8:44 AM > To: linux-xfs@oss.sgi.com > Subject: Re: TAKE - mount msgs > > > At 9/4/01 04:39 PM, Ethan Benson wrote: > >On Tue, Sep 04, 2001 at 04:23:02PM +0200, Andi Kleen wrote: > >> > >> The point is that you can quickly blame XFS for it ("it > crashed in XFS log > >> replay"). With no message it is a lot harder to find which > subsystem to > >> debug. > > > >so print the messages in debug mode, but not otherwise. > > > > Ethan, so what next ? > pppd authors ? ethernet drivers authors ? maybe guys doing scsi ? > What should be changed next to produce less initial output ? > From owner-linux-xfs@oss.sgi.com Tue Sep 4 16:48:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f84NmR803909 for linux-xfs-outgoing; Tue, 4 Sep 2001 16:48:27 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f84NmOd03886 for ; Tue, 4 Sep 2001 16:48:24 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f84NmI527080 for ; Tue, 4 Sep 2001 16:48:18 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA03253; Wed, 5 Sep 2001 10:47:02 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA52461; Wed, 5 Sep 2001 10:47:00 +1100 (AEDT) Date: Wed, 5 Sep 2001 10:47:00 +1100 From: Nathan Scott To: Ethan Benson Cc: linux-xfs@oss.sgi.com Subject: Re: smaller mkfs.xfs Message-ID: <20010905104700.E324361@wobbly.melbourne.sgi.com> References: <20010904043952.V14519@plato.local.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010904043952.V14519@plato.local.lan>; from erbenson@alaska.net on Tue, Sep 04, 2001 at 04:39:52AM -0800 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Tue, Sep 04, 2001 at 04:39:52AM -0800, Ethan Benson wrote: > > Is there any possible ways to reduce the size of the mkfs.xfs binary? > > I am working on adding support for direct XFS installation to the > Debian boot-floppies, but the size of mkfs.xfs is proving to be a real > problem (we are already very tight on space as it is). > > from what i can tell by briefly looking at it, libuuid appears to be > statically linked into this binary? is this correct? making this > dynamic would help a little (probably not much but i can use every > kbyte i can get). also its built with -O1 optimization, is there any > reason for this? would -Os be potentially problematic? > yes, you could link dynamically with libuuid, might help (esp. if you already have mkfs.ext2 on the floppy already, as this uses the same library). libuuid is not very big though, so I doubt this will help much in practice. I have never compiled userspace with -Os, so don't know whether that will cause issues for you - I have compiled at -O2 and I seem to recall some gcc versions broke xfs_db at that optimization level (looked like bad code from gcc) - in particular this was the 2.95.3 gcc in Debian unstable several months ago (long gone though). cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 4 17:06:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8506ia04422 for linux-xfs-outgoing; Tue, 4 Sep 2001 17:06:44 -0700 Received: from alaska.net (kitsune.nwc.alaska.net [209.112.130.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8506ed04402 for ; Tue, 4 Sep 2001 17:06:40 -0700 Received: from erbenson.alaska.net (97-pm18.nwc.alaska.net [209.112.142.97]) by alaska.net (8.9.1/8.9.1) with ESMTP id QAA07448 for ; Tue, 4 Sep 2001 16:06:37 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 757B13924 for ; Tue, 4 Sep 2001 16:06:33 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id AFC0910246; Tue, 4 Sep 2001 16:06:32 -0800 (AKDT) Date: Tue, 4 Sep 2001 16:06:32 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: smaller mkfs.xfs Message-ID: <20010904160632.I14519@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010904043952.V14519@plato.local.lan> <20010905104700.E324361@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kTN++mu+z+U/mv0o" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010905104700.E324361@wobbly.melbourne.sgi.com>; from nathans@sgi.com on Wed, Sep 05, 2001 at 10:47:00AM +1100 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --kTN++mu+z+U/mv0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 05, 2001 at 10:47:00AM +1100, Nathan Scott wrote: > yes, you could link dynamically with libuuid, might help > (esp. if you already have mkfs.ext2 on the floppy already, > as this uses the same library). libuuid is not very big > though, so I doubt this will help much in practice. i could help just enough combined with other bloat reduction im looking into. =20 > I have never compiled userspace with -Os, so don't know > whether that will cause issues for you - I have compiled > at -O2 and I seem to recall some gcc versions broke xfs_db > at that optimization level (looked like bad code from gcc) > - in particular this was the 2.95.3 gcc in Debian unstable > several months ago (long gone though). yes 2.95.4 is whats there now.. is there any kind of regression testing i can do to see if any bugs are introduced by -Os ? --=20 Ethan Benson http://www.alaska.net/~erbenson/ --kTN++mu+z+U/mv0o 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 iEYEARECAAYFAjuVbIgACgkQJKx7GixEevw2EQCeIFgd7Z3W/jxbJcf7M4Y0fX6I a9UAoIqfkNbZke0JxRk24OhtwObwHgIG =DodV -----END PGP SIGNATURE----- --kTN++mu+z+U/mv0o-- From owner-linux-xfs@oss.sgi.com Tue Sep 4 18:52:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f851q0L06742 for linux-xfs-outgoing; Tue, 4 Sep 2001 18:52:00 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f851pwd06723 for ; Tue, 4 Sep 2001 18:51:58 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id SAA02710 for ; Tue, 4 Sep 2001 18:50:20 -0700 (PDT) mail_from (tes@snort.melbourne.sgi.com) Received: (from tes@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA25920 for linux-xfs@oss.sgi.com; Wed, 5 Sep 2001 11:50:39 +1000 (EST) Date: Wed, 5 Sep 2001 11:50:39 +1000 (EST) From: Timothy Shimmin Message-Id: <200109050150.LAA25920@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - cmd/xfstests/common.dump Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Tue Sep 4 18:50:05 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/tes/slinx-xfs-acl The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102157a cmd/xfstests/common.dump - 1.14 - specify scratch_dev on mount - don't rely on fstab or mtab. From owner-linux-xfs@oss.sgi.com Tue Sep 4 18:58:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f851wBB06959 for linux-xfs-outgoing; Tue, 4 Sep 2001 18:58:11 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f851w9d06940 for ; Tue, 4 Sep 2001 18:58:09 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f851w3J08296 for ; Tue, 4 Sep 2001 18:58:04 -0700 Received: from smack.melbourne.sgi.com (smack.melbourne.sgi.com [134.14.55.210]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA03918; Wed, 5 Sep 2001 12:56:47 +1100 Received: from localhost (mg@localhost) by smack.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id LAA38265; Wed, 5 Sep 2001 11:56:47 +1000 (EST) Date: Wed, 5 Sep 2001 11:56:46 +1000 From: Mike Gigante To: Eric Sandeen cc: linux-xfs@oss.sgi.com Subject: man pages on reality (was Re: Preallocation of space) In-Reply-To: <3B94F5D7.C4E4CD75@sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 4 Sep 2001, Eric Sandeen wrote: > If you want to use it as a reference, save it locally... reality *might* > going away... :( > > -Eric Reality *is* going away soon. It has been confirmed on the reality mailing list by senior management. Mike From owner-linux-xfs@oss.sgi.com Wed Sep 5 01:03:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8583en16039 for linux-xfs-outgoing; Wed, 5 Sep 2001 01:03:40 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8583Zd15992 for ; Wed, 5 Sep 2001 01:03:35 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id BAA01624 for ; Wed, 5 Sep 2001 01:01:58 -0700 (PDT) mail_from (ivanr@melbourne.sgi.com) Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA06005; Wed, 5 Sep 2001 19:02:17 +1100 From: ivanr@melbourne.sgi.com (Ivan Rayner) Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id SAA57126; Wed, 5 Sep 2001 18:02:16 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Wed, 5 Sep 2001 18:02:15 +1000 To: Matteo Centonza cc: Subject: Re: xfsdump question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 27 Aug 2001, Matteo Centonza wrote: > | xfsdump: creating dump session media file 0 (media 0, file 0) > | xfsdump: dumping ino map > | xfsdump: dumping directories > | xfsdump: dumping non-directory files > | xfsdump: WARNING: could not open regular file ino 17048187 mode > 0x000081a4: No such file or directory: not dumped > | xfsdump: WARNING: could not open regular file ino 17048190 mode > 0x000081a4: No such file or directory: not dumped > | xfsdump: WARNING: could not open regular file ino 17109993 mode > 0x000081a4: No such file or directory: not dumped > | xfsdump: ending media file > | xfsdump: media file size 6217415200 bytes > | xfsdump: dump size (non-dir files) : 6188187768 bytes > | xfsdump: dump complete: 1135 seconds elapsed ... > getting rid of quota informations which probably has a path problem, > the strange thing is that xfsdump doesn't dump three files that i'm > able to pick up with find: > > xxxxx:/home# find /home -inum 17048187 > /xxxx/xxxxxx/.gnome/panel.d/default/Applet_7_Extern > > and so the remaining two. The same three files were mentioned in the last > week backup as not dumped too. > This filesystem is on a LVM'ed soft RAID5 array with quota enabled, using > CVS copy as of 2001-07-24 (kernel 2.4.7, xfsdump 1.1.2-0). We've had another look at this, and I'd like you to try something else. In the xfstests rpm, there's a program called bstat. It's job is to bulkstat the filesystem and for every directory and file, it compares the stat info with the info from bulkstat. (Bulkstat is an XFS specific system call which will return blocks of inode stat information, which is much faster than stat'ing every file.) The bstat program will also try to open each file in the same way that xfsdump does (using jdm_open, which is a method of opening a file using only the inode number, rather than a pathname). Run bstat like so (assuming /home is an xfs filesystem): # ./bstat -c /home/[some_file_in_the_filesystem] > bstat.log bstat will output a tonne of info, so be sure to redirect it to a log file. When it's done, take a look to see if you can find any failures in the log (look for "unable"). This info could be interesting. Ivan -- Ivan Rayner ivanr@sgi.com From owner-linux-xfs@oss.sgi.com Wed Sep 5 02:01:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8591XP17190 for linux-xfs-outgoing; Wed, 5 Sep 2001 02:01:33 -0700 Received: from mail.loewe-komp.de (mail.loewe-komp.de [62.156.155.230]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8591Td17171 for ; Wed, 5 Sep 2001 02:01:29 -0700 Received: from loewe-komp.de (pippin.loewe-komp.de [192.168.169.19]) by mail.loewe-komp.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id f8597wU30966; Wed, 5 Sep 2001 11:08:02 +0200 X-Authentication-Warning: mail.loewe-komp.de: Host pippin.loewe-komp.de [192.168.169.19] claimed to be loewe-komp.de Message-ID: <3B95EA01.15350CE@loewe-komp.de> Date: Wed, 05 Sep 2001 11:01:53 +0200 From: Peter =?iso-8859-1?Q?W=E4chtler?= Organization: LOEWE. Hannover X-Mailer: Mozilla 4.76 [de] (X11; U; Linux 2.4.9-ac3 i686) X-Accept-Language: de, en MIME-Version: 1.0 To: Seth Mos CC: XFS mailing list Subject: Re: System lock while accessing files causes file corruption References: <3B94F726.E978C299@sgi.com> <85063BBE668FD411944400D0B744267A888526@AUSMAIL> <3B94F726.E978C299@sgi.com> <4.3.2.7.2.20010904193203.032499a0@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > > At 17:57 4-9-2001 +0200, utz lehmann wrote: > >Hi Eric > > > >Eric Sandeen [sandeen@sgi.com] wrote: > > > But in any case, it occurred to me that you could make /etc on it's own > > > partition, and mount that O_SYNC - I don't think that would be too much > > > overhead, /etc doesn't get written that much on a normal system (?). If > > > Oracle puts config files elsewhere, you could simlink them onto this > > > filesystem. > > > >You can't make /etc on a different partition than /. > >/etc, /sbin, /dev (without devfs) must on the / partition otherwise your > >system will not boot. > > If you use a decent layout fopr your data it does not matter. > If you have a separate /usr /var /tmp /home like most servers do you could > just mount your / fs O_SYNC since it would only have a _very_ slight > performance loss since you almost never write to the root fs. :-) > What about the access time? If you mount your / with sync,noatime then it only gets changed when users are logging in (chown user.group /dev/pty and alike). But yes, it's still acceptable ;) From owner-linux-xfs@oss.sgi.com Wed Sep 5 02:25:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f859PEj17641 for linux-xfs-outgoing; Wed, 5 Sep 2001 02:25:14 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f859PAd17622 for ; Wed, 5 Sep 2001 02:25:10 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id LAA22000; Wed, 5 Sep 2001 11:25:03 +0200 (CEST) Message-Id: <4.3.2.7.2.20010905112116.033227e0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 05 Sep 2001 11:25:12 +0200 To: Peter =?iso-8859-1?Q?W=E4chtler?= From: Seth Mos Subject: Re: System lock while accessing files causes file corruption Cc: XFS mailing list In-Reply-To: <3B95EA01.15350CE@loewe-komp.de> References: <3B94F726.E978C299@sgi.com> <85063BBE668FD411944400D0B744267A888526@AUSMAIL> <3B94F726.E978C299@sgi.com> <4.3.2.7.2.20010904193203.032499a0@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f859PBd17623 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 11:01 5-9-2001 +0200, Peter Wächtler wrote: >Seth Mos wrote: > > If you use a decent layout fopr your data it does not matter. > > If you have a separate /usr /var /tmp /home like most servers do you could > > just mount your / fs O_SYNC since it would only have a _very_ slight > > performance loss since you almost never write to the root fs. :-) > > > >What about the access time? If you mount your / with sync,noatime >then it only gets changed when users are logging in >(chown user.group /dev/pty and alike). > >But yes, it's still acceptable ;) Remember, these operations are metadata operations and these _do_ get journaled. It's just to protect the the data files from magically getting emptied if you had just touched them. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Sep 5 05:53:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85CrT521125 for linux-xfs-outgoing; Wed, 5 Sep 2001 05:53:29 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85CrOd21106 for ; Wed, 5 Sep 2001 05:53:24 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id C80A0C00FA5 for ; Wed, 5 Sep 2001 20:53:21 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 87CA1C00FA4 for ; Wed, 5 Sep 2001 20:53:19 +0800 (PHT) Date: Wed, 5 Sep 2001 20:53:19 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Re: kernel spam when mounting xfs In-Reply-To: <20010904162714.A1567@agestado.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 4 Sep 2001 at 16:27, Adriano Nagelschmidt Rodrigues wrote: > Ok, I'll bite, I use ReiserFS and I'm new to this list. Aha! Another target for conversion. Just kidding. I'm also new to the list (especially relative to the real gurus like Eric, Nathan, Steve or Seth, among others), but not quite as new as you I guess. ;> I started out using ReiserFS before XFS because ReiserFS was around in the Linux scene before XFS. I tested XFS when it first got out, wasn't satisfied by the speed (because I felt the significant delete hit), and reverted to ReiserFS. This was with my old server. I got a new server after that and had to decide which filesystem to use. I chose XFS for most everything except my boot partition which uses ext2 and my Squid cache which uses ReiserFS (because ReiserFS has phenomenal delete speeds). > What are the technical reasons not to use ReiserFS? There are a number, and these all depend on your usage patterns. For starters you may want to check the mongo.pl benchmarks in the Namesys (ReiserFS) webpage. ReiserFS is great for small files but you will note that except for delete performance, XFS will start beating ReiserFS at around 10000 bytes. That's rougly 10KB, and for a number of systems (like my Samba+NFS data partition), that's small enough. XFS is stable with NFS. I've done relatively small stress tests and know that for loads beyond our typical here, XFS+NFS is stable. Others like Dan Yocum, who is also on the list, I believe have done even more XFS+NFS stress testing. ReiserFS is supposed to be approaching stability with NFS, but ... XFS has stuff like ACLs, and you'll need to wait for Reiser4 to get that. I made a small talk for the local Linux10 celebrations. If you're interested you can go to to take a look at my slides. --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Wed Sep 5 07:00:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85E0EB22300 for linux-xfs-outgoing; Wed, 5 Sep 2001 07:00:14 -0700 Received: from seralph5.essex.ac.uk (seralph5.essex.ac.uk [155.245.240.155]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85E0Ad22279 for ; Wed, 5 Sep 2001 07:00:10 -0700 Received: from sernt14.essex.ac.uk ([155.245.240.183]) by seralph5.essex.ac.uk with esmtp (Exim 3.13 #1) id 15edDg-0007II-00 for linux-xfs@oss.sgi.com; Wed, 05 Sep 2001 14:59:56 +0100 Received: by sernt14.essex.ac.uk with Internet Mail Service (5.5.2653.19) id ; Wed, 5 Sep 2001 14:57:41 +0100 Message-ID: <7AC902A40BEDD411A3A800D0B7847B660882F5@sernt14.essex.ac.uk> From: "Giddings, Bret" To: "'linux-xfs@oss.sgi.com'" Subject: XFS, Quotas and Samba Date: Wed, 5 Sep 2001 14:57:39 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am investigating whether I can replace my expensive Compaq Alphas file servers with cheaper (and invariably faster given my budget) Intel based ones. I have so far been pleased with the ease with which xfs has installed and run on my hardware of choice. To make my life easier, I have picked up the pre-built RedHat kernels with xfs support. Everything appears to be fine except that when connecting to a share from Samba, the amount of free space reported is the amount of free disk space left on the device rather than the amount of free space in the users quota (this is on a disk mounted with usrquota and a quota set for the users). The usual tools (edquota, setquota work as expected). I have downloaded the source rpm for samba and it appears that RedHat build their smbd to support quotas. I have also checked whether /usr/include/sys/quota.h is modified by installing your updated quota rpm (quota-3.01pre8) and it isn't. So, is there another reason why quotas don't appear to work with xfs/samba? Thanks in advance, Bret -- Bret Giddings, Systems Manager, Computing Service, University of Essex Tel: (01206) 872577 Email: bret@essex.ac.uk Fax: (01206) 860585 From owner-linux-xfs@oss.sgi.com Wed Sep 5 08:04:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85F4se23436 for linux-xfs-outgoing; Wed, 5 Sep 2001 08:04:54 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85F4od23416 for ; Wed, 5 Sep 2001 08:04:51 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id E1F0F1E3E4; Wed, 5 Sep 2001 17:04:44 +0200 (MEST) Date: Wed, 5 Sep 2001 17:04:27 +0200 From: Andi Kleen To: Federico Sevilla III Cc: Linux XFS Mailing List Subject: Re: kernel spam when mounting xfs Message-ID: <20010905170427.A20994@gruyere.muc.suse.de> References: <20010904162714.A1567@agestado.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jijo@leathercollection.ph on Wed, Sep 05, 2001 at 08:53:19PM +0800 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Sep 05, 2001 at 08:53:19PM +0800, Federico Sevilla III wrote: > XFS is stable with NFS. I've done relatively small stress tests and know > that for loads beyond our typical here, XFS+NFS is stable. Others like Dan > Yocum, who is also on the list, I believe have done even more XFS+NFS > stress testing. ReiserFS is supposed to be approaching stability with NFS, > but ... Just to stop the FUD a bit: The last known reiserfs NFS problem (not being able to resolve file handles again under heavy load) has been fixed with 2.4.5. Before that it has been several years been documented as being fixable with a patch. The basic problem BTW was that Linux cannot handle 64bit inode numbers. XFS runs into the same problem when you start using filesystems >2TB. -Andi From owner-linux-xfs@oss.sgi.com Wed Sep 5 08:05:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85F5jI23548 for linux-xfs-outgoing; Wed, 5 Sep 2001 08:05:45 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85F5hd23526 for ; Wed, 5 Sep 2001 08:05:43 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f85F5b520015 for ; Wed, 5 Sep 2001 08:05:38 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2893275; Wed, 5 Sep 2001 10:04:22 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA57772; Wed, 5 Sep 2001 10:04:21 -0500 (CDT) Message-ID: <3B963E97.B99B4FA0@sgi.com> Date: Wed, 05 Sep 2001 10:02:47 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Ethan Benson CC: linux-xfs@oss.sgi.com Subject: Re: smaller mkfs.xfs References: <20010904043952.V14519@plato.local.lan> <20010905104700.E324361@wobbly.melbourne.sgi.com> <20010904160632.I14519@plato.local.lan> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ethan Benson wrote: > yes 2.95.4 is whats there now.. is there any kind of regression > testing i can do to see if any bugs are introduced by -Os ? There is a suite of tests under cmd/xfstests, edit common.config for your machine, and then just run ./check 0?? - none of this is specifically designed to test -0s, but it will make filesystems and check them in various ways... it would be a place to start, in any case. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Sep 5 08:19:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85FJmJ23908 for linux-xfs-outgoing; Wed, 5 Sep 2001 08:19:48 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85FJhd23889 for ; Wed, 5 Sep 2001 08:19:43 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 9A0F1C00FA5; Wed, 5 Sep 2001 23:19:41 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 3F89BC00FA4; Wed, 5 Sep 2001 23:19:40 +0800 (PHT) Date: Wed, 5 Sep 2001 23:19:40 +0800 (PHT) From: Federico Sevilla III To: Dan Yocum Cc: Linux XFS Mailing List , "Philippine Linux Users' Group Mailing List" Subject: On RAID, inode size, stripe size (was: Playing around with NFS+XFS) In-Reply-To: <3B953C69.BBACF47@fnal.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Dan, (cc PLUG, XFS mailing lists) On Tue, 4 Sep 2001 at 15:41, yocum@fnal.gov wrote: > That's the best you'll get out of your 3ware 6400 card under RAID5, so > your bottleneck is the card, not the network, here. :-( Ugh! Ouch. Boohoohoo. I presume this has something to do with the on-board controller and/or the algorithm they use? :( > If you want good performance out of a 3ware card, use RAID 1 or 10 (if > you have a 6x00 card) or get a 7x10, which will do about 17MB/s in > RAID5. It's still not great, but a lot better than 6MB/s. RAID1/10 > on the 7810 is >>100MB/s for writes, and about 180MB/s reads. D*mn! Information like this makes me wonder why I chose RAID5 anyway. I guess it's because I didn't have access to such information before making the decision, and with RAID5 I get significantly more disk space so I said, what the heck. Perhaps I will find the time to take the server offline in the not-so-far-away future to back up all the data onto some hard drives and then re-do the RAID so that it'll be RAID10, which aside from being much faster, is more fault tolerant in that as long as you don't get the right pair, it can handle two drives down. Maybe you're the expert for this: what is RAID5 good for then? And no, I don't think I can afford to upgrade to RAID50 like you. ;> > So, here's what I get for performance on NFSv3 over gigabit ethernet > to XFS (I didn't tweak the r/wmem_default values, only the r/wmem_max. I presume only tweaking the r/wmem_max is safer than meddling with the defaults? > The XFS volume is RAID50, hw RAID5, then sw RAID0 (striped), hence the > reason I can get >17MB/s. I used a 512kb chunksize for the sw RAID0, > but I think I might be able to get better performance if I used 448kb. > *and* no data/inode corruption now that '-i size=512' now. Would you mind explaining to my young mind how using an inode size of 512 bytes protects from data/inode corruption with hardware RAID5? Will this be significant for other setups (hardware RAID10, software RAID, no RAID at all)? Does this have any major disk space or performance impacts? Also with the 3ware 6x00 controllers, RAID5 is limited to 64K stripe size, while RAID0 and RAID10 use 64K, 128K, 256K, 512K or 1M stripe size. How does the stripe size of hardware RAID affect performance and disk utilization? And how can/should the filesystem be tuned to "match" the stripe size of hardware RAID? I'm full of questions. Thanks a lot for the info (that you already gave and that you will hopefully continue to give, hehehe). ;> --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Wed Sep 5 08:25:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85FPXI24105 for linux-xfs-outgoing; Wed, 5 Sep 2001 08:25:33 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85FPUd24086 for ; Wed, 5 Sep 2001 08:25:30 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id C8913C00FA5; Wed, 5 Sep 2001 23:25:28 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 6618EC00FA4; Wed, 5 Sep 2001 23:25:27 +0800 (PHT) Date: Wed, 5 Sep 2001 23:25:27 +0800 (PHT) From: Federico Sevilla III To: Andi Kleen Cc: Linux XFS Mailing List Subject: Re: kernel spam when mounting xfs In-Reply-To: <20010905170427.A20994@gruyere.muc.suse.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 5 Sep 2001 at 17:04, Andi Kleen wrote: > Just to stop the FUD a bit: Oops. I didn't mean that as FUD but now that I think about it, it was. My sincerest apologies, and thank you very much Andi for that wakeup call. > The last known reiserfs NFS problem (not being able to resolve file > handles again under heavy load) has been fixed with 2.4.5. Before that > it has been several years been documented as being fixable with a > patch. I was not quite sure about the stability of ReiserFS+NFS despite the patches, but just checked and indeed the knfsd patches stopped at 2.4.5. > The basic problem BTW was that Linux cannot handle 64bit inode > numbers. So it is indeed more of a problem with the implementation of NFS on Linux than any of the filesystems? --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Wed Sep 5 08:40:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85FeBR24442 for linux-xfs-outgoing; Wed, 5 Sep 2001 08:40:11 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85Fe3d24422 for ; Wed, 5 Sep 2001 08:40:03 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f85FdvJ28760 for ; Wed, 5 Sep 2001 08:39:57 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2881244; Wed, 5 Sep 2001 10:38:41 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA89218; Wed, 5 Sep 2001 10:38:41 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f85FaOO05864; Wed, 5 Sep 2001 10:36:24 -0500 Message-Id: <200109051536.f85FaOO05864@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Federico Sevilla III cc: Dan Yocum , Linux XFS Mailing List , "Philippine Linux Users' Group Mailing List" Subject: Re: On RAID, inode size, stripe size (was: Playing around with NFS+XFS) In-Reply-To: Message from Federico Sevilla III of "Wed, 05 Sep 2001 23:19:40 +0800." Date: Wed, 05 Sep 2001 10:36:24 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Would you mind explaining to my young mind how using an inode size of 512 > bytes protects from data/inode corruption with hardware RAID5? Will this > be significant for other setups (hardware RAID10, software RAID, no RAID > at all)? Does this have any major disk space or performance impacts? > This is not a raid5 thing, it is a filesystem size issue, once you get above 1 Tbyte in filesystem size then xfs inode numbers (which are really a disk address) can take more than 32 bits. Since lots of linux code, including NFS, does not cope with this, we need to change things in xfs so that a larger inode is used, this reduces the number of addressing bits required down to below 32 bits again. This is an interim measure, we have a design for keeping inodes down in the low part of the filesystem (low Tbyte that is) to avoid the address space overflow. Steve From owner-linux-xfs@oss.sgi.com Wed Sep 5 08:49:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85FnAq24802 for linux-xfs-outgoing; Wed, 5 Sep 2001 08:49:10 -0700 Received: from mail.loewe-komp.de (mail.loewe-komp.de [62.156.155.230]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85Fn5d24780 for ; Wed, 5 Sep 2001 08:49:05 -0700 Received: from loewe-komp.de (pippin.loewe-komp.de [192.168.169.19]) by mail.loewe-komp.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id f85FtjU00724 for ; Wed, 5 Sep 2001 17:55:45 +0200 X-Authentication-Warning: mail.loewe-komp.de: Host pippin.loewe-komp.de [192.168.169.19] claimed to be loewe-komp.de Message-ID: <3B964994.CAD96E21@loewe-komp.de> Date: Wed, 05 Sep 2001 17:49:40 +0200 From: Peter =?iso-8859-1?Q?W=E4chtler?= Organization: LOEWE. Hannover X-Mailer: Mozilla 4.76 [de] (X11; U; Linux 2.4.9-ac3 i686) X-Accept-Language: de, en MIME-Version: 1.0 CC: Linux XFS Mailing List Subject: Re: kernel spam when mounting xfs References: <20010904162714.A1567@agestado.com.br> <20010905170427.A20994@gruyere.muc.suse.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Andi Kleen wrote: > > On Wed, Sep 05, 2001 at 08:53:19PM +0800, Federico Sevilla III wrote: > > XFS is stable with NFS. I've done relatively small stress tests and know > > that for loads beyond our typical here, XFS+NFS is stable. Others like Dan > > Yocum, who is also on the list, I believe have done even more XFS+NFS > > stress testing. ReiserFS is supposed to be approaching stability with NFS, > > but ... > > Just to stop the FUD a bit: > > The last known reiserfs NFS problem (not being able to resolve file handles > again under heavy load) has been fixed with 2.4.5. Before that > it has been several years been documented as being fixable with a patch. > The basic problem BTW was that Linux cannot handle 64bit inode numbers. > XFS runs into the same problem when you start using filesystems >2TB. > Another topic that scares me: Is gcc 2.95.[23] considered bad to compile xfs? Why is egcs-2.91-something recommended? I use 2.4.3-xfs on an i686 SMP machine as NFS server, and I had at least two hard lockups (the last happened when mounting a CDROM on aic7xxx). Now if I want to give 2.4.9 a try: do I have to use egcs-2.91 (not there on SuSE)? From owner-linux-xfs@oss.sgi.com Wed Sep 5 09:01:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85G1o225135 for linux-xfs-outgoing; Wed, 5 Sep 2001 09:01:50 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85G1ld25115 for ; Wed, 5 Sep 2001 09:01:47 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 34C7BC00FA5 for ; Thu, 6 Sep 2001 00:01:46 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id BE893C00FA4 for ; Thu, 6 Sep 2001 00:01:44 +0800 (PHT) Date: Thu, 6 Sep 2001 00:01:44 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Re: On RAID, inode size, stripe size (was: Playing around with NFS+XFS) In-Reply-To: <200109051536.f85FaOO05864@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 5 Sep 2001 at 10:36, Steve Lord wrote: > This is not a raid5 thing, it is a filesystem size issue, once you get > above 1 Tbyte in filesystem size then xfs inode numbers (which are > really a disk address) can take more than 32 bits. Since lots of linux > code, including NFS, does not cope with this, we need to change things > in xfs so that a larger inode is used, this reduces the number of > addressing bits required down to below 32 bits again. So on filesystems <1TB you can safely use the default of 256 bytes? --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Wed Sep 5 09:07:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85G70425319 for linux-xfs-outgoing; Wed, 5 Sep 2001 09:07:00 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85G6vd25300 for ; Wed, 5 Sep 2001 09:06:57 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id JAA07687 for ; Wed, 5 Sep 2001 09:06:36 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2890233; Wed, 5 Sep 2001 11:05:15 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA40992; Wed, 5 Sep 2001 11:05:15 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f85G2wX05922; Wed, 5 Sep 2001 11:02:58 -0500 Message-Id: <200109051602.f85G2wX05922@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Federico Sevilla III cc: Linux XFS Mailing List Subject: Re: On RAID, inode size, stripe size (was: Playing around with NFS+XFS) In-Reply-To: Message from Federico Sevilla III of "Thu, 06 Sep 2001 00:01:44 +0800." Date: Wed, 05 Sep 2001 11:02:58 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Wed, 5 Sep 2001 at 10:36, Steve Lord wrote: > > This is not a raid5 thing, it is a filesystem size issue, once you get > > above 1 Tbyte in filesystem size then xfs inode numbers (which are > > really a disk address) can take more than 32 bits. Since lots of linux > > code, including NFS, does not cope with this, we need to change things > > in xfs so that a larger inode is used, this reduces the number of > > addressing bits required down to below 32 bits again. > > So on filesystems <1TB you can safely use the default of 256 bytes? Yes, also mkfs has recently been changed to do this automatically, so provided someones mkfs has been updated recently enough, this scenario should not arise anymore. At least until Linux support 16 Tbyte devices at which point the more complex fix is needed. Steve > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. > GnuPG Key: From owner-linux-xfs@oss.sgi.com Wed Sep 5 09:20:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85GK4D25640 for linux-xfs-outgoing; Wed, 5 Sep 2001 09:20:04 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85GK1d25621 for ; Wed, 5 Sep 2001 09:20:01 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id JAA01931 for ; Wed, 5 Sep 2001 09:18:24 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2892993; Wed, 5 Sep 2001 11:18:43 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA67609; Wed, 5 Sep 2001 11:18:43 -0500 (CDT) Message-ID: <3B965004.3CF7AEBD@sgi.com> Date: Wed, 05 Sep 2001 11:17:08 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 CC: Federico Sevilla III , Linux XFS Mailing List Subject: Re: On RAID, inode size, stripe size (was: Playing around with NFS+XFS) References: <200109051602.f85G2wX05922@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: > Yes, also mkfs has recently been changed to do this automatically, so > provided someones mkfs has been updated recently enough, this scenario > should not arise anymore. At least until Linux support 16 Tbyte devices > at which point the more complex fix is needed. And if you'd like to check an existing filesystem, the latest xfs_info will print the current inode size you can expect (the "imaxbits" line). Also, bear in mind that if you want to grow your filesystem later, you may hit the inode number size problem again. Doubling your filesystem size will add one bit to the maximum inode number, on average. So, if you make a filesystem at 1TB, but anticipate growing it to 4TB, you should choose an inode size of 1024 or so to give you some room in the bits. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Sep 5 09:21:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85GLu825779 for linux-xfs-outgoing; Wed, 5 Sep 2001 09:21:56 -0700 Received: from imapserverb.fnal.gov (imapserverb.fnal.gov [131.225.9.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85GLnd25758 for ; Wed, 5 Sep 2001 09:21:49 -0700 Received: from imapserverb.fnal.gov ([131.225.9.17]) by imapserverb.fnal.gov (Netscape Messaging Server 4.15) with SMTP id GJ76SC00.M67 for ; Wed, 5 Sep 2001 11:21:48 -0500 Received: from fnal.gov ([131.225.7.82]) by imapserverb.fnal.gov (NAVIEG 2.1 bld 63) with SMTP id M2001090511214726611 ; Wed, 05 Sep 2001 11:21:47 -0500 Message-ID: <3B96511C.99471DEE@fnal.gov> Date: Wed, 05 Sep 2001 11:21:48 -0500 From: yocum@fnal.gov X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Federico Sevilla III , xfs-list Subject: Re: On RAID, inode size, stripe size (was: Playing around with NFS+XFS) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jijo, OK, I know we're off topic of the list (XFS) so lets take this to the ide-array list (majordomo@lists.math.uh.edu), after this response. Federico Sevilla III wrote: > > Dan, > (cc PLUG, XFS mailing lists) > > On Tue, 4 Sep 2001 at 15:41, yocum@fnal.gov wrote: > > That's the best you'll get out of your 3ware 6400 card under RAID5, so > > your bottleneck is the card, not the network, here. :-( > > Ugh! Ouch. Boohoohoo. I presume this has something to do with the on-board > controller and/or the algorithm they use? :( I talked to one of the 3ware VPs one day and he said that a) the 6x00 CPU is way underpowered to do RAID5 parity calculations at a decent speed, b) there's no on-board cache, and c) they've had troubles with the FPGAs on the cards. How the last item affects write speed I don't know, maybe he was complaining about their reliability. Anyway, the 7810 has a faster CPU and uses APICs instead of FPGAs, but still doesn't have an on-board cache. The 6x00 cards were made RAID5 capable through a firmware update after Promise came out with a RAID5 card. It was clearly a "me too!" reaction to the competition. > Maybe you're the expert for this: what is RAID5 good for then? And no, I We're more concerned with maximum filesystem size and _read_ speed since we'll write once, read *a lot*. Read speed on the 6x00 cards isn't terrible (85MB/s IIRC) but is even better under the 7x10 cards (180MB/s!!). > > > So, here's what I get for performance on NFSv3 over gigabit ethernet > > to XFS (I didn't tweak the r/wmem_default values, only the r/wmem_max. > > I presume only tweaking the r/wmem_max is safer than meddling with the > defaults? To be honest, I forgot to change the r/wmem_default values when I did the test. > > *and* no data/inode corruption now that '-i size=512' now. (hm. note to self: wipe out and erradicate superfluous redundancies) > > Would you mind explaining to my young mind how using an inode size of 512 > bytes protects from data/inode corruption with hardware RAID5? Will this Yeah, what Steve said. I just threw that comment in there so this thread sort-of remained on topic. Sorry for the confusion. Speaking of being off topic, I'm about to post a technical note on the ide-array list about the systems we've got and what I had to do to get them to where they are now (which is pretty damn stable). I'm pretty sure I've got all the major bugs taken care of (with lots of help from mkp and Eric and Adam at 3ware and....) > Also with the 3ware 6x00 controllers, RAID5 is limited to 64K stripe size, > while RAID0 and RAID10 use 64K, 128K, 256K, 512K or 1M stripe size. How > does the stripe size of hardware RAID affect performance and disk > utilization? And how can/should the filesystem be tuned to "match" the > stripe size of hardware RAID? No effect on utilization. Definitely a factor in speed, but specifics I don't know. In fact, I'm not sure any other RAID card manufacturer allows for anything other than 64k stripe size under RAID 5, but my RAID experience is admittedly limited. > > I'm full of questions. Thanks a lot for the info (that you already gave > and that you will hopefully continue to give, hehehe). ;> "And my consulting fee is.... " ;-) I'm just happy to have systems that I can turn on and forget at the moment. Get me back into the commercial world, and my tune may change. But, for the time being, I live in a purely open source, open information Xanadu! I have achieved Nirvana. Hooooommmmmmeeee, Hoooooommmmmmmeee. Cheers, Dan -- Dan Yocum Sloan Digital Sky Survey, Fermilab 630.840.6509 yocum@fnal.gov, http://www.sdss.org SDSS. Mapping the Universe. From owner-linux-xfs@oss.sgi.com Wed Sep 5 13:31:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85KVCn31151 for linux-xfs-outgoing; Wed, 5 Sep 2001 13:31:12 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85KRUd31104; Wed, 5 Sep 2001 13:27:33 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id 834F86703E; Wed, 5 Sep 2001 22:27:17 +0200 (CEST) Subject: Re: kernel spam when mounting xfs To: Peter =?iso-8859-1?Q?W=E4chtler?= Cc: Linux XFS Mailing List , owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Wed, 5 Sep 2001 22:27:16 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 05.09.2001 22:27:18 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f85KRbd31106 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 05.09.2001 17:49:40 Peter Wächtler wrote: >I use 2.4.3-xfs on an i686 SMP machine as NFS server, and I had at >least >two hard lockups (the last happened when mounting a CDROM on aic7xxx). >Now if I want to give 2.4.9 a try: do I have to use egcs-2.91 (not >there on SuSE)? Hi Peter, They told me to do so last week, fetch the following packages from redhat.com: kgcc-1.1.2-40.i386.rpm compat-egcs-6.2-1.1.2.9.i386.rpm compat-glibc-6.2-2.1.3.2.i386.rpm and install them with rpm -i it works fine for me on Suse 7.2! That kgcc will be used for compiling the kernel, look in the toplevel Makefile of the Kernel for kgcc and uncomment the line........ thats it ;-) cu micha -- Michael Wahlbrink IT Services Propack Data GmbH Karlsruhe miw@propack-data.com +49 721 9650-851 From owner-linux-xfs@oss.sgi.com Wed Sep 5 15:20:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85MKRP00668 for linux-xfs-outgoing; Wed, 5 Sep 2001 15:20:27 -0700 Received: from c4solutions.net (IDENT:qmailr@mail.c4solutions.net [216.143.5.130]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85MK2d00634 for ; Wed, 5 Sep 2001 15:20:23 -0700 Received: (qmail 26987 invoked by uid 100); 5 Sep 2001 22:19:10 -0000 To: linux-xfs@oss.sgi.com Subject: Installer Source Message-ID: <999728350.3b96a4de0bf70@www.c4solutions.net> Date: Wed, 05 Sep 2001 18:19:10 -0400 (EDT) From: Barrett Gay MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.6 X-Originating-IP: 216.143.5.139 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am trying to create a custom Redhat based distrobution and I would like to include support for XFS. I was wondering if the installer that is used for the SGi Redhat Install Disk is open-source and where I could get a copy of it. Thanks, Barrett Gay From owner-linux-xfs@oss.sgi.com Wed Sep 5 15:34:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f85MYT601038 for linux-xfs-outgoing; Wed, 5 Sep 2001 15:34:29 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f85MYQd01013 for ; Wed, 5 Sep 2001 15:34:26 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f85MYKJ19438 for ; Wed, 5 Sep 2001 15:34:21 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2883122; Wed, 5 Sep 2001 17:33:05 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id RAA56672; Wed, 5 Sep 2001 17:33:04 -0500 (CDT) Message-ID: <3B96A7BF.21E1D341@sgi.com> Date: Wed, 05 Sep 2001 17:31:27 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Barrett Gay CC: linux-xfs@oss.sgi.com Subject: Re: Installer Source References: <999728350.3b96a4de0bf70@www.c4solutions.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Barrett Gay wrote: > > I am trying to create a custom Redhat based distrobution and > I would like to include support for XFS. I was wondering if > the installer that is used for the SGi Redhat Install Disk > is open-source and where I could get a copy of it. Barrett - Just grab the modified anaconda SRPM from our ftp site, it should be under the Release-1.0.1 directory. If you have the ISO image, it's on there as well. The patch for XFS is in the SRPM. Are you working on RH 7.1, or the latest RH beta? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Sep 5 17:01:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8601o602670 for linux-xfs-outgoing; Wed, 5 Sep 2001 17:01:50 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8601Od02651 for ; Wed, 5 Sep 2001 17:01:25 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id QAA01275 for ; Wed, 5 Sep 2001 16:59:37 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA10138; Thu, 6 Sep 2001 10:59:53 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA63118; Thu, 6 Sep 2001 10:59:52 +1100 (AEDT) Date: Thu, 6 Sep 2001 10:59:52 +1100 From: Nathan Scott To: "Giddings, Bret" Cc: "'linux-xfs@oss.sgi.com'" , samba-technical@lists.samba.org Subject: Re: XFS, Quotas and Samba Message-ID: <20010906105952.B345981@wobbly.melbourne.sgi.com> References: <7AC902A40BEDD411A3A800D0B7847B660882F5@sernt14.essex.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <7AC902A40BEDD411A3A800D0B7847B660882F5@sernt14.essex.ac.uk>; from bret@essex.ac.uk on Wed, Sep 05, 2001 at 02:57:39PM +0100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Wed, Sep 05, 2001 at 02:57:39PM +0100, Giddings, Bret wrote: > I am investigating whether I can replace my expensive Compaq Alphas file > servers with cheaper (and invariably faster given my budget) Intel based > ones. I have so far been pleased with the ease with which xfs has installed > and run on my hardware of choice. To make my life easier, I have picked up > the pre-built RedHat kernels with xfs support. Everything appears to be fine > except that when connecting to a share from Samba, the amount of free space > reported is the amount of free disk space left on the device rather than the > amount of free space in the users quota (this is on a disk mounted with > usrquota and a quota set for the users). The usual tools (edquota, setquota > work as expected). > > I have downloaded the source rpm for samba and it appears that RedHat build > their smbd to support quotas. I have also checked whether > /usr/include/sys/quota.h is modified by installing your updated quota rpm > (quota-3.01pre8) and it isn't. So, is there another reason why quotas don't > appear to work with xfs/samba? The samba code needs to be updated to support XFS quota under Linux. There was someone on the list a little while ago who was looking to add in the samba support for XFS quota, but I don't know how far they got. I know very little about samba unfortunately, but it should be quite simple to add this stuff for XFS - the disk_quotas() routine in samba-2.2.1a/source/smbd/quotas.c is all that needs to be changed, by the look of things. For XFS filesystems on Linux this needs to: - have logic to handle getmntent's of type "xfs" separately; - issue a quotactl(QCMD(Q_XGETQUOTA,USRQUOTA), ..., &xdq) where xdq is of type "struct fs_disk_quota_t" from - set *bsize to 512 for XFS - refer to the code later in that same file for dealing with XFS on IRIX - basically, do exactly the same thing and it should just work. - to do it properly, the configure scripts will need to check for linux/xqm.h (or might be simpler to keep a local copy? - I dunno what sort of policy the samba folk have on this sort of thing, but this header isn't going to change and probably isn't going to appear in the libc headers for quite awhile...) cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Wed Sep 5 18:36:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f861arJ04870 for linux-xfs-outgoing; Wed, 5 Sep 2001 18:36:53 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f861ald04851 for ; Wed, 5 Sep 2001 18:36:47 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f861ad506957 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Wed, 5 Sep 2001 18:36:40 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id DAA24009 for ; Thu, 6 Sep 2001 03:36:41 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA10829; Thu, 6 Sep 2001 12:35:16 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id MAA72785; Thu, 6 Sep 2001 12:35:15 +1100 (AEDT) Date: Thu, 6 Sep 2001 12:35:15 +1100 From: Nathan Scott To: Jan Kara Cc: "'linux-xfs@oss.sgi.com'" , samba-technical@lists.samba.org Subject: Re: XFS, Quotas and Samba Message-ID: <20010906123515.A380241@wobbly.melbourne.sgi.com> References: <7AC902A40BEDD411A3A800D0B7847B660882F5@sernt14.essex.ac.uk> <20010906105952.B345981@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010906105952.B345981@wobbly.melbourne.sgi.com>; from nathans@sgi.com on Thu, Sep 06, 2001 at 10:59:52AM +1100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Jan, Just a quick followup - this is what I mentioned in my earlier mail to you. I think your new VFS quota code (as in Alan Cox's series of 2.4 kernels, for the Samba folk) will have exactly the same problem as XFS. This "grep" would seem to confirm it - but you'll know better than I here: 11:31 nathans@troppo ~/cvs/quota-tools 73> grep GETQUOTA dqblk*h dqblk_rpc.h:#define Q_RPC_GETQUOTA 0x0300 /* get limits and usage */ dqblk_v1.h:#define Q_V1_GETQUOTA 0x300 dqblk_v2.h:#define Q_V2_GETQUOTA 0x0D00 /* Get limits and usage */ dqblk_xfs.h:#define Q_XFS_GETQUOTA Q_XGETQUOTA 11:31 nathans@troppo ~/cvs/quota-tools 74> The samba code does a good old Q_GETQUOTA (ie. your V1 above). cheers. On Thu, Sep 06, 2001 at 10:59:52AM +1100, Nathan Scott wrote: > hi, > > On Wed, Sep 05, 2001 at 02:57:39PM +0100, Giddings, Bret wrote: > > I am investigating whether I can replace my expensive Compaq Alphas file > > servers with cheaper (and invariably faster given my budget) Intel based > > ones. I have so far been pleased with the ease with which xfs has installed > > and run on my hardware of choice. To make my life easier, I have picked up > > the pre-built RedHat kernels with xfs support. Everything appears to be fine > > except that when connecting to a share from Samba, the amount of free space > > reported is the amount of free disk space left on the device rather than the > > amount of free space in the users quota (this is on a disk mounted with > > usrquota and a quota set for the users). The usual tools (edquota, setquota > > work as expected). > > > > I have downloaded the source rpm for samba and it appears that RedHat build > > their smbd to support quotas. I have also checked whether > > /usr/include/sys/quota.h is modified by installing your updated quota rpm > > (quota-3.01pre8) and it isn't. So, is there another reason why quotas don't > > appear to work with xfs/samba? > > The samba code needs to be updated to support XFS quota under > Linux. There was someone on the list a little while ago who > was looking to add in the samba support for XFS quota, but I > don't know how far they got. > > I know very little about samba unfortunately, but it should be > quite simple to add this stuff for XFS - the disk_quotas() > routine in samba-2.2.1a/source/smbd/quotas.c is all that needs > to be changed, by the look of things. > > For XFS filesystems on Linux this needs to: > - have logic to handle getmntent's of type "xfs" separately; > - issue a quotactl(QCMD(Q_XGETQUOTA,USRQUOTA), ..., &xdq) where > xdq is of type "struct fs_disk_quota_t" from > - set *bsize to 512 for XFS > - refer to the code later in that same file for dealing with XFS > on IRIX - basically, do exactly the same thing and it should > just work. > - to do it properly, the configure scripts will need to check > for linux/xqm.h (or might be simpler to keep a local copy? - > I dunno what sort of policy the samba folk have on this sort of > thing, but this header isn't going to change and probably isn't > going to appear in the libc headers for quite awhile...) > > cheers. > > -- > Nathan -- Nathan From owner-linux-xfs@oss.sgi.com Wed Sep 5 19:28:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f862SDS05708 for linux-xfs-outgoing; Wed, 5 Sep 2001 19:28:13 -0700 Received: from plato.arts.usyd.edu.au (plato.arts.usyd.edu.au [129.78.16.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f862S6d05688 for ; Wed, 5 Sep 2001 19:28:07 -0700 Received: from arts.usyd.edu.au (IDENT:matthew@whitestar.arts.usyd.edu.au [129.78.16.20]) by plato.arts.usyd.edu.au (8.9.3/8.9.3) with ESMTP id MAA18490; Thu, 6 Sep 2001 12:28:01 +1000 (EST) Message-ID: <3B96E0AF.20DF0FBF@arts.usyd.edu.au> Date: Thu, 06 Sep 2001 12:34:23 +1000 From: Matthew Geier Organization: Arts IT Unit, Sydney University X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i686) X-Accept-Language: en, pdf MIME-Version: 1.0 To: "Giddings, Bret" CC: "'linux-xfs@oss.sgi.com'" Subject: Re: XFS, Quotas and Samba References: <7AC902A40BEDD411A3A800D0B7847B660882F5@sernt14.essex.ac.uk> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms9D010F1D9EE124DC7B2A3473" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a cryptographically signed message in MIME format. --------------ms9D010F1D9EE124DC7B2A3473 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Giddings, Bret" wrote: > > I have downloaded the source rpm for samba and it appears that RedHat build > their smbd to support quotas. I have also checked whether > /usr/include/sys/quota.h is modified by installing your updated quota rpm > (quota-3.01pre8) and it isn't. So, is there another reason why quotas don't > appear to work with xfs/samba? yes. XFS quotas work differently from other Linux file system Quotas. I've hacked a 2.2.1a quota.c to support XFS quotas and it seems to work for me. It was a QOD patch though, it basicly replaced parts of the Linux quota code with bits taken out of the SGI quota section, thus ext2 quotas would be broken. I think I posted a diff to samba'a quota.c here a while back. If you are interested I could email you my quota.c. -- Matthew Geier matthew@arts.usyd.edu.au Arts IT Unit +61 2 9351 4713 Sydney University --------------ms9D010F1D9EE124DC7B2A3473 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIH0AYJKoZIhvcNAQcCoIIHwTCCB70CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BbswggKKMIIB86ADAgECAgMFMYswDQYJKoZIhvcNAQECBQAwgZIxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMTA3MDkxOTEyNThaFw0wMjA3MDkxOTEyNTha MEoxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxJzAlBgkqhkiG9w0BCQEWGG1h dHRoZXdAYXJ0cy51c3lkLmVkdS5hdTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA1H+o MQ4xn5lDS/7p9rYboPW7grw13lXOj7Xisip37QttkX7Ga3ITBXnsAKnuFK3Z7GtILACBXil1 BngLBOd0AlW9zqQBXEOP9aODNJzBsTb3+tOHwQo6shcORKQArKEinG00SuwBdzxALU3KWT6E yIUSvoz7q0PN4C8qUF3t00sCAwEAAaM1MDMwIwYDVR0RBBwwGoEYbWF0dGhld0BhcnRzLnVz eWQuZWR1LmF1MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQECBQADgYEAiJu7SNBXsW7I+ZH9 e2+0M47BmR3DxV31VbW9mKcwuamusWSJJEy5MAKZc8b0snRX/XDkCpM+av3VxDJX8T3rxOE0 siyCC6Tclu6wjwjw0goXK4N6Xhsz+qwIfdoclNZkqK5yInEZtc5ijKr0IPRgch79f35WP82C SNHVYApmjzgwggMpMIICkqADAgECAgEMMA0GCSqGSIb3DQEBBAUAMIHRMQswCQYDVQQGEwJa QTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoT EVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERp dmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG 9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDAwODMwMDAwMDAwWhcN MDIwODI5MjM1OTU5WjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTES MBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmlj YXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMw MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMzKmY8cJJUU+0m54J2eBxdqIGYKXDuNE KYpjNSptcDz63K737nRvMLwzkH/5NHGgo22Y8cNPomXbDfpL8dbdYaX5hc1VmjUanZJ1qCeu 2HL5ugL217CR3hzpq+AYA6h8Q0JQUYeDPPA5tJtUihOH/7ObnUlmAC0JieyUa+mhaQIDAQAB o04wTDApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMS0yOTcwEgYDVR0T AQH/BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAcxtvJmWL/xU0 S1liiu1EvknH6A27j7kNaiYqYoQfuIdjdBxtt88aU5FL4c3mONntUPQ6bDSSrOaSnG7BIwHC CafvS65y3QZn9VBvLli4tgvBUFe17BzX7xe21Yibt6KIGu05Wzl9NPy2lhglTWr0ncXDkS+p lrgFPFL83eliA0gxggHdMIIB2QIBATCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNV BAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBS U0EgMjAwMC44LjMwAgMFMYswCQYFKw4DAhoFAKCBmTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0wMTA5MDYwMjM0MjVaMCMGCSqGSIb3DQEJBDEWBBT3zuXX 8OhbLwaIJleuznqT97ADZDA6BgkqhkiG9w0BCQ8xLTArMAoGCCqGSIb3DQMHMA4GCCqGSIb3 DQMCAgIAgDANBggqhkiG9w0DAgIBQDANBgkqhkiG9w0BAQEFAASBgM/CbZ0QuTB6fwGx7RxV WvRW4W1R5lr4NwFb5rZw4dc9mnynBE45KY58tfnAcsNjmZBCRQNOMkWRkNQHeEJ4bEL5EU+S D3d0Q77qdeBW7ghH7CiTxYnCi2EmeWeJHniiFJ956ILexcjsBIH9IIYcyjfRJTleq2AtlC22 kODjeK2J --------------ms9D010F1D9EE124DC7B2A3473-- From owner-linux-xfs@oss.sgi.com Thu Sep 6 07:34:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86EYv518189 for linux-xfs-outgoing; Thu, 6 Sep 2001 07:34:57 -0700 Received: from atrey.karlin.mff.cuni.cz (root@atrey.karlin.mff.cuni.cz [195.113.31.123]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86EYnd18168 for ; Thu, 6 Sep 2001 07:34:49 -0700 Received: (from jack@localhost) by atrey.karlin.mff.cuni.cz (8.9.3/8.9.3/Debian 8.9.3-21) id QAA29808; Thu, 6 Sep 2001 16:34:42 +0200 Date: Thu, 6 Sep 2001 16:34:41 +0200 From: Jan Kara To: Nathan Scott Cc: "'linux-xfs@oss.sgi.com'" , samba-technical@lists.samba.org Subject: Re: XFS, Quotas and Samba Message-ID: <20010906163441.C24754@atrey.karlin.mff.cuni.cz> References: <7AC902A40BEDD411A3A800D0B7847B660882F5@sernt14.essex.ac.uk> <20010906105952.B345981@wobbly.melbourne.sgi.com> <20010906123515.A380241@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <20010906123515.A380241@wobbly.melbourne.sgi.com>; from nathans@sgi.com on Thu, Sep 06, 2001 at 12:35:15PM +1100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, Actually it depends whether the samba code was compiled with proper kernel headers. If so the Q_GETQUOTA is defined to be right value and so everything should work fine. Ok, to be more precise the utils probably won't compile in that case as struct dqblk is no more and mem_dqblk should be used instead... But anyway it shouldn't break silently. Honza > Just a quick followup - this is what I mentioned in my earlier > mail to you. I think your new VFS quota code (as in Alan Cox's > series of 2.4 kernels, for the Samba folk) will have exactly the > same problem as XFS. This "grep" would seem to confirm it - but > you'll know better than I here: > > 11:31 nathans@troppo ~/cvs/quota-tools 73> grep GETQUOTA dqblk*h > dqblk_rpc.h:#define Q_RPC_GETQUOTA 0x0300 /* get limits and usage */ > dqblk_v1.h:#define Q_V1_GETQUOTA 0x300 > dqblk_v2.h:#define Q_V2_GETQUOTA 0x0D00 /* Get limits and usage */ > dqblk_xfs.h:#define Q_XFS_GETQUOTA Q_XGETQUOTA > 11:31 nathans@troppo ~/cvs/quota-tools 74> > > The samba code does a good old Q_GETQUOTA (ie. your V1 above). > > cheers. > > > On Thu, Sep 06, 2001 at 10:59:52AM +1100, Nathan Scott wrote: > > hi, > > > > On Wed, Sep 05, 2001 at 02:57:39PM +0100, Giddings, Bret wrote: > > > I am investigating whether I can replace my expensive Compaq Alphas file > > > servers with cheaper (and invariably faster given my budget) Intel based > > > ones. I have so far been pleased with the ease with which xfs has installed > > > and run on my hardware of choice. To make my life easier, I have picked up > > > the pre-built RedHat kernels with xfs support. Everything appears to be fine > > > except that when connecting to a share from Samba, the amount of free space > > > reported is the amount of free disk space left on the device rather than the > > > amount of free space in the users quota (this is on a disk mounted with > > > usrquota and a quota set for the users). The usual tools (edquota, setquota > > > work as expected). > > > > > > I have downloaded the source rpm for samba and it appears that RedHat build > > > their smbd to support quotas. I have also checked whether > > > /usr/include/sys/quota.h is modified by installing your updated quota rpm > > > (quota-3.01pre8) and it isn't. So, is there another reason why quotas don't > > > appear to work with xfs/samba? > > > > The samba code needs to be updated to support XFS quota under > > Linux. There was someone on the list a little while ago who > > was looking to add in the samba support for XFS quota, but I > > don't know how far they got. > > > > I know very little about samba unfortunately, but it should be > > quite simple to add this stuff for XFS - the disk_quotas() > > routine in samba-2.2.1a/source/smbd/quotas.c is all that needs > > to be changed, by the look of things. > > > > For XFS filesystems on Linux this needs to: > > - have logic to handle getmntent's of type "xfs" separately; > > - issue a quotactl(QCMD(Q_XGETQUOTA,USRQUOTA), ..., &xdq) where > > xdq is of type "struct fs_disk_quota_t" from > > - set *bsize to 512 for XFS > > - refer to the code later in that same file for dealing with XFS > > on IRIX - basically, do exactly the same thing and it should > > just work. > > - to do it properly, the configure scripts will need to check > > for linux/xqm.h (or might be simpler to keep a local copy? - > > I dunno what sort of policy the samba folk have on this sort of > > thing, but this header isn't going to change and probably isn't > > going to appear in the libc headers for quite awhile...) > > > > cheers. > > > > -- > > Nathan > > -- > Nathan -- Jan Kara SuSE Labs From owner-linux-xfs@oss.sgi.com Thu Sep 6 11:31:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86IVwG21933 for linux-xfs-outgoing; Thu, 6 Sep 2001 11:31:58 -0700 Received: from e31.bld.us.ibm.com (e31.co.us.ibm.com [32.97.110.129]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86IVtd21914 for ; Thu, 6 Sep 2001 11:31:55 -0700 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.99.140.23]) by e31.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id OAA77674 for ; Thu, 6 Sep 2001 14:29:38 -0400 Received: from d03nm080.boulder.ibm.com (d03nm080.boulder.ibm.com [9.99.140.64]) by westrelay02.boulder.ibm.com (8.11.1m3/NCO v4.97.1) with ESMTP id f86IV6t130852 for ; Thu, 6 Sep 2001 12:31:06 -0600 Subject: GPL and DMAPI To: linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "James A Goodwin" Date: Thu, 6 Sep 2001 13:31:03 -0500 X-MIMETrack: Serialize by Router on D03NM080/03/M/IBM(Release 5.0.8 |June 18, 2001) at 09/06/2001 12:31:06 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The GPL indicates that linking with libraries distributed under it results in an executable which is also under GPL. This means that any client program written as a client to the Linux XFS DMAPI library is sucked in under GPL, even though no GPL code was modified. Was this SGI's intent? If so, it seems to effectively destroy any chance of commercial software interfacing with Linux XFS, via DMAPI or any other supplied library. If not, is there any plan to distribute Linux XFS under the LGPL, which does allow non-GPL linking? Thanks, -James Goodwin Software Engineer IBM Global Services - Federal From owner-linux-xfs@oss.sgi.com Thu Sep 6 11:43:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86Ihah22307 for linux-xfs-outgoing; Thu, 6 Sep 2001 11:43:36 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86IhXd22288 for ; Thu, 6 Sep 2001 11:43:34 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 343DA1E57C; Thu, 6 Sep 2001 20:43:28 +0200 (MEST) Date: Thu, 6 Sep 2001 20:43:21 +0200 From: Andi Kleen To: Steve Lord Cc: Federico Sevilla III , Dan Yocum , Linux XFS Mailing List , "Philippine Linux Users' Group Mailing List" Subject: Re: On RAID, inode size, stripe size (was: Playing around with NFS+XFS) Message-ID: <20010906204321.A11973@gruyere.muc.suse.de> References: <200109051536.f85FaOO05864@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: <200109051536.f85FaOO05864@jen.americas.sgi.com>; from lord@sgi.com on Wed, Sep 05, 2001 at 10:36:24AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Sep 05, 2001 at 10:36:24AM -0500, Steve Lord wrote: > This is not a raid5 thing, it is a filesystem size issue, once you get > above 1 Tbyte in filesystem size then xfs inode numbers (which are really > a disk address) can take more than 32 bits. Since lots of linux code, > including NFS, does not cope with this, we need to change things in xfs Since 2.4.5 or so mainstream 2.4 has the fh_to_dentry/dentry_to_fh super block interfaces. They are currently only used by reiserfs to handle their equivalent of 64bit inodes; but XFS could use them too to at least avoid problems with NFS for the big file systems. -Andi From owner-linux-xfs@oss.sgi.com Thu Sep 6 11:56:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86IuBw22716 for linux-xfs-outgoing; Thu, 6 Sep 2001 11:56:11 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86Iu8d22692 for ; Thu, 6 Sep 2001 11:56:08 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA06542 for ; Thu, 6 Sep 2001 11:54:33 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2866037; Thu, 6 Sep 2001 13:53:35 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA69978; Thu, 6 Sep 2001 13:53:34 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f86Ip7V14446; Thu, 6 Sep 2001 13:51:07 -0500 Message-Id: <200109061851.f86Ip7V14446@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andi Kleen cc: Steve Lord , Federico Sevilla III , Dan Yocum , Linux XFS Mailing List , "Philippine Linux Users' Group Mailing List" Subject: Re: On RAID, inode size, stripe size (was: Playing around with NFS+XFS) In-Reply-To: Message from Andi Kleen of "Thu, 06 Sep 2001 20:43:21 +0200." <20010906204321.A11973@gruyere.muc.suse.de> Date: Thu, 06 Sep 2001 13:51:06 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Wed, Sep 05, 2001 at 10:36:24AM -0500, Steve Lord wrote: > > This is not a raid5 thing, it is a filesystem size issue, once you get > > above 1 Tbyte in filesystem size then xfs inode numbers (which are really > > a disk address) can take more than 32 bits. Since lots of linux code, > > including NFS, does not cope with this, we need to change things in xfs > > Since 2.4.5 or so mainstream 2.4 has the fh_to_dentry/dentry_to_fh super > block interfaces. They are currently only used by reiserfs to handle > their equivalent of 64bit inodes; but XFS could use them too to at least > avoid problems with NFS for the big file systems. > > -Andi Hmm, it does not solve the problem of stat calls etc which return a 32 bit inode to user space. We also have an application issue with XFS on Irix which means we need to do the solution where we force inodes into 32 bits by placement within the filesystem. Steve From owner-linux-xfs@oss.sgi.com Thu Sep 6 12:08:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86J8jV23215 for linux-xfs-outgoing; Thu, 6 Sep 2001 12:08:45 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86J8gd23196 for ; Thu, 6 Sep 2001 12:08:42 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA05450 for ; Thu, 6 Sep 2001 12:07:07 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2898046; Thu, 6 Sep 2001 14:07:25 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA77452; Thu, 6 Sep 2001 14:07:25 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f86J4vl14613; Thu, 6 Sep 2001 14:04:57 -0500 Message-Id: <200109061904.f86J4vl14613@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "James A Goodwin" cc: linux-xfs@oss.sgi.com Subject: Re: GPL and DMAPI In-Reply-To: Message from "James A Goodwin" of "Thu, 06 Sep 2001 13:31:03 CDT." Date: Thu, 06 Sep 2001 14:04:57 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > The GPL indicates that linking with libraries distributed under it results > in an executable which is also under GPL. This means that any client > program written as a client to the Linux XFS DMAPI library is sucked in > under GPL, even though no GPL code was modified. > > Was this SGI's intent? If so, it seems to effectively destroy any chance > of commercial software interfacing with Linux XFS, via DMAPI or any other > supplied library. > > If not, is there any plan to distribute Linux XFS under the LGPL, which > does allow non-GPL linking? > We will have to think about this one I guess, but how much of a cut can SGI get from IBM if you start selling something ;-). No seriously you have a good point. Steve > Thanks, > > -James Goodwin > Software Engineer > IBM Global Services - Federal From owner-linux-xfs@oss.sgi.com Thu Sep 6 12:12:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86JCff23439 for linux-xfs-outgoing; Thu, 6 Sep 2001 12:12:41 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86JCcd23412 for ; Thu, 6 Sep 2001 12:12:38 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 7BAF71E57B; Thu, 6 Sep 2001 21:12:32 +0200 (MEST) Date: Thu, 6 Sep 2001 21:12:31 +0200 From: Andi Kleen To: Steve Lord Cc: Andi Kleen , Federico Sevilla III , Dan Yocum , Linux XFS Mailing List , "Philippine Linux Users' Group Mailing List" Subject: Re: On RAID, inode size, stripe size (was: Playing around with NFS+XFS) Message-ID: <20010906211231.B12207@gruyere.muc.suse.de> References: <200109061851.f86Ip7V14446@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: <200109061851.f86Ip7V14446@jen.americas.sgi.com>; from lord@sgi.com on Thu, Sep 06, 2001 at 01:51:06PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Sep 06, 2001 at 01:51:06PM -0500, Steve Lord wrote: > > On Wed, Sep 05, 2001 at 10:36:24AM -0500, Steve Lord wrote: > > > This is not a raid5 thing, it is a filesystem size issue, once you get > > > above 1 Tbyte in filesystem size then xfs inode numbers (which are really > > > a disk address) can take more than 32 bits. Since lots of linux code, > > > including NFS, does not cope with this, we need to change things in xfs > > > > Since 2.4.5 or so mainstream 2.4 has the fh_to_dentry/dentry_to_fh super > > block interfaces. They are currently only used by reiserfs to handle > > their equivalent of 64bit inodes; but XFS could use them too to at least > > avoid problems with NFS for the big file systems. > > > > -Andi > > Hmm, it does not solve the problem of stat calls etc which return a 32 > bit inode to user space. We also have an application issue with XFS on > Irix which means we need to do the solution where we force inodes into > 32 bits by placement within the filesystem. It requires LFS aware applications yes and for those a glibc change, but luckily no recompile. [I guess as soon as 2.5 started a new stat syscall should be reserved for that] If you have a nice way to make the lower 32bit of your inodes unique that would be of course more compatible. I just wanted to point out that it is not required for NFS. -Andi From owner-linux-xfs@oss.sgi.com Thu Sep 6 12:31:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86JVh623886 for linux-xfs-outgoing; Thu, 6 Sep 2001 12:31:43 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86JVed23867 for ; Thu, 6 Sep 2001 12:31:40 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f86JVX521705 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Thu, 6 Sep 2001 12:31:33 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA73743 for ; Thu, 6 Sep 2001 21:31:36 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2906527; Thu, 6 Sep 2001 14:30:13 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA95822; Thu, 6 Sep 2001 14:30:13 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f86JRj914879; Thu, 6 Sep 2001 14:27:45 -0500 Message-Id: <200109061927.f86JRj914879@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "James A Goodwin" cc: linux-xfs@oss.sgi.com Subject: Re: GPL and DMAPI In-Reply-To: Message from "James A Goodwin" of "Thu, 06 Sep 2001 13:31:03 CDT." Date: Thu, 06 Sep 2001 14:27:45 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > The GPL indicates that linking with libraries distributed under it results > in an executable which is also under GPL. This means that any client > program written as a client to the Linux XFS DMAPI library is sucked in > under GPL, even though no GPL code was modified. > > Was this SGI's intent? If so, it seems to effectively destroy any chance > of commercial software interfacing with Linux XFS, via DMAPI or any other > supplied library. > > If not, is there any plan to distribute Linux XFS under the LGPL, which > does allow non-GPL linking? As James found out, the dmapi library is actually already LGPL. so there is no constraint on using it. Steve From owner-linux-xfs@oss.sgi.com Thu Sep 6 12:34:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86JYkr24025 for linux-xfs-outgoing; Thu, 6 Sep 2001 12:34:46 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86JYid24006 for ; Thu, 6 Sep 2001 12:34:44 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f86JYc522016 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Thu, 6 Sep 2001 12:34:38 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA73685 for ; Thu, 6 Sep 2001 21:34:40 +0200 (CEST) mail_from (roehrich@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2883044; Thu, 6 Sep 2001 14:33:16 -0500 (CDT) Received: from slobber.americas.sgi.com (slobber.americas.sgi.com [128.162.187.52]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA44218; Thu, 6 Sep 2001 14:33:16 -0500 (CDT) Received: from slobber.americas.sgi.com by slobber.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) via ESMTP id OAA73113; Thu, 6 Sep 2001 14:33:15 -0500 (CDT) Message-Id: <200109061933.OAA73113@slobber.americas.sgi.com> To: "James A Goodwin" cc: kenmcd@sgi.com, linux-xfs@oss.sgi.com Subject: Re: GPL and DMAPI Date: Thu, 06 Sep 2001 14:33:15 -0500 From: Dean Roehrich Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >From: "James A Goodwin" >The GPL indicates that linking with libraries distributed under it results >in an executable which is also under GPL. This means that any client >program written as a client to the Linux XFS DMAPI library is sucked in >under GPL, even though no GPL code was modified. > >Was this SGI's intent? If so, it seems to effectively destroy any chance >of commercial software interfacing with Linux XFS, via DMAPI or any other >supplied library. > >If not, is there any plan to distribute Linux XFS under the LGPL, which >does allow non-GPL linking? Maybe we just need to change the relevant libraries to be LGPL? This would include all of cmd/dmapi and all of cmd/xfsprogs/libhandle. Do we also need to change the license on any header files used when building these libraries? Ken, do we have an LGPL comment block to put in place of the GPL comment block on these files? Do I just change all instances of "General Public License" with "Lesser General Public License"? And change the license version from 2 to 2.1? Dean From owner-linux-xfs@oss.sgi.com Thu Sep 6 12:44:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86Jisr24436 for linux-xfs-outgoing; Thu, 6 Sep 2001 12:44:54 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86Jiqd24417 for ; Thu, 6 Sep 2001 12:44:52 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f86Jik522722 for ; Thu, 6 Sep 2001 12:44:46 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2906481; Thu, 6 Sep 2001 14:43:31 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id OAA21614; Thu, 6 Sep 2001 14:43:30 -0500 (CDT) Message-ID: <3B97D17A.E7E3228D@sgi.com> Date: Thu, 06 Sep 2001 14:41:46 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Lord CC: James A Goodwin , linux-xfs@oss.sgi.com Subject: Re: GPL and DMAPI References: <200109061927.f86JRj914879@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: > As James found out, the dmapi library is actually already LGPL. so there > is no constraint on using it. That's what cmd/dmapi/doc/COPYING says, but the headers in the individual files say otherwise - I guess we need to sync that up. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Sep 6 12:54:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86Js6c24705 for linux-xfs-outgoing; Thu, 6 Sep 2001 12:54:06 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86Js4d24686 for ; Thu, 6 Sep 2001 12:54:04 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f86Jrw523365 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Thu, 6 Sep 2001 12:53:58 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA74316 for ; Thu, 6 Sep 2001 21:54:01 +0200 (CEST) mail_from (roehrich@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2892102; Thu, 6 Sep 2001 14:52:34 -0500 (CDT) Received: from slobber.americas.sgi.com (slobber.americas.sgi.com [128.162.187.52]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA48330; Thu, 6 Sep 2001 14:52:34 -0500 (CDT) Received: from slobber.americas.sgi.com by slobber.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) via ESMTP id OAA64576; Thu, 6 Sep 2001 14:52:33 -0500 (CDT) Message-Id: <200109061952.OAA64576@slobber.americas.sgi.com> To: Eric Sandeen cc: Steve Lord , James A Goodwin , linux-xfs@oss.sgi.com Subject: Re: GPL and DMAPI Date: Thu, 06 Sep 2001 14:52:33 -0500 From: Dean Roehrich Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >From: Eric Sandeen >Steve Lord wrote: > >> As James found out, the dmapi library is actually already LGPL. so there >> is no constraint on using it. > >That's what cmd/dmapi/doc/COPYING says, but the headers in the >individual files say otherwise - I guess we need to sync that up. Ah, thank you. So, I can modify the license comment block in each file under cmd/dmapi. Now, what do we do with libhandle? This is used by libdm. The cmd/xfsprogs/doc/COPYING file does not mention the LGPL. Dean From owner-linux-xfs@oss.sgi.com Thu Sep 6 13:27:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86KRrj25829 for linux-xfs-outgoing; Thu, 6 Sep 2001 13:27:53 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86KRod25810 for ; Thu, 6 Sep 2001 13:27:50 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id NAA07989 for ; Thu, 6 Sep 2001 13:26:15 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2897973 for ; Thu, 6 Sep 2001 15:26:33 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA11573 for ; Thu, 6 Sep 2001 15:26:33 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f86KO5415202; Thu, 6 Sep 2001 15:24:05 -0500 Message-Id: <200109062024.f86KO5415202@jen.americas.sgi.com> Date: Thu, 6 Sep 2001 15:24:05 -0500 Subject: TAKE - fix mongo_pl hangs Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk We may be falling victim to the 'page aging does not work' thread on linux-kernel in that we appear to be having very recently used blocks pulled out from under us. However, there is a problem with XFS getting called in the non-transaction case. If we end up in page_launder() and call back into XFS which does a transaction which ends up needing to flush the log there is a deadlock. This actually pulls us back more in line with the way things work on Irix. Date: Thu Sep 6 12:52:37 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102267a linux/fs/xfs/xfs_trans_buf.c - 1.96 - Add in BUF_BUSY flag into the non-transaction cases in trans_get_buf and trans_read_buf to avoid deadlocks where we come back into the filesystem again via page_launder. From owner-linux-xfs@oss.sgi.com Thu Sep 6 15:28:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86MSN928489 for linux-xfs-outgoing; Thu, 6 Sep 2001 15:28:23 -0700 Received: from mfive.engr.matrixsemi.com ([64.3.134.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86MSJd28467 for ; Thu, 6 Sep 2001 15:28:21 -0700 Received: from matrixsemi.com (mfive.engr.matrixsemi.com [192.168.128.51]) by mfive.engr.matrixsemi.com (Postfix) with ESMTP id 06221B15ABE for ; Thu, 6 Sep 2001 15:30:05 -0700 (PDT) Message-ID: <3B97F8ED.11008423@matrixsemi.com> Date: Thu, 06 Sep 2001 15:30:05 -0700 From: Shiv Sikand Organization: Matrix Semiconductor X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.5-xfs-1.0.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS Rules Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk XFS People, We have 10+ machines running 2.4.5-xfs-1.0.1 on ATA-100 drives here at Matrix. We install using the Mandrake 8 Cooker XFS CD's that we downloaded and burnt. It's been about 3 months now and we now have 200+ GIGS of data on XFS. Not a single problem, brilliant performance. Awesome stuff people. Please don't stop. Cheers, Shiv From owner-linux-xfs@oss.sgi.com Thu Sep 6 16:41:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f86NfC229903 for linux-xfs-outgoing; Thu, 6 Sep 2001 16:41:12 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f86Nf9d29884 for ; Thu, 6 Sep 2001 16:41:09 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f86Nf3508208 for ; Thu, 6 Sep 2001 16:41:03 -0700 Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id QAA54994 for ; Thu, 6 Sep 2001 16:46:10 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id DAEE715A213 for ; Thu, 6 Sep 2001 16:39:42 -0700 (PDT) Subject: Re: kernel spam when mounting xfs From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 06 Sep 2001 16:39:42 -0700 Message-Id: <999819582.7485.106.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 05 Sep 2001 20:53:19 +0800, Federico Sevilla III wrote: > > I made a small talk for the local Linux10 celebrations. If you're > interested you can go to > to take a look at > my slides. Just to point out a small thing: in your presentation, you say "full data journalling offers a severe performance impact, effectively halfing write performance". Well, this may or may not be true. In fact, for some workloads, Ext3 is faster than Ext2 even with full data journalling turned on: http://marc.theaimsgroup.com/?l=postfix-users&m=99654359818329&w=2 - full-journalling ext3 can offer a 3x to 10x improvement over ext2, depending upon how ext2 is used and the directory layout/task count (it's actually Postfix having its mail spool directory on Ext2/3, and it seems to be true only for such usage patterns as with MTAs) Thanks to ppetru@ppetru.net for pointing out this link. But, anyway, your presentation is great. ;-) -- Florin Andrei "Our kernel does have source control: its name is Linus Torvalds, CVS with a brain." - Nicholas Knight From owner-linux-xfs@oss.sgi.com Thu Sep 6 22:09:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8759r102637 for linux-xfs-outgoing; Thu, 6 Sep 2001 22:09:53 -0700 Received: from mailhost.mil.ameritech.net (mpdr0.milwaukee.wi.ameritech.net [206.141.239.126]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8759nd02618 for ; Thu, 6 Sep 2001 22:09:50 -0700 Received: from there ([64.108.133.55]) by mailhost.mil.ameritech.net (InterMail v4.01.01.07 201-229-111-110) with SMTP id <20010907050943.DBDK10497.mailhost.mil.ameritech.net@there>; Fri, 7 Sep 2001 00:09:43 -0500 Content-Type: text/plain; charset="iso-8859-1" From: James To: linux-xfs@oss.sgi.com Subject: Are there any issues with Sparcstations Date: Fri, 7 Sep 2001 00:04:58 -0500 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20010907050943.DBDK10497.mailhost.mil.ameritech.net@there> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi I am happily running XFS on my main home file server (intel), and am thinking about using XFS on my new ( for me, anyway) Sparcstation 5, it will be a couple of small partitions less than 5gig each, that will house a small news feed, is XFS (cvs) ready/compatible with Sparc's running Linux ? Thanks for the input, and keep up the good work, James linux-xfs 2.4.9 : uptime 12 days 12 hours From owner-linux-xfs@oss.sgi.com Fri Sep 7 01:11:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f878BHM05458 for linux-xfs-outgoing; Fri, 7 Sep 2001 01:11:17 -0700 Received: from gateway1.brets.elevating.com (adsl-216-63-236-137.dsl.tulsok.swbell.net [216.63.236.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f878BDd05437 for ; Fri, 7 Sep 2001 01:11:13 -0700 Received: from elevating.com (bretdell.brets.elevating.com [192.168.0.128]) by gateway1.brets.elevating.com (8.9.3/8.8.7) with ESMTP id DAA29336; Fri, 7 Sep 2001 03:11:02 -0500 Message-ID: <3B988116.E31FAF1C@elevating.com> Date: Fri, 07 Sep 2001 03:11:02 -0500 From: Bret Hughes X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, ja MIME-Version: 1.0 To: linux-xfs Subject: compaq smart 2 raid and XFS 1.0.1 redhat install problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I give up. I have totally hosed a compaq 3000 machine that was working perfectly under rh6.2. fortunately it is not our main production box but I still need to get this thing up and running. First I tried an upgrade that appeared to be fine but lilo and I got confused ( at least I was ) I told the installer to use the MBR and that is where compaq utilities stuff gets started from. It was still booting the 2.2.3-16 kernel. Very weird. I putzed with it for too long trying different iterations of upgrades (both XFS and regular redhat 7.1) trying to figure out what was happening. My partner found the deal about compaq needing the mbr so I did the old dos diskette and fdisk /mbr. This let me boot to the right kernel but the system hung right after the compaq smart 2 initialization and gave the message checking partitions: and a reference to using ida/c0d0 I figured I had screwed up the packages so I did an install (not an upgrade ) to an unused partition and get the same error. I have worn out my mouse and me searching the mailing list archives for references to what might be happening. I tried various things like linux devfs=nomount at the lilo prompt. No joy. Are ther issues with the Compaq smart-2 raid controllers and XFS? I see that there is some patching that went on but in reference to it but I could not tell exactly what the issues are. do I need to do the CVS deal and compile my own kernel? How do I get it onto a machine that I cannot boot? Please help. I am fried. Bret From owner-linux-xfs@oss.sgi.com Fri Sep 7 01:36:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f878akk05903 for linux-xfs-outgoing; Fri, 7 Sep 2001 01:36:46 -0700 Received: from alaska.net (sephiroth.nwc.alaska.net [209.112.130.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f878aed05884 for ; Fri, 7 Sep 2001 01:36:41 -0700 Received: from erbenson.alaska.net (198-pm16.nwc.alaska.net [209.112.141.198]) by alaska.net (8.11.5/8.11.5) with ESMTP id f878acP11513 for ; Fri, 7 Sep 2001 00:36:38 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id DFC49397B for ; Fri, 7 Sep 2001 00:36:36 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 1404710246; Fri, 7 Sep 2001 00:36:37 -0800 (AKDT) Date: Fri, 7 Sep 2001 00:36:37 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: Are there any issues with Sparcstations Message-ID: <20010907003636.F23184@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010907050943.DBDK10497.mailhost.mil.ameritech.net@there> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="iVCmgExH7+hIHJ1A" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010907050943.DBDK10497.mailhost.mil.ameritech.net@there>; from jdickens@ameritech.net on Fri, Sep 07, 2001 at 12:04:58AM -0500 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --iVCmgExH7+hIHJ1A Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 07, 2001 at 12:04:58AM -0500, James wrote: >=20 > Hi=20 >=20 > I am happily running XFS on my main home file server (intel), and am thin= king=20 > about using XFS on my new ( for me, anyway) Sparcstation 5, it will be a= =20 > couple of small partitions less than 5gig each, that will house a small n= ews=20 > feed, is XFS (cvs) ready/compatible with Sparc's running Linux ? one problem i can think of is the way sparcs are partitioned and how the bootloader (silo) works... correct me if im wrong anywhere i don't own a sparc and have only done a couple installs (plain ext2) on them. in all the install docs ive read your told to create the first partition (the root partition) starting at cylinder 0, this has the affect of the partition table (which is also at cylinder 0) being ON the root partition, this normally isn't a problem since with ext2 the first 2 blocks are unused to make room for bootloaders generally. =20 so from what i can tell the partition table is on the first 512 byte block, and the silo first stage goes in the second 512 byte block, ext2 doesn't care since that 1k is its unused space for bootloaders. =20 XFS however has no such space, its superblock (or something) starts right at the very start of the partition, so if you partition the way all the docs say to and intend to make your root partition XFS the partition table will be destroyed the moment you create the XFS filesystem. =20 an obvious (to me) solution would simply be don't create the first partition on cylinder 0, but i imagine there is some reason why all the docs say to do that (something to do with silo?) someone with more knowledge of sparcs would have to comment, but it seems XFS on root is not possible on sparcs. silo would also be unable to read its configuration file since it currently doesn't support xfs. another possibility is putting a ext2 /boot partition first and then telling silo to read its config from there instead. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --iVCmgExH7+hIHJ1A 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 iEYEARECAAYFAjuYhxQACgkQJKx7GixEevwIuQCgjCTdwHMNHeWWuFvFY0tXMcSE Ou0An0T/epN96J5T1zdCoBeV7K4wk6Ae =jeWd -----END PGP SIGNATURE----- --iVCmgExH7+hIHJ1A-- From owner-linux-xfs@oss.sgi.com Fri Sep 7 01:38:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f878cQP06039 for linux-xfs-outgoing; Fri, 7 Sep 2001 01:38:26 -0700 Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f878bqd06014 for ; Fri, 7 Sep 2001 01:37:52 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.193]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f878boQ04381 for ; Fri, 7 Sep 2001 17:37:50 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f878bmI05582 for ; Fri, 7 Sep 2001 17:37:48 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id f878bhF18075 for ; Fri, 7 Sep 2001 17:37:45 +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 AAA493 for ; Fri, 7 Sep 2001 17:37:40 +0900 Received: FROM mailsv.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Fri Sep 07 17:37:18 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by mailsv.tnes.nec.co.jp (8.9.3/3.7W01031510) with ESMTP id RAA14936 for ; Fri, 7 Sep 2001 17:37:17 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f878bGL08984 for ; Fri, 7 Sep 2001 17:37:17 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id RAA22356; Fri, 7 Sep 2001 17:37:15 +0900 (JST) Message-Id: <200109070837.RAA22356@tagajo.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: xfsdump/xfsrestore failed sometimes when running QA suite 022 Date: Fri, 07 Sep 2001 17:37:15 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I have run QA suite ( cmd/xfstests/022 ) on my box, but sometimes it failed because the size or owner of a few files are mismatched before xfsdump / after xfsrestore. The error message is attached at the end of this mail. If I edit script 022 to erase a tape with writing an eof instead of erasing actually ( i.e. call _erase_soft instead of _erase_hard which are defined in cmd/xfstest/common.dump ), this issue never occured until now. Machine: Pentium III (Coppermine) 733MHz + SiS 630 chip set + 128MB RAM Tape: HP C1533A DDS2 SCSI Kernel: linux-2.4.10-pre1 with 20010829 CVS Tree xfsdump: 20010829 CVS Tree gcc: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) This have been tested on kernel 2.4.8 and 2.4.9, but same issue occured... Why these files are destroyed? Are there any ideas? Thanks in advance. Taka root [108] > ./022 QA output created by 022 Put scsi tape driver into variable block size mode Creating directory system to dump using src/fsstress. ----------------------------------------------- fsstress : -f link=10 -f creat=10 -f mkdir=10 -f truncate=5 -f symlink=10 ----------------------------------------------- Erasing tape Dumping to tape... xfsdump -s DUMP_SUBDIR -f TAPE_DEV -M stress_tape_media -L stress_022 SCRATCH_MNT xfsdump: version 3.0 - Running single-threaded xfsdump: level 0 dump of HOSTNAME:SCRATCH_MNT xfsdump: dump date: DATE xfsdump: session id: ID xfsdump: session label: "stress_022" xfsdump: ino map phase 1: parsing subtree selections xfsdump: ino map phase 2: constructing initial dump list xfsdump: ino map phase 3: pruning unneeded subtrees xfsdump: ino map phase 4: estimating dump size xfsdump: ino map phase 5: skipping (only one dump stream) xfsdump: ino map construction complete xfsdump: estimated dump size: NUM bytes xfsdump: /var/xfsdump/inventory created xfsdump: preparing drive xfsdump: creating dump session media file 0 (media 0, file 0) xfsdump: dumping ino map xfsdump: dumping directories xfsdump: dumping non-directory files xfsdump: ending media file xfsdump: media file size NUM bytes xfsdump: dumping session inventory xfsdump: beginning inventory media file xfsdump: media file 1 (media 0, file 1) xfsdump: ending inventory media file xfsdump: inventory media file size NUM bytes xfsdump: writing stream terminator xfsdump: beginning media stream terminator xfsdump: media file 2 (media 0, file 2) xfsdump: ending media stream terminator xfsdump: media stream terminator size 1048576 bytes xfsdump: dump size (non-dir files) : NUM bytes xfsdump: dump complete: SECS seconds elapsed Rewinding tape Restoring from tape... xfsrestore -f TAPE_DEV -L stress_022 RESTORE_DIR xfsrestore: version 3.0 - Running single-threaded xfsrestore: using online session inventory xfsrestore: searching media for directory dump xfsrestore: preparing drive xfsrestore: examining media file 0 xfsrestore: reading directories xfsrestore: directory post-processing xfsrestore: restoring non-directory files xfsrestore: restore complete: SECS seconds elapsed Comparing listing of dump directory with restore directory *** TMP.dump_dir Wed Aug 29 17:24:12 2001 --- TMP.restore_dir Wed Aug 29 17:24:12 2001 *************** *** 13,24 **** drwxrwxrwx 2 root root 16 Aug 29 16:16 d39 drwxrwxrwx 5 root root 76 Aug 29 16:16 da drwxrwxrwx 4 root root 55 Aug 29 16:16 db ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 f21 -rw-rw-rw- 1 root root 712704 Aug 29 16:16 f47 -rw-rw-rw- 1 root root 0 Aug 29 16:16 f4f ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 f6 -rw-rw-rw- 3 root root 0 Aug 29 16:16 f61 ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 f7 lrwxrwxrwx 2 root root 939 Aug 29 DATE l29 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxx lrwxrwxrwx 2 root root 939 Aug 29 DATE l29 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxx lrwxrwxrwx 2 root root 939 Aug 29 DATE l36 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxx --- 13,24 ---- drwxrwxrwx 2 root root 16 Aug 29 16:16 d39 drwxrwxrwx 5 root root 76 Aug 29 16:16 da drwxrwxrwx 4 root root 55 Aug 29 16:16 db ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 f21 -rw-rw-rw- 1 root root 712704 Aug 29 16:16 f47 -rw-rw-rw- 1 root root 0 Aug 29 16:16 f4f ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 f6 -rw-rw-rw- 3 root root 0 Aug 29 16:16 f61 ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 f7 lrwxrwxrwx 2 root root 939 Aug 29 DATE l29 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxx lrwxrwxrwx 2 root root 939 Aug 29 DATE l29 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxx lrwxrwxrwx 2 root root 939 Aug 29 DATE l36 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxx *************** *** 31,37 **** /mnt/xfstest1/dump.1655/p0/d5/d2e: total TOTAL drwxrwxrwx 2 root root 26 Aug 29 16:16 d53 ! -rw-rw-rw- 1 root root 420819 Aug 29 16:16 f2f /mnt/xfstest1/dump.1655/p0/d5/d2e/d53: total TOTAL --- 31,37 ---- /mnt/xfstest1/dump.1655/p0/d5/d2e: total TOTAL drwxrwxrwx 2 root root 26 Aug 29 16:16 d53 ! -rw-rw-rw- 1 root root 0 Aug 29 16:16 f2f /mnt/xfstest1/dump.1655/p0/d5/d2e/d53: total TOTAL *************** *** 40,46 **** /mnt/xfstest1/dump.1655/p0/d5/d39: total TOTAL ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 f3e /mnt/xfstest1/dump.1655/p0/d5/da: total TOTAL --- 40,46 ---- /mnt/xfstest1/dump.1655/p0/d5/d39: total TOTAL ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 f3e /mnt/xfstest1/dump.1655/p0/d5/da: total TOTAL *************** *** 55,61 **** /mnt/xfstest1/dump.1655/p0/d5/da/d10: total TOTAL ! -rw-rw-rw- 2 root root 584907 Aug 29 16:16 f62 lrwxrwxrwx 6 root root 1018 Aug 29 DATE l25 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx lrwxrwxrwx 6 root root 1018 Aug 29 DATE l25 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx lrwxrwxrwx 1 root root 1011 Aug 29 DATE l5a -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxxx --- 55,61 ---- /mnt/xfstest1/dump.1655/p0/d5/da/d10: total TOTAL ! -rw-rw-rw- 2 root root 635646 Aug 29 16:16 f62 lrwxrwxrwx 6 root root 1018 Aug 29 DATE l25 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx lrwxrwxrwx 6 root root 1018 Aug 29 DATE l25 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx lrwxrwxrwx 1 root root 1011 Aug 29 DATE l5a -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxxx *************** *** 64,71 **** /mnt/xfstest1/dump.1655/p0/d5/da/d14: total TOTAL drwxrwxrwx 4 root root 56 Aug 29 16:16 d1f ! drwxrwxrwx 2 root root 36 Aug 29 16:16 d26 ! -rw-rw-rw- 3 root root 1906129 Aug 29 16:16 f55 /mnt/xfstest1/dump.1655/p0/d5/da/d14/d1f: total TOTAL --- 64,71 ---- /mnt/xfstest1/dump.1655/p0/d5/da/d14: total TOTAL drwxrwxrwx 4 root root 56 Aug 29 16:16 d1f ! drwxrwxrwx 2 root root 26 Aug 29 16:16 d26 ! -rw-rw-rw- 3 root root 956273 Aug 29 16:16 f55 /mnt/xfstest1/dump.1655/p0/d5/da/d14/d1f: total TOTAL *************** *** 95,101 **** /mnt/xfstest1/dump.1655/p0/d5/da/d14/d26: total TOTAL - -rw-rw-rw- 1 root root 0 Aug 29 16:16 f44 lrwxrwxrwx 2 root root 868 Aug 29 DATE l4e -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx lrwxrwxrwx 2 root root 868 Aug 29 DATE l4e -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx lrwxrwxrwx 1 root root 217 Aug 29 DATE l5e -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxx --- 95,100 ---- *************** *** 103,109 **** /mnt/xfstest1/dump.1655/p0/d5/da/d22: total TOTAL ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 f49 lrwxrwxrwx 1 root root 294 Aug 29 DATE l2c -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxx lrwxrwxrwx 1 root root 294 Aug 29 DATE l2c -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxx lrwxrwxrwx 1 root root 392 Aug 29 DATE l54 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/x --- 102,108 ---- /mnt/xfstest1/dump.1655/p0/d5/da/d22: total TOTAL ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 f49 lrwxrwxrwx 1 root root 294 Aug 29 DATE l2c -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxx lrwxrwxrwx 1 root root 294 Aug 29 DATE l2c -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxx lrwxrwxrwx 1 root root 392 Aug 29 DATE l54 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/x *************** *** 113,119 **** total TOTAL drwxrwxrwx 4 root root 46 Aug 29 16:16 d15 drwxrwxrwx 4 root root 44 Aug 29 16:16 dc ! -rw-rw-rw- 2 root root 1720320 Aug 29 16:16 f18 -rw-rw-rw- 1 root root 0 Aug 29 16:16 f67 lrwxrwxrwx 2 root root 868 Aug 29 DATE l20 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx lrwxrwxrwx 2 root root 868 Aug 29 DATE l20 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx --- 112,118 ---- total TOTAL drwxrwxrwx 4 root root 46 Aug 29 16:16 d15 drwxrwxrwx 4 root root 44 Aug 29 16:16 dc ! -rw-rw-rw- 2 root root 0 Aug 29 16:16 f18 -rw-rw-rw- 1 root root 0 Aug 29 16:16 f67 lrwxrwxrwx 2 root root 868 Aug 29 DATE l20 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx lrwxrwxrwx 2 root root 868 Aug 29 DATE l20 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx *************** *** 122,128 **** total TOTAL drwxrwxrwx 2 root root 6 Aug 29 16:16 d30 drwxrwxrwx 2 root root 16 Aug 29 16:16 d3a ! -rw-rw-rw- 3 root root 1906129 Aug 29 16:16 f1e lrwxrwxrwx 6 root root 1018 Aug 29 DATE l17 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx lrwxrwxrwx 6 root root 1018 Aug 29 DATE l17 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx --- 121,127 ---- total TOTAL drwxrwxrwx 2 root root 6 Aug 29 16:16 d30 drwxrwxrwx 2 root root 16 Aug 29 16:16 d3a ! -rw-rw-rw- 3 root root 956273 Aug 29 16:16 f1e lrwxrwxrwx 6 root root 1018 Aug 29 DATE l17 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx lrwxrwxrwx 6 root root 1018 Aug 29 DATE l17 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx *************** *** 131,144 **** /mnt/xfstest1/dump.1655/p0/d5/db/d15/d3a: total TOTAL ! -rw-rw-rw- 3 root root 1906129 Aug 29 16:16 f6e /mnt/xfstest1/dump.1655/p0/d5/db/dc: total TOTAL drwxrwxrwx 4 root root 46 Aug 29 16:16 d11 drwxrwxrwx 4 root root 36 Aug 29 16:16 d23 ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 fd ! -rw-rw-rw- 2 root root 584907 Aug 29 16:16 fe /mnt/xfstest1/dump.1655/p0/d5/db/dc/d11: total TOTAL --- 130,143 ---- /mnt/xfstest1/dump.1655/p0/d5/db/d15/d3a: total TOTAL ! -rw-rw-rw- 3 root root 956273 Aug 29 16:16 f6e /mnt/xfstest1/dump.1655/p0/d5/db/dc: total TOTAL drwxrwxrwx 4 root root 46 Aug 29 16:16 d11 drwxrwxrwx 4 root root 36 Aug 29 16:16 d23 ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 fd ! -rw-rw-rw- 2 root root 635646 Aug 29 16:16 fe /mnt/xfstest1/dump.1655/p0/d5/db/dc/d11: total TOTAL *************** *** 163,169 **** /mnt/xfstest1/dump.1655/p0/d5/db/dc/d11/d37: total TOTAL -rw-rw-rw- 1 root root 0 Aug 29 16:16 f4a ! -rw-rw-rw- 2 root root 1720320 Aug 29 16:16 f5c /mnt/xfstest1/dump.1655/p0/d5/db/dc/d23: total TOTAL --- 162,168 ---- /mnt/xfstest1/dump.1655/p0/d5/db/dc/d11/d37: total TOTAL -rw-rw-rw- 1 root root 0 Aug 29 16:16 f4a ! -rw-rw-rw- 2 root root 0 Aug 29 16:16 f5c /mnt/xfstest1/dump.1655/p0/d5/db/dc/d23: total TOTAL root [109] > From owner-linux-xfs@oss.sgi.com Fri Sep 7 01:52:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f878qUX06403 for linux-xfs-outgoing; Fri, 7 Sep 2001 01:52:30 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f878qRd06384 for ; Fri, 7 Sep 2001 01:52:27 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15fHNB-00079K-00; Fri, 07 Sep 2001 04:52:26 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f878qPD14548; Fri, 7 Sep 2001 04:52:25 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: James Cc: linux-xfs@oss.sgi.com Subject: Re: Are there any issues with Sparcstations References: <20010907050943.DBDK10497.mailhost.mil.ameritech.net@there> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 07 Sep 2001 04:52:25 -0400 In-Reply-To: <20010907050943.DBDK10497.mailhost.mil.ameritech.net@there> Message-ID: Lines: 18 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "James" == James writes: James> I am happily running XFS on my main home file server (intel), James> and am thinking about using XFS on my new ( for me, anyway) James> Sparcstation 5, it will be a couple of small partitions less James> than 5gig each, that will house a small news feed, is XFS (cvs) James> ready/compatible with Sparc's running Linux ? I haven't tried XFS on SPARC in a long time, so I don't know for sure. With a SPARCstation 5 you should be fine, though. On sun4u, on the other hand, we have a few issues with the userland utilities because kernel is 64-bit and userland is 32. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Sep 7 02:18:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f879Ih807041 for linux-xfs-outgoing; Fri, 7 Sep 2001 02:18:43 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f879Idd07022 for ; Fri, 7 Sep 2001 02:18:40 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15fHmY-0007Cr-00; Fri, 07 Sep 2001 05:18:38 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f879IbU14574; Fri, 7 Sep 2001 05:18:37 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Bret Hughes Cc: linux-xfs Subject: Re: compaq smart 2 raid and XFS 1.0.1 redhat install problems References: <3B988116.E31FAF1C@elevating.com> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 07 Sep 2001 05:18:37 -0400 In-Reply-To: <3B988116.E31FAF1C@elevating.com> Message-ID: Lines: 31 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Bret" == Bret Hughes writes: Bret> but the system hung right after the compaq smart 2 Bret> initialization and gave the message checking partitions: and a Bret> reference to using ida/c0d0 I've had several hangs at that exact spot with Smart RAIDs. In two of the cases it was bad hardware (bad DIMM and bad CPU respectively). Moved the bad DIMM to an identical box, and that would freeze too during Smart RAID init. And I've gotten into situations where all the Compaq BIOS/RAID/config goo would enter an inconsistent state. Windows would boot fine, but Linux would lock up at every attempt to grok the Smart RAID partitions. I solved that by booting the SmartStart CD and do a factory init of the box. Bret> Are ther issues with the Compaq smart-2 raid controllers and Bret> XFS? I'm going all my development on a box with a Compaq Smart-2. So XFS-specific issues, no. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Sep 7 02:26:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f879QAa07370 for linux-xfs-outgoing; Fri, 7 Sep 2001 02:26:10 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f879Q7d07351 for ; Fri, 7 Sep 2001 02:26:07 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 87CF01E688; Fri, 7 Sep 2001 11:26:01 +0200 (MEST) Date: Fri, 7 Sep 2001 11:26:00 +0200 From: Andi Kleen To: "Martin K. Petersen" Cc: James , linux-xfs@oss.sgi.com Subject: Re: Are there any issues with Sparcstations Message-ID: <20010907112600.A23598@gruyere.muc.suse.de> References: <20010907050943.DBDK10497.mailhost.mil.ameritech.net@there> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mkp@linuxcare.com on Fri, Sep 07, 2001 at 04:52:25AM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Sep 07, 2001 at 04:52:25AM -0400, Martin K. Petersen wrote: > >>>>> "James" == James writes: > > James> I am happily running XFS on my main home file server (intel), > James> and am thinking about using XFS on my new ( for me, anyway) > James> Sparcstation 5, it will be a couple of small partitions less > James> than 5gig each, that will house a small news feed, is XFS (cvs) > James> ready/compatible with Sparc's running Linux ? > > I haven't tried XFS on SPARC in a long time, so I don't know for sure. > With a SPARCstation 5 you should be fine, though. At least _pagebuf_free_lockable_buffer is clearly not sparc32 safe, because it gets save_flags flags arguments passed as an argument and will mess up the register window. So I doubt it'll work. -Andi From owner-linux-xfs@oss.sgi.com Fri Sep 7 02:32:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f879W7s07604 for linux-xfs-outgoing; Fri, 7 Sep 2001 02:32:07 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f879W3d07585 for ; Fri, 7 Sep 2001 02:32:03 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15fHzW-0007EA-00; Fri, 07 Sep 2001 05:32:02 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f879W2t14583; Fri, 7 Sep 2001 05:32:02 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: linux-xfs@oss.sgi.com Subject: Re: Are there any issues with Sparcstations References: <20010907050943.DBDK10497.mailhost.mil.ameritech.net@there> <20010907003636.F23184@plato.local.lan> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 07 Sep 2001 05:32:02 -0400 In-Reply-To: <20010907003636.F23184@plato.local.lan> Message-ID: Lines: 32 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Ethan" == Ethan Benson writes: Ethan> in all the install docs ive read your told to create the first Ethan> partition (the root partition) starting at cylinder 0, this has Ethan> the affect of the partition table (which is also at cylinder 0) Ethan> being ON the root partition, this normally isn't a problem Ethan> since with ext2 the first 2 blocks are unused to make room for Ethan> bootloaders generally. The issue here is that you shouldn't put neither swap, nor XFS on your first partition. None of them leave enough space at the beginning of the partition. Which partition root is on doesn't really matter. Make first partition start at cylinder 1, and Bob's your uncle (Having the third partition span the whole disk for Sun compatibility reasons isn't a problem, as long as you don't try to write your silo config to that slice). Ethan> silo would also be unable to read its configuration file since Ethan> it currently doesn't support xfs. another possibility is Ethan> putting a ext2 /boot partition first and then telling silo to Ethan> read its config from there instead. Yep. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Sep 7 02:33:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f879XJp07822 for linux-xfs-outgoing; Fri, 7 Sep 2001 02:33:19 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f879X9d07792 for ; Fri, 7 Sep 2001 02:33:09 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id LAA18349; Fri, 7 Sep 2001 11:32:27 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id LAA03915; Fri, 7 Sep 2001 11:32:06 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id DF7AB57306; Fri, 7 Sep 2001 11:31:07 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 54A0325835; Fri, 7 Sep 2001 11:31:07 +0200 (CEST) Message-ID: <3B9893DB.F59296E@ch.sauter-bc.com> Date: Fri, 07 Sep 2001 11:31:07 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Bret Hughes Cc: linux-xfs Subject: Re: compaq smart 2 raid and XFS 1.0.1 redhat install problems References: <3B988116.E31FAF1C@elevating.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Bret Hughes schrieb: > > I give up. I have totally hosed a compaq 3000 machine that was working > perfectly under rh6.2. fortunately it is not our main production box > but I still need to get this thing up and running. > > First I tried an upgrade that appeared to be fine but lilo and I got > confused ( at least I was ) I told the installer to use the MBR and that > is where compaq utilities stuff gets started from. It was still booting > the 2.2.3-16 kernel. Very weird. I putzed with it for too long trying > different iterations of upgrades (both XFS and regular redhat 7.1) > trying to figure out what was happening. My partner found the deal > about compaq needing the mbr so I did the old dos diskette and fdisk > /mbr. This let me boot to the right kernel but the system hung right > after the compaq smart 2 initialization and gave the message checking > partitions: > and a reference to using ida/c0d0 > > I figured I had screwed up the packages so I did an install (not an > upgrade ) to an unused partition and get the same error. I have worn > out my mouse and me searching the mailing list archives for references > to what might be happening. I tried various things like linux > devfs=nomount at the lilo prompt. No joy. > > Are ther issues with the Compaq smart-2 raid controllers and XFS? I see > that there is some patching that went on but in reference to it but I > could not tell exactly what the issues are. do I need to do the CVS > deal and compile my own kernel? How do I get it onto a machine that I > cannot boot? Please help. I am fried. > > Bret To avoid problems sometimes you need to ged rid of all those special things on PC 'servers'. Usually I'm doing the following: - Zeroing the partitiontable, so getting rid of all those 'built in' tools. - Disable all kind of LBA (DOS 1G support) in the BIOS. Just put /boot in a small patition at beginning of the disk and you don't need any LBA. This has solved my problems on almost every PC 'server'. -Simon From owner-linux-xfs@oss.sgi.com Fri Sep 7 02:35:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f879ZFs07977 for linux-xfs-outgoing; Fri, 7 Sep 2001 02:35:15 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f879ZCd07958 for ; Fri, 7 Sep 2001 02:35:12 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15fI2X-0007Eb-00; Fri, 07 Sep 2001 05:35:09 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f879Z8714586; Fri, 7 Sep 2001 05:35:08 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Andi Kleen Cc: James , linux-xfs@oss.sgi.com Subject: Re: Are there any issues with Sparcstations References: <20010907050943.DBDK10497.mailhost.mil.ameritech.net@there> <20010907112600.A23598@gruyere.muc.suse.de> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 07 Sep 2001 05:35:08 -0400 In-Reply-To: <20010907112600.A23598@gruyere.muc.suse.de> Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Andi" == Andi Kleen writes: >> I haven't tried XFS on SPARC in a long time, so I don't know for >> sure. With a SPARCstation 5 you should be fine, though. Andi> At least _pagebuf_free_lockable_buffer is clearly not sparc32 Andi> safe, because it gets save_flags flags arguments passed as an Andi> argument and will mess up the register window. So I doubt it'll Andi> work. Oh, right. I remember talking to DaveM about that. I've never actually tried XFS on sparc32... -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Sep 7 06:21:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87DL0w11796 for linux-xfs-outgoing; Fri, 7 Sep 2001 06:21:00 -0700 Received: from e31.bld.us.ibm.com (e31.co.us.ibm.com [32.97.110.129]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87DKtd11777 for ; Fri, 7 Sep 2001 06:20:55 -0700 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.99.140.23]) by e31.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id JAA54442; Fri, 7 Sep 2001 09:18:39 -0400 Received: from d03nm080.boulder.ibm.com (d03nm080.boulder.ibm.com [9.99.140.64]) by westrelay02.boulder.ibm.com (8.11.1m3/NCO v4.97.1) with ESMTP id f87DKrb243778; Fri, 7 Sep 2001 07:20:53 -0600 Subject: Re: GPL and DMAPI To: Dean Roehrich Cc: Steve Lord , Eric Sandeen , linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "James A Goodwin" Date: Fri, 7 Sep 2001 08:20:51 -0500 X-MIMETrack: Serialize by Router on D03NM080/03/M/IBM(Release 5.0.8 |June 18, 2001) at 09/07/2001 07:20:53 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Are you saying that libdm.so is LGPL but libhandle.a is not? Since DMAPI applications don't directly utilize libhandle.a (it is utilized by the LGPL libdm.o) that doesn't make much sense. That would mean something like, "Here is this LGPL library to let your commercial applications use our code, but it has this dependency on a GPL library that makes you open source your software, ha ha!" What can be done to get the libhandle.a under LGPL? -James Goodwin Software Engineer IBM Global Services - Federal jagoodwi@us.ibm.com Phone: (281) 336 2578 Fax: (281) 335 4231 T/L 260-2578 Dean Roehrich com> cc: Steve Lord , James A Goodwin/Houston/IBM@IBMUS, linux-xfs@oss.sgi.com 09/06/2001 Subject: Re: GPL and DMAPI 02:52 PM >From: Eric Sandeen >Steve Lord wrote: > >> As James found out, the dmapi library is actually already LGPL. so there >> is no constraint on using it. > >That's what cmd/dmapi/doc/COPYING says, but the headers in the >individual files say otherwise - I guess we need to sync that up. Ah, thank you. So, I can modify the license comment block in each file under cmd/dmapi. Now, what do we do with libhandle? This is used by libdm. The cmd/xfsprogs/doc/COPYING file does not mention the LGPL. Dean From owner-linux-xfs@oss.sgi.com Fri Sep 7 07:22:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87EM1d13060 for linux-xfs-outgoing; Fri, 7 Sep 2001 07:22:01 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87ELwd13040 for ; Fri, 7 Sep 2001 07:21:58 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id HAA01944 for ; Fri, 7 Sep 2001 07:20:23 -0700 (PDT) mail_from (roehrich@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2914211; Fri, 7 Sep 2001 09:19:25 -0500 (CDT) Received: from slobber.americas.sgi.com (slobber.americas.sgi.com [128.162.187.52]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA64314; Fri, 7 Sep 2001 09:19:24 -0500 (CDT) Received: from slobber.americas.sgi.com by slobber.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) via ESMTP id JAA73981; Fri, 7 Sep 2001 09:19:24 -0500 (CDT) Message-Id: <200109071419.JAA73981@slobber.americas.sgi.com> To: "James A Goodwin" cc: Steve Lord , Eric Sandeen , linux-xfs@oss.sgi.com Subject: Re: GPL and DMAPI Date: Fri, 07 Sep 2001 09:19:23 -0500 From: Dean Roehrich Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >From: "James A Goodwin" > >Are you saying that libdm.so is LGPL but libhandle.a is not? Since DMAPI >applications don't directly utilize libhandle.a (it is utilized by the LGPL >libdm.o) that doesn't make much sense. That would mean something like, >"Here is this LGPL library to let your commercial applications use our >code, but it has this dependency on a GPL library that makes you open >source your software, ha ha!" > >What can be done to get the libhandle.a under LGPL? We'll get it sorted out. Dean From owner-linux-xfs@oss.sgi.com Fri Sep 7 07:33:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87EXqj13328 for linux-xfs-outgoing; Fri, 7 Sep 2001 07:33:52 -0700 Received: from k-7.stesmi.com (IDENT:root@as4-1-7.has.s.bonet.se [217.215.31.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87EXnd13309 for ; Fri, 7 Sep 2001 07:33:49 -0700 Received: from stesmi.com (voyager.stesmi.com [192.168.1.11]) by k-7.stesmi.com (8.11.2/8.8.7) with ESMTP id f87Cvpc12888 for ; Fri, 7 Sep 2001 14:57:51 +0200 Message-ID: <3B98C3C0.3000706@stesmi.com> Date: Fri, 07 Sep 2001 14:55:28 +0200 From: Stefan Smietanowski User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.3) Gecko/20010801 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Preallocation of space References: <200109030908.f83988S26342@monkeyiq.dnsalias.org> <3B94F5D7.C4E4CD75@sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi. >>I've found this page which I'll use as my reference to syssgi() >>unless there is a better online version. >>http://reality.sgi.com/cgi-bin/getman?syssgi-2#toc1 >> > > If you want to use it as a reference, save it locally... reality *might* > going away... :( No! If nothing more is real all we will have is surreality! I refuse it! I just got a new job so I like my reality! (Porting linux to an embedded application) Don't take it away from me! :) // Stefan From owner-linux-xfs@oss.sgi.com Fri Sep 7 09:37:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87GboY15114 for linux-xfs-outgoing; Fri, 7 Sep 2001 09:37:50 -0700 Received: from bogon.blenke.com (653224hfc205.tampabay.rr.com [65.32.24.205]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87Gbid15094 for ; Fri, 7 Sep 2001 09:37:44 -0700 Received: (from icblenke@localhost) by bogon.blenke.com (8.9.3/8.9.3/Debian 8.9.3-21) id MAA11157; Fri, 7 Sep 2001 12:37:28 -0400 From: "Ian C. Blenke" Date: Fri, 7 Sep 2001 12:37:28 -0400 To: Simon Matter Cc: Bret Hughes , linux-xfs Subject: Re: compaq smart 2 raid and XFS 1.0.1 redhat install problems Message-ID: <20010907123728.A10983@blenke.com> References: <3B988116.E31FAF1C@elevating.com> <3B9893DB.F59296E@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B9893DB.F59296E@ch.sauter-bc.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Sep 07, 2001 at 11:31:07AM +0200, Simon Matter wrote: > > First I tried an upgrade that appeared to be fine but lilo and I got > > confused ( at least I was ) I told the installer to use the MBR and that > > is where compaq utilities stuff gets started from. It was still booting > > the 2.2.3-16 kernel. Very weird. I putzed with it for too long trying > > different iterations of upgrades (both XFS and regular redhat 7.1) > > trying to figure out what was happening. My partner found the deal > > about compaq needing the mbr so I did the old dos diskette and fdisk > > /mbr. This let me boot to the right kernel but the system hung right > > after the compaq smart 2 initialization and gave the message checking > > partitions: > > and a reference to using ida/c0d0 I'm using two 1850Rs with SmartArray2 controllers with no problems. Both are running Debian 2.2 (Potato) with handbuilt 2.4.6 XFS kernels, the CVS XFS cmd tools, and lvs 0.9.1_beta6 (all built from source). When building the servers, I used the SmartStart 4.70 (from memory) wipe, configured the RAID array, and installed the SmartStart partition. From there it took a little hand holding to get Potato on the system. I'm using grub (the older build from potato no less - what fun), not lilo. The biggest pain was getting lvm's vgscan to deal well with the /dev/ida/c0t0d2 style device naming (ended up with a symlink to /dev/sda devices to get it to act consistently). If you're using a I2O device, good luck (/dev/i2o/hda is even more obtuse). In the end, I ended up building everything as a module and hacked up /sbin/lvmcreate_initrd to include xfs/xfs_support/pagebuf, cpqarray, scsi_mod, aic7xxx, and sd_mod (the latter three for the onboard controller). Now I can build a new kernel, run lvmcreate_initrd, and avoid hand-building an initrd everytime. > > I figured I had screwed up the packages so I did an install (not an > > upgrade ) to an unused partition and get the same error. I have worn > > out my mouse and me searching the mailing list archives for references > > to what might be happening. I tried various things like linux > > devfs=nomount at the lilo prompt. No joy. I'll not get into religious debates about RedHat's RPM hell on this list ;) Been there. Done that. Burned the t-shirt. While I've built the CVS xfs cmd tools as DEBs, it's just not proper to pass them around ;) "Use the source". Keep it handy. > > Are ther issues with the Compaq smart-2 raid controllers and XFS? I see > > that there is some patching that went on but in reference to it but I > > could not tell exactly what the issues are. do I need to do the CVS > > deal and compile my own kernel? How do I get it onto a machine that I > > cannot boot? Please help. I am fried. None. I have two systems working wonderfully now: one with ~27GB (raid5), and the other with 54GB+44GB (raid5). No worries. You may *want* to build from CVS (I do, habitually now). I'm running two VA Linux boxen with XFS/LVM, and two Compaq 1850R boxen on SmartStart2 controllers with XFS/LVM, as well as a couple of happy XFS laptops. I've had incredibly few problems with XFS so far.. and lvextend/xfs_growfs really is a lifesaver. Good luck. - Ian C. Blenke From owner-linux-xfs@oss.sgi.com Fri Sep 7 12:04:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87J4VA16941 for linux-xfs-outgoing; Fri, 7 Sep 2001 12:04:31 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87J4Sd16921 for ; Fri, 7 Sep 2001 12:04:28 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id 6CD6C139DC; Fri, 7 Sep 2001 15:04:25 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: fsck equivalent? Message-Id: <20010907190425.6CD6C139DC@linux.compucomis.net> Date: Fri, 7 Sep 2001 15:04:25 -0400 (EDT) From: mburger@compucomis.net (Mike Burger) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've got a drive that I think is flakey...but right now, it holds my /var file system. I've done some considerable customization (considering that the installation of the OS only occurred yesterday) and I'd hate to have to reinstall the whole damned OS, again. So, since the drive can't be mounted (error involves bad superblock), I'm in need of the name of a program I can run, manually, to check and repair the filesystem, if possible, so that I can then move the contents off to a replacement drive. Help? Thanks. --Mike PS: The system was installed using the latest SGI ISO installer and RH7.1 CDs. Thanks. From owner-linux-xfs@oss.sgi.com Fri Sep 7 12:10:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87JA3v17123 for linux-xfs-outgoing; Fri, 7 Sep 2001 12:10:03 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87JA0d17093 for ; Fri, 7 Sep 2001 12:10:00 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15fR0p-000891-00; Fri, 07 Sep 2001 15:09:59 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f87J9w115237; Fri, 7 Sep 2001 15:09:58 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: mburger@compucomis.net (Mike Burger) Cc: linux-xfs@oss.sgi.com Subject: Re: fsck equivalent? References: <20010907190425.6CD6C139DC@linux.compucomis.net> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 07 Sep 2001 15:09:58 -0400 In-Reply-To: <20010907190425.6CD6C139DC@linux.compucomis.net> Message-ID: Lines: 19 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Mike" == Mike Burger writes: Mike> I've got a drive that I think is flakey...but right now, it Mike> holds my /var file system. I've done some considerable Mike> customization (considering that the installation of the OS only Mike> occurred yesterday) and I'd hate to have to reinstall the whole Mike> damned OS, again. Mike> So, since the drive can't be mounted (error involves bad Mike> superblock), I'm in need of the name of a program I can run, Mike> manually, to check and repair the filesystem, if possible, so Mike> that I can then move the contents off to a replacement drive. xfs_repair -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Sep 7 12:12:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87JCEe17264 for linux-xfs-outgoing; Fri, 7 Sep 2001 12:12:14 -0700 Received: from afara-gw.afara.com (mx1.afara.com [63.113.218.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87JCBd17245 for ; Fri, 7 Sep 2001 12:12:12 -0700 Received: from tduffy-lnx.afara.com ([10.2.4.191]) by afara-gw.afara.com with Microsoft SMTPSVC(5.0.2195.1600); Fri, 7 Sep 2001 12:07:44 -0700 Subject: Re: fsck equivalent? From: Thomas Duffy To: Mike Burger Cc: linux-xfs@oss.sgi.com In-Reply-To: <20010907190425.6CD6C139DC@linux.compucomis.net> References: <20010907190425.6CD6C139DC@linux.compucomis.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13.99+cvs.2001.09.05.07.08 (Preview Release) Date: 07 Sep 2001 12:11:40 -0700 Message-Id: <999889901.8754.5.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 X-OriginalArrivalTime: 07 Sep 2001 19:07:44.0223 (UTC) FILETIME=[5FC006F0:01C137D0] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 2001-09-07 at 12:04, Mike Burger wrote: > Help? xfs_repair -tduffy From owner-linux-xfs@oss.sgi.com Fri Sep 7 12:13:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87JDxE17417 for linux-xfs-outgoing; Fri, 7 Sep 2001 12:13:59 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87JDud17398 for ; Fri, 7 Sep 2001 12:13:56 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA07536 for ; Fri, 7 Sep 2001 12:12:21 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2914046; Fri, 7 Sep 2001 14:12:37 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id OAA61879; Fri, 7 Sep 2001 14:12:37 -0500 (CDT) Message-ID: <3B991C24.9493F1C0@sgi.com> Date: Fri, 07 Sep 2001 14:12:36 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Mike Burger CC: linux-xfs@oss.sgi.com Subject: Re: fsck equivalent? References: <20010907190425.6CD6C139DC@linux.compucomis.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Mike Burger wrote: > > I've got a drive that I think is flakey...but right now, it holds my > /var file system. I've done some considerable customization (considering > that the installation of the OS only occurred yesterday) and I'd hate to > have to reinstall the whole damned OS, again. > > So, since the drive can't be mounted (error involves bad superblock), I'm > in need of the name of a program I can run, manually, to check and repair > the filesystem, if possible, so that I can then move the contents off to > a replacement drive. You can try xfs_repair - the filesystem should be unmounted, and you can give it the "-n" option to see what it _would_ do, without actually doing anything. What sort of errors did you run into? (Just making sure it's a hardware problem...) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Sep 7 12:22:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87JM7b17657 for linux-xfs-outgoing; Fri, 7 Sep 2001 12:22:07 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87JM2d17638 for ; Fri, 7 Sep 2001 12:22:03 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id 2BA11139DC; Fri, 7 Sep 2001 15:22:09 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id 28A77139DA; Fri, 7 Sep 2001 15:22:09 -0400 (EDT) Date: Fri, 7 Sep 2001 15:22:09 -0400 (EDT) From: Mike Burger To: Eric Sandeen Cc: Subject: Re: fsck equivalent? In-Reply-To: <3B991C24.9493F1C0@sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Well, yesterday it was the disappearance of everything in the /var directory. I shutdown and rebooted the system, and received a message during boot that /dev/hdb1 couldn't be mounted due to missing file system or bad superblock. df showed mounts of /dev/hda1 (/boot), /devhda2 (/) and /dev/hdc1 (/home). I tried, just for kicks, to fsck /dev/hdb1, but it came back with a message about a bad superblock (as it should have.) I then tried to mkfs.xfs /dev/hdb1, and it came back with a message that there was already an XFS filesystem on the device. The system, upon POST, does recognize the drive, just fine, physically...but this is the third time I've lost the /var filesystem. Right now, after trying to do a remote shutdown -r now, the system is hung, at some point, which I won't be able to view until I get back onsite. On Fri, 7 Sep 2001, Eric Sandeen wrote: > Mike Burger wrote: > > > > I've got a drive that I think is flakey...but right now, it holds my > > /var file system. I've done some considerable customization (considering > > that the installation of the OS only occurred yesterday) and I'd hate to > > have to reinstall the whole damned OS, again. > > > > So, since the drive can't be mounted (error involves bad superblock), I'm > > in need of the name of a program I can run, manually, to check and repair > > the filesystem, if possible, so that I can then move the contents off to > > a replacement drive. > > You can try xfs_repair - the filesystem should be unmounted, and you can > give it the "-n" option to see what it _would_ do, without actually > doing anything. > > What sort of errors did you run into? (Just making sure it's a hardware > problem...) > > -Eric > > > From owner-linux-xfs@oss.sgi.com Fri Sep 7 12:32:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87JW3U17890 for linux-xfs-outgoing; Fri, 7 Sep 2001 12:32:03 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87JVxd17871 for ; Fri, 7 Sep 2001 12:31:59 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f87JVr524473 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Fri, 7 Sep 2001 12:31:53 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA142342 for ; Fri, 7 Sep 2001 21:31:57 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2916792; Fri, 7 Sep 2001 14:30:33 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id OAA60629; Fri, 7 Sep 2001 14:30:33 -0500 (CDT) Message-ID: <3B992055.AE786AC5@sgi.com> Date: Fri, 07 Sep 2001 14:30:29 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Mike Burger CC: linux-xfs@oss.sgi.com Subject: Re: fsck equivalent? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Mike Burger wrote: > > Well, yesterday it was the disappearance of everything in the /var > directory. I shutdown and rebooted the system, and received a message > during boot that /dev/hdb1 couldn't be mounted due to missing file system > or bad superblock. Hm, that's a generic mount error message that will happen for a variety of reasons... Sort of "windows-esque" if you ask me. :) Any other messages in the syslogs when you try to mount it? > df showed mounts of /dev/hda1 (/boot), /devhda2 (/) and /dev/hdc1 (/home). > > I tried, just for kicks, to fsck /dev/hdb1, but it came back with a > message about a bad superblock (as it should have.) Actually, fsck should have run fsck.xfs, which is pretty simple: int main(int argc, char **argv) { return 0; } :) > I then tried to > mkfs.xfs /dev/hdb1, and it came back with a message that there was > already an XFS filesystem on the device. Well, that's good news... I suppose it's pretty possible that it is a bad disk, just wondered what you had run into. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Sep 7 12:40:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87JesX18080 for linux-xfs-outgoing; Fri, 7 Sep 2001 12:40:54 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87Jeod18061 for ; Fri, 7 Sep 2001 12:40:50 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id 7FC61139DC; Fri, 7 Sep 2001 15:40:56 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id 7CC4B139DA; Fri, 7 Sep 2001 15:40:56 -0400 (EDT) Date: Fri, 7 Sep 2001 15:40:56 -0400 (EDT) From: Mike Burger To: Eric Sandeen Cc: Subject: Re: fsck equivalent? In-Reply-To: <3B992055.AE786AC5@sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 7 Sep 2001, Eric Sandeen wrote: > Mike Burger wrote: > > > > Well, yesterday it was the disappearance of everything in the /var > > directory. I shutdown and rebooted the system, and received a message > > during boot that /dev/hdb1 couldn't be mounted due to missing file system > > or bad superblock. > > Hm, that's a generic mount error message that will happen for a variety > of reasons... > Sort of "windows-esque" if you ask me. :) Well, Windows used to be on the hard drive, but it's a non-booting slave, drive, now...dedicated entirely to XFS and Linux. > Any other messages in the syslogs when you try to mount it? No way for me to know...since it's the drive that houses /var, I can't get to the syslogs. I can reboot and note the errors that come up during boot. Most of them involve not being able to find the appropriate dirctories under /var for lock files, PID files, etc. > > df showed mounts of /dev/hda1 (/boot), /devhda2 (/) and /dev/hdc1 (/home). > > > > I tried, just for kicks, to fsck /dev/hdb1, but it came back with a > > message about a bad superblock (as it should have.) > > Actually, fsck should have run fsck.xfs, which is pretty simple: I kinda thought so, too... > > I then tried to > > mkfs.xfs /dev/hdb1, and it came back with a message that there was > > already an XFS filesystem on the device. > > Well, that's good news... > I suppose it's pretty possible that it is a bad disk, just wondered what > you had run into. I'll be rebooting into single user mode and trying xfs.repair on the drive when I get home...I'll let you know what I come up with, if anything. From owner-linux-xfs@oss.sgi.com Fri Sep 7 14:06:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87L61J19246 for linux-xfs-outgoing; Fri, 7 Sep 2001 14:06:01 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87L5ud19227 for ; Fri, 7 Sep 2001 14:05:56 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id 25CD7139E1; Fri, 7 Sep 2001 17:06:03 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id 1CA84139DF; Fri, 7 Sep 2001 17:06:03 -0400 (EDT) Date: Fri, 7 Sep 2001 17:06:02 -0400 (EDT) From: Mike Burger To: Eric Sandeen Cc: Subject: Re: fsck equivalent? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Well, the good news is that I didn't lose the /var filesystem, this time...but I did lose the database that I had just created (no data in it, though, so it works out ok. ). xfs_repair did help, though. On Fri, 7 Sep 2001, Mike Burger wrote: > On Fri, 7 Sep 2001, Eric Sandeen wrote: > > > Mike Burger wrote: > > > > > > Well, yesterday it was the disappearance of everything in the /var > > > directory. I shutdown and rebooted the system, and received a message > > > during boot that /dev/hdb1 couldn't be mounted due to missing file system > > > or bad superblock. > > > > Hm, that's a generic mount error message that will happen for a variety > > of reasons... > > Sort of "windows-esque" if you ask me. :) > > Well, Windows used to be on the hard drive, but it's a non-booting slave, > drive, now...dedicated entirely to XFS and Linux. > > > Any other messages in the syslogs when you try to mount it? > > No way for me to know...since it's the drive that houses /var, I can't get > to the syslogs. > > I can reboot and note the errors that come up during boot. Most of them > involve not being able to find the appropriate dirctories under /var for > lock files, PID files, etc. > > > > df showed mounts of /dev/hda1 (/boot), /devhda2 (/) and /dev/hdc1 (/home). > > > > > > I tried, just for kicks, to fsck /dev/hdb1, but it came back with a > > > message about a bad superblock (as it should have.) > > > > Actually, fsck should have run fsck.xfs, which is pretty simple: > > I kinda thought so, too... > > > > I then tried to > > > mkfs.xfs /dev/hdb1, and it came back with a message that there was > > > already an XFS filesystem on the device. > > > > Well, that's good news... > > > > > I suppose it's pretty possible that it is a bad disk, just wondered what > > you had run into. > > I'll be rebooting into single user mode and trying xfs.repair on the drive > when I get home...I'll let you know what I come up with, if anything. > > From owner-linux-xfs@oss.sgi.com Fri Sep 7 15:23:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87MN5P20820 for linux-xfs-outgoing; Fri, 7 Sep 2001 15:23:05 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87MN2d20800 for ; Fri, 7 Sep 2001 15:23:03 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id AAA09345; Sat, 8 Sep 2001 00:22:56 +0200 (CEST) Message-Id: <4.3.2.7.2.20010908002120.035e8b20@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 08 Sep 2001 00:23:06 +0200 To: Mike Burger , Eric Sandeen From: Seth Mos Subject: Re: fsck equivalent? Cc: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:06 7-9-2001 -0400, Mike Burger wrote: >Well, the good news is that I didn't lose the /var filesystem, this >time...but I did lose the database that I had just created (no data in it, >though, so it works out ok. ). If you see this often can you then specify sopme details like what compiler you used ig you compiled your own or what hardware you are on. >xfs_repair did help, though. As it should :-) Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Sep 7 16:47:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f87NlCq22610 for linux-xfs-outgoing; Fri, 7 Sep 2001 16:47:12 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f87Nl1d22590 for ; Fri, 7 Sep 2001 16:47:01 -0700 Received: from cvo-exchange.cvo.roguewave.com (cvo-ext.roguewave.com [12.22.36.198]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id QAA03605 for ; Fri, 7 Sep 2001 16:46:58 -0700 (PDT) mail_from (petersp@roguewave.com) Received: by cvo-exchange.roguewave.com with Internet Mail Service (5.5.2650.21) id ; Fri, 7 Sep 2001 16:45:24 -0700 Message-ID: From: Poul Petersen To: linux-xfs@oss.sgi.com, linux-scsi@vger.kernel.org Subject: Problems with 2.4.5 + XFS 1.0.1 + qlogicfc driver Date: Fri, 7 Sep 2001 16:45:24 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've been noticing a problem which I have worked down to a reliable test case. We have a SAN with three servers (2 Dell 6450 dual CPU and a Dell Optiplex Gx running RedHat 7.1 with the 2.4.5 kernel (SMP enabled on the duals) and XFS 1.0.1) a Qualstar tape library, and a Zzyzx RocketStor 2000 disk array. These machines are all connected together with a SANbox. The Dell's have Qlogic 2100 cards and are running the stock qlogicfc kernel driver as a module. Other than XFS, we have modified the scsi_scan.c driver (patch below). Everything else is unchanged. I orignally observed the problem with the tape library and created the following test case: 1) unload st, sg, qlogicfc from host 2) unplug Qualstar library from SAN 3) load qlogic on host 4) mount a disk on host from the Zzyzx array 5) start a large dd write to the disk 6) load st,sg module on host 7) plug Qualstar library into SAN 8) unload sg (or st) This sequence of actions will cause the host running the dd's to report I/O errors and eventually force the disk offline. On occassion, I had been able to duplicate this by simply connecting the library to the san while a disk write is occuring. We worked around this problem by installing a second HBA into the Optiplex and plugging the tape library directly into this host, effectively isolating the library from the rest of the SAN (this one machine is the backup server, so it's no big deal.) However, early today one of the Dell servers crashed and when we rebooted it the *other* Dell, which serves the disk space on the SAN via NFS, reported the attached errors in its log. When I tried to unexport the file-system and unmount the disk, the VFS dies with the all too pleasant "Have a nice day" error. We then rebooted the machine and all of the disks recovered OK. Should I run xfs_repair manually, or is the recovery XFS runs at mount sufficient? Any ideas on how we can avoid this in the future? Thanks! -poul Sep 7 14:01:05 albatross kernel: qlogicfc0 : RSCN Received Sep 7 14:01:05 albatross kernel: qlogicfc0 : Fabric found. Sep 7 14:01:05 albatross kernel: qlogicfc0 : Error performing port login 4008 Sep 7 14:01:05 albatross kernel: qlogicfc0 : Port Database Sep 7 14:01:05 albatross kernel: wwn: 210000e08b02bcf9 scsi_id: 0 loop_id: 0 Sep 7 14:01:05 albatross kernel: wwn: 210000e08b02e5f9 scsi_id: 1 loop_id: Not Available Sep 7 14:01:05 albatross kernel: wwn: 201200208d010d71 scsi_id: 2 loop_id: Not Available Sep 7 14:01:05 albatross kernel: wwn: 201000208d010d71 scsi_id: 3 loop_id: 81 Sep 7 14:01:05 albatross kernel: wwn: 201300208d010d71 scsi_id: 4 loop_id: 82 Sep 7 14:01:05 albatross kernel: wwn: 201100208d010d71 scsi_id: 5 loop_id: 83 Sep 7 14:01:05 albatross kernel: wwn: 210000e08b02dcf9 scsi_id: 6 loop_id: 84 Sep 7 14:01:37 albatross kernel: qlogicfc0 : scsi abort failure: 4006 Sep 7 14:01:37 albatross kernel: qlogicfc0 : abort failed Sep 7 14:01:37 albatross kernel: qlogicfc0 : firmware status is 4000 3 Sep 7 14:01:37 albatross kernel: qlogicfc0 : scsi abort failure: 4006 Sep 7 14:01:37 albatross kernel: qlogicfc0 : abort failed Sep 7 14:01:37 albatross kernel: qlogicfc0 : firmware status is 4000 3 ..etc.. Sep 7 14:01:38 albatross kernel: scsi: device set offline - command error recover failed: host 2 channel 0 id 2 lun 0 Sep 7 14:01:38 albatross kernel: SCSI disk error : host 2 channel 0 id 2 lun 0 return code = 6040000 Sep 7 14:01:38 albatross kernel: I/O error: dev 08:21, sector 125941000 Sep 7 14:01:38 albatross kernel: XFS: device 0x821- XFS write error in file system meta-data block 0x781b508 in sd(8,33) Sep 7 14:01:38 albatross kernel: I/O error: dev 08:21, sector 100740168 Sep 7 14:01:38 albatross kernel: I/O error: dev 08:21, sector 100740400 Sep 7 14:01:38 albatross kernel: I/O error: dev 08:21, sector 100741088 ...etc... many many lines here... Sep 7 14:01:40 albatross kernel: I/O error: dev 08:21, sector 16864360 Sep 7 14:01:40 albatross kernel: I/O error: dev 08:21, sector 25165825 Sep 7 14:01:40 albatross kernel: I/O error: dev 08:21, sector 25165848 Sep 7 14:01:40 albatross kernel: I/O error: dev 08:21, sector 25168072 Sep 7 14:01:40 albatross kernel: I/O error: dev 08:21, sector 25173472 Sep 7 14:01:44 albatross kernel: SCSI disk error : host 2 channel 0 id 2 lun 0 return code = 6040000 Sep 7 14:01:44 albatross kernel: I/O error: dev 08:21, sector 125829376 Sep 7 14:01:44 albatross kernel: xfs_force_shutdown(sd(8,33),0x2) called from line 942 of file xfs_log.c. Return address = 0xc01d580d Sep 7 14:01:44 albatross kernel: I/O Error Detected. Shutting down filesystem: sd(8,33) Sep 7 14:01:45 albatross kernel: Please umount the filesystem, and rectify the problem(s) Sep 7 14:01:45 albatross kernel: I/O error: dev 08:21, sector 42011112 Sep 7 14:01:45 albatross kernel: xfs_force_shutdown(sd(8,33),0x2) called from line 714 of file xfs_log.c. Return address = 0xc01d5527 Sep 7 14:01:45 albatross kernel: xfs_force_shutdown(sd(8,33),0x2) called from line 714 of file xfs_log.c. Return address = 0xc01d5527 Sep 7 14:01:45 albatross kernel: SCSI disk error : host 2 channel 0 id 2 lun 0 return code = 6040000 Sep 7 14:01:45 albatross kernel: I/O error: dev 08:21, sector 41969056 Sep 7 14:01:45 albatross kernel: SCSI disk error : host 2 channel 0 id 2 lun 0 return code = 6040000 Sep 7 14:01:45 albatross kernel: I/O error: dev 08:21, sector 92286648 Sep 7 14:01:45 albatross kernel: I/O error: dev 08:21, sector 92286655 Sep 7 14:01:45 albatross kernel: xfs_force_shutdown(sd(8,33),0x2) called from line 942 of file xfs_log.c. Return address = 0xc01d580d Sep 7 14:01:45 albatross kernel: I/O error: dev 08:21, sector 67525328 Sep 7 14:01:45 albatross kernel: I/O error in filesystem ("sd(8,33)") meta-data dev 0x821 block 0x4065ad0: Sep 7 14:01:45 albatross kernel: xfs_trans_read_buf --- scsi_scan.c.orig Mon Jul 23 09:24:53 2001 +++ scsi_scan.c Thu Jul 26 16:29:14 2001 @@ -153,6 +153,8 @@ {"DELL", "PSEUDO DEVICE .", "*", BLIST_SPARSELUN}, // Dell PV 530F {"DELL", "PV530F", "*", BLIST_SPARSELUN}, // Dell PV 530F {"EMC", "SYMMETRIX", "*", BLIST_SPARSELUN}, + {"CMD", "CRA-7280", "*", BLIST_SPARSELUN}, // CMD RAID Controller + {"Zzyzx", "RocketStor 2000S", "*", BLIST_SPARSELUN}, // Zzyzx RocketStor Raid {"SONY", "TSL", "*", BLIST_FORCELUN}, // DDS3 & DDS4 autoloaders {"DELL", "PERCRAID", "*", BLIST_FORCELUN}, {"HP", "NetRAID-4M", "*", BLIST_FORCELUN}, @@ -565,20 +567,26 @@ } /* - * Check the peripheral qualifier field - this tells us whether LUNS - * are supported here or not. + * Check for SPARSELUN before checking the peripheral qualifier, + * so sparse lun devices are completely scanned. */ - if ((scsi_result[0] >> 5) == 3) { - scsi_release_request(SRpnt); - return 0; /* assume no peripheral if any sort of error */ - } /* * Get any flags for this device. */ bflags = get_device_flags (scsi_result); - + if (bflags & BLIST_SPARSELUN) { + *sparse_lun = 1; + } + /* + * Check the peripheral qualifier field - this tells us whether LUNS + * are supported here or not. + */ + if ((scsi_result[0] >> 5) == 3) { + scsi_release_request(SRpnt); + return 0; /* assume no peripheral if any sort of error */ + } /* The Toshiba ROM was "gender-changed" here as an inline hack. This is now much more generic. This is a mess: What we really want is to leave the scsi_result From owner-linux-xfs@oss.sgi.com Fri Sep 7 23:04:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8864WA28407 for linux-xfs-outgoing; Fri, 7 Sep 2001 23:04:32 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8864Ud28388 for ; Fri, 7 Sep 2001 23:04:30 -0700 Received: from idcomm.com (IDENT:olWK+amd5CygftXhVjK8BazaslJ45HzK@x2-pip57.idcomm.com [209.60.72.68]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f886EaQ10485 for ; Sat, 8 Sep 2001 00:14:36 -0600 Message-ID: <3B99B55E.CF8F4F16@idcomm.com> Date: Sat, 08 Sep 2001 00:06:22 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 To: "XFS: linux-xfs@oss.sgi.com" Subject: ".", "..", and cd Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is probably not an XFS question per se, but might be, I'm not sure. I use XFS on the root system, and am working on some directory and file scanning code. One of the banes of this is to scan for files or directories beginning with ".", without always viewing the current directory and its parent directory, "..". While doing some testing of special cases, I discovered that if I look for files in the root directory "/" (on XFS), through the "glob" function (which presumably is used in code of some shells for its pattern matching), looking for files of pattern ".*", then doing so in "/" results in both "/./" (I have the flag set to append "/" to the end of directory values) and "/../". This latter entry is a curiosity, seeing as the root partition does not have a parent. If I cd to "/", and then do "cd ..", there is no error either, I just end up where I started. Is this the standard, expected behavior (possibly POSIX or HFS designated)? Or would different filesystems behave differently, where some complain about "cd .." when already in the root? At this point it is really nothing more than a curiosity, but it sticks out during testing. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Fri Sep 7 23:13:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f886Dqh28690 for linux-xfs-outgoing; Fri, 7 Sep 2001 23:13:52 -0700 Received: from mail.fmonkey.net (24-28-209-226.ff.cox.rr.com [24.28.209.226]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f886Dmd28671 for ; Fri, 7 Sep 2001 23:13:48 -0700 Received: (qmail 8467 invoked from network); 8 Sep 2001 06:12:31 -0000 Received: from softdnserror (HELO galadriel) (192.168.11.1) by 192.168.11.25 with SMTP; 8 Sep 2001 06:12:31 -0000 From: "Adam H. Pendleton" To: , Subject: RE: ".", "..", and cd Date: Sat, 8 Sep 2001 02:13:08 -0400 Message-ID: <000101c1382d$60694500$fb0aa8c0@galadriel> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <3B99B55E.CF8F4F16@idcomm.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I don't have the "correct" answer to this question, but I am using a box with reiserfs as its root partition (shh, it's my dirty little secret -- don't tell anyone), and a "cd .." on the root partition gives me no error. Adam H. Pendleton -----Original Message----- From: owner-linux-xfs@oss.sgi.com [mailto:owner-linux-xfs@oss.sgi.com] On Behalf Of D. Stimits Sent: Saturday, September 08, 2001 02:06 To: XFS: linux-xfs@oss.sgi.com Subject: ".", "..", and cd This is probably not an XFS question per se, but might be, I'm not sure. I use XFS on the root system, and am working on some directory and file scanning code. One of the banes of this is to scan for files or directories beginning with ".", without always viewing the current directory and its parent directory, "..". While doing some testing of special cases, I discovered that if I look for files in the root directory "/" (on XFS), through the "glob" function (which presumably is used in code of some shells for its pattern matching), looking for files of pattern ".*", then doing so in "/" results in both "/./" (I have the flag set to append "/" to the end of directory values) and "/../". This latter entry is a curiosity, seeing as the root partition does not have a parent. If I cd to "/", and then do "cd ..", there is no error either, I just end up where I started. Is this the standard, expected behavior (possibly POSIX or HFS designated)? Or would different filesystems behave differently, where some complain about "cd .." when already in the root? At this point it is really nothing more than a curiosity, but it sticks out during testing. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Fri Sep 7 23:18:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f886I8u28875 for linux-xfs-outgoing; Fri, 7 Sep 2001 23:18:08 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f886I5d28856 for ; Fri, 7 Sep 2001 23:18:05 -0700 Received: (qmail 29707 invoked from network); 8 Sep 2001 06:18:01 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 8 Sep 2001 06:18:01 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 4D514300090; Sat, 8 Sep 2001 16:17:14 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 2C86EAA; Sat, 8 Sep 2001 16:17:14 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: stimits@idcomm.com Cc: "XFS: linux-xfs@oss.sgi.com" Subject: Re: ".", "..", and cd In-reply-to: Your message of "Sat, 08 Sep 2001 00:06:22 CST." <3B99B55E.CF8F4F16@idcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Sep 2001 16:17:08 +1000 Message-ID: <4765.999929828@ocs3.intra.ocs.com.au> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 08 Sep 2001 00:06:22 -0600, "D. Stimits" wrote: >If I cd to "/", and then do "cd ..", there is no error either, >Is this the standard, expected behavior (possibly POSIX or HFS >designated)? Every hierarchical filesystem I have ever worked on has this behaviour, / is its own parent. Even non-Unix hierarchical systems do this. From owner-linux-xfs@oss.sgi.com Sat Sep 8 00:26:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f887QuA29802 for linux-xfs-outgoing; Sat, 8 Sep 2001 00:26:56 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f887Qpd29782 for ; Sat, 8 Sep 2001 00:26:51 -0700 Received: from idcomm.com (IDENT:i6mVzjMmujgFTaggmfFy1kGerRW0an/M@x2-pip57.idcomm.com [209.60.72.68]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f887awQ15465 for ; Sat, 8 Sep 2001 01:36:58 -0600 Message-ID: <3B99C8AF.57BBDA78@idcomm.com> Date: Sat, 08 Sep 2001 01:28:47 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: "XFS: linux-xfs@oss.sgi.com" Subject: Re: ".", "..", and cd References: <4765.999929828@ocs3.intra.ocs.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Keith Owens wrote: > > On Sat, 08 Sep 2001 00:06:22 -0600, > "D. Stimits" wrote: > >If I cd to "/", and then do "cd ..", there is no error either, > >Is this the standard, expected behavior (possibly POSIX or HFS > >designated)? > > Every hierarchical filesystem I have ever worked on has this behaviour, > / is its own parent. Even non-Unix hierarchical systems do this. Ok, this makes sense, it allows a state-machine description with no undefined state when it is defined that "." and ".." are properties of every node. (an arrow circling back to point at the node it starts from) D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Sat Sep 8 00:37:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f887bgD30054 for linux-xfs-outgoing; Sat, 8 Sep 2001 00:37:42 -0700 Received: from dms.digistar.com (root@digistar.com [216.88.176.30]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f887bcd30034 for ; Sat, 8 Sep 2001 00:37:38 -0700 Received: from localhost (alanb@localhost) by dms.digistar.com (8.12.0.Beta19/8.11.5) with ESMTP id f887baej001822 for ; Sat, 8 Sep 2001 02:37:37 -0500 Date: Sat, 8 Sep 2001 02:37:36 -0500 (CDT) From: Alan Brown To: Subject: Patch comments. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk 1: Judicious use of the --exclude-from directive will keep your patch virgin vs third party stuff you may have incorporated to your source tree. Right now your filesystem patch is fundamentally incompatible with things like Alan Cox's jumbo patches because of this. Also your inclusion of non-related code may interfere with application of other single patches people may be applying. 2: Why submit these to Linus? The guy is snowed under and has more pressing priorities right now in his life than including patches to stable code (other than bugfixes). You're really better off cleaning up your patches and feeding them to Alan Cox. There's a large pool of ac-testers out there, your code will get tested and debugged faster this way and you'll end up in the mainstream kernel tree that much more quickly. (incidentally, Linus' priorities are why 2.4.* releases are such a pig right now. The ac trees are more stable in my experience.) AB From owner-linux-xfs@oss.sgi.com Sat Sep 8 05:42:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f88CgeB01672 for linux-xfs-outgoing; Sat, 8 Sep 2001 05:42:40 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f88Cgbd01653 for ; Sat, 8 Sep 2001 05:42:37 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id 260F8139E0; Sat, 8 Sep 2001 08:42:34 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: kernel-BOOT? Message-Id: <20010908124234.260F8139E0@linux.compucomis.net> Date: Sat, 8 Sep 2001 08:42:34 -0400 (EDT) From: mburger@compucomis.net (Mike Burger) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Well, after seeming to again lose the /var filesystem, I went ahead and replaced the drive where it was stored...all seems to be well, now, with it. So, I thought I'd go ahead and upgrade to the 2.4.5-SGI_XFS kernel. I've downloaded each of the processor specific rpms (deciding which I'll use), as well as the kernel headers and kernel-source packages. I'm wondering, though, about the kernel-BOOT package. I noticed that the SGI installer did not install that package on my system, so I was wondering what the kernel-BOOT package is/does, and whether or not I need it for anything. Thanks. --Mike From owner-linux-xfs@oss.sgi.com Sat Sep 8 06:43:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f88DhLW02652 for linux-xfs-outgoing; Sat, 8 Sep 2001 06:43:21 -0700 Received: from mta01ps.bigpond.com (juicer46.bigpond.com [144.135.25.133]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f88DhDd02625 for ; Sat, 8 Sep 2001 06:43:13 -0700 Received: from HERCULES ([144.135.25.81]) by mta01ps.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GJCJQ400.12P for ; Sat, 8 Sep 2001 23:49:16 +1000 Received: from CPE-61-9-140-28.vic.bigpond.net.au ([61.9.140.28]) by psmam05.mailsvc.email.bigpond.com(MailRouter V2.9i 8410/4021714); 08 Sep 2001 23:49:16 Content-Type: text/plain; charset="iso-8859-1" From: Adrian Head Reply-To: adrian.head@bytecomm.com.au To: linux-xfs@oss.sgi.com Subject: Problems with many processes copying large directories across an XFS volume. Date: Sat, 8 Sep 2001 23:43:07 +1000 X-Mailer: KMail [version 1.2] Organization: Bytecomm P/L MIME-Version: 1.0 Message-Id: <01090823430700.01184@HERCULES> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am in the process of building a couple of file servers for various purposes and over the last week have been running quite a few tests in an attempt to determine if I trust the hardware/software combination enough for it to be put into production. One of the tests I was doing was trying to simulate many users copying large directories across an XFS volume. To do this I was generating many background jobs copying a 4G directory to another directory on the XFS volume. eg. #>cp -r 001 002& #>cp -r 001 003& #>cp -r 001 004& ..... ..... #>cp -r 001 019& #>cp -r 001 020& Everything would start fine but less than a minute into the test various hundreds of errors are displayed like: cp: cannot stat file `/mnt/raid5/filename`: Input/output error Once this has happened the XFS volume disappears. By this I mean that it is still mounted but all files and directories are no longer visible using ls. Any other file activity results in an Input/Output error. Once I unmount & mount the volume again the data is again visible up to the point where the copy failed. In the /var/log/messages log around the same time as the copy test I get entries like: Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device The problem is reproduceable on XFS volumes on a 2 disk (IDE) raid0 (SW raid) partition and on a 5 disk (IDE) raid5 (SW raid) partition. However, there is no problem with the copy test using ext2 volumes on the above partitions. The copy test also passes when run on a non-raid drive. I am using Kernel 2.4.9 and the relevant latest XFS patch from the patches directory on the XFS ftp site. patch-2.4.9-xfs-2001-08-19 The thing that really puzzles me is that the above directory copy test runs fine when I only have 10 background copy jobs running at a time. As soon as I have 20 background copy jobs running the problem occurs. The system passes both bonnie++ and mongo.pl tests/benchmarks. So from the results I have at the moment it would seem that XFS is stomping over the raid code or the raid code is stomping over XFS. Should I cross post this to the raid list as well? P.S. I have just noticed on the mailing list archive a note about fixing a problem that caused mongo.pl to hang. Although my systems don't hang in mongo do people think I'm seeing the same problem just a different symptom? Another issue that I think is not related is that when using the 2.4.9-xfs kernel, when the kernel identifies the drives during bootup I get IRQ probe failed errors. hda: IC35L040AVER07-0, ATA DISK drive hda: IRQ probe failed (0xfffffff8) hdb: IC35L040AVER07-0, ATA DISK drive hdb: IRQ probe failed (0xfffffff8) ........the rest as normal The errors occur when the kernel is run on an ASUS A7V133 motherboard but not on a ASUS A7V133C. The errors don't happen with a native 2.4.9 kernel either. Since the errors occur for the 2 drives on the 1st channel of the 1st IDE controller (which is not related to the raid arrays mentioned above) and the system still boots - I have not been worried about it. Should I be worried? At this stage I'm unsure what other info people would like. If anyone wants logs, config files, more information or more testing please tell me. Thanks for your time. Adrian Head Bytecomm P/L From owner-linux-xfs@oss.sgi.com Sat Sep 8 09:30:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f88GUcu05000 for linux-xfs-outgoing; Sat, 8 Sep 2001 09:30:38 -0700 Received: from picklock.adams.family ([145.254.147.195]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f88GUWd04981 for ; Sat, 8 Sep 2001 09:30:33 -0700 Received: from loewe-komp.de (localhost [127.0.0.1]) by picklock.adams.family (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id f88GXjL16623 for ; Sat, 8 Sep 2001 18:33:45 +0200 Message-ID: <3B9A4869.1FF5D169@loewe-komp.de> Date: Sat, 08 Sep 2001 18:33:45 +0200 From: Peter =?iso-8859-1?Q?W=E4chtler?= Organization: B16 X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.4.9-ac5 i686) X-Accept-Language: de, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Patch comments. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Alan Brown wrote: > > 1: Judicious use of the --exclude-from directive will keep your patch > virgin vs third party stuff you may have incorporated to your source > tree. > > Right now your filesystem patch is fundamentally incompatible with > things like Alan Cox's jumbo patches because of this. > > Also your inclusion of non-related code may interfere with application > of other single patches people may be applying. > > 2: Why submit these to Linus? The guy is snowed under and has more > pressing priorities right now in his life than including patches to > stable code (other than bugfixes). > > You're really better off cleaning up your patches and feeding them to > Alan Cox. There's a large pool of ac-testers out there, your code will > get tested and debugged faster this way and you'll end up in the > mainstream kernel tree that much more quickly. I want to second this. New functionality like drivers or even filesystems should first be included in the -ac series of the Linux kernel. The other option would be to include it in 2.5 - but this will give you: no xfs in "user" kernel for the next year ;) From owner-linux-xfs@oss.sgi.com Sat Sep 8 12:02:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f88J2ws06434 for linux-xfs-outgoing; Sat, 8 Sep 2001 12:02:58 -0700 Received: from c4solutions.net (IDENT:qmailr@mail.c4solutions.net [216.143.5.130]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f88J2ud06415 for ; Sat, 8 Sep 2001 12:02:56 -0700 Received: (qmail 865 invoked by uid 100); 8 Sep 2001 19:02:53 -0000 To: linux-xfs@oss.sgi.com Subject: Kickstart on Bootable CDROM Message-ID: <999975773.3b9a6b5d2b4e0@www.c4solutions.net> Date: Sat, 08 Sep 2001 15:02:53 -0400 (EDT) From: Barrett Gay MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.6 X-Originating-IP: 216.143.5.139 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm trying to create an automated install using kickstart off a bootable cd. I specify the install method as "cdrom" in my ks.cfg on the cd. When I boot the cd, it gives me the error: "No install method specified in Kickstart". However, if I use the same image (with the same kickstart file) on a floppy, the install goes fine. Any ideas? Should I specify the install method as Harddrive and point it to /tmp/cdrom? Thanks, Barrett From owner-linux-xfs@oss.sgi.com Sat Sep 8 17:43:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f890hRb11429 for linux-xfs-outgoing; Sat, 8 Sep 2001 17:43:27 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f890hNd11410 for ; Sat, 8 Sep 2001 17:43:23 -0700 Received: (qmail 1504 invoked from network); 9 Sep 2001 00:43:20 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 9 Sep 2001 00:43:20 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id DEA3D300095; Sun, 9 Sep 2001 10:42:34 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id D23B0AB; Sun, 9 Sep 2001 10:42:34 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: mburger@compucomis.net (Mike Burger) Cc: linux-xfs@oss.sgi.com Subject: Re: kernel-BOOT? In-reply-to: Your message of "Sat, 08 Sep 2001 08:42:34 -0400." <20010908124234.260F8139E0@linux.compucomis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Sep 2001 10:42:29 +1000 Message-ID: <12875.999996149@ocs3.intra.ocs.com.au> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 8 Sep 2001 08:42:34 -0400 (EDT), mburger@compucomis.net (Mike Burger) wrote: >I'm wondering, though, about the kernel-BOOT package. I noticed that >the SGI installer did not install that package on my system, so I was >wondering what the kernel-BOOT package is/does, and whether or not I >need it for anything. rpm -qip /mnt/cdrom/RedHat/RPMS/kernel-BOOT-2.4.2-2.i386.rpm This package includes a trimmed down version of the Linux kernel. This kernel is used on the installation boot disks only and should not be used for an installed system, as many features in this kernel are turned off because of the size constraints. From owner-linux-xfs@oss.sgi.com Sat Sep 8 18:45:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f891j2L12333 for linux-xfs-outgoing; Sat, 8 Sep 2001 18:45:02 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f891ixd12304 for ; Sat, 8 Sep 2001 18:44:59 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id 20B21139E4; Sat, 8 Sep 2001 21:45:07 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id 1D6FB139DC; Sat, 8 Sep 2001 21:45:07 -0400 (EDT) Date: Sat, 8 Sep 2001 21:45:07 -0400 (EDT) From: Mike Burger To: Keith Owens Cc: Subject: Re: kernel-BOOT? In-Reply-To: <12875.999996149@ocs3.intra.ocs.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Aaahhh...thanks. That explains it. On Sun, 9 Sep 2001, Keith Owens wrote: > On Sat, 8 Sep 2001 08:42:34 -0400 (EDT), > mburger@compucomis.net (Mike Burger) wrote: > >I'm wondering, though, about the kernel-BOOT package. I noticed that > >the SGI installer did not install that package on my system, so I was > >wondering what the kernel-BOOT package is/does, and whether or not I > >need it for anything. > > rpm -qip /mnt/cdrom/RedHat/RPMS/kernel-BOOT-2.4.2-2.i386.rpm > This package includes a trimmed down version of the Linux kernel. > This kernel is used on the installation boot disks only and should > not be used for an installed system, as many features in this kernel > are turned off because of the size constraints. > > From owner-linux-xfs@oss.sgi.com Sun Sep 9 02:59:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f899xoU18361 for linux-xfs-outgoing; Sun, 9 Sep 2001 02:59:50 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f899xMd18341 for ; Sun, 9 Sep 2001 02:59:22 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id CAA08654 for ; Sun, 9 Sep 2001 02:59:29 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id UAA27842; Sun, 9 Sep 2001 20:57:56 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id UAA42103; Sun, 9 Sep 2001 20:57:53 +1100 (AEDT) Date: Sun, 9 Sep 2001 20:57:52 +1100 From: Nathan Scott To: Jan Kara , Bret Giddings Cc: linux-xfs@oss.sgi.com, samba-technical@lists.samba.org Subject: [patch] Re: XFS, Quotas and Samba Message-ID: <20010909205752.A397355@wobbly.melbourne.sgi.com> References: <7AC902A40BEDD411A3A800D0B7847B660882F5@sernt14.essex.ac.uk> <20010906105952.B345981@wobbly.melbourne.sgi.com> <20010906123515.A380241@wobbly.melbourne.sgi.com> <20010906163441.C24754@atrey.karlin.mff.cuni.cz> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010906163441.C24754@atrey.karlin.mff.cuni.cz>; from jack@suse.cz on Thu, Sep 06, 2001 at 04:34:41PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline hi, On Thu, Sep 06, 2001 at 04:34:41PM +0200, Jan Kara wrote: > Hello, > > Actually it depends whether the samba code was compiled with > proper kernel headers. If so the Q_GETQUOTA is defined to be > right value and so everything should work fine. Ok, to be more > precise the utils probably won't compile in that case as struct dqblk > is no more and mem_dqblk should be used instead... But anyway it shouldn't > break silently. Hmm ... I can't see any case where the new VFS quota code will work (ie. Jan's patches/AC kernels/Redhat 7.1+) with the smbd code, even if the kernel headers happened to correspond to the running kernel. As I understand it, the new code returns a u64 byte count in one field (curspace) where before there was a u32 block count (curblocks). Is that correct? If so, smbd is in a bit of strife here cos it peeks at that field in particular... I took a stab at implementing the fix for this problem and for XFS quota - the XFS code should be correct, the VFS quota code (v1/v2 stuff) should be too, but I'm less certain on that - see attached patch. The approach is basically to attempt the old Linux quotactl for non-XFS filesystems - if that fails, try the new version. And for XFS filesystems, always use the XFS quotactl command, which is always the right thing to do. Bret - could you let me know if this helps you? cheers. > > > Just a quick followup - this is what I mentioned in my earlier > > mail to you. I think your new VFS quota code (as in Alan Cox's > > series of 2.4 kernels, for the Samba folk) will have exactly the > > same problem as XFS. This "grep" would seem to confirm it - but > > you'll know better than I here: > > > > 11:31 nathans@troppo ~/cvs/quota-tools 73> grep GETQUOTA dqblk*h > > dqblk_rpc.h:#define Q_RPC_GETQUOTA 0x0300 /* get limits and usage */ > > dqblk_v1.h:#define Q_V1_GETQUOTA 0x300 > > dqblk_v2.h:#define Q_V2_GETQUOTA 0x0D00 /* Get limits and usage */ > > dqblk_xfs.h:#define Q_XFS_GETQUOTA Q_XGETQUOTA > > 11:31 nathans@troppo ~/cvs/quota-tools 74> > > > > The samba code does a good old Q_GETQUOTA (ie. your V1 above). > > > > cheers. > > > > > > On Thu, Sep 06, 2001 at 10:59:52AM +1100, Nathan Scott wrote: > > > hi, > > > > > > On Wed, Sep 05, 2001 at 02:57:39PM +0100, Giddings, Bret wrote: > > > > I am investigating whether I can replace my expensive Compaq Alphas file > > > > servers with cheaper (and invariably faster given my budget) Intel based > > > > ones. I have so far been pleased with the ease with which xfs has installed > > > > and run on my hardware of choice. To make my life easier, I have picked up > > > > the pre-built RedHat kernels with xfs support. Everything appears to be fine > > > > except that when connecting to a share from Samba, the amount of free space > > > > reported is the amount of free disk space left on the device rather than the > > > > amount of free space in the users quota (this is on a disk mounted with > > > > usrquota and a quota set for the users). The usual tools (edquota, setquota > > > > work as expected). > > > > > > > > I have downloaded the source rpm for samba and it appears that RedHat build > > > > their smbd to support quotas. I have also checked whether > > > > /usr/include/sys/quota.h is modified by installing your updated quota rpm > > > > (quota-3.01pre8) and it isn't. So, is there another reason why quotas don't > > > > appear to work with xfs/samba? > > > > > > The samba code needs to be updated to support XFS quota under > > > Linux. There was someone on the list a little while ago who > > > was looking to add in the samba support for XFS quota, but I > > > don't know how far they got. > > > > > > I know very little about samba unfortunately, but it should be > > > quite simple to add this stuff for XFS - the disk_quotas() > > > routine in samba-2.2.1a/source/smbd/quotas.c is all that needs > > > to be changed, by the look of things. > > > > > > For XFS filesystems on Linux this needs to: > > > - have logic to handle getmntent's of type "xfs" separately; > > > - issue a quotactl(QCMD(Q_XGETQUOTA,USRQUOTA), ..., &xdq) where > > > xdq is of type "struct fs_disk_quota_t" from > > > - set *bsize to 512 for XFS > > > - refer to the code later in that same file for dealing with XFS > > > on IRIX - basically, do exactly the same thing and it should > > > just work. > > > - to do it properly, the configure scripts will need to check > > > for linux/xqm.h (or might be simpler to keep a local copy? - > > > I dunno what sort of policy the samba folk have on this sort of > > > thing, but this header isn't going to change and probably isn't > > > going to appear in the libc headers for quite awhile...) > > > > > > cheers. > > > > > > -- > > > Nathan > > > > -- > > Nathan > -- > Jan Kara > SuSE Labs -- Nathan --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="smbd+quota.patch" diff -Naur samba-2.2.1a/source/smbd/quotas.c samba-2.2.1a+ns/source/smbd/quotas.c --- samba-2.2.1a/source/smbd/quotas.c Thu Jul 5 21:02:03 2001 +++ samba-2.2.1a+ns/source/smbd/quotas.c Sun Sep 9 09:29:58 2001 @@ -44,13 +44,10 @@ #ifdef LINUX #include -#include +#include #include - #include -#include - -_syscall4(int, quotactl, int, cmd, const char *, special, int, id, caddr_t, addr); +#include "quotas.h" /**************************************************************************** try to get the disk space from disk quotas (LINUX version) @@ -59,18 +56,20 @@ BOOL disk_quotas(char *path, SMB_BIG_UINT *bsize, SMB_BIG_UINT *dfree, SMB_BIG_UINT *dsize) { int r; - struct dqblk D; + v1_kern_dqblk_t D1; + v2_kern_dqblk_t D2; + fs_disk_quota_t DX; SMB_STRUCT_STAT S; FILE *fp; struct mntent *mnt; SMB_DEV_T devno; int found; uid_t euser_id; + static int version = 1; /* VFS quota version */ euser_id = geteuid(); - + /* find the block device file */ - if ( sys_stat(path, &S) == -1 ) { return(False) ; } @@ -91,47 +90,109 @@ endmntent(fp) ; if (!found) { - return(False); - } + return(False); + } save_re_uid(); set_effective_uid(0); - r=quotactl(QCMD(Q_GETQUOTA,USRQUOTA), mnt->mnt_fsname, euser_id, (caddr_t)&D); + if (strcmp(mnt->mnt_type, "xfs") == 0) + r = quotactl(QCMD(Q_XGETQUOTA,USRQUOTA), mnt->mnt_fsname, euser_id, (caddr_t)&DX); + else { + if (version == 1) { + r = quotactl(QCMD(Q_V1_GETQUOTA,USRQUOTA), mnt->mnt_fsname, euser_id, (caddr_t)&D1); + if (r == EINVAL) + version = 2; + } + if (version == 2) + r = quotactl(QCMD(Q_V2_GETQUOTA,USRQUOTA), mnt->mnt_fsname, euser_id, (caddr_t)&D2); + } restore_re_uid(); - /* Use softlimit to determine disk space, except when it has been exceeded */ - *bsize = 1024; if (r) - { - if (errno == EDQUOT) - { - *dfree =0; - *dsize =D.dqb_curblocks; - return (True); - } - else return(False); + return(False); + + if (version == 1) + { + *bsize = 1024; + /* Use softlimit to determine disk space, except when its been exceeded */ + if ( + (D1.dqb_bsoftlimit && D1.dqb_curblocks>=D1.dqb_bsoftlimit) || + (D1.dqb_bhardlimit && D1.dqb_curblocks>=D1.dqb_bhardlimit) || + (D1.dqb_isoftlimit && D1.dqb_curinodes>=D1.dqb_isoftlimit) || + (D1.dqb_ihardlimit && D1.dqb_curinodes>=D1.dqb_ihardlimit) + ) + { + *dfree = 0; + *dsize = D1.dqb_curblocks; + } + else if (D1.dqb_bsoftlimit==0 && D1.dqb_bhardlimit==0) + { + return(False); + } + else + { + if (D1.dqb_bsoftlimit == 0) + D1.dqb_bsoftlimit = D1.dqb_bhardlimit; + *dfree = D1.dqb_bsoftlimit - D1.dqb_curblocks; + *dsize = D1.dqb_bsoftlimit; + } + } + else if (version == 2) + { + *bsize = 1024; + D2.dqb_curspace >>= 10; /* bytes to Kbytes */ + /* Use softlimit to determine disk space, except when its been exceeded */ + if ( + (D2.dqb_bsoftlimit && D2.dqb_curspace >=D2.dqb_bsoftlimit) || + (D2.dqb_bhardlimit && D2.dqb_curspace >=D2.dqb_bhardlimit) || + (D2.dqb_isoftlimit && D2.dqb_curinodes>=D2.dqb_isoftlimit) || + (D2.dqb_ihardlimit && D2.dqb_curinodes>=D2.dqb_ihardlimit) + ) + { + *dfree = 0; + *dsize = D2.dqb_curspace; + } + else if (D2.dqb_bsoftlimit==0 && D2.dqb_bhardlimit==0) + { + return(False); + } + else + { + if (D2.dqb_bsoftlimit == 0) + D2.dqb_bsoftlimit = D2.dqb_bhardlimit; + *dfree = D2.dqb_bsoftlimit - D2.dqb_curspace; + *dsize = D2.dqb_bsoftlimit; + } } - /* Use softlimit to determine disk space, except when it has been exceeded */ - if ( - (D.dqb_bsoftlimit && D.dqb_curblocks>=D.dqb_bsoftlimit) || - (D.dqb_bhardlimit && D.dqb_curblocks>=D.dqb_bhardlimit) || - (D.dqb_isoftlimit && D.dqb_curinodes>=D.dqb_isoftlimit) || - (D.dqb_ihardlimit && D.dqb_curinodes>=D.dqb_ihardlimit) - ) + else if (strcmp(mnt->mnt_type, "xfs") == 0) + { + *bsize = 512; + /* Use softlimit to determine disk space, except when its been exceeded */ + if ( + (DX.d_blk_softlimit && DX.d_bcount>=DX.d_blk_softlimit) || + (DX.d_blk_hardlimit && DX.d_bcount>=DX.d_blk_hardlimit) || + (DX.d_ino_softlimit && DX.d_icount>=DX.d_ino_softlimit) || + (DX.d_ino_hardlimit && DX.d_icount>=DX.d_ino_hardlimit) + ) { *dfree = 0; - *dsize = D.dqb_curblocks; + *dsize = DX.d_bcount; } - else if (D.dqb_bsoftlimit==0 && D.dqb_bhardlimit==0) + else if (DX.d_blk_softlimit==0 && DX.d_blk_hardlimit==0) { return(False); } - else { - if (D.dqb_bsoftlimit == 0) - D.dqb_bsoftlimit = D.dqb_bhardlimit; - *dfree = D.dqb_bsoftlimit - D.dqb_curblocks; - *dsize = D.dqb_bsoftlimit; + else + { + *dfree = (DX.d_blk_softlimit - DX.d_bcount); + *dsize = DX.d_blk_softlimit; + } } + else + { + return(False); + } + return (True); } diff -Naur samba-2.2.1a/source/smbd/quotas.h samba-2.2.1a+ns/source/smbd/quotas.h --- samba-2.2.1a/source/smbd/quotas.h Wed Dec 31 19:00:00 1969 +++ samba-2.2.1a+ns/source/smbd/quotas.h Sun Sep 9 09:29:58 2001 @@ -0,0 +1,58 @@ +#ifdef LINUX + +#define Q_V1_GETQUOTA 0x0300 /* VFS quota, version 1 */ +#define Q_V2_GETQUOTA 0x0D00 /* VFS quota, version 2 */ +#define Q_XGETQUOTA (('X'<<8)+0x3) /* XFS quota */ + +/* struct for Q_V1_GETQUOTA */ +typedef struct v1_kern_dqblk { + u_int32_t dqb_bhardlimit; /* absolute limit on disk blks alloc */ + u_int32_t dqb_bsoftlimit; /* preferred limit on disk blks */ + u_int32_t dqb_curblocks; /* current block count */ + u_int32_t dqb_ihardlimit; /* maximum # allocated inodes */ + u_int32_t dqb_isoftlimit; /* preferred inode limit */ + u_int32_t dqb_curinodes; /* current # allocated inodes */ + time_t dqb_btime; /* time limit for excessive disk use */ + time_t dqb_itime; /* time limit for excessive files */ +} v1_kern_dqblk_t; + +/* struct for Q_V2_GETQUOTA */ +typedef u_int64_t qsize_t; +typedef struct v2_kern_dqblk { + unsigned int dqb_ihardlimit; + unsigned int dqb_isoftlimit; + unsigned int dqb_curinodes; + unsigned int dqb_bhardlimit; + unsigned int dqb_bsoftlimit; + qsize_t dqb_curspace; + time_t dqb_btime; + time_t dqb_itime; +} v2_kern_dqblk_t; + +/* struct for Q_XGETQUOTA */ +typedef struct fs_disk_quota { + __s8 d_version; /* version of this structure */ + __s8 d_flags; /* XFS_{USER,PROJ,GROUP}_QUOTA */ + __u16 d_fieldmask; /* field specifier */ + __u32 d_id; /* user, project, or group ID */ + __u64 d_blk_hardlimit; /* absolute limit on disk blks */ + __u64 d_blk_softlimit; /* preferred limit on disk blks */ + __u64 d_ino_hardlimit; /* maximum # allocated inodes */ + __u64 d_ino_softlimit; /* preferred inode limit */ + __u64 d_bcount; /* # disk blocks owned by the user */ + __u64 d_icount; /* # inodes owned by the user */ + __s32 d_itimer; /* zero if within inode limits */ + __s32 d_btimer; /* similar to above; for disk blocks */ + __u16 d_iwarns; /* # warnings issued wrt num inodes */ + __u16 d_bwarns; /* # warnings issued wrt disk blocks */ + __s32 d_padding2; /* padding2 - for future use */ + __u64 d_rtb_hardlimit; /* absolute limit on realtime blks */ + __u64 d_rtb_softlimit; /* preferred limit on RT disk blks */ + __u64 d_rtbcount; /* # realtime blocks owned */ + __s32 d_rtbtimer; /* similar to above; for RT disk blks */ + __u16 d_rtbwarns; /* # warnings issued wrt RT disk blks */ + __s16 d_padding3; /* padding3 - for future use */ + char d_padding4[8]; /* yet more padding */ +} fs_disk_quota_t; + +#endif /* LINUX */ --82I3+IH0IqGh5yIs-- From owner-linux-xfs@oss.sgi.com Sun Sep 9 04:22:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f89BMPG21847 for linux-xfs-outgoing; Sun, 9 Sep 2001 04:22:25 -0700 Received: from exocore.com ([202.4.185.25]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f89BMJd21385 for ; Sun, 9 Sep 2001 04:22:20 -0700 Received: (from shanu@localhost) by exocore.com (8.11.6/8.11.6) id f89BMcW03319 for linux-xfs@oss.sgi.com; Sun, 9 Sep 2001 16:52:38 +0530 Date: Sun, 9 Sep 2001 16:52:38 +0530 From: Shanker Balan To: Linux-XFS Subject: Re: Umask bug in the Installer - Solved? Message-ID: <20010909165238.E1750@exocore.com> Reply-To: Shanker Balan Mail-Followup-To: Linux-XFS References: <3B8BA1ED.8B5CCBC3@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: <3B8BA1ED.8B5CCBC3@sgi.com>; from sandeen@sgi.com on Tue, Aug 28, 2001 at 08:51:41AM -0500 Organisation: Exocore Consulting (P) Ltd Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello: Eric Sandeen wrote, > We did not re-spin the original ISO, but if you use one of the two > above methods when installing, everything will be fine... Ok. I will use the updated boot floppy meth0d. Thank you for your time. -- Darth Vader: Your powers are weak, old man. Ben (Obi-Wan) Kenobi: You can't win, Darth. If you strike me down, I shall become more powerful than you could possibly imagine. From owner-linux-xfs@oss.sgi.com Sun Sep 9 09:03:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f89G3QL28292 for linux-xfs-outgoing; Sun, 9 Sep 2001 09:03:26 -0700 Received: from mail21.jump.net (mail21.jump.net [206.196.91.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f89G3Nd28273 for ; Sun, 9 Sep 2001 09:03:24 -0700 Received: from there (jump-redback-BRYA0012.jump.net [216.30.81.5] (may be forged)) by mail21.jump.net (8.11.6/) with SMTP id f89G3NM22280 for ; Sun, 9 Sep 2001 11:03:23 -0500 (CDT) Message-Id: <200109091603.f89G3NM22280@mail21.jump.net> Content-Type: text/plain; charset="iso-8859-1" From: Bryan Payne Reply-To: damasta@teknospy.com To: linux-xfs@oss.sgi.com Subject: Mounting onboard raid Date: Sun, 9 Sep 2001 11:05:32 -0500 X-Mailer: KMail [version 1.3.1] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have onboard raid. I only use it so I can have 8 drives so there is actually no raid running. Here is the situation: I have 3 harddrives. Hda has a swap, an ext2 boot and a xfs root. Hdb is xfs and Hdg is xfs. If I attempt to mount hdg1, I get the wrong fs type error. However, I moved hdg to to hdb and it mounts fine. Is this because of the highpoint controller? The funny thing is I can mount hdg as vfat. I haven't tried it as ext2 though. Any suggestions? -- Linux, Multimedia and More... http://www.teknospy.com From owner-linux-xfs@oss.sgi.com Sun Sep 9 10:15:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f89HFsw29060 for linux-xfs-outgoing; Sun, 9 Sep 2001 10:15:54 -0700 Received: from sciurus.rentec.com (sciurus.rentec.com [192.5.35.161]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f89HFkd29041 for ; Sun, 9 Sep 2001 10:15:46 -0700 Received: from rentec.com (pooh [172.16.99.2]) by sciurus.rentec.com (8.11.3/8.11.3) with ESMTP id f89HFab22853; Sun, 9 Sep 2001 13:15:37 -0400 (EDT) Message-ID: <3B9BA43B.5020904@rentec.com> Date: Sun, 09 Sep 2001 13:17:47 -0400 From: Dirk Wetter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3+) Gecko/20010817 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com CC: Karsten =?ISO-8859-1?Q?K=FCnne?= Subject: 10minutes for rm -rf on 400MB Content-Type: multipart/alternative; boundary="------------060407080307050309050409" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --------------060407080307050309050409 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, we've been running XFS on the data disks of our HPC Linux cluster since a while. we are quite happy with xfs, thx guys for your work! the setup is: - dual >=1GHZ box, 4GB mem - lvm 0.9beta7, phys. volume size ~140 GB, logical vol for xfs: 100GB - no additional mount options or options for mkfs.xfs were given - kernel 2.4.8pre4-xfs, highly patched SuSE 7.0 (not that it should matter) a user complained that /rm -rf of 400MB / takes ~10 minutes (!) until the command returns, whereas on the systems with reiserfs we have e.g. it takes seconds. i don't know so much about the quality of the data, my guess is that some files are small (~100k), others a big (a few hundred MB). i read in the FAQ that XFS isn't particular good in rm-rf'ing files, which isn't really *the *issue for us, because in 99.9%of the time data is being read from the volume and not removed via rm -rf. is there an mount/filecreation option to tweak without loosing performance while reading? cheers, ~dirkw --------------060407080307050309050409 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
Hi,

we've been running XFS on the data disks of our HPC Linux cluster since
a while. we are quite happy with xfs, thx guys for your work!
the setup is:

- dual >=1GHZ box, 4GB mem
- lvm 0.9beta7, phys. volume size ~140 GB, logical vol for xfs: 100GB
- no additional mount options or options for mkfs.xfs were given
- kernel 2.4.8pre4-xfs, highly patched SuSE 7.0 (not that it should matter)

a user complained that rm -rf of 400MB  takes ~10 minutes (!) until the
command returns, whereas on the systems with reiserfs we have e.g. it
takes seconds.

i don't know so much about the quality of the data, my guess is that some files
are small (~100k), others a big (a few hundred MB). i read in the FAQ that
XFS isn't particular good in rm-rf'ing  files, which isn't really the issue for
us, because in 99.9%of the time data is being read from the volume and not
removed via rm -rf.

is there an mount/filecreation option to tweak without loosing performance while
reading?



cheers,
                ~dirkw





--------------060407080307050309050409-- From owner-linux-xfs@oss.sgi.com Sun Sep 9 15:06:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f89M6h331969 for linux-xfs-outgoing; Sun, 9 Sep 2001 15:06:43 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f89M6fd31950 for ; Sun, 9 Sep 2001 15:06:41 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f89M6YB14098 for linux-xfs@oss.sgi.com; Sun, 9 Sep 2001 18:06:34 -0400 Date: Sun, 9 Sep 2001 18:06:34 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: ftp.thebarn.com Message-ID: <20010909180634.A14095@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Is Russell's CVSup daemon dead? Or is something else wrong? I can traceroute it but I can't do a CVSup connect. :( -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Sun Sep 9 16:58:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f89NwrO00371 for linux-xfs-outgoing; Sun, 9 Sep 2001 16:58:53 -0700 Received: from ente.berdmann.de (frnk-d5141a34.dsl.mediaWays.net [213.20.26.52]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f89Nwmd00352 for ; Sun, 9 Sep 2001 16:58:48 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.22 #1) id 15gETJ-00030Q-00; Mon, 10 Sep 2001 01:58:41 +0200 Message-ID: <3B9C0231.67E2BF01@berdmann.de> Date: Mon, 10 Sep 2001 01:58:41 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.10-pre4-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Dirk Wetter CC: Linux XFS Mailing List Subject: Re: 10minutes for rm -rf on 400MB References: <3B9BF400.1050900@rentec.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >we've been running XFS on the data disks of our HPC Linux cluster since
>a while. we are quite happy with xfs, thx guys for your work!
>the setup is:
>
>- dual >=1GHZ box, 4GB mem
>- lvm 0.9beta7, phys. volume size ~140 GB, logical vol for xfs: 100GB
>- no additional mount options or options for mkfs.xfs were given
>- kernel 2.4.8pre4-xfs, highly patched SuSE 7.0 (not that it should matter)
>
>a user complained that rm -rf of 400MB  takes ~10 minutes (!) until >the
>command returns, whereas on the systems with reiserfs we have e.g. it
>takes seconds.
Some very important data is missing: - what's the I/O performance of the disk subsystem? - what was the system doing during the observed 10 min? CPU power doesn't count as much as disk I/O performance because unlink(2) on XFS is a synchronous operation. >i don't know so much about the quality of the data, my guess is that some >files
>are small (~100k), others a big (a few hundred MB). i read in the FAQ that
>XFS isn't particular good in rm-rf'ing  files, which isn't really the >issue for
>us, because in 99.9%of the time data is being read from the volume and not >
>removed via rm -rf.
So, three files à 100 MB and 1,024 files à 100 KB are 400 MB in sum and even a busy system shouldn't take 10 min for deleting 1,027 files. I guess your estimate of the file sizes is slightly wrong. From owner-linux-xfs@oss.sgi.com Sun Sep 9 17:40:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A0etH00847 for linux-xfs-outgoing; Sun, 9 Sep 2001 17:40:55 -0700 Received: from sciurus.rentec.com (sciurus.rentec.com [192.5.35.161]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A0eld00828 for ; Sun, 9 Sep 2001 17:40:48 -0700 Received: from rentec.com (pooh [172.16.99.2]) by sciurus.rentec.com (8.11.3/8.11.3) with ESMTP id f8A0eeb22988; Sun, 9 Sep 2001 20:40:40 -0400 (EDT) Message-ID: <3B9C0C8B.2070201@rentec.com> Date: Sun, 09 Sep 2001 20:42:51 -0400 From: Dirk Wetter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3+) Gecko/20010817 X-Accept-Language: en-us MIME-Version: 1.0 To: "Bernhard R. Erdmann" CC: Linux XFS Mailing List Subject: Re: 10minutes for rm -rf on 400MB References: <3B9BF400.1050900@rentec.com> <3B9C0231.67E2BF01@berdmann.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8A0emd00829 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, Bernhard R. Erdmann wrote: >>we've been running XFS on the data disks of our HPC Linux cluster since >>a while. we are quite happy with xfs, thx guys for your work! >>the setup is: >> >>- dual >=1GHZ box, 4GB mem >>- lvm 0.9beta7, phys. volume size ~140 GB, logical vol for xfs: 100GB >>- no additional mount options or options for mkfs.xfs were given >>- kernel 2.4.8pre4-xfs, highly patched SuSE 7.0 (not that it should matter) >> >>a user complained that "rm -rf of 400MB" takes ~10 minutes (!) until >>the >>command returns, whereas on the systems with reiserfs we have e.g. it >>takes seconds. >> > >Some very important data is missing: >- what's the I/O performance of the disk subsystem? > why is that relevant? with reiserfs it takes seconds, so the disks/controller cannot be the bottleneck. but to answer your question: we don't have hamster cage style disks hooked up, in this case the lvm containing XFS is a concatenated volume over to 10krpm 72GB IBM SCSI disks on a single channel of a plain aic controller. which disk subsystem you think would take 10 minutes for the task? > >- what was the system doing during the observed 10 min? > don't know, since i wasn't doing that. but my good guess is nothing else. also if the system would have been in really use, we don't see high i/o read numbers. > >CPU power doesn't count as much as disk I/O performance because >unlink(2) on XFS is a synchronous operation. > :-( why is that? >>i don't know so much about the quality of the data, my guess is that some >>files >>are small (~100k), others a big (a few hundred MB). i read in the FAQ that >>XFS isn't particular good in rm-rf'ing files, which isn't really the >>issue for >>us, because in 99.9% of the time data is being read from the volume and not >>removed via rm -rf. >> > >So, three files à 100 MB and 1,024 files à 100 KB are 400 MB in sum and >even a busy system shouldn't take 10 min for deleting 1,027 files. I >guess your estimate of the file sizes is slightly wrong. > as i said above, the number of 10 minutes is what i was told. i am not working with our HPC cluster, i set it up. concerning the estimate of the file size, this is also info i got. and since the dataset is a couple of 10GB, i am not really into headcounting here. consider it please as an estimate and pick a lower number if it doesn't make sense. so, again the question: are there mkfs options or mount options which i should set, without bringing the filesystem into imbalance? i'd love to have my users not to experience this dent, since they won't likely accept this and despite other technical reasons might vote against using xfs. cheers, ~dirkw ______________________________ Dirk Wetter @ Renaissance Techn. mailto: From owner-linux-xfs@oss.sgi.com Sun Sep 9 18:10:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A1AOJ01279 for linux-xfs-outgoing; Sun, 9 Sep 2001 18:10:24 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A1AJd01255 for ; Sun, 9 Sep 2001 18:10:19 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id CEE41C00B61 for ; Mon, 10 Sep 2001 09:10:16 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 71331C00B60 for ; Mon, 10 Sep 2001 09:10:15 +0800 (PHT) Date: Mon, 10 Sep 2001 09:10:15 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Re: 10minutes for rm -rf on 400MB In-Reply-To: <3B9BA43B.5020904@rentec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 9 Sep 2001 at 13:17, Dirk Wetter wrote: > a user complained that /rm -rf of 400MB / takes ~10 minutes (!) until > the command returns, whereas on the systems with reiserfs we have e.g. > it takes seconds. This is expected. XFS does deletes synchronously. ReiserFS doesn't. ReiserFS is really good at deleting, as a matter of fact, for which reason I highly recommend it over any other Linux filesystem for such delete-intensive operations as Squid caches. You may be interested to study the mongo.pl results comparing ReiserFS and XFS for various file sizes in . > i don't know so much about the quality of the data, my guess is that > some files are small (~100k), others a big (a few hundred MB). Note that ~100k is not small relative to the mongo.pl benchmarks that will show you that XFS starts "beating" ReserFS in most performances except deletes at around 10k. So IMHO you're still better off with XFS. > i read in the FAQ that XFS isn't particular good in rm-rf'ing files, > which isn't really *the *issue for us, because in 99.9%of the time > data is being read from the volume and not removed via rm -rf. It's not good for deleting massive numbers of files. Deleting one large file is instantaneous, though. But like you said, 99.9% (only?) of the time, you don't delete all your data, right? Unless you're talking of a cache. > is there an mount/filecreation option to tweak without loosing > performance while reading? None that I know of. One developer (was it Steve Lord? I can't remember clearly now) joked that you could mount the filesystem synchronously. That way you don't feel the speed difference. Hahaha. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Sun Sep 9 18:41:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A1fD101816 for linux-xfs-outgoing; Sun, 9 Sep 2001 18:41:13 -0700 Received: from femail25.sdc1.sfba.home.com (femail25.sdc1.sfba.home.com [24.254.60.15]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A1fBd01797 for ; Sun, 9 Sep 2001 18:41:11 -0700 Received: from there ([24.10.81.118]) by femail25.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010910014106.YHFS569.femail25.sdc1.sfba.home.com@there> for ; Sun, 9 Sep 2001 18:41:06 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Mike Reply-To: machack@sscsonline.org Organization: SSCS To: Linux XFS Mailing List Subject: ac kernels Date: Sun, 9 Sep 2001 21:21:50 -0400 X-Mailer: KMail [version 1.3.1] MIME-Version: 1.0 Message-Id: <20010910014106.YHFS569.femail25.sdc1.sfba.home.com@there> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8A1fBd01798 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Just a quick question. Is there anybody working to create a patch for the ac kernels? -- http://machack.sscsonline.org/ZapQuake/ Don't just play quake feel it! Free Dmitry Sklyarov! http://www.freesklyarov.org/ From owner-linux-xfs@oss.sgi.com Sun Sep 9 19:00:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A20fO02220 for linux-xfs-outgoing; Sun, 9 Sep 2001 19:00:41 -0700 Received: from mailin10.bigpond.com (juicer35.bigpond.com [139.134.6.87]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A20Wd02193 for ; Sun, 9 Sep 2001 19:00:32 -0700 Received: from HERCULES ([144.135.24.69]) by mailin10.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GJFCIZ00.6LE for ; Mon, 10 Sep 2001 12:06:35 +1000 Received: from CPE-61-9-140-28.vic.bigpond.net.au ([61.9.140.28]) by bwmam01.mailsvc.email.bigpond.com(MailRouter V2.9i 8311/11141664); 10 Sep 2001 12:06:35 Content-Type: text/plain; charset="iso-8859-1" From: Adrian Head Reply-To: adrian.head@bytecomm.com.au To: linux-xfs@oss.sgi.com Subject: Re: Problems with many processes copying large directories across an XFS volume. Date: Mon, 10 Sep 2001 12:00:30 +1000 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01091012003000.01147@HERCULES> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Over the last few days I have had the opportunity to try a few more tests to try and find more information to describe the problem I am seeing when I run multiple copy jobs in the background across an XFS volume. I downloaded the 2.4.9-xfs-2001-08-26 kernel patch from the XFS ftp server and gave it a run with the multiple cp test. After running through the same procedure as in my previous post - a few minutes into the test I still got the Input/Output error messages printed on the console, but this time I also had the following messages printed in /var/log/messages: Sep 10 10:14:57 ATLAS kernel: I/O error in filesystem ("md(9,0)") meta-data dev 0x900 block 0x9802bdc Sep 10 10:14:57 ATLAS kernel: (xlog_iodone") error 5 buf count 32768 Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called from line 940 of file xfs_log.c. Return address - 0xd8cb66f8 Sep 10 10:14:57 ATLAS kernel: Log I/O Error Detected. Shutting down filesystem: md(9,0) Sep 10 10:14:57 ATLAS kernel: Please umount the filesystem, and rectify the problem(s) Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called from line 714 of file xfs_log.c. Return address = 0xd8cb65d3 Sep 10 10:14:57 ATLAS kernel: attempt to access beyond end of device Sep 10 10:14:57 ATLAS kernel: 02:82: rw=0, want=1602235696, limit=4 I'm not sure what these really mean or what caused the I/O error but I hope this sheds some more light on the problem. (I had to transfer this by hand so if there are any uncertainties I'll go to the effort of getting the log and posting it.) The other attempt I tried was to download the 2.4.10-pre2-xfs-2001-09-02 kernel patch and run the same multiple cp test. This time things were different: This time it did not die a few minutes into the test like the previous attempts. Because it had not died I added more background processes - 40 total instead of the 20 in the previous tests. About halfway through the test for some unknown reason one cp process segfaulted because of a null kernel pointer. Why this happened to only one cp process I'm not sure - it certainly did not affect the other processes and the test continued. The test ran fine for almost 3 hours until I noticed that all HDD activity had stopped. Thinking that the test had completed I checked the jobs in the shell and it was reported that all jobs but the one that had segfaulted were still running. I checked `top` but it showed that all cp processes were running. Thinking it might have been a hardware issue I `ls *` a couple of drives including the raid5 (SW) where I was running the test. Although it was slow everything worked as normal until I did a `du -sh` on the volume that I had run the test on - with this the console froze. I switched to another console and did a `df -h` which gave me a result. The multiple cp test had stopped with only 20G left to fill on the 154G raid5 volume (about 83% complete). I was able to ping the machine from another box on the network but I was unable to log in remotely through telnet. I left the machine for another few hours but the status did not change. In the running console I shutdown the machine. The machine started to go down but hung not long after. Nothing was written to the logs. Note: The consoles I am talking about are the virtual kind Alt+F1, Alt+F2 etc. I'm not running anything graphical just plain text consoles. Some details from 'top' (just in case it helps) up 2:45 4 users load average 40.15 40.41 40.70 66 processes 27 sleeping 39 running CPU states 0% user 36.6% sys 0% nice 63.3% idle. Mem 384520k av 381956k used 2564k free 0k shrd 216k buff 353916k cached Swap 524624 av 14464k used 510160k free The 2nd test has thrown me for a complete spin. Am I seeing the same problem as the original test or is this something else? Considering that I was pushing the machine way past what I would expect to see in the production environment do I need to worry? The IRQ probe failure I talked about in the original post still exists on both of the kernels built for these test attempts. Do I need to worry about these IRQ probe failures? At this stage I'm unsure what other info people would like.  If anyone wants logs, config files, more information or more testing please tell me. Thanks for your time. Adrian Head Bytecomm P/L From owner-linux-xfs@oss.sgi.com Sun Sep 9 20:18:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A3Idc03567 for linux-xfs-outgoing; Sun, 9 Sep 2001 20:18:39 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A3I4d03547 for ; Sun, 9 Sep 2001 20:18:04 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id UAA23762 for ; Sun, 9 Sep 2001 20:18:06 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id OAA37461; Mon, 10 Sep 2001 14:16:41 +1100 (EDT) Date: Mon, 10 Sep 2001 14:16:41 +1100 From: Timothy Shimmin To: Takayuki Sasaki Cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump/xfsrestore failed sometimes when running QA suite 022 Message-ID: <20010910141641.L96131@boing.melbourne.sgi.com> References: <200109070837.RAA22356@tagajo.bsd.tnes.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200109070837.RAA22356@tagajo.bsd.tnes.nec.co.jp>; from sasaki@bsd.tnes.nec.co.jp on Fri, Sep 07, 2001 at 05:37:15PM +0900 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Takayuki, Do you have top of tree cmds and kernel ? cmd/xfstests/022 has failed reliably for us in recent times, but over the last few days (Nathan looks after our QA he'll know exactly when), it has been passing reliably. I have been meaning to look into 022 and 024 but only looked at 024 recently. I do not know exactly what has changed to cause 022 to pass now. xfsdump uses an xfs feature called bulkstat'ing to speed up the stat'ing of all the inodes of the file system. However, it apparently snapshots the info from the disk blocks instead of going through the in-core data structures. This means that if this data is not flushed to disk completely when xfsdump is running then it won't have the latest stat information. So for the QA testing, after populating an FS I would call _stable_fs to do sync and sleep. However, I didn't do this in every case such as the case where I append to files to test out incremental dumps in 024. So I added the call to _stable_fs in common.dump for this. I also changed from sync/sleep to umount/mount to be sure that the changes are flushed to disk before proceeding. So this may have also affected 022. However, by putting back the old behaviour I was still unable to get 022 to fail. --Tim On Fri, Sep 07, 2001 at 05:37:15PM +0900, Takayuki Sasaki wrote: > Hi, > > I have run QA suite ( cmd/xfstests/022 ) on my box, but > sometimes it failed because the size or owner of a few files are > mismatched before xfsdump / after xfsrestore. The error message > is attached at the end of this mail. > > If I edit script 022 to erase a tape with writing an eof instead > of erasing actually ( i.e. call _erase_soft instead of > _erase_hard which are defined in cmd/xfstest/common.dump ), this > issue never occured until now. > > Machine: Pentium III (Coppermine) 733MHz + SiS 630 chip set + 128MB RAM > Tape: HP C1533A DDS2 SCSI > Kernel: linux-2.4.10-pre1 with 20010829 CVS Tree > xfsdump: 20010829 CVS Tree > gcc: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) > > This have been tested on kernel 2.4.8 and 2.4.9, but same issue > occured... Why these files are destroyed? Are there any ideas? > > Thanks in advance. > > Taka > > root [108] > ./022 > QA output created by 022 > Put scsi tape driver into variable block size mode > Creating directory system to dump using src/fsstress. > > ----------------------------------------------- > fsstress : -f link=10 -f creat=10 -f mkdir=10 -f truncate=5 -f symlink=10 > ----------------------------------------------- > Erasing tape > Dumping to tape... > xfsdump -s DUMP_SUBDIR -f TAPE_DEV -M stress_tape_media -L stress_022 SCRATCH_MNT > xfsdump: version 3.0 - Running single-threaded > xfsdump: level 0 dump of HOSTNAME:SCRATCH_MNT > xfsdump: dump date: DATE > xfsdump: session id: ID > xfsdump: session label: "stress_022" > xfsdump: ino map phase 1: parsing subtree selections > xfsdump: ino map phase 2: constructing initial dump list > xfsdump: ino map phase 3: pruning unneeded subtrees > xfsdump: ino map phase 4: estimating dump size > xfsdump: ino map phase 5: skipping (only one dump stream) > xfsdump: ino map construction complete > xfsdump: estimated dump size: NUM bytes > xfsdump: /var/xfsdump/inventory created > xfsdump: preparing drive > xfsdump: creating dump session media file 0 (media 0, file 0) > xfsdump: dumping ino map > xfsdump: dumping directories > xfsdump: dumping non-directory files > xfsdump: ending media file > xfsdump: media file size NUM bytes > xfsdump: dumping session inventory > xfsdump: beginning inventory media file > xfsdump: media file 1 (media 0, file 1) > xfsdump: ending inventory media file > xfsdump: inventory media file size NUM bytes > xfsdump: writing stream terminator > xfsdump: beginning media stream terminator > xfsdump: media file 2 (media 0, file 2) > xfsdump: ending media stream terminator > xfsdump: media stream terminator size 1048576 bytes > xfsdump: dump size (non-dir files) : NUM bytes > xfsdump: dump complete: SECS seconds elapsed > Rewinding tape > Restoring from tape... > xfsrestore -f TAPE_DEV -L stress_022 RESTORE_DIR > xfsrestore: version 3.0 - Running single-threaded > xfsrestore: using online session inventory > xfsrestore: searching media for directory dump > xfsrestore: preparing drive > xfsrestore: examining media file 0 > xfsrestore: reading directories > xfsrestore: directory post-processing > xfsrestore: restoring non-directory files > xfsrestore: restore complete: SECS seconds elapsed > Comparing listing of dump directory with restore directory > *** TMP.dump_dir Wed Aug 29 17:24:12 2001 > --- TMP.restore_dir Wed Aug 29 17:24:12 2001 > *************** > *** 13,24 **** > drwxrwxrwx 2 root root 16 Aug 29 16:16 d39 > drwxrwxrwx 5 root root 76 Aug 29 16:16 da > drwxrwxrwx 4 root root 55 Aug 29 16:16 db > ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 f21 > -rw-rw-rw- 1 root root 712704 Aug 29 16:16 f47 > -rw-rw-rw- 1 root root 0 Aug 29 16:16 f4f > ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 f6 > -rw-rw-rw- 3 root root 0 Aug 29 16:16 f61 > ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 f7 > lrwxrwxrwx 2 root root 939 Aug 29 DATE l29 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxx > lrwxrwxrwx 2 root root 939 Aug 29 DATE l29 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxx > lrwxrwxrwx 2 root root 939 Aug 29 DATE l36 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxx > --- 13,24 ---- > drwxrwxrwx 2 root root 16 Aug 29 16:16 d39 > drwxrwxrwx 5 root root 76 Aug 29 16:16 da > drwxrwxrwx 4 root root 55 Aug 29 16:16 db > ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 f21 > -rw-rw-rw- 1 root root 712704 Aug 29 16:16 f47 > -rw-rw-rw- 1 root root 0 Aug 29 16:16 f4f > ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 f6 > -rw-rw-rw- 3 root root 0 Aug 29 16:16 f61 > ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 f7 > lrwxrwxrwx 2 root root 939 Aug 29 DATE l29 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxx > lrwxrwxrwx 2 root root 939 Aug 29 DATE l29 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxx > lrwxrwxrwx 2 root root 939 Aug 29 DATE l36 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxx > *************** > *** 31,37 **** > /mnt/xfstest1/dump.1655/p0/d5/d2e: > total TOTAL > drwxrwxrwx 2 root root 26 Aug 29 16:16 d53 > ! -rw-rw-rw- 1 root root 420819 Aug 29 16:16 f2f > > /mnt/xfstest1/dump.1655/p0/d5/d2e/d53: > total TOTAL > --- 31,37 ---- > /mnt/xfstest1/dump.1655/p0/d5/d2e: > total TOTAL > drwxrwxrwx 2 root root 26 Aug 29 16:16 d53 > ! -rw-rw-rw- 1 root root 0 Aug 29 16:16 f2f > > /mnt/xfstest1/dump.1655/p0/d5/d2e/d53: > total TOTAL > *************** > *** 40,46 **** > > /mnt/xfstest1/dump.1655/p0/d5/d39: > total TOTAL > ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 f3e > > /mnt/xfstest1/dump.1655/p0/d5/da: > total TOTAL > --- 40,46 ---- > > /mnt/xfstest1/dump.1655/p0/d5/d39: > total TOTAL > ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 f3e > > /mnt/xfstest1/dump.1655/p0/d5/da: > total TOTAL > *************** > *** 55,61 **** > > /mnt/xfstest1/dump.1655/p0/d5/da/d10: > total TOTAL > ! -rw-rw-rw- 2 root root 584907 Aug 29 16:16 f62 > lrwxrwxrwx 6 root root 1018 Aug 29 DATE l25 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > lrwxrwxrwx 6 root root 1018 Aug 29 DATE l25 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > lrwxrwxrwx 1 root root 1011 Aug 29 DATE l5a -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxxx > --- 55,61 ---- > > /mnt/xfstest1/dump.1655/p0/d5/da/d10: > total TOTAL > ! -rw-rw-rw- 2 root root 635646 Aug 29 16:16 f62 > lrwxrwxrwx 6 root root 1018 Aug 29 DATE l25 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > lrwxrwxrwx 6 root root 1018 Aug 29 DATE l25 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > lrwxrwxrwx 1 root root 1011 Aug 29 DATE l5a -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxxx > *************** > *** 64,71 **** > /mnt/xfstest1/dump.1655/p0/d5/da/d14: > total TOTAL > drwxrwxrwx 4 root root 56 Aug 29 16:16 d1f > ! drwxrwxrwx 2 root root 36 Aug 29 16:16 d26 > ! -rw-rw-rw- 3 root root 1906129 Aug 29 16:16 f55 > > /mnt/xfstest1/dump.1655/p0/d5/da/d14/d1f: > total TOTAL > --- 64,71 ---- > /mnt/xfstest1/dump.1655/p0/d5/da/d14: > total TOTAL > drwxrwxrwx 4 root root 56 Aug 29 16:16 d1f > ! drwxrwxrwx 2 root root 26 Aug 29 16:16 d26 > ! -rw-rw-rw- 3 root root 956273 Aug 29 16:16 f55 > > /mnt/xfstest1/dump.1655/p0/d5/da/d14/d1f: > total TOTAL > *************** > *** 95,101 **** > > /mnt/xfstest1/dump.1655/p0/d5/da/d14/d26: > total TOTAL > - -rw-rw-rw- 1 root root 0 Aug 29 16:16 f44 > lrwxrwxrwx 2 root root 868 Aug 29 DATE l4e -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > lrwxrwxrwx 2 root root 868 Aug 29 DATE l4e -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > lrwxrwxrwx 1 root root 217 Aug 29 DATE l5e -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxx > --- 95,100 ---- > *************** > *** 103,109 **** > > /mnt/xfstest1/dump.1655/p0/d5/da/d22: > total TOTAL > ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 f49 > lrwxrwxrwx 1 root root 294 Aug 29 DATE l2c -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxx > lrwxrwxrwx 1 root root 294 Aug 29 DATE l2c -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxx > lrwxrwxrwx 1 root root 392 Aug 29 DATE l54 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/x > --- 102,108 ---- > > /mnt/xfstest1/dump.1655/p0/d5/da/d22: > total TOTAL > ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 f49 > lrwxrwxrwx 1 root root 294 Aug 29 DATE l2c -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxx > lrwxrwxrwx 1 root root 294 Aug 29 DATE l2c -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxx > lrwxrwxrwx 1 root root 392 Aug 29 DATE l54 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/x > *************** > *** 113,119 **** > total TOTAL > drwxrwxrwx 4 root root 46 Aug 29 16:16 d15 > drwxrwxrwx 4 root root 44 Aug 29 16:16 dc > ! -rw-rw-rw- 2 root root 1720320 Aug 29 16:16 f18 > -rw-rw-rw- 1 root root 0 Aug 29 16:16 f67 > lrwxrwxrwx 2 root root 868 Aug 29 DATE l20 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > lrwxrwxrwx 2 root root 868 Aug 29 DATE l20 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > --- 112,118 ---- > total TOTAL > drwxrwxrwx 4 root root 46 Aug 29 16:16 d15 > drwxrwxrwx 4 root root 44 Aug 29 16:16 dc > ! -rw-rw-rw- 2 root root 0 Aug 29 16:16 f18 > -rw-rw-rw- 1 root root 0 Aug 29 16:16 f67 > lrwxrwxrwx 2 root root 868 Aug 29 DATE l20 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > lrwxrwxrwx 2 root root 868 Aug 29 DATE l20 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > *************** > *** 122,128 **** > total TOTAL > drwxrwxrwx 2 root root 6 Aug 29 16:16 d30 > drwxrwxrwx 2 root root 16 Aug 29 16:16 d3a > ! -rw-rw-rw- 3 root root 1906129 Aug 29 16:16 f1e > lrwxrwxrwx 6 root root 1018 Aug 29 DATE l17 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > lrwxrwxrwx 6 root root 1018 Aug 29 DATE l17 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > > --- 121,127 ---- > total TOTAL > drwxrwxrwx 2 root root 6 Aug 29 16:16 d30 > drwxrwxrwx 2 root root 16 Aug 29 16:16 d3a > ! -rw-rw-rw- 3 root root 956273 Aug 29 16:16 f1e > lrwxrwxrwx 6 root root 1018 Aug 29 DATE l17 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > lrwxrwxrwx 6 root root 1018 Aug 29 DATE l17 -> xxxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxx > xxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxxxx/xxxxxxx > > *************** > *** 131,144 **** > > /mnt/xfstest1/dump.1655/p0/d5/db/d15/d3a: > total TOTAL > ! -rw-rw-rw- 3 root root 1906129 Aug 29 16:16 f6e > > /mnt/xfstest1/dump.1655/p0/d5/db/dc: > total TOTAL > drwxrwxrwx 4 root root 46 Aug 29 16:16 d11 > drwxrwxrwx 4 root root 36 Aug 29 16:16 d23 > ! -rw-rw-rw- 6 root root 551986 Aug 29 16:16 fd > ! -rw-rw-rw- 2 root root 584907 Aug 29 16:16 fe > > /mnt/xfstest1/dump.1655/p0/d5/db/dc/d11: > total TOTAL > --- 130,143 ---- > > /mnt/xfstest1/dump.1655/p0/d5/db/d15/d3a: > total TOTAL > ! -rw-rw-rw- 3 root root 956273 Aug 29 16:16 f6e > > /mnt/xfstest1/dump.1655/p0/d5/db/dc: > total TOTAL > drwxrwxrwx 4 root root 46 Aug 29 16:16 d11 > drwxrwxrwx 4 root root 36 Aug 29 16:16 d23 > ! -rw-rw-rw- 6 root root 730637 Aug 29 16:16 fd > ! -rw-rw-rw- 2 root root 635646 Aug 29 16:16 fe > > /mnt/xfstest1/dump.1655/p0/d5/db/dc/d11: > total TOTAL > *************** > *** 163,169 **** > /mnt/xfstest1/dump.1655/p0/d5/db/dc/d11/d37: > total TOTAL > -rw-rw-rw- 1 root root 0 Aug 29 16:16 f4a > ! -rw-rw-rw- 2 root root 1720320 Aug 29 16:16 f5c > > /mnt/xfstest1/dump.1655/p0/d5/db/dc/d23: > total TOTAL > --- 162,168 ---- > /mnt/xfstest1/dump.1655/p0/d5/db/dc/d11/d37: > total TOTAL > -rw-rw-rw- 1 root root 0 Aug 29 16:16 f4a > ! -rw-rw-rw- 2 root root 0 Aug 29 16:16 f5c > > /mnt/xfstest1/dump.1655/p0/d5/db/dc/d23: > total TOTAL > root [109] > > From owner-linux-xfs@oss.sgi.com Sun Sep 9 20:19:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A3JrI03654 for linux-xfs-outgoing; Sun, 9 Sep 2001 20:19:53 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A3JXd03635 for ; Sun, 9 Sep 2001 20:19:33 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id UAA07886 for ; Sun, 9 Sep 2001 20:19:03 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id NAA21473; Mon, 10 Sep 2001 13:15:16 +1000 Date: Mon, 10 Sep 2001 13:15:16 +1000 From: Keith Owens Message-Id: <200109100315.NAA21473@sherman.melbourne.sgi.com> Subject: TAKE - Upgrade to 2.4.10-pre5 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Upgrade to 2.4.10-pre5. This compiles but has not been tested yet. AL Viro has changed fs/super.c (again) and the dmapi patch no longer makes sense, I have ifdeffed it out so do not expect dmapi to work. Dean, it looks like do_kern_mount has to return a struct vsfmount that is marked as IS_ERR and release the superblock lock yourself. Date: Sun Sep 9 20:09:11 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102419a linux/drivers/scsi/dpt/osd_util.h - 1.1 linux/include/net/bluetooth/hci_vhci.h - 1.1 linux/include/linux/prefetch.h - 1.1 linux/Documentation/arm/SA1100/DMA - 1.1 linux/Documentation/arm/SA1100/FreeBird - 1.1 linux/drivers/video/tx3912fb.h - 1.1 linux/Documentation/arm/SA1100/HUW_WEBPANEL - 1.1 linux/drivers/video/tx3912fb.c - 1.1 linux/Documentation/arm/SA1100/PCMCIA - 1.1 linux/drivers/video/sstfb.h - 1.1 linux/Documentation/arm/SA1100/Yopy - 1.1 linux/drivers/video/sstfb.c - 1.1 linux/drivers/video/radeonfb.c - 1.1 linux/Documentation/fb/README-sstfb.txt - 1.1 linux/drivers/video/radeon.h - 1.1 linux/drivers/usb/usbvideo.h - 1.1 linux/drivers/usb/usbvideo.c - 1.1 linux/drivers/telephony/ixj_pcmcia.c - 1.1 linux/drivers/telephony/ixj-ver.h - 1.1 linux/Documentation/sound/WaveArtist - 1.1 linux/drivers/sound/nec_vrc5477.c - 1.1 linux/drivers/sound/ite8172.c - 1.1 linux/drivers/scsi/dpti.h - 1.1 linux/drivers/scsi/dpt_i2o.c - 1.1 linux/drivers/scsi/dpt/sys_info.h - 1.1 linux/drivers/scsi/dpt/osd_defs.h - 1.1 linux/drivers/scsi/dpt/dptsig.h - 1.1 linux/drivers/scsi/dpt/dpti_ioctl.h - 1.1 linux/drivers/scsi/dpt/dpti_i2o.h - 1.1 linux/drivers/scsi/dpt/dpt_osdutil.h - 1.1 linux/drivers/net/starfire_firmware.pl - 1.1 linux/drivers/media/video/vino.h - 1.1 linux/drivers/ide/qd65xx.h - 1.1 linux/drivers/ide/qd65xx.c - 1.1 linux/drivers/char/serial_tx3912.h - 1.1 linux/drivers/char/serial_tx3912.c - 1.1 linux/drivers/bluetooth/hci_vhci.c - 1.1 linux/net/sunrpc/xdr.c - 1.4 linux/net/sunrpc/svc.c - 1.8 linux/net/sunrpc/sunrpc_syms.c - 1.9 linux/net/sunrpc/clnt.c - 1.13 linux/net/netrom/af_netrom.c - 1.19 linux/net/lapb/lapb_iface.c - 1.9 linux/net/irda/irda_device.c - 1.19 linux/net/ipv6/udp.c - 1.22 linux/net/ipv6/tcp_ipv6.c - 1.25 linux/net/ipv6/sit.c - 1.16 linux/net/ipv6/ip6_output.c - 1.10 linux/net/ipv6/icmp.c - 1.13 linux/net/ipv6/datagram.c - 1.8 linux/net/ipv6/addrconf.c - 1.20 linux/net/ipv4/udp.c - 1.24 linux/net/ipv4/tcp_ipv4.c - 1.33 linux/net/ipv4/ipip.c - 1.17 linux/net/ipv4/ip_output.c - 1.26 linux/net/ipv4/ip_options.c - 1.5 linux/net/ipv4/ip_fragment.c - 1.14 linux/net/ipv4/icmp.c - 1.22 linux/net/ipv4/arp.c - 1.19 linux/net/core/dev.c - 1.40 linux/kernel/ksyms.c - 1.104 linux/include/scsi/sg.h - 1.11 linux/include/linux/sunrpc/xdr.h - 1.5 linux/include/linux/module.h - 1.20 linux/include/linux/minix_fs.h - 1.10 linux/include/linux/lockd/xdr.h - 1.4 linux/include/linux/fs.h - 1.115 linux/include/asm-sparc64/system.h - 1.13 linux/include/asm-sparc64/pgtable.h - 1.22 linux/include/asm-sparc64/elf.h - 1.9 linux/fs/super.c - 1.52 linux/fs/qnx4/inode.c - 1.24 linux/fs/proc/generic.c - 1.23 linux/fs/open.c - 1.30 linux/fs/nfsd/nfsfh.c - 1.30 linux/fs/nfsd/export.c - 1.20 linux/fs/nfs/inode.c - 1.28 linux/fs/nfs/file.c - 1.23 linux/fs/minix/namei.c - 1.15 linux/fs/minix/inode.c - 1.22 linux/fs/minix/file.c - 1.11 linux/fs/minix/dir.c - 1.8 linux/fs/minix/bitmap.c - 1.11 linux/fs/lockd/clntlock.c - 1.9 linux/fs/file_table.c - 1.15 linux/fs/exec.c - 1.44 linux/fs/dquot.c - 1.35 linux/fs/adfs/inode.c - 1.16 linux/drivers/zorro/zorro.c - 1.8 linux/drivers/video/fbcon.c - 1.21 linux/drivers/usb/hub.h - 1.15 linux/drivers/usb/hub.c - 1.37 linux/drivers/sound/sonicvibes.c - 1.33 linux/drivers/sound/msnd_pinnacle.c - 1.17 linux/drivers/sound/ad1848.c - 1.12 linux/drivers/sound/Config.in - 1.27 linux/drivers/scsi/sg.c - 1.20 linux/drivers/scsi/seagate.h - 1.4 linux/drivers/scsi/seagate.c - 1.12 linux/drivers/scsi/sd.c - 1.41 linux/drivers/scsi/qlogicfc_asm.c - 1.7 linux/drivers/scsi/qlogicfc.c - 1.21 linux/drivers/scsi/gdth_proc.h - 1.5 linux/drivers/scsi/gdth_proc.c - 1.11 linux/drivers/scsi/gdth_ioctl.h - 1.4 linux/drivers/scsi/gdth.h - 1.6 linux/drivers/scsi/gdth.c - 1.14 linux/drivers/scsi/aha1542.c - 1.17 linux/drivers/net/via-rhine.c - 1.27 linux/drivers/net/ni5010.c - 1.14 linux/drivers/net/net_init.c - 1.21 linux/drivers/macintosh/nvram.c - 1.9 linux/drivers/isdn/pcbit/layer2.h - 1.5 linux/drivers/isdn/pcbit/layer2.c - 1.7 linux/drivers/isdn/isdn_audio.c - 1.8 linux/drivers/isdn/icn/icn.h - 1.8 linux/drivers/isdn/icn/icn.c - 1.14 linux/drivers/char/wdt.c - 1.12 linux/drivers/char/tty_io.c - 1.34 linux/drivers/char/tpqic02.c - 1.14 linux/drivers/char/softdog.c - 1.12 linux/drivers/char/selection.c - 1.6 linux/drivers/char/qpmouse.c - 1.11 linux/drivers/char/pc110pad.c - 1.12 linux/drivers/char/misc.c - 1.26 linux/drivers/char/dsp56k.c - 1.16 linux/drivers/char/busmouse.c - 1.17 linux/drivers/cdrom/sjcd.c - 1.11 linux/drivers/cdrom/mcdx.c - 1.9 linux/drivers/cdrom/mcd.c - 1.11 linux/drivers/cdrom/isp16.c - 1.5 linux/drivers/cdrom/gscd.c - 1.11 linux/drivers/cdrom/cm206.c - 1.12 linux/drivers/cdrom/cdu31a.c - 1.8 linux/drivers/cdrom/aztcd.c - 1.12 linux/drivers/block/rd.c - 1.31 linux/drivers/block/floppy.c - 1.26 linux/arch/sparc64/vmlinux.lds - 1.10 linux/arch/sparc64/mm/ultra.S - 1.16 linux/arch/sparc64/mm/init.c - 1.30 linux/arch/sparc64/mm/fault.c - 1.18 linux/arch/sparc64/kernel/sparc64_ksyms.c - 1.32 linux/arch/sparc64/kernel/ioctl32.c - 1.41 linux/arch/sparc64/kernel/head.S - 1.9 linux/arch/sparc64/defconfig - 1.47 linux/arch/ppc/amiga/config.c - 1.11 linux/arch/i386/mm/fault.c - 1.18 linux/arch/i386/kernel/setup.c - 1.51 linux/arch/i386/defconfig - 1.66 linux/arch/arm/mm/fault-armv.c - 1.17 linux/arch/arm/kernel/process.c - 1.19 linux/Makefile - 1.118 linux/MAINTAINERS - 1.70 linux/Documentation/watchdog.txt - 1.6 linux/Documentation/ide.txt - 1.7 linux/include/linux/ide.h - 1.31 linux/drivers/sound/cmpci.c - 1.25 linux/drivers/isdn/hisax/isar.c - 1.13 linux/arch/arm/kernel/arthur.c - 1.7 linux/Documentation/sound/CMI8338 - 1.5 linux/drivers/char/vino.h - 1.2 linux/drivers/parport/parport_pc.c - 1.37 linux/drivers/char/sx.c - 1.20 linux/drivers/sound/esssolo1.c - 1.31 linux/fs/partitions/check.c - 1.29 linux/drivers/sound/ac97.h - 1.5 linux/drivers/net/starfire.c - 1.19 linux/Documentation/arm/SA1100/Itsy - 1.2 linux/drivers/pci/pci.ids - 1.32 linux/include/linux/mmzone.h - 1.16 linux/drivers/sound/trident.h - 1.12 linux/drivers/sound/trident.c - 1.25 linux/include/linux/i2c-id.h - 1.9 linux/include/linux/telephony.h - 1.6 linux/drivers/telephony/phonedev.c - 1.7 linux/drivers/telephony/ixj.h - 1.6 linux/drivers/telephony/ixj.c - 1.17 linux/drivers/telephony/Makefile - 1.4 linux/drivers/telephony/Config.in - 1.2 linux/drivers/usb/devices.c - 1.12 linux/drivers/usb/devio.c - 1.17 linux/drivers/ieee1394/ieee1394_core.h - 1.9 linux/drivers/ieee1394/ieee1394_core.c - 1.14 linux/drivers/ieee1394/highlevel.c - 1.5 linux/drivers/scsi/3w-xxxx.h - 1.6 linux/drivers/scsi/3w-xxxx.c - 1.12 linux/drivers/zorro/names.c - 1.3 linux/drivers/usb/usb-uhci.c - 1.25 linux/drivers/sound/ac97_codec.c - 1.18 linux/drivers/sound/via82cxxx_audio.c - 1.19 linux/drivers/char/wdt977.c - 1.6 linux/drivers/char/wdt285.c - 1.8 linux/include/linux/ac97_codec.h - 1.10 linux/drivers/video/riva/fbdev.c - 1.12 linux/include/linux/usb.h - 1.18 linux/drivers/parport/ChangeLog - 1.18 linux/drivers/ide/via82cxxx.c - 1.17 linux/drivers/ide/sl82c105.c - 1.5 linux/drivers/ide/sis5513.c - 1.12 linux/drivers/ide/qd6580.c - 1.6 linux/drivers/ide/pdc202xx.c - 1.10 linux/drivers/ide/ide.c - 1.27 linux/drivers/ide/ide-proc.c - 1.7 linux/drivers/ide/ide-floppy.c - 1.8 linux/drivers/ide/Makefile - 1.10 linux/drivers/ide/Config.in - 1.13 linux/Documentation/DocBook/Makefile - 1.17 linux/include/linux/generic_serial.h - 1.3 linux/drivers/char/wdt_pci.c - 1.7 linux/Documentation/DocBook/parportbook.tmpl - 1.6 linux/drivers/usb/serial/visor.h - 1.6 linux/drivers/usb/serial/visor.c - 1.20 linux/drivers/sound/i810_audio.c - 1.14 linux/drivers/char/rio/riocmd.c - 1.6 linux/drivers/char/rio/rio_linux.c - 1.10 linux/Documentation/arm/SA1100/Assabet - 1.2 linux/Documentation/kernel-doc-nano-HOWTO.txt - 1.4 linux/Documentation/arm/SA1100/nanoEngine - 1.2 linux/drivers/sound/cs46xx.c - 1.14 linux/arch/arm/tools/mach-types - 1.8 linux/drivers/md/raid5.c - 1.18 linux/drivers/md/md.c - 1.20 linux/fs/minix/itree_common.c - 1.4 linux/fs/minix/itree_v1.c - 1.2 linux/fs/minix/itree_v2.c - 1.2 linux/Documentation/arm/SA1100/GraphicsClient - 1.2 linux/Documentation/arm/SA1100/Pangolin - 1.2 linux/Documentation/arm/SA1100/serial_UART - 1.2 linux/arch/arm/lib/io-writesl.S - 1.4 linux/fs/reiserfs/inode.c - 1.9 linux/arch/arm/lib/io-readsl-armv4.S - 1.3 linux/arch/arm/tools/Makefile - 1.3 linux/drivers/s390/char/tuball.c - 1.3 linux/drivers/s390/char/tubfs.c - 1.3 linux/drivers/s390/char/tubio.h - 1.3 linux/drivers/s390/char/tubtty.c - 1.3 linux/drivers/s390/char/tubttybld.c - 1.2 linux/Documentation/s390/3270.txt - 1.3 linux/Documentation/s390/config3270.sh - 1.2 linux/drivers/block/paride/ppc6lnx.c - 1.2 linux/drivers/usb/pwc.h - 1.4 linux/drivers/usb/pwc-if.c - 1.4 linux/drivers/bluetooth/hci_uart.c - 1.3 linux/include/net/bluetooth/bluetooth.h - 1.2 linux/include/net/bluetooth/bluez.h - 1.2 linux/include/net/bluetooth/hci.h - 1.2 linux/include/net/bluetooth/hci_core.h - 1.2 linux/include/net/bluetooth/hci_emu.h - 1.2 linux/include/net/bluetooth/hci_uart.h - 1.2 linux/include/net/bluetooth/hci_usb.h - 1.2 linux/include/net/bluetooth/l2cap.h - 1.2 linux/include/net/bluetooth/l2cap_core.h - 1.2 linux/drivers/bluetooth/hci_usb.c - 1.3 linux/drivers/bluetooth/hci_emu.c - 1.3 linux/drivers/bluetooth/Makefile - 1.2 linux/drivers/bluetooth/Config.in - 1.2 linux/net/bluetooth/af_bluetooth.c - 1.2 linux/net/bluetooth/hci_core.c - 1.2 linux/net/bluetooth/hci_sock.c - 1.2 linux/net/bluetooth/l2cap_core.c - 1.2 linux/net/bluetooth/l2cap_proc.c - 1.2 linux/net/bluetooth/lib.c - 1.2 linux/drivers/usb/se401.c - 1.4 linux/drivers/usb/se401.h - 1.2 linux/drivers/usb/serial/pl2303.c - 1.2 linux/drivers/scsi/pcmcia/nsp_cs.c - 1.5 linux/drivers/scsi/pcmcia/nsp_debug.c - 1.5 linux/drivers/parport/parport_serial.c - 1.2 linux/drivers/message/fusion/scsi3.h - 1.2 linux/drivers/message/fusion/mptscsih.c - 1.2 linux/drivers/message/fusion/mptlan.h - 1.2 linux/drivers/message/fusion/mptlan.c - 1.2 linux/drivers/message/fusion/mptctl.c - 1.3 linux/drivers/message/fusion/mptbase.h - 1.2 linux/drivers/message/fusion/mptbase.c - 1.2 linux/drivers/message/fusion/lsi/mpi_targ.h - 1.2 linux/drivers/message/fusion/lsi/mpi_lan.h - 1.2 linux/drivers/message/fusion/lsi/mpi_ioc.h - 1.2 linux/drivers/message/fusion/lsi/mpi_init.h - 1.2 linux/drivers/message/fusion/lsi/mpi_history.txt - 1.2 linux/drivers/message/fusion/lsi/mpi_fc.h - 1.2 linux/drivers/message/fusion/lsi/mpi_cnfg.h - 1.2 linux/drivers/message/fusion/lsi/mpi.h - 1.2 linux/drivers/message/fusion/Makefile - 1.2 linux/drivers/message/fusion/isense.c - 1.2 linux/drivers/message/fusion/lsi/fc_log.h - 1.2 linux/fs/partitions/ldm.c - 1.2 linux/drivers/scsi/pcmcia/nsp_message.c - 1.2 linux/drivers/ide/it8172.c - 1.2 From owner-linux-xfs@oss.sgi.com Sun Sep 9 20:29:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A3TWm03857 for linux-xfs-outgoing; Sun, 9 Sep 2001 20:29:32 -0700 Received: from gateway1.brets.elevating.com (adsl-216-63-236-137.dsl.tulsok.swbell.net [216.63.236.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A3TTd03838 for ; Sun, 9 Sep 2001 20:29:29 -0700 Received: from elevating.com (bretdell.brets.elevating.com [192.168.0.128]) by gateway1.brets.elevating.com (8.9.3/8.8.7) with ESMTP id WAA10306 for ; Sun, 9 Sep 2001 22:29:18 -0500 Message-ID: <3B9C338E.500C917B@elevating.com> Date: Sun, 09 Sep 2001 22:29:18 -0500 From: Bret Hughes X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, ja MIME-Version: 1.0 To: linux-xfs Subject: Re: compaq smart 2 raid and XFS 1.0.1 redhat install problems References: <3B988116.E31FAF1C@elevating.com> <3B9893DB.F59296E@ch.sauter-bc.com> <20010907123728.A10983@blenke.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Ian C. Blenke" wrote: > > I'm running two VA Linux boxen with XFS/LVM, and two Compaq 1850R boxen > on SmartStart2 controllers with XFS/LVM, as well as a couple of happy XFS > laptops. I've had incredibly few problems with XFS so far.. and > lvextend/xfs_growfs really is a lifesaver. > > Good luck. > > - Ian C. Blenke Thanks to all who responded. I ended up having to follow Ians advice and wiping out everything and doing a new install. bummer. I have backups but the real pain in the neck is that this was my amanda index and tape server, so I get to dig around on the 18 tapes in my daily rotation to find the latest stuff. oh well it IS working. I have another box with the identical hardware that is really important and I am hoping that if I keep my head out of my $%# I will be able to do an upgrade. For those of you perusing the archives inthe future on a compaq proliant 3000 dual processor, 1GB memory with smart-2dh raid controller do NOT let lilo install on the MBR. I ended up making /boot as the first partition (non-XFS) and putting lilo there. works like a champ but boy was it painful. BTW I had to do the compaq erase routine and the associated build twice before it too. Not sure what I screwed up the first time. Thanks again for your help and comments. Bret From owner-linux-xfs@oss.sgi.com Sun Sep 9 21:49:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A4n5k04473 for linux-xfs-outgoing; Sun, 9 Sep 2001 21:49:05 -0700 Received: from gateway1.brets.elevating.com (adsl-216-63-236-137.dsl.tulsok.swbell.net [216.63.236.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A4n0d04454 for ; Sun, 9 Sep 2001 21:49:01 -0700 Received: from elevating.com (bretdell.brets.elevating.com [192.168.0.128]) by gateway1.brets.elevating.com (8.9.3/8.8.7) with ESMTP id XAA10551; Sun, 9 Sep 2001 23:48:50 -0500 Message-ID: <3B9C4632.2408E16@elevating.com> Date: Sun, 09 Sep 2001 23:48:50 -0500 From: Bret Hughes X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, ja MIME-Version: 1.0 To: linux-xfs Subject: directory cache problems (I think) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have a configuration on 6 boxes, Duron 700 with 128 MB ram and 10GB ide harddrives. These machines are all XFS 1.0.1 using the kernel from the 1.0.1 RH install iso and most of the RH updates. They were all placed into service the same day and yesterday 5 days after they were turned on they all stopped responding to ssh. A couple would still respond to a ping but nothing else. Actually I caough one before it quit altogether and rebooted it last night. These machines a kiosk type display that scroll html and flash pages using (netscape as the browser). There is no user interaction infact not any input device at all. A different page is displayed every 10 seconds. Now, After rebooting them I can get to the sadc data and looking through the logs shows really bad stuff happening at 1:00PM yesterday on the one machine I have really looked at closely. interrupt 14s out the wazoo and what I think must be the cause, the dentunusd goes to 0. Looking over the logs of the last few days I can see the dentunusd creeping down from the beginning at boot of over 20K to 0. Since netscape is such a pig I kill it and restart it once an hour and restart X once a day. both these events seem to take a tremendous toll on this value and never gain it all back. I don't know if this is an XFS issue or not but I thought that I would start here. Any ideas? I can send all the log data anyone might use if it would help. Right now I am going to reboot the damn things nightly like they were windows machines for Christ's sake. BTW the same scenario and control scripts run for months on end on RH 6.2 using the 2.2.3-16 kernel. Any tips and or other places to ask are appreciated. TIA Bret From owner-linux-xfs@oss.sgi.com Sun Sep 9 21:53:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A4r1x04624 for linux-xfs-outgoing; Sun, 9 Sep 2001 21:53:01 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A4qsd04605 for ; Sun, 9 Sep 2001 21:52:55 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id VAA08761 for ; Sun, 9 Sep 2001 21:51:22 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id OAA26810; Mon, 10 Sep 2001 14:52:30 +1000 Date: Mon, 10 Sep 2001 14:52:30 +1000 From: Keith Owens Message-Id: <200109100452.OAA26810@sherman.melbourne.sgi.com> Subject: TAKE - Sync RCS identifiers with 2.4.10-pre5 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sync RCS identifiers with 2.4.10-pre5. The use of separate respositories had resulted in a drift of RCS identifiers in ptools, compared to LInus's tree. Annoying when generating patches, so I resynced with Linus's tree. No code changes. Date: Sun Sep 9 21:49:45 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102423a linux/net/ipv6/udp.c - 1.23 linux/net/ipv6/tcp_ipv6.c - 1.26 linux/net/ipv6/sit.c - 1.17 linux/net/ipv6/ip6_output.c - 1.11 linux/net/ipv6/icmp.c - 1.14 linux/net/ipv6/datagram.c - 1.9 linux/net/ipv6/addrconf.c - 1.21 linux/net/ipv4/udp.c - 1.25 linux/net/ipv4/tcp_ipv4.c - 1.34 linux/net/ipv4/ip_output.c - 1.27 linux/net/ipv4/ip_options.c - 1.6 linux/net/ipv4/ip_fragment.c - 1.15 linux/net/ipv4/icmp.c - 1.23 linux/net/ipv4/arp.c - 1.20 linux/include/asm-sparc64/system.h - 1.14 linux/include/asm-sparc64/pgtable.h - 1.23 linux/include/asm-sparc64/elf.h - 1.10 linux/fs/Config.in - 1.65 linux/drivers/sound/msnd_pinnacle.c - 1.18 linux/drivers/scsi/gdth_proc.h - 1.6 linux/drivers/scsi/gdth_proc.c - 1.12 linux/drivers/scsi/gdth_ioctl.h - 1.5 linux/drivers/scsi/gdth.h - 1.7 linux/drivers/scsi/gdth.c - 1.15 linux/drivers/isdn/isdn_audio.c - 1.9 linux/drivers/isdn/icn/icn.h - 1.9 linux/drivers/isdn/icn/icn.c - 1.15 linux/arch/sparc64/mm/ultra.S - 1.17 linux/arch/sparc64/mm/init.c - 1.31 linux/arch/sparc64/mm/fault.c - 1.19 linux/arch/sparc64/lib/blockops.S - 1.12 linux/arch/sparc64/kernel/sparc64_ksyms.c - 1.33 linux/arch/sparc64/kernel/ioctl32.c - 1.42 linux/arch/sparc64/kernel/head.S - 1.10 linux/drivers/isdn/hisax/isar.c - 1.14 linux/include/linux/telephony.h - 1.7 linux/drivers/telephony/ixj.h - 1.7 linux/drivers/telephony/ixj.c - 1.18 linux/drivers/usb/usb-uhci.c - 1.26 linux/drivers/ide/via82cxxx.c - 1.18 linux/drivers/usb/storage/transport.c - 1.12 linux/drivers/usb/storage/scsiglue.c - 1.13 linux/drivers/usb/storage/sddr09.c - 1.9 linux/drivers/usb/storage/unusual_devs.h - 1.6 linux/fs/freevxfs/vxfs_super.c - 1.4 linux/fs/freevxfs/vxfs_olt.c - 1.3 linux/fs/freevxfs/vxfs_inode.c - 1.5 linux/fs/freevxfs/vxfs_fshead.c - 1.3 linux/fs/freevxfs/vxfs_extern.h - 1.3 linux/fs/freevxfs/vxfs_bmap.c - 1.3 linux/drivers/bluetooth/hci_uart.c - 1.4 linux/include/net/bluetooth/bluetooth.h - 1.3 linux/include/net/bluetooth/bluez.h - 1.3 linux/include/net/bluetooth/hci.h - 1.3 linux/include/net/bluetooth/hci_core.h - 1.3 linux/include/net/bluetooth/hci_uart.h - 1.3 linux/include/net/bluetooth/hci_usb.h - 1.3 linux/include/net/bluetooth/l2cap.h - 1.3 linux/include/net/bluetooth/l2cap_core.h - 1.3 linux/drivers/bluetooth/hci_usb.c - 1.4 linux/net/bluetooth/af_bluetooth.c - 1.3 linux/net/bluetooth/hci_core.c - 1.3 linux/net/bluetooth/hci_sock.c - 1.3 linux/net/bluetooth/l2cap_core.c - 1.3 linux/net/bluetooth/l2cap_proc.c - 1.3 linux/net/bluetooth/lib.c - 1.3 linux/net/bluetooth/syms.c - 1.2 linux/drivers/message/fusion/scsi3.h - 1.3 linux/drivers/message/fusion/mptscsih.c - 1.3 linux/drivers/message/fusion/mptlan.c - 1.3 linux/drivers/message/fusion/mptctl.c - 1.4 linux/drivers/message/fusion/mptbase.h - 1.3 linux/drivers/message/fusion/mptbase.c - 1.3 linux/drivers/message/fusion/isense.c - 1.3 linux/drivers/message/fusion/lsi/fc_log.h - 1.3 linux/include/net/bluetooth/hci_vhci.h - 1.2 linux/drivers/video/sstfb.h - 1.2 linux/drivers/video/sstfb.c - 1.2 linux/Documentation/fb/README-sstfb.txt - 1.2 linux/drivers/bluetooth/hci_vhci.c - 1.2 From owner-linux-xfs@oss.sgi.com Sun Sep 9 21:56:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A4uFU04756 for linux-xfs-outgoing; Sun, 9 Sep 2001 21:56:15 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A4uAd04737; Sun, 9 Sep 2001 21:56:10 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8A4uBd04738 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Sun Sep 9 22:34:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A5Y2405183 for linux-xfs-outgoing; Sun, 9 Sep 2001 22:34:02 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A5Xtd05164; Sun, 9 Sep 2001 22:33:55 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8A5Xud05165 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Sun Sep 9 22:45:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A5jXo05405 for linux-xfs-outgoing; Sun, 9 Sep 2001 22:45:33 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A5jHd05380 for ; Sun, 9 Sep 2001 22:45:17 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id WAA00241 for ; Sun, 9 Sep 2001 22:43:45 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id PAA08694; Mon, 10 Sep 2001 15:45:14 +1000 Date: Mon, 10 Sep 2001 15:45:14 +1000 From: Keith Owens Message-Id: <200109100545.PAA08694@sherman.melbourne.sgi.com> Subject: TAKE - Sync to 2.4.10-pre6 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sync to 2.4.10-pre6. This will not compile if ramdisk or quota are selected, due to bugs in the base 2.4.10-pre6 kernel. Date: Sun Sep 9 22:42:43 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102424a linux/arch/sh/kernel/pcibios.c - 1.1 linux/arch/sh/kernel/rtc-aica.c - 1.1 linux/arch/sh/kernel/setup_7751se.c - 1.1 linux/arch/sh/kernel/setup_adx.c - 1.1 linux/arch/sh/lib/strlen.S - 1.1 linux/arch/sh/mm/__clear_user_page-sh4.S - 1.1 linux/arch/sh/mm/__copy_user_page-sh4.S - 1.1 linux/arch/sh/mm/cache-sh3.c - 1.1 linux/arch/sh/kernel/mach_adx.c - 1.1 linux/arch/ppc/8xx_io/micropatch.c - 1.1 linux/arch/sh/kernel/mach_7751se.c - 1.1 linux/arch/sh/mm/cache-sh4.c - 1.1 linux/arch/sh/kernel/led_7751se.c - 1.1 linux/arch/sh/kernel/irq_maskreg.c - 1.1 linux/include/asm-sh/io_adx.h - 1.1 linux/include/asm-sh/io_7751se.h - 1.1 linux/include/asm-sh/hitachi_7751se.h - 1.1 linux/arch/sh/mm/clear_page.S - 1.1 linux/include/asm-ppc/sections.h - 1.1 linux/include/asm-ppc/ppcboot.h - 1.1 linux/arch/sh/mm/copy_page.S - 1.1 linux/arch/sh/kernel/io_adx.c - 1.1 linux/arch/sh/kernel/io_7751se.c - 1.1 linux/arch/sh/kernel/dma.c - 1.1 linux/net/irda/af_irda.c - 1.23 linux/net/core/dev.c - 1.41 linux/mm/slab.c - 1.25 linux/kernel/softirq.c - 1.14 linux/include/linux/ntfs_fs_sb.h - 1.10 linux/include/linux/ntfs_fs_i.h - 1.8 linux/include/linux/ntfs_fs.h - 1.5 linux/include/linux/mc146818rtc.h - 1.6 linux/include/linux/interrupt.h - 1.16 linux/include/linux/genhd.h - 1.14 linux/include/linux/blkdev.h - 1.37 linux/include/asm-sparc64/softirq.h - 1.9 linux/include/asm-sparc/softirq.h - 1.10 linux/include/asm-ppc/softirq.h - 1.14 linux/include/asm-ppc/init.h - 1.11 linux/include/asm-i386/softirq.h - 1.13 linux/include/asm-i386/page.h - 1.18 linux/include/asm-arm/softirq.h - 1.8 linux/include/asm-alpha/softirq.h - 1.9 linux/fs/ntfs/util.h - 1.6 linux/fs/ntfs/support.h - 1.5 linux/fs/ntfs/support.c - 1.10 linux/fs/ntfs/super.h - 1.7 linux/fs/ntfs/super.c - 1.11 linux/fs/ntfs/struct.h - 1.7 linux/fs/ntfs/macros.h - 1.6 linux/fs/ntfs/inode.h - 1.5 linux/fs/ntfs/inode.c - 1.12 linux/fs/ntfs/fs.c - 1.30 linux/fs/ntfs/dir.c - 1.8 linux/fs/ntfs/attr.h - 1.5 linux/fs/ntfs/attr.c - 1.7 linux/fs/ntfs/Makefile - 1.11 linux/drivers/scsi/sd.c - 1.42 linux/drivers/net/smc9194.h - 1.4 linux/drivers/net/smc9194.c - 1.16 linux/drivers/macintosh/via-pmu.c - 1.16 linux/drivers/macintosh/mediabay.c - 1.12 linux/drivers/macintosh/macserial.c - 1.18 linux/drivers/block/xd.c - 1.20 linux/drivers/block/ps2esdi.c - 1.19 linux/drivers/block/paride/pd.c - 1.15 linux/drivers/block/ll_rw_blk.c - 1.74 linux/drivers/block/genhd.c - 1.17 linux/drivers/block/acsi.c - 1.14 linux/drivers/acorn/block/mfmhd.c - 1.11 linux/arch/ppc/kernel/smp.c - 1.27 linux/arch/ppc/kernel/setup.c - 1.35 linux/arch/ppc/kernel/residual.c - 1.7 linux/arch/ppc/kernel/prom.c - 1.26 linux/arch/ppc/kernel/prep_time.c - 1.7 linux/arch/ppc/kernel/prep_setup.c - 1.24 linux/arch/ppc/kernel/prep_pci.c - 1.13 linux/arch/ppc/kernel/prep_nvram.c - 1.8 linux/arch/ppc/kernel/pmac_time.c - 1.14 linux/arch/ppc/kernel/pmac_setup.c - 1.25 linux/arch/ppc/kernel/pmac_pic.c - 1.20 linux/arch/ppc/kernel/pmac_pci.c - 1.18 linux/arch/ppc/kernel/open_pic.c - 1.20 linux/arch/ppc/kernel/indirect_pci.c - 1.6 linux/arch/ppc/kernel/feature.c - 1.15 linux/arch/ppc/kernel/chrp_time.c - 1.10 linux/arch/ppc/kernel/chrp_setup.c - 1.26 linux/arch/ppc/kernel/chrp_pci.c - 1.19 linux/arch/ppc/kernel/apus_setup.c - 1.18 linux/arch/ppc/8xx_io/Makefile - 1.6 linux/arch/i386/kernel/setup.c - 1.52 linux/arch/i386/kernel/entry.S - 1.35 linux/Makefile - 1.119 linux/Documentation/filesystems/ntfs.txt - 1.9 linux/Documentation/Configure.help - 1.97 linux/drivers/i2o/i2o_block.c - 1.27 linux/drivers/block/blkpg.c - 1.10 linux/drivers/block/cpqarray.c - 1.26 linux/fs/partitions/check.c - 1.30 linux/drivers/block/DAC960.c - 1.34 linux/arch/sh/vmlinux.lds.S - 1.12 linux/arch/sh/mm/ioremap.c - 1.7 linux/arch/sh/mm/init.c - 1.15 linux/arch/sh/mm/fault.c - 1.16 linux/arch/sh/mm/extable.c - 1.4 linux/arch/sh/mm/Makefile - 1.5 linux/arch/sh/lib/Makefile - 1.7 linux/arch/sh/kernel/traps.c - 1.10 linux/arch/sh/kernel/time.c - 1.16 linux/arch/sh/kernel/sys_sh.c - 1.8 linux/arch/sh/kernel/sh_ksyms.c - 1.10 linux/arch/sh/kernel/setup.c - 1.16 linux/arch/sh/kernel/ptrace.c - 1.10 linux/arch/sh/kernel/process.c - 1.14 linux/arch/sh/kernel/irq.c - 1.12 linux/arch/sh/kernel/entry.S - 1.19 linux/arch/sh/kernel/Makefile - 1.13 linux/arch/sh/config.in - 1.18 linux/arch/sh/Makefile - 1.7 linux/include/asm-sh/uaccess.h - 1.9 linux/include/asm-sh/system.h - 1.11 linux/include/asm-sh/string.h - 1.7 linux/include/asm-sh/softirq.h - 1.9 linux/include/asm-sh/shmparam.h - 1.3 linux/include/asm-sh/semaphore.h - 1.6 linux/include/asm-sh/ptrace.h - 1.7 linux/include/asm-sh/processor.h - 1.14 linux/include/asm-sh/pgtable.h - 1.19 linux/include/asm-sh/page.h - 1.11 linux/include/asm-sh/mmu_context.h - 1.10 linux/include/asm-sh/irq.h - 1.11 linux/include/asm-sh/io.h - 1.11 linux/include/asm-sh/hardirq.h - 1.8 linux/include/asm-sh/elf.h - 1.7 linux/include/asm-sh/dma.h - 1.5 linux/include/asm-sh/checksum.h - 1.8 linux/include/asm-sh/cache.h - 1.5 linux/include/asm-sh/atomic.h - 1.5 linux/arch/ppc/kernel/m8xx_setup.c - 1.16 linux/arch/ppc/8xx_io/Config.in - 1.5 linux/drivers/net/wan/sdla_x25.c - 1.10 linux/drivers/net/wan/sdla_ppp.c - 1.13 linux/drivers/net/wan/sdla_fr.c - 1.14 linux/arch/sh/mm/cache.c - 1.13 linux/arch/sh/lib/checksum.S - 1.7 linux/include/asm-sh/smplock.h - 1.3 linux/include/asm-sh/ide.h - 1.9 linux/include/asm-sh/pgtable-2level.h - 1.7 linux/arch/ppc/kernel/pmac_nvram.c - 1.10 linux/drivers/net/wan/sdla_chdlc.c - 1.12 linux/include/linux/raid/md.h - 1.8 linux/include/asm-ia64/softirq.h - 1.6 linux/include/asm-sh/pgalloc.h - 1.5 linux/include/asm-sh/pci.h - 1.9 linux/drivers/char/sh-sci.c - 1.13 linux/arch/sh/kernel/irq_imask.c - 1.7 linux/arch/sh/kernel/cf-enabler.c - 1.5 linux/drivers/ide/ide.c - 1.28 linux/drivers/ide/ide-probe.c - 1.16 linux/drivers/ide/hd.c - 1.10 linux/include/asm-s390/softirq.h - 1.5 linux/drivers/s390/block/dasd.c - 1.11 linux/arch/sh/kernel/irq_ipr.c - 1.6 linux/include/asm-sh/hd64461.h - 1.4 linux/include/asm-sh/keyboard.h - 1.4 linux/include/asm-sh/linux_logo.h - 1.3 linux/drivers/acpi/Makefile - 1.8 linux/drivers/mtd/ftl.c - 1.6 linux/arch/sh/kernel/setup_hd64461.c - 1.4 linux/arch/ppc/kernel/pmac_backlight.c - 1.4 linux/include/asm-sh/machvec.h - 1.4 linux/arch/sh/kernel/setup_cqreek.c - 1.4 linux/arch/sh/kernel/mach_hp600.c - 1.3 linux/arch/sh/kernel/led_se.c - 1.2 linux/drivers/md/lvm.c - 1.17 linux/arch/i386/kernel/bluesmoke.c - 1.12 linux/drivers/block/cciss.c - 1.13 linux/drivers/macintosh/rtc.c - 1.4 linux/drivers/md/md.c - 1.21 linux/drivers/atm/firestream.c - 1.5 linux/drivers/atm/firestream.h - 1.4 linux/fs/reiserfs/stree.c - 1.7 linux/fs/reiserfs/super.c - 1.7 linux/fs/reiserfs/tail_conversion.c - 1.5 linux/fs/reiserfs/resize.c - 1.2 linux/fs/reiserfs/prints.c - 1.4 linux/fs/reiserfs/objectid.c - 1.3 linux/fs/reiserfs/namei.c - 1.6 linux/fs/reiserfs/lbalance.c - 1.2 linux/fs/reiserfs/journal.c - 1.7 linux/fs/reiserfs/item_ops.c - 1.2 linux/fs/reiserfs/ioctl.c - 1.3 linux/fs/reiserfs/inode.c - 1.10 linux/fs/reiserfs/ibalance.c - 1.2 linux/fs/reiserfs/hashes.c - 1.2 linux/fs/reiserfs/fix_node.c - 1.7 linux/fs/reiserfs/file.c - 1.3 linux/fs/reiserfs/do_balan.c - 1.3 linux/fs/reiserfs/dir.c - 1.5 linux/fs/reiserfs/buffer2.c - 1.2 linux/include/linux/reiserfs_fs.h - 1.8 linux/fs/reiserfs/bitmap.c - 1.4 linux/include/asm-s390x/softirq.h - 1.4 linux/include/asm-cris/softirq.h - 1.3 linux/include/asm-ppc/tqm8xx.h - 1.5 linux/drivers/net/wan/sdla_ft1.c - 1.3 linux/drivers/net/wan/wanpipe_multppp.c - 1.5 linux/arch/sh/kernel/setup_hd64465.c - 1.2 linux/arch/sh/kernel/setup_ec3104.c - 1.3 linux/arch/sh/kernel/setup_dc.c - 1.4 linux/arch/sh/kernel/pci_st40.c - 1.3 linux/arch/sh/kernel/mach_dc.c - 1.4 linux/arch/sh/kernel/irq_intc2.c - 1.4 linux/drivers/net/irda/irda-usb.c - 1.4 linux/arch/ppc/kernel/apus_pci.c - 1.3 linux/drivers/mtd/nftlcore.c - 1.2 linux/arch/sh/kernel/setup_bigsur.c - 1.2 linux/arch/sh/kernel/pci-sh7751.c - 1.2 linux/arch/sh/kernel/pci-dma.c - 1.2 linux/arch/sh/kernel/pci-dc.c - 1.2 linux/arch/sh/kernel/pci-7751se.c - 1.2 linux/Documentation/DocBook/procfs-guide.tmpl - 1.2 linux/drivers/net/wan/farsync.c - 1.2 linux/arch/ppc/kernel/pmac_smp.c - 1.2 linux/arch/ppc/kernel/chrp_smp.c - 1.2 linux/arch/ppc/kernel/btext.c - 1.2 From owner-linux-xfs@oss.sgi.com Sun Sep 9 23:40:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A6eAD06407 for linux-xfs-outgoing; Sun, 9 Sep 2001 23:40:10 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A6dVd06383 for ; Sun, 9 Sep 2001 23:39:32 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8A6dP511990 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Sun, 9 Sep 2001 23:39:25 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id IAA212469 for ; Mon, 10 Sep 2001 08:39:31 +0200 (CEST) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id QAA21231; Mon, 10 Sep 2001 16:39:05 +1000 Date: Mon, 10 Sep 2001 16:39:05 +1000 From: Keith Owens Message-Id: <200109100639.QAA21231@sherman.melbourne.sgi.com> Subject: TAKE - Upgrade to 2.4.10-pre7 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Upgrade to 2.4.10-pre7. Ramdisk and quota should compile again. Date: Sun Sep 9 23:34:52 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102429a linux/include/asm-mips/ddb5xxx/pci.h - 1.1 linux/arch/mips64/sgi-ip32/ip32-timer.c - 1.1 linux/arch/mips64/mips-boards/atlas/atlas_setup.c - 1.1 linux/arch/mips64/sgi-ip32/ip32-setup.c - 1.1 linux/arch/mips64/sgi-ip32/ip32-rtc.c - 1.1 linux/arch/mips64/sgi-ip32/ip32-pci.c - 1.1 linux/arch/mips64/sgi-ip32/ip32-pci-dma.c - 1.1 linux/arch/mips64/sgi-ip32/ip32-irq.c - 1.1 linux/arch/mips64/sgi-ip32/ip32-irq-glue.S - 1.1 linux/arch/mips/au1000/common/Makefile - 1.1 linux/arch/mips/au1000/common/dbg_io.c - 1.1 linux/arch/mips/au1000/common/int-handler.S - 1.1 linux/arch/mips/au1000/common/irq.c - 1.1 linux/arch/mips/au1000/common/prom.c - 1.1 linux/arch/mips/au1000/common/puts.c - 1.1 linux/arch/mips/au1000/common/reset.c - 1.1 linux/arch/mips/au1000/common/serial.c - 1.1 linux/arch/mips/au1000/common/time.c - 1.1 linux/arch/mips/au1000/pb1000/Makefile - 1.1 linux/arch/mips/au1000/pb1000/init.c - 1.1 linux/arch/mips/au1000/pb1000/setup.c - 1.1 linux/include/asm-mips/mips-boards/saa9730_uart.h - 1.1 linux/arch/mips64/mips-boards/generic/pci.c - 1.1 linux/include/asm-mips/linux_logo_dec.h - 1.1 linux/arch/mips/ite-boards/ivr/Makefile - 1.1 linux/include/asm-mips64/tlb.h - 1.1 linux/arch/mips64/sgi-ip32/ip32-berr.c - 1.1 linux/arch/mips64/sgi-ip32/crime.c - 1.1 linux/arch/mips64/sgi-ip32/Makefile - 1.1 linux/include/asm-mips64/mips-boards/saa9730_uart.h - 1.1 linux/include/asm-mips64/mips-boards/prom.h - 1.1 linux/include/asm-mips64/mips-boards/piix4.h - 1.1 linux/include/asm-mips64/mips-boards/maltaint.h - 1.1 linux/arch/mips/ddb5xxx/common/Makefile - 1.1 linux/arch/mips/ddb5xxx/common/irq.c - 1.1 linux/arch/mips/ddb5xxx/common/irq_cpu.c - 1.1 linux/arch/mips/ddb5xxx/common/nile4.c - 1.1 linux/arch/mips/ddb5xxx/common/pci.c - 1.1 linux/arch/mips/ddb5xxx/common/pci_auto.c - 1.1 linux/arch/mips/ddb5xxx/common/prom.c - 1.1 linux/arch/mips/ddb5xxx/common/rtc_ds1386.c - 1.1 linux/arch/mips/ddb5xxx/ddb5477/Makefile - 1.1 linux/arch/mips/ddb5xxx/ddb5477/debug.c - 1.1 linux/arch/mips/ddb5xxx/ddb5477/int-handler.S - 1.1 linux/arch/mips/ddb5xxx/ddb5477/irq.c - 1.1 linux/arch/mips/ddb5xxx/ddb5477/irq_5477.c - 1.1 linux/arch/mips/ddb5xxx/ddb5477/kgdb_io.c - 1.1 linux/arch/mips/ddb5xxx/ddb5477/pci.c - 1.1 linux/arch/mips/ddb5xxx/ddb5477/pci_ops.c - 1.1 linux/arch/mips/ddb5xxx/ddb5477/setup.c - 1.1 linux/include/asm-mips64/mips-boards/malta.h - 1.1 linux/include/asm-mips64/mips-boards/io.h - 1.1 linux/include/asm-mips64/mips-boards/gt64120.h - 1.1 linux/include/asm-mips64/mips-boards/generic.h - 1.1 linux/include/asm-mips64/mips-boards/atlasint.h - 1.1 linux/include/asm-mips64/mips-boards/atlas.h - 1.1 linux/arch/mips64/mips-boards/generic/printf.c - 1.1 linux/arch/mips64/mips-boards/generic/reset.c - 1.1 linux/arch/mips64/mips-boards/generic/time.c - 1.1 linux/arch/mips/philips/nino/time.c - 1.1 linux/arch/mips/philips/nino/setup.c - 1.1 linux/arch/mips64/mips-boards/atlas/atlas_rtc.c - 1.1 linux/arch/mips/defconfig-atlas - 1.1 linux/arch/mips/philips/nino/rtc.c - 1.1 linux/arch/mips/philips/nino/reset.c - 1.1 linux/arch/mips/defconfig-ddb5477 - 1.1 linux/arch/mips/philips/nino/ramdisk/ld.script - 1.1 linux/arch/mips/philips/nino/ramdisk/Makefile - 1.1 linux/arch/mips/philips/nino/prom.c - 1.1 linux/arch/mips/defconfig-malta - 1.1 linux/arch/mips/defconfig-nino - 1.1 linux/arch/mips/defconfig-ocelot - 1.1 linux/arch/mips/philips/nino/power.c - 1.1 linux/arch/mips/defconfig-pb1000 - 1.1 linux/include/asm-mips/pci_channel.h - 1.1 linux/arch/mips/gt64120/common/Makefile - 1.1 linux/arch/mips/gt64120/common/gt_irq.c - 1.1 linux/arch/mips/gt64120/common/pci.c - 1.1 linux/arch/mips/gt64120/momenco_ocelot/Makefile - 1.1 linux/arch/mips/gt64120/momenco_ocelot/dbg_io.c - 1.1 linux/arch/mips/gt64120/momenco_ocelot/int-handler.S - 1.1 linux/arch/mips/gt64120/momenco_ocelot/irq.c - 1.1 linux/arch/mips/gt64120/momenco_ocelot/ocelot_pld.h - 1.1 linux/arch/mips/gt64120/momenco_ocelot/pci.c - 1.1 linux/arch/mips/gt64120/momenco_ocelot/prom.c - 1.1 linux/arch/mips/gt64120/momenco_ocelot/reset.c - 1.1 linux/arch/mips/gt64120/momenco_ocelot/setup.c - 1.1 linux/arch/mips/philips/nino/kgdb.c - 1.1 linux/arch/mips/philips/nino/irq.c - 1.1 linux/include/asm-mips/mips-boards/prom.h - 1.1 linux/arch/mips64/mips-boards/malta/malta_int.c - 1.1 linux/include/asm-mips/mips-boards/piix4.h - 1.1 linux/include/asm-mips/mips-boards/maltaint.h - 1.1 linux/include/asm-mips/mips-boards/malta.h - 1.1 linux/include/asm-mips/mips-boards/generic.h - 1.1 linux/include/asm-mips/mips-boards/atlasint.h - 1.1 linux/include/asm-mips/mips-boards/atlas.h - 1.1 linux/include/asm-mips/linux_logo_sgi.h - 1.1 linux/arch/mips/kernel/pci_auto.c - 1.1 linux/arch/mips/philips/nino/int-handler.S - 1.1 linux/arch/mips/ite-boards/ivr/README - 1.1 linux/arch/mips/ite-boards/ivr/init.c - 1.1 linux/arch/mips/ite-boards/ivr/pci_fixup.c - 1.1 linux/arch/mips/philips/nino/Makefile - 1.1 linux/arch/mips64/mips-boards/generic/mipsIRQ.S - 1.1 linux/arch/mips64/mips-boards/malta/Makefile - 1.1 linux/arch/mips/jazz/irq.c - 1.1 linux/arch/mips64/mips-boards/atlas/atlas_int.c - 1.1 linux/arch/mips64/mips-boards/atlas/Makefile - 1.1 linux/drivers/isdn/hisax/hisax_if.h - 1.1 linux/drivers/isdn/hisax/st5481.h - 1.1 linux/drivers/isdn/hisax/st5481_b.c - 1.1 linux/drivers/isdn/hisax/st5481_d.c - 1.1 linux/drivers/isdn/hisax/st5481_hdlc.c - 1.1 linux/drivers/isdn/hisax/st5481_hdlc.h - 1.1 linux/drivers/isdn/hisax/st5481_init.c - 1.1 linux/drivers/isdn/hisax/st5481_usb.c - 1.1 linux/drivers/scsi/README.53c700 - 1.1 linux/drivers/net/ns83820.c - 1.1 linux/drivers/scsi/53c700-mem.c - 1.1 linux/drivers/scsi/53c700.c - 1.1 linux/drivers/scsi/53c700.h - 1.1 linux/drivers/scsi/53c700.scr - 1.1 linux/arch/mips64/mips-boards/generic/cmdline.c - 1.1 linux/drivers/scsi/NCR_D700.c - 1.1 linux/drivers/char/decserial.c - 1.1 linux/drivers/scsi/NCR_D700.h - 1.1 linux/drivers/char/ite_gpio.c - 1.1 linux/include/asm-mips/gt64120/gt64120.h - 1.1 linux/drivers/scsi/README.dpti - 1.1 linux/drivers/i2c/i2c-adap-ite.c - 1.1 linux/drivers/i2c/i2c-algo-ite.c - 1.1 linux/drivers/i2c/i2c-ite.h - 1.1 linux/arch/mips64/defconfig-ip32 - 1.1 linux/drivers/scsi/lasi700.c - 1.1 linux/drivers/scsi/lasi700.h - 1.1 linux/arch/mips64/mips-boards/generic/Makefile - 1.1 linux/include/asm-mips/gcc/sgidefs.h - 1.1 linux/arch/mips/sni/irq.c - 1.1 linux/drivers/isdn/hisax/fsm.h - 1.1 linux/include/asm-mips/ddb5xxx/debug.h - 1.1 linux/include/asm-mips/gt64120/momenco_ocelot/gt64120_dep.h - 1.1 linux/include/asm-mips/gt64120.h - 1.1 linux/include/asm-mips/ddb5xxx/ddb5477.h - 1.1 linux/arch/mips64/mips-boards/generic/display.c - 1.1 linux/include/asm-mips/dec/ioasic.h - 1.1 linux/arch/mips64/mips-boards/generic/gdb_hook.c - 1.1 linux/arch/mips64/mips-boards/generic/init.c - 1.1 linux/include/asm-mips/ddb5xxx/ddb5xxx.h - 1.1 linux/drivers/isdn/hisax/hisax_debug.h - 1.1 linux/arch/mips64/mips-boards/malta/malta_setup.c - 1.1 linux/arch/mips64/mips-boards/generic/memory.c - 1.1 linux/include/asm-mips/au1000.h - 1.1 linux/arch/mips64/mips-boards/malta/malta_rtc.c - 1.1 linux/net/ax25/ax25_in.c - 1.10 linux/kernel/ksyms.c - 1.105 linux/include/linux/soundcard.h - 1.6 linux/include/linux/module.h - 1.21 linux/include/linux/isdn.h - 1.18 linux/include/asm-mips/uaccess.h - 1.8 linux/include/asm-mips/termios.h - 1.10 linux/include/asm-mips/termbits.h - 1.3 linux/include/asm-mips/system.h - 1.10 linux/include/asm-mips/string.h - 1.6 linux/include/asm-mips/softirq.h - 1.6 linux/include/asm-mips/sgidefs.h - 1.3 linux/include/asm-mips/semaphore.h - 1.9 linux/include/asm-mips/reboot.h - 1.4 linux/include/asm-mips/processor.h - 1.16 linux/include/asm-mips/pgtable.h - 1.14 linux/include/asm-mips/pci.h - 1.11 linux/include/asm-mips/mipsregs.h - 1.9 linux/include/asm-mips/linux_logo.h - 1.6 linux/include/asm-mips/keyboard.h - 1.9 linux/include/asm-mips/irq.h - 1.7 linux/include/asm-mips/ioctls.h - 1.6 linux/include/asm-mips/io.h - 1.8 linux/include/asm-mips/ide.h - 1.9 linux/include/asm-mips/hardirq.h - 1.10 linux/include/asm-mips/elf.h - 1.10 linux/include/asm-mips/cpu.h - 1.6 linux/include/asm-mips/cachectl.h - 1.3 linux/include/asm-mips/bootinfo.h - 1.10 linux/include/asm-mips/bitops.h - 1.8 linux/include/asm-mips/atomic.h - 1.8 linux/include/asm-mips/asm.h - 1.4 linux/fs/super.c - 1.53 linux/fs/ntfs/support.h - 1.6 linux/fs/minix/file.c - 1.12 linux/fs/dquot.c - 1.36 linux/drivers/sound/sound_core.c - 1.18 linux/drivers/sound/opl3sa2.c - 1.9 linux/drivers/scsi/sgiwd93.c - 1.11 linux/drivers/scsi/sd.c - 1.43 linux/drivers/scsi/scsi_error.c - 1.20 linux/drivers/scsi/megaraid.c - 1.26 linux/drivers/scsi/Makefile - 1.27 linux/drivers/scsi/Config.in - 1.23 linux/drivers/pci/Makefile - 1.17 linux/drivers/net/pcnet32.c - 1.25 linux/drivers/net/dgrs.c - 1.18 linux/drivers/net/cs89x0.c - 1.19 linux/drivers/isdn/isdnloop/isdnloop.h - 1.7 linux/drivers/isdn/isdnloop/isdnloop.c - 1.8 linux/drivers/isdn/isdn_tty.h - 1.9 linux/drivers/isdn/isdn_tty.c - 1.16 linux/drivers/isdn/isdn_net.h - 1.9 linux/drivers/isdn/isdn_net.c - 1.23 linux/drivers/isdn/isdn_common.c - 1.27 linux/drivers/isdn/hisax/isdnl1.h - 1.5 linux/drivers/isdn/hisax/isdnl1.c - 1.13 linux/drivers/isdn/hisax/hisax.h - 1.21 linux/drivers/isdn/hisax/fsm.c - 1.9 linux/drivers/isdn/hisax/config.c - 1.23 linux/drivers/isdn/hisax/callc.c - 1.14 linux/drivers/isdn/hisax/Makefile - 1.13 linux/drivers/isdn/act2000/act2000_isa.c - 1.6 linux/drivers/isdn/Config.in - 1.19 linux/drivers/char/rtc.c - 1.22 linux/drivers/char/mem.c - 1.38 linux/drivers/char/epca.c - 1.17 linux/drivers/char/Makefile - 1.48 linux/drivers/char/Config.in - 1.47 linux/drivers/cdrom/sonycd535.c - 1.13 linux/drivers/cdrom/sbpcd.c - 1.14 linux/drivers/cdrom/optcd.c - 1.12 linux/drivers/cdrom/mcd.h - 1.4 linux/drivers/cdrom/mcd.c - 1.12 linux/drivers/cdrom/aztcd.c - 1.13 linux/drivers/block/xd.c - 1.21 linux/drivers/block/rd.c - 1.32 linux/drivers/block/ps2esdi.c - 1.20 linux/drivers/block/paride/pd.c - 1.16 linux/drivers/block/genhd.c - 1.18 linux/drivers/block/acsi.c - 1.15 linux/drivers/block/Makefile - 1.22 linux/drivers/acorn/block/mfmhd.c - 1.12 linux/arch/mips/sni/setup.c - 1.9 linux/arch/mips/sni/pci.c - 1.9 linux/arch/mips/sni/int-handler.S - 1.6 linux/arch/mips/sgi/kernel/time.c - 1.8 linux/arch/mips/sgi/kernel/setup.c - 1.10 linux/arch/mips/sgi/kernel/reset.c - 1.7 linux/arch/mips/sgi/kernel/indy_timer.c - 1.9 linux/arch/mips/sgi/kernel/indy_sc.c - 1.9 linux/arch/mips/sgi/kernel/indy_rtc.c - 1.5 linux/arch/mips/sgi/kernel/indy_int.c - 1.10 linux/arch/mips/sgi/kernel/indy_hpc.c - 1.7 linux/arch/mips/mm/r4xx0.c - 1.9 linux/arch/mips/mm/r2300.c - 1.10 linux/arch/mips/mm/loadmmu.c - 1.9 linux/arch/mips/mm/andes.c - 1.9 linux/arch/mips/mm/Makefile - 1.7 linux/arch/mips/lib/memcpy.S - 1.7 linux/arch/mips/lib/ide-std.c - 1.5 linux/arch/mips/kernel/unaligned.c - 1.7 linux/arch/mips/kernel/traps.c - 1.11 linux/arch/mips/kernel/time.c - 1.11 linux/arch/mips/kernel/softfp.S - 1.6 linux/arch/mips/kernel/signal.c - 1.13 linux/arch/mips/kernel/setup.c - 1.12 linux/arch/mips/kernel/scall_o32.S - 1.9 linux/arch/mips/kernel/reset.c - 1.3 linux/arch/mips/kernel/r4k_switch.S - 1.8 linux/arch/mips/kernel/r2300_switch.S - 1.8 linux/arch/mips/kernel/ptrace.c - 1.12 linux/arch/mips/kernel/process.c - 1.12 linux/arch/mips/kernel/proc.c - 1.6 linux/arch/mips/kernel/pci.c - 1.7 linux/arch/mips/kernel/mips_ksyms.c - 1.11 linux/arch/mips/kernel/irq.c - 1.11 linux/arch/mips/kernel/head.S - 1.10 linux/arch/mips/kernel/gdb-stub.c - 1.7 linux/arch/mips/kernel/gdb-low.S - 1.6 linux/arch/mips/kernel/fpe.c - 1.6 linux/arch/mips/kernel/entry.S - 1.8 linux/arch/mips/kernel/branch.c - 1.4 linux/arch/mips/kernel/Makefile - 1.8 linux/arch/mips/jazz/setup.c - 1.7 linux/arch/mips/jazz/rtc-jazz.c - 1.6 linux/arch/mips/jazz/jazzdma.c - 1.5 linux/arch/mips/defconfig - 1.19 linux/arch/mips/config.in - 1.23 linux/arch/mips/boot/mkboot.c - 1.4 linux/arch/mips/boot/Makefile - 1.7 linux/arch/mips/Makefile - 1.10 linux/arch/i386/kernel/setup.c - 1.53 linux/arch/i386/defconfig - 1.67 linux/Makefile - 1.120 linux/MAINTAINERS - 1.71 linux/Documentation/isdn/README - 1.7 linux/Documentation/CodingStyle - 1.4 linux/CREDITS - 1.60 linux/drivers/net/irda/toshoboe.c - 1.24 linux/drivers/isdn/hisax/elsa_ser.c - 1.9 linux/drivers/i2o/i2o_block.c - 1.28 linux/include/asm-mips/semaphore-helper.h - 1.6 linux/include/asm-mips/dec/tcmodule.h - 1.2 linux/include/asm-mips/dec/kn03.h - 1.2 linux/include/asm-mips/dec/kn02xa.h - 1.2 linux/include/asm-mips/dec/kn02.h - 1.2 linux/include/asm-mips/dec/ioasic_addrs.h - 1.2 linux/include/asm-mips/dec/interrupts.h - 1.2 linux/drivers/net/jazzsonic.c - 1.8 linux/drivers/net/declance.c - 1.12 linux/drivers/char/dz.c - 1.13 linux/arch/mips/sgi/kernel/promcon.c - 1.5 linux/arch/mips/dec/time.c - 1.6 linux/arch/mips/dec/setup.c - 1.4 linux/arch/mips/dec/serial.c - 1.5 linux/arch/mips/dec/rtc-dec.c - 1.4 linux/arch/mips/dec/reset.c - 1.3 linux/arch/mips/dec/prom/memory.c - 1.8 linux/arch/mips/dec/prom/init.c - 1.5 linux/arch/mips/dec/prom/cmdline.c - 1.5 linux/arch/mips/dec/irq.c - 1.7 linux/arch/mips/dec/int-handler.S - 1.2 linux/arch/mips/dec/Makefile - 1.4 linux/arch/mips/baget/vacserial.c - 1.10 linux/arch/mips/baget/time.c - 1.5 linux/arch/mips/baget/setup.c - 1.5 linux/arch/mips/baget/prom/init.c - 1.5 linux/arch/mips/baget/irq.c - 1.8 linux/drivers/net/ppp_generic.c - 1.22 linux/drivers/isdn/isdn_ttyfax.c - 1.6 linux/drivers/net/sis900.c - 1.26 linux/drivers/block/DAC960.c - 1.35 linux/drivers/net/dmfe.c - 1.19 linux/include/linux/pci_ids.h - 1.44 linux/drivers/net/wan/z85230.c - 1.10 linux/drivers/net/wan/sealevel.c - 1.9 linux/drivers/net/wan/sbni.c - 1.14 linux/drivers/net/wan/hostess_sv11.c - 1.9 linux/drivers/scsi/dec_esp.c - 1.6 linux/drivers/net/sk98lin/h/skdrv1st.h - 1.6 linux/drivers/telephony/ixj.c - 1.19 linux/drivers/char/moxa.c - 1.8 linux/drivers/sound/via82cxxx_audio.c - 1.20 linux/arch/mips/ddb5074/pci.c - 1.7 linux/arch/mips/defconfig-decstation - 1.7 linux/arch/mips/defconfig-ip22 - 1.8 linux/drivers/net/tulip/tulip_core.c - 1.27 linux/include/asm-mips64/ioctl.h - 1.4 linux/include/asm-mips64/io.h - 1.6 linux/include/asm-mips64/inst.h - 1.3 linux/include/asm-mips64/init.h - 1.4 linux/include/asm-mips64/ide.h - 1.6 linux/include/asm-mips64/hardirq.h - 1.5 linux/include/asm-mips64/gfx.h - 1.3 linux/include/asm-mips64/fcntl.h - 1.7 linux/include/asm-mips64/elf.h - 1.7 linux/include/asm-mips64/ds1286.h - 1.3 linux/include/asm-mips64/div64.h - 1.3 linux/include/asm-mips64/current.h - 1.3 linux/include/asm-mips64/cachectl.h - 1.2 linux/include/asm-mips64/byteorder.h - 1.3 linux/include/asm-mips64/bugs.h - 1.3 linux/include/asm-mips64/branch.h - 1.3 linux/include/asm-mips64/bootinfo.h - 1.5 linux/include/asm-mips64/bitops.h - 1.6 linux/include/asm-mips64/bcache.h - 1.4 linux/include/asm-mips64/asmmacro.h - 1.3 linux/include/asm-mips64/asm.h - 1.3 linux/include/asm-mips64/arc/hinv.h - 1.3 linux/include/asm-mips64/addrspace.h - 1.4 linux/include/asm-mips64/a.out.h - 1.3 linux/include/asm-mips/isadep.h - 1.3 linux/include/asm-mips/div64.h - 1.4 linux/include/asm-mips64/sn/sn0/ip27.h - 1.5 linux/include/asm-mips64/sn/sn0/addrs.h - 1.3 linux/include/asm-mips64/sn/klconfig.h - 1.4 linux/include/asm-mips64/sn/gda.h - 1.3 linux/include/asm-mips64/sn/arch.h - 1.4 linux/include/asm-mips64/signal.h - 1.3 linux/include/asm-mips64/xtalk/xwidget.h - 1.3 linux/include/asm-mips64/sigcontext.h - 1.3 linux/include/asm-mips64/shmparam.h - 1.3 linux/include/asm-mips64/shmiq.h - 1.4 linux/include/asm-mips64/sgidefs.h - 1.3 linux/include/asm-mips64/xtalk/xtalk.h - 1.3 linux/include/asm-mips64/sgiarcs.h - 1.4 linux/include/asm-mips64/sgialib.h - 1.4 linux/include/asm-mips64/sgi/sgint23.h - 1.5 linux/include/asm-mips64/sgi/sgimc.h - 1.3 linux/include/asm-mips64/sgi/sgihpc.h - 1.3 linux/include/asm-mips64/usioctl.h - 1.3 linux/include/asm-mips64/sgi/sgi.h - 1.3 linux/include/asm-mips64/sgi/io.h - 1.3 linux/include/asm-mips64/serial.h - 1.5 linux/include/asm-mips64/user.h - 1.3 linux/include/asm-mips64/resource.h - 1.6 linux/include/asm-mips64/regdef.h - 1.3 linux/include/asm-mips64/r4kcacheops.h - 1.3 linux/include/asm-mips64/r4kcache.h - 1.3 linux/include/asm-mips64/r10kcacheops.h - 1.3 linux/include/asm-mips64/r10kcache.h - 1.3 linux/include/asm-mips64/ucontext.h - 1.3 linux/include/asm-mips64/poll.h - 1.3 linux/include/asm-mips64/pgtable.h - 1.9 linux/include/asm-mips64/uaccess.h - 1.5 linux/include/asm-mips64/pci/bridge.h - 1.4 linux/include/asm-mips64/pci.h - 1.7 linux/include/asm-mips64/parport.h - 1.4 linux/include/asm-mips64/types.h - 1.3 linux/include/asm-mips64/paccess.h - 1.3 linux/include/asm-mips64/timex.h - 1.3 linux/include/asm-mips64/termios.h - 1.6 linux/include/asm-mips64/termbits.h - 1.3 linux/include/asm-mips64/sysmips.h - 1.3 linux/include/asm-mips64/statfs.h - 1.3 linux/include/asm-mips64/softirq.h - 1.3 linux/include/asm-mips64/sockios.h - 1.3 linux/include/asm-mips64/sn/types.h - 1.5 linux/include/asm-mips64/sn/sn0/sn0_fru.h - 1.3 linux/include/asm-mips64/ng1.h - 1.3 linux/include/asm-mips64/namei.h - 1.4 linux/include/asm-mips64/sn/sn0/hubpi.h - 1.3 linux/include/asm-mips64/ioctls.h - 1.5 linux/include/asm-mips64/mmu_context.h - 1.6 linux/include/asm-mips64/sn/sn0/hubni.h - 1.3 linux/include/asm-mips64/sn/sn0/hub.h - 1.3 linux/include/asm-mips64/sn/sn0/hubmd.h - 1.3 linux/include/asm-mips64/sn/sn0/arch.h - 1.3 linux/include/asm-mips64/sn/sn0/hubio.h - 1.3 linux/include/asm-mips64/keyboard.h - 1.4 linux/include/asm-mips64/linux_logo.h - 1.4 linux/include/asm-mips64/mman.h - 1.3 linux/include/asm-mips64/mipsregs.h - 1.7 linux/include/asm-mips64/mc146818rtc.h - 1.4 linux/arch/mips64/defconfig - 1.15 linux/arch/mips64/sgi-ip22/ip22-rtc.c - 1.3 linux/arch/mips64/arc/env.c - 1.3 linux/arch/mips64/sgi-ip22/ip22-reset.c - 1.4 linux/arch/mips64/sgi-ip22/ip22-int.c - 1.6 linux/arch/mips64/sgi-ip22/ip22-mc.c - 1.3 linux/arch/mips64/sgi-ip22/ip22-irq.S - 1.3 linux/arch/mips64/sgi-ip22/ip22-hpc.c - 1.4 linux/arch/mips64/sgi-ip22/ip22-berr.c - 1.3 linux/arch/mips64/mm/umap.c - 1.6 linux/arch/mips64/arc/file.c - 1.3 linux/arch/mips64/arc/memory.c - 1.6 linux/arch/mips64/mm/fault.c - 1.8 linux/arch/mips64/mm/extable.c - 1.4 linux/arch/mips64/lib/strlen_user.S - 1.3 linux/arch/mips64/lib/strnlen_user.S - 1.3 linux/arch/mips64/lib/strncpy_user.S - 1.3 linux/arch/mips64/lib/memcpy.S - 1.5 linux/arch/mips64/arc/init.c - 1.3 linux/arch/mips64/mm/andes.c - 1.7 linux/arch/mips64/lib/kbd-no.c - 1.3 linux/arch/mips64/lib/floppy-no.c - 1.3 linux/arch/mips64/lib/ide-std.c - 1.3 linux/arch/mips64/lib/ide-no.c - 1.3 linux/arch/mips64/lib/dump_tlb.c - 1.3 linux/arch/mips64/lib/csum_partial_copy.c - 1.3 linux/arch/mips64/lib/csum_partial.S - 1.3 linux/arch/mips64/kernel/traps.c - 1.6 linux/arch/mips64/kernel/unaligned.c - 1.5 linux/arch/mips64/sgi-ip27/ip27-timer.c - 1.8 linux/arch/mips64/sgi-ip27/ip27-setup.c - 1.6 linux/arch/mips64/sgi-ip27/ip27-pci.c - 1.5 linux/arch/mips64/sgi-ip27/ip27-pci-dma.c - 1.4 linux/arch/mips64/sgi-ip27/ip27-memory.c - 1.8 linux/arch/mips64/arc/time.c - 1.3 linux/arch/mips64/sgi-ip27/ip27-klconfig.c - 1.4 linux/arch/mips64/sgi-ip27/ip27-irq.c - 1.8 linux/arch/mips64/sgi-ip27/ip27-irq-glue.S - 1.3 linux/arch/mips64/arc/tree.c - 1.4 linux/arch/mips64/sgi-ip27/ip27-init.c - 1.8 linux/arch/mips64/sgi-ip27/ip27-berr.c - 1.4 linux/arch/mips64/config.in - 1.15 linux/arch/mips64/sgi-ip27/Makefile - 1.6 linux/arch/mips64/sgi-ip22/time.c - 1.3 linux/arch/mips64/sgi-ip22/system.c - 1.3 linux/arch/mips64/sgi-ip22/ip22-timer.c - 1.6 linux/arch/mips64/defconfig-ip22 - 1.10 linux/arch/mips64/kernel/binfmt_elf32.c - 1.6 linux/arch/mips64/kernel/scall_o32.S - 1.7 linux/arch/mips64/kernel/r4k_tlb_debug.c - 1.3 linux/arch/mips64/sgi-ip22/ip22-setup.c - 1.6 linux/arch/mips/sni/dma.c - 1.3 linux/arch/mips64/Makefile - 1.8 linux/arch/mips64/mm/r4xx0.c - 1.8 linux/arch/mips64/mm/loadmmu.c - 1.5 linux/arch/mips64/lib/kbd-std.c - 1.3 linux/arch/mips64/kernel/syscall.c - 1.8 linux/arch/mips64/kernel/signal32.c - 1.8 linux/arch/mips64/kernel/signal.c - 1.7 linux/arch/mips64/arc/misc.c - 1.3 linux/arch/mips64/arc/salone.c - 1.3 linux/arch/mips64/kernel/setup.c - 1.7 linux/arch/mips64/sgi-ip22/ip22-sc.c - 1.5 linux/arch/mips64/kernel/linux32.c - 1.10 linux/arch/mips64/kernel/scall_64.S - 1.9 linux/arch/mips64/defconfig-ip27 - 1.9 linux/arch/mips64/kernel/r4k_tlb_glue.S - 1.4 linux/arch/mips64/kernel/entry.S - 1.6 linux/arch/mips64/kernel/r4k_switch.S - 1.3 linux/arch/mips64/kernel/mips64_ksyms.c - 1.7 linux/arch/mips64/kernel/proc.c - 1.5 linux/arch/mips64/kernel/ptrace.c - 1.7 linux/arch/mips64/kernel/r4k_cache.S - 1.3 linux/arch/mips64/kernel/r4k_genex.S - 1.3 linux/drivers/net/appletalk/ltpc.c - 1.10 linux/drivers/net/appletalk/ipddp.c - 1.8 linux/drivers/net/appletalk/cops.c - 1.12 linux/drivers/ide/ide-pci.c - 1.16 linux/drivers/ide/ide-dma.c - 1.12 linux/drivers/ide/hd.c - 1.11 linux/drivers/ide/amd7409.c - 1.8 linux/Documentation/DocBook/kernel-api.tmpl - 1.11 linux/drivers/sound/i810_audio.c - 1.15 linux/include/asm-mips64/sn/launch.h - 1.2 linux/arch/mips/defconfig-cobalt - 1.4 linux/arch/mips/defconfig-orion - 1.4 linux/arch/mips/defconfig-rm200 - 1.4 linux/arch/mips64/sgi-ip27/ip27-klnuma.c - 1.3 linux/drivers/media/video/zr36120.c - 1.8 linux/drivers/isdn/eicon/sys.h - 1.3 linux/drivers/isdn/eicon/pc.h - 1.3 linux/drivers/isdn/eicon/kprintf.c - 1.5 linux/drivers/isdn/eicon/idi.c - 1.3 linux/drivers/md/lvm.c - 1.18 linux/include/asm-mips/module.h - 1.2 linux/include/asm-mips64/module.h - 1.2 linux/arch/mips64/sgi-ip27/ip27-console.c - 1.2 linux/drivers/net/gt96100eth.h - 1.2 linux/drivers/net/gt96100eth.c - 1.2 linux/drivers/char/qtronix.c - 1.2 linux/arch/mips/mips-boards/malta/malta_setup.c - 1.2 linux/arch/mips/mips-boards/malta/malta_rtc.c - 1.2 linux/arch/mips/mips-boards/malta/malta_int.c - 1.2 linux/arch/mips/mips-boards/generic/time.c - 1.2 linux/arch/mips/mips-boards/generic/pci.c - 1.2 linux/arch/mips/mips-boards/generic/memory.c - 1.2 linux/arch/mips/mips-boards/generic/gdb_hook.c - 1.2 linux/arch/mips/mips-boards/generic/cmdline.c - 1.2 linux/arch/mips/mips-boards/atlas/atlas_setup.c - 1.2 linux/arch/mips/mips-boards/atlas/atlas_rtc.c - 1.2 linux/arch/mips/mips-boards/atlas/atlas_int.c - 1.2 linux/arch/mips/math-emu/cp1emu.c - 1.3 linux/arch/mips/ite-boards/qed-4n-s01b/pci_fixup.c - 1.2 linux/arch/mips/ite-boards/qed-4n-s01b/init.c - 1.2 linux/arch/mips/ite-boards/qed-4n-s01b/Makefile - 1.2 linux/arch/mips/ite-boards/generic/time.c - 1.2 linux/arch/mips/ite-boards/generic/reset.c - 1.2 linux/arch/mips/ite-boards/generic/puts.c - 1.2 linux/arch/mips/ite-boards/generic/pmon_prom.c - 1.2 linux/arch/mips/ite-boards/generic/lpc.c - 1.2 linux/arch/mips/ite-boards/generic/it8172_setup.c - 1.2 linux/arch/mips/ite-boards/generic/it8172_rtc.c - 1.2 linux/arch/mips/ite-boards/generic/it8172_pci.c - 1.2 linux/arch/mips/ite-boards/generic/it8172_cir.c - 1.2 linux/arch/mips/ite-boards/generic/irq.c - 1.3 linux/arch/mips/ite-boards/generic/dbg_io.c - 1.2 linux/arch/mips/ite-boards/generic/Makefile - 1.2 linux/arch/mips/defconfig-it8172 - 1.2 linux/include/asm-mips/it8172/it8172.h - 1.2 linux/include/asm-mips/it8172/it8172_cir.h - 1.2 linux/arch/mips/defconfig-ddb5476 - 1.2 linux/include/asm-mips/it8172/it8172_dbg.h - 1.2 linux/include/asm-mips/it8172/it8172_int.h - 1.2 linux/include/asm-mips/it8172/it8172_lpc.h - 1.2 linux/arch/mips/ddb5476/setup.c - 1.2 linux/arch/mips/ddb5476/pci.c - 1.2 linux/arch/mips/ddb5476/int-handler.S - 1.2 linux/include/asm-mips/it8172/it8172_pci.h - 1.2 linux/drivers/net/irda/irda-usb.c - 1.5 linux/net/bluetooth/hci_core.c - 1.4 linux/drivers/mtd/nftlcore.c - 1.3 linux/include/asm-mips/time.h - 1.2 linux/include/asm-mips/tx3912.h - 1.2 linux/arch/mips/kernel/i8259.c - 1.2 linux/arch/mips/kernel/old-irq.c - 1.2 linux/arch/mips/kernel/old-time.c - 1.2 linux/arch/mips/kernel/pci-dma.c - 1.2 linux/arch/mips64/math-emu/cp1emu.c - 1.2 linux/arch/mips/mm/r5432.c - 1.2 linux/arch/mips/mm/mips32.c - 1.2 linux/drivers/media/video/zr36067.c - 1.3 linux/drivers/net/au1000_eth.c - 1.2 linux/drivers/net/lp486e.c - 1.3 linux/drivers/net/wan/farsync.c - 1.3 linux/drivers/ide/serverworks.c - 1.2 linux/drivers/video/radeonfb.c - 1.2 linux/drivers/video/radeon.h - 1.2 linux/drivers/scsi/dpt_i2o.c - 1.2 From owner-linux-xfs@oss.sgi.com Sun Sep 9 23:47:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A6lOT06633 for linux-xfs-outgoing; Sun, 9 Sep 2001 23:47:24 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A6lJd06614; Sun, 9 Sep 2001 23:47:19 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8A6lKd06615 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 00:11:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A7BMH07057 for linux-xfs-outgoing; Mon, 10 Sep 2001 00:11:22 -0700 Received: from alpha.bytecomm.com.au (byt130674-1.gw.connect.com.au [202.21.11.108]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A7BFd07032 for ; Mon, 10 Sep 2001 00:11:15 -0700 Received: (qmail 23426 invoked from network); 10 Sep 2001 07:11:02 -0000 Received: from unknown (HELO herbie.local) (192.168.0.11) by 192.168.0.1 with SMTP; 10 Sep 2001 07:11:02 -0000 Received: by herbie.local with Internet Mail Service (5.5.1960.3) id ; Mon, 10 Sep 2001 17:11:02 +1000 Message-ID: From: Adrian Head To: Michael Wahlbrink , Adrian Head Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com Subject: RE: Problems with many processes copying large directories across an XFS volume. Date: Mon, 10 Sep 2001 17:11:01 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thanks for your reply. Very interesting - I will definitely investigate this further. Just a little more info on the actual computers: I'm running these tests on 3 different machines in 2 different places but the common component are the IBM hard drives. On the 2 machines at work I have 4 x 20G IBM drives in a software raid5 and on the machine at home I have 5 x 40G IBM drives in a software raid5 and 2 x 40G IBM drives in a software raid0. The 4 drive array is in a machine at work where it is airconditioned and it has a 200cm3/sec AC fan installed in the case. The drives are spaced about 5mm apart between the top of one drive and the bottom of the other. The 5 drive raid5 and 2 drive raid0 machine at home at the moment is not in an airconditioned room but the case cover is off and the case has 2 x 200cm3/sec AC fans in it and for good measure I also have a 40cm pedestal fan blowing air through the case. The drives in this machine are spaced about 2cm apart from the top of one drive to the bottom of the other. In both environments I have never noticed hard drives that are hot to touch during any of the tests. Therefore, it may not be the external temperature that I have to worry about but the internal temperature of the drive. I'll try to get a thermometer and measure the average external hard drive temperature some time latter this week. Does anyone have any other ideas on this? Michael, what hard drives are you running in your machine and what spacings and what is the ambient temperature please. You can email this directly if you wish as it is a little OT for this list I think. Thanks again Adrian Head Bytecomm P/L > -----Original Message----- > From: Michael Wahlbrink [SMTP:miw@propack-data.com] > Sent: Monday, 10 September 2001 14:56 > To: adrian.head@bytecomm.com.au > Cc: linux-xfs@oss.sgi.com; owner-linux-xfs@oss.sgi.com > Subject: Re: Problems with many processes copying large > directories across an XFS volume. > > > On 10.09.2001 04:00:30 Adrian Head wrote: > [....see subject...] > Hi Adrian, > I've had a quite similar phenomen last weekend. When copiing with many > cp-processes on my xfs-volume i run into io errors or kernel oops. > The solution was that the two disks of the Raidsystem are getting to > hot when I > run these extensive tests (30cp processes and 15 tar processes on > thesame 60 GB > raid 1 volume). Added another fan and all was fine ;-)........... > > cu > michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 00:46:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A7kvE07652 for linux-xfs-outgoing; Mon, 10 Sep 2001 00:46:57 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A7knd07630 for ; Mon, 10 Sep 2001 00:46:49 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id JAA14374; Mon, 10 Sep 2001 09:46:12 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id JAA20134; Mon, 10 Sep 2001 09:46:06 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 8A06957306; Mon, 10 Sep 2001 09:45:10 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id B6F7325835; Mon, 10 Sep 2001 09:45:09 +0200 (CEST) Message-ID: <3B9C6F85.94B63D87@ch.sauter-bc.com> Date: Mon, 10 Sep 2001 09:45:09 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com Subject: Re: Problems with many processes copying large directories across an XFS volume. References: <01090823430700.01184@HERCULES> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Adrian Adrian Head schrieb: > > I am in the process of building a couple of file servers for various purposes > and over the last week have been running quite a few tests in an attempt to > determine if I trust the hardware/software combination enough for it to be > put into production. > > One of the tests I was doing was trying to simulate many users copying large > directories across an XFS volume. To do this I was generating many > background jobs copying a 4G directory to another directory on the XFS volume. > eg. > #>cp -r 001 002& > #>cp -r 001 003& > #>cp -r 001 004& > ..... > ..... > #>cp -r 001 019& > #>cp -r 001 020& I did similar tests two months ago. I was having problems as well but ufurtunately I don't remember what is was exactly. First question: You created Softraid5, was the raid synced when you started the tests? > Everything would start fine but less than a minute into the test various > hundreds of errors are displayed like: > cp: cannot stat file `/mnt/raid5/filename`: Input/output error > > Once this has happened the XFS volume disappears. By this I mean that it is > still mounted but all files and directories are no longer visible using ls. > Any other file activity results in an Input/Output error. Once I unmount & > mount the volume again the data is again visible up to the point where the > copy failed. > > In the /var/log/messages log around the same time as the copy test I get > entries like: > Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 > Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device This looks interesting. I don't know what this means exactly but it looks to me like you managed to create a filesystem bigger than the raid volume was? I got the very same error when I tried to restore data with xfsrestore from DAT (xfsrestore from DLT was fine). The issue is still open. > > The problem is reproduceable on XFS volumes on a 2 disk (IDE) raid0 (SW raid) > partition and on a 5 disk (IDE) raid5 (SW raid) partition. However, there is > no problem with the copy test using ext2 volumes on the above partitions. > The copy test also passes when run on a non-raid drive. > > I am using Kernel 2.4.9 and the relevant latest XFS patch from the patches > directory on the XFS ftp site. > patch-2.4.9-xfs-2001-08-19 > > The thing that really puzzles me is that the above directory copy test runs > fine when I only have 10 background copy jobs running at a time. As soon as > I have 20 background copy jobs running the problem occurs. The system passes > both bonnie++ and mongo.pl tests/benchmarks. > > So from the results I have at the moment it would seem that XFS is stomping > over the raid code or the raid code is stomping over XFS. Should I cross > post this to the raid list as well? > > P.S. I have just noticed on the mailing list archive a note about fixing a > problem that caused mongo.pl to hang. Although my systems don't hang in > mongo do people think I'm seeing the same problem just a different symptom? > > Another issue that I think is not related is that when using the 2.4.9-xfs > kernel, when the kernel identifies the drives during bootup I get IRQ probe > failed errors. > hda: IC35L040AVER07-0, ATA DISK drive > hda: IRQ probe failed (0xfffffff8) > hdb: IC35L040AVER07-0, ATA DISK drive > hdb: IRQ probe failed (0xfffffff8) > ........the rest as normal > > The errors occur when the kernel is run on an ASUS A7V133 motherboard but not > on a ASUS A7V133C. The errors don't happen with a native 2.4.9 kernel > either. Since the errors occur for the 2 drives on the 1st channel of the > 1st IDE controller (which is not related to the raid arrays mentioned above) > and the system still boots - I have not been worried about it. Should I be > worried? > > At this stage I'm unsure what other info people would like. If anyone wants > logs, config files, more information or more testing please tell me. > > Thanks for your time. > > Adrian Head > Bytecomm P/L I have a test system here with SoftRAID5 on 4 U160 SCSI disks. I'll try to kill it today with cp jobs. -Simon From owner-linux-xfs@oss.sgi.com Mon Sep 10 01:02:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A82dY07986 for linux-xfs-outgoing; Mon, 10 Sep 2001 01:02:39 -0700 Received: from atrey.karlin.mff.cuni.cz (root@atrey.karlin.mff.cuni.cz [195.113.31.123]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A82Xd07966 for ; Mon, 10 Sep 2001 01:02:33 -0700 Received: (from jack@localhost) by atrey.karlin.mff.cuni.cz (8.9.3/8.9.3/Debian 8.9.3-21) id KAA03540; Mon, 10 Sep 2001 10:00:26 +0200 Date: Mon, 10 Sep 2001 10:00:26 +0200 From: Jan Kara To: Nathan Scott Cc: Bret Giddings , linux-xfs@oss.sgi.com, samba-technical@lists.samba.org Subject: Re: [patch] Re: XFS, Quotas and Samba Message-ID: <20010910100026.A2992@atrey.karlin.mff.cuni.cz> References: <7AC902A40BEDD411A3A800D0B7847B660882F5@sernt14.essex.ac.uk> <20010906105952.B345981@wobbly.melbourne.sgi.com> <20010906123515.A380241@wobbly.melbourne.sgi.com> <20010906163441.C24754@atrey.karlin.mff.cuni.cz> <20010909205752.A397355@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <20010909205752.A397355@wobbly.melbourne.sgi.com>; from nathans@sgi.com on Sun, Sep 09, 2001 at 08:57:52PM +1100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, > On Thu, Sep 06, 2001 at 04:34:41PM +0200, Jan Kara wrote: > > Hello, > > > > Actually it depends whether the samba code was compiled with > > proper kernel headers. If so the Q_GETQUOTA is defined to be > > right value and so everything should work fine. Ok, to be more > > precise the utils probably won't compile in that case as struct dqblk > > is no more and mem_dqblk should be used instead... But anyway it shouldn't > > break silently. > > Hmm ... I can't see any case where the new VFS quota code will > work (ie. Jan's patches/AC kernels/Redhat 7.1+) with the smbd > code, even if the kernel headers happened to correspond to the > running kernel. As I understand it, the new code returns a u64 > byte count in one field (curspace) where before there was a u32 > block count (curblocks). Is that correct? If so, smbd is in a > bit of strife here cos it peeks at that field in particular... Yes. The returned structure is different and that was a reason why it was renamed to struct mem_dqblk :). So code which is using old structure doesn't compile... > I took a stab at implementing the fix for this problem and for > XFS quota - the XFS code should be correct, the VFS quota code > (v1/v2 stuff) should be too, but I'm less certain on that - see > attached patch. The approach is basically to attempt the old > Linux quotactl for non-XFS filesystems - if that fails, try > the new version. And for XFS filesystems, always use the XFS > quotactl command, which is always the right thing to do. > > Bret - could you let me know if this helps you? The patch seems to have one small problem: if version == 2 then size is set to D2.dqb_curspace but IMHO it should be something like toqb(D2.dqb_curspace). Honza -- Jan Kara SuSE Labs From owner-linux-xfs@oss.sgi.com Mon Sep 10 01:10:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A8AsA08295 for linux-xfs-outgoing; Mon, 10 Sep 2001 01:10:54 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A8Acd08276; Mon, 10 Sep 2001 01:10:39 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8A8Add08277 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 01:30:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A8Upv08690 for linux-xfs-outgoing; Mon, 10 Sep 2001 01:30:51 -0700 Received: from alpha.bytecomm.com.au (byt130674-1.gw.connect.com.au [202.21.11.108]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A8UVd08667 for ; Mon, 10 Sep 2001 01:30:35 -0700 Received: (qmail 23520 invoked from network); 10 Sep 2001 08:30:10 -0000 Received: from unknown (HELO herbie.local) (192.168.0.11) by 192.168.0.1 with SMTP; 10 Sep 2001 08:30:10 -0000 Received: by herbie.local with Internet Mail Service (5.5.1960.3) id ; Mon, 10 Sep 2001 18:30:04 +1000 Message-ID: From: Adrian Head To: Simon Matter , Adrian Head Cc: linux-xfs@oss.sgi.com Subject: RE: Problems with many processes copying large directories across an XFS volume. Date: Mon, 10 Sep 2001 18:29:55 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thanks for your reply Simon Yes the softraid was fully synced before I started any test. The XFS patch I used to obtain these errors was patch-2.4.9-xfs-2001-08-19 and the errors were: Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device When I used a later version of the XFS patch I had more descriptive errors written to /var/log/messages: Sep 10 10:14:57 ATLAS kernel: I/O error in filesystem ("md(9,0)") meta-data dev 0x900 block 0x9802bdc Sep 10 10:14:57 ATLAS kernel: (xlog_iodone") error 5 buf count 32768 Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called from line 940 of file xfs_log.c. Return address - 0xd8cb66f8 Sep 10 10:14:57 ATLAS kernel: Log I/O Error Detected. Shutting down filesystem: md(9,0) Sep 10 10:14:57 ATLAS kernel: Please umount the filesystem, and rectify the problem(s) Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called from line 714 of file xfs_log.c. Return address = 0xd8cb65d3 Sep 10 10:14:57 ATLAS kernel: attempt to access beyond end of device Sep 10 10:14:57 ATLAS kernel: 02:82: rw=0, want=1602235696, limit=4 I did think at the time that it may have been issues with XFS stomping all over raid code or raid code stomping all over XFS. Although I not sure now as the 2.4.10-pre2-xfs-2001-09-02 patch never wrote any errors out at all. (please see my 2nd post for more info) Thanks for taking the time to test this on your own machine. Adrian Head Bytecomm P/L > -----Original Message----- > From: Simon Matter [SMTP:simon.matter@ch.sauter-bc.com] > Sent: Monday, 10 September 2001 17:45 > To: adrian.head@bytecomm.com.au > Cc: linux-xfs@oss.sgi.com > Subject: Re: Problems with many processes copying large > directories across an XFS volume. > > Hi Adrian > > I did similar tests two months ago. I was having problems as well but > ufurtunately I don't remember what is was exactly. > First question: You created Softraid5, was the raid synced when you > started the tests? > > > In the /var/log/messages log around the same time as the copy test I > get > > entries like: > > Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 > > Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device > > This looks interesting. I don't know what this means exactly but it > looks to me like you managed to create a filesystem bigger than the > raid > volume was? I got the very same error when I tried to restore data > with > xfsrestore from DAT (xfsrestore from DLT was fine). The issue is still > open. > > I have a test system here with SoftRAID5 on 4 U160 SCSI disks. I'll > try > to kill it today with cp jobs. > > -Simon > From owner-linux-xfs@oss.sgi.com Mon Sep 10 01:59:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A8xDl09276 for linux-xfs-outgoing; Mon, 10 Sep 2001 01:59:13 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A8x2d09232 for ; Mon, 10 Sep 2001 01:59:02 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id KAA29419; Mon, 10 Sep 2001 10:58:26 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id KAA26232; Mon, 10 Sep 2001 10:58:14 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 9D5D957306; Mon, 10 Sep 2001 10:57:12 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 4B50E25835; Mon, 10 Sep 2001 10:57:12 +0200 (CEST) Message-ID: <3B9C8068.AF14F8E6@ch.sauter-bc.com> Date: Mon, 10 Sep 2001 10:57:12 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Bret Hughes Cc: linux-xfs Subject: Re: directory cache problems (I think) References: <3B9C4632.2408E16@elevating.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Bret Bret Hughes schrieb: > > I have a configuration on 6 boxes, Duron 700 with 128 MB ram and 10GB > ide harddrives. These machines are all XFS 1.0.1 using the kernel from > the 1.0.1 RH install iso and most of the RH updates. > > They were all placed into service the same day and yesterday 5 days > after they were turned on they all stopped responding to ssh. A couple > would still respond to a ping but nothing else. Actually I caough one > before it quit altogether and rebooted it last night. These machines a > kiosk type display that scroll html and flash pages using (netscape as > the browser). There is no user interaction infact not any input device > at all. A different page is displayed every 10 seconds. > > Now, After rebooting them I can get to the sadc data and looking through > the logs shows really bad stuff happening at 1:00PM yesterday on the one > machine I have really looked at closely. interrupt 14s out the wazoo > and what I think must be the cause, the dentunusd goes to 0. Looking > over the logs of the last few days I can see the dentunusd creeping down > from the beginning at boot of over 20K to 0. > > Since netscape is such a pig I kill it and restart it once an hour and > restart X once a day. both these events seem to take a tremendous toll > on this value and never gain it all back. > > I don't know if this is an XFS issue or not but I thought that I would > start here. Any ideas? I can send all the log data anyone might use if > it would help. Right now I am going to reboot the damn things nightly > like they were windows machines for Christ's sake. > > BTW the same scenario and control scripts run for months on end on RH > 6.2 using the 2.2.3-16 kernel. > > Any tips and or other places to ask are appreciated. > > TIA > > Bret Did you run the RH-6.2 stuff on exactly the same hardware (including same disks?) What about the disks, are they running with DMA enabled? Over here our mailservers used to be IBM PC's with Fujitsu Harddrives. After some time of operation they started to slow down and load started to increase. They even did not respond to ssh sometimes. In the end I saw that those disks failed under the heavy load of the mailserver and I replaced them with other disks. We have hundreds of the same disks in windows desktop PC's with no problem. Linux just pushes the hardware more. Simon From owner-linux-xfs@oss.sgi.com Mon Sep 10 01:59:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A8x8Y09244 for linux-xfs-outgoing; Mon, 10 Sep 2001 01:59:08 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A8wwd09209 for ; Mon, 10 Sep 2001 01:58:59 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id KAA29420; Mon, 10 Sep 2001 10:58:26 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id KAA26246; Mon, 10 Sep 2001 10:58:19 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 3A1B157306; Mon, 10 Sep 2001 10:57:34 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 3527925835; Mon, 10 Sep 2001 10:57:34 +0200 (CEST) Message-ID: <3B9C807E.2D7488E5@ch.sauter-bc.com> Date: Mon, 10 Sep 2001 10:57:34 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Adrian Head Cc: linux-xfs@oss.sgi.com Subject: Re: Problems with many processes copying large directories acrossan XFS volume. References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Adrian Head schrieb: > > Thanks for your reply Simon > > Yes the softraid was fully synced before I started any test. When I started playing around with XFS I used Raid5 and did stress tests while the disks were syncing. The syncing failed several times and I was afraid it is not stable not stress the raid while it is syncing. Fortunately it is not true but the sync aborted due to bad disks. So no problem even if raid is not synced. > > The XFS patch I used to obtain these errors was > patch-2.4.9-xfs-2001-08-19 and the errors were: > Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 > Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device > > When I used a later version of the XFS patch I had more descriptive > errors written to /var/log/messages: > Sep 10 10:14:57 ATLAS kernel: I/O error in filesystem ("md(9,0)") > meta-data dev 0x900 block 0x9802bdc > Sep 10 10:14:57 ATLAS kernel: (xlog_iodone") error 5 buf count 32768 > Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called > from line 940 of file xfs_log.c. Return address - 0xd8cb66f8 > Sep 10 10:14:57 ATLAS kernel: Log I/O Error Detected. Shutting down > filesystem: md(9,0) > Sep 10 10:14:57 ATLAS kernel: Please umount the filesystem, and rectify > the problem(s) > Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called > from line 714 of file xfs_log.c. Return address = 0xd8cb65d3 > Sep 10 10:14:57 ATLAS kernel: attempt to access beyond end of device > Sep 10 10:14:57 ATLAS kernel: 02:82: rw=0, want=1602235696, limit=4 > > I did think at the time that it may have been issues with XFS stomping > all over raid code or raid code stomping all over XFS. Although I not > sure now as the 2.4.10-pre2-xfs-2001-09-02 patch never wrote any errors > out at all. (please see my 2nd post for more info) I don't use anything special here and no cutting edge stuff. Just the good old 2.4.3-XFS from the RH-7.1-XFS installer. > > Thanks for taking the time to test this on your own machine. The test with 20 simultaneous has just finished successfully. I'm now trying with 40 cp processes. Due to limited disk space I copy only 470M per process. -Simon > > Adrian Head > Bytecomm P/L > > > -----Original Message----- > > From: Simon Matter [SMTP:simon.matter@ch.sauter-bc.com] > > Sent: Monday, 10 September 2001 17:45 > > To: adrian.head@bytecomm.com.au > > Cc: linux-xfs@oss.sgi.com > > Subject: Re: Problems with many processes copying large > > directories across an XFS volume. > > > > Hi Adrian > > > > I did similar tests two months ago. I was having problems as well but > > ufurtunately I don't remember what is was exactly. > > First question: You created Softraid5, was the raid synced when you > > started the tests? > > > > > In the /var/log/messages log around the same time as the copy test I > > get > > > entries like: > > > Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 > > > Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device > > > > This looks interesting. I don't know what this means exactly but it > > looks to me like you managed to create a filesystem bigger than the > > raid > > volume was? I got the very same error when I tried to restore data > > with > > xfsrestore from DAT (xfsrestore from DLT was fine). The issue is still > > open. > > > > I have a test system here with SoftRAID5 on 4 U160 SCSI disks. I'll > > try > > to kill it today with cp jobs. > > > > -Simon > > From owner-linux-xfs@oss.sgi.com Mon Sep 10 02:05:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A95G109644 for linux-xfs-outgoing; Mon, 10 Sep 2001 02:05:16 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A95Dd09623 for ; Mon, 10 Sep 2001 02:05:13 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8A951523078 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Mon, 10 Sep 2001 02:05:01 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id LAA225341 for ; Mon, 10 Sep 2001 11:05:07 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id UAA02931; Mon, 10 Sep 2001 20:03:33 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id UAA60160; Mon, 10 Sep 2001 20:03:31 +1100 (AEDT) Date: Mon, 10 Sep 2001 20:03:31 +1100 From: Nathan Scott To: Jan Kara Cc: Bret Giddings , linux-xfs@oss.sgi.com, samba-technical@lists.samba.org Subject: Re: [patch] Re: XFS, Quotas and Samba Message-ID: <20010910200331.B341029@wobbly.melbourne.sgi.com> References: <7AC902A40BEDD411A3A800D0B7847B660882F5@sernt14.essex.ac.uk> <20010906105952.B345981@wobbly.melbourne.sgi.com> <20010906123515.A380241@wobbly.melbourne.sgi.com> <20010906163441.C24754@atrey.karlin.mff.cuni.cz> <20010909205752.A397355@wobbly.melbourne.sgi.com> <20010910100026.A2992@atrey.karlin.mff.cuni.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010910100026.A2992@atrey.karlin.mff.cuni.cz>; from jack@suse.cz on Mon, Sep 10, 2001 at 10:00:26AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Jan, On Mon, Sep 10, 2001 at 10:00:26AM +0200, Jan Kara wrote: > Hello, > ... > The patch seems to have one small problem: if version == 2 then > size is set to D2.dqb_curspace but IMHO it should be something like > toqb(D2.dqb_curspace). > There's a line in there before "curspace" is used which converts from bytes to 1K blocks ("curspace >>= 10;"), and we set blocksize to 1K for both VFS quota versions ... is that approach too simple? (do I need to do the FIOQSIZE thing or something more complex like that?) thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Sep 10 02:34:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8A9YJE10341 for linux-xfs-outgoing; Mon, 10 Sep 2001 02:34:19 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8A9Xxd10315; Mon, 10 Sep 2001 02:33:59 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8A9Y0d10318 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 04:04:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AB4H912216 for linux-xfs-outgoing; Mon, 10 Sep 2001 04:04:17 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AB3vd12193; Mon, 10 Sep 2001 04:03:57 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8AB3wd12194 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 05:02:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AC2cX13280 for linux-xfs-outgoing; Mon, 10 Sep 2001 05:02:38 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AC2Zd13261 for ; Mon, 10 Sep 2001 05:02:35 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id OAA06593 for ; Mon, 10 Sep 2001 14:02:18 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id OAA10818 for linux-xfs@oss.sgi.com; Mon, 10 Sep 2001 14:02:07 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id C15A057306 for ; Mon, 10 Sep 2001 14:01:33 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id B7C8D25835 for ; Mon, 10 Sep 2001 14:01:33 +0200 (CEST) Message-ID: <3B9CAB9D.28502B00@ch.sauter-bc.com> Date: Mon, 10 Sep 2001 14:01:33 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: Updated quota RPM for RedHat 7.1 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've just checked for updates for RH-7.1 and found a new quota RPM. I guess it wouldn't be a good idea to install this one since the quota package for XFS is modified. Did I assume right? Simon From owner-linux-xfs@oss.sgi.com Mon Sep 10 05:27:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ACRNg13804 for linux-xfs-outgoing; Mon, 10 Sep 2001 05:27:23 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ACRId13782; Mon, 10 Sep 2001 05:27:18 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8ACRJd13783 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 05:45:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ACjxn14258 for linux-xfs-outgoing; Mon, 10 Sep 2001 05:45:59 -0700 Received: from atlas.cc.itu.edu.tr (atlas.cc.itu.edu.tr [160.75.2.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ACjrd14237 for ; Mon, 10 Sep 2001 05:45:54 -0700 Received: from aontws4044 (AONTWS4044.cc.itu.edu.tr [160.75.5.44]) by atlas.cc.itu.edu.tr (8.9.3/8.9.3) with SMTP id PAA05720 for ; Mon, 10 Sep 2001 15:45:46 +0300 From: "Seref Tufan Sen" To: Subject: RE: Problems with many processes copying large directories across an XFS volume.[Offtpic] Date: Mon, 10 Sep 2001 15:51:52 +0300 Message-ID: <001201c139f7$5d5b62a0$2c054ba0@aontws4044> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I got 7 copies of this message. Am I the only one with this problem ??? -----Original Message----- From: owner-linux-xfs@oss.sgi.com [mailto:owner-linux-xfs@oss.sgi.com]On Behalf Of Michael Wahlbrink Sent: Monday, September 10, 2001 7:56 AM To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com; owner-linux-xfs@oss.sgi.com Subject: Re: Problems with many processes copying large directories across an XFS volume. On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 05:47:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AClE814397 for linux-xfs-outgoing; Mon, 10 Sep 2001 05:47:14 -0700 Received: from TYO201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.214]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ACl8d14377 for ; Mon, 10 Sep 2001 05:47:09 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.195]) by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8ACl2a15101 for ; Mon, 10 Sep 2001 21:47:02 +0900 (JST) Received: from mailsv.nec.co.jp (mailgate51.nec.co.jp [10.7.69.196]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8ACl2c13613 for ; Mon, 10 Sep 2001 21:47:02 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv.nec.co.jp (8.11.6/3.7W-MAILSV-NEC) with ESMTP id f8ACl1l07835 for ; Mon, 10 Sep 2001 21:47:01 +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 AAA401 for ; Mon, 10 Sep 2001 21:46:58 +0900 Received: FROM mailsv.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Mon Sep 10 21:46:57 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by mailsv.tnes.nec.co.jp (8.9.3/3.7W01031510) with ESMTP id VAA80635; Mon, 10 Sep 2001 21:46:58 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f8ACkwL10115; Mon, 10 Sep 2001 21:46:58 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id VAA27978; Mon, 10 Sep 2001 21:46:58 +0900 (JST) Message-Id: <200109101246.VAA27978@tagajo.bsd.tnes.nec.co.jp> To: Timothy Shimmin cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump/xfsrestore failed sometimes when running QA suite 022 In-reply-to: Your message of Mon, 10 Sep 2001 14:16:41 +1100. <20010910141641.L96131@boing.melbourne.sgi.com> Date: Mon, 10 Sep 2001 21:46:58 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thank you for your fast response. Timothy Shimmin wrote, > Do you have top of tree cmds and kernel ? In this morning, I could not do a CVSup too as someone reported, so, I tried QA suite 022 three times using the CVS kernel and cmds which were updated on last friday. Then, all of them have been passed :-) I'll try more tonight. > cmd/xfstests/022 has failed reliably for us in recent times, > but over the last few days (Nathan looks after our QA he'll > know exactly when), it has been passing reliably. > I have been meaning to look into 022 and 024 but only > looked at 024 recently. > I do not know exactly what has changed to cause 022 > to pass now. > > xfsdump uses an xfs feature called bulkstat'ing to speed up > the stat'ing of all the inodes of the file system. > However, it apparently snapshots the info from the disk blocks > instead of going through the in-core data structures. > This means that if this data is not flushed to disk completely > when xfsdump is running then it won't have the latest stat > information. Hmmm... I see. > So for the QA testing, after populating an FS I would call > _stable_fs to do sync and sleep. However, I didn't do this > in every case such as the case where I append to files to > test out incremental dumps in 024. > So I added the call to _stable_fs in common.dump for this. > I also changed from sync/sleep to umount/mount to be sure > that the changes are flushed to disk before proceeding. > So this may have also affected 022. > However, by putting back the old behaviour I was still unable > to get 022 to fail. I would like to know that whether it is correct way or workaround to dump the XFS file system which requires preceding unmount and mount, not only for QA suite but also on a production environment. Could you explain me about this? Best Regards, Takayuki From owner-linux-xfs@oss.sgi.com Mon Sep 10 05:56:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ACuIp14740 for linux-xfs-outgoing; Mon, 10 Sep 2001 05:56:18 -0700 Received: from linux.compucomis.net (linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ACsud14684 for ; Mon, 10 Sep 2001 05:55:35 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id 46662139E5; Mon, 10 Sep 2001 08:50:19 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id 5E5B3139E4; Mon, 10 Sep 2001 08:50:19 -0400 (EDT) Date: Mon, 10 Sep 2001 08:50:18 -0400 (EDT) From: Mike Burger To: Simon Matter Cc: linux-xfs Subject: Re: Updated quota RPM for RedHat 7.1 In-Reply-To: <3B9CAB9D.28502B00@ch.sauter-bc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hmm...that probably explains why I can't seem to enable quotas. What is the version of the quota package that comes with the XFS install? On Mon, 10 Sep 2001, Simon Matter wrote: > I've just checked for updates for RH-7.1 and found a new quota RPM. I > guess it wouldn't be a good idea to install this one since the quota > package for XFS is modified. Did I assume right? > > Simon > > > From owner-linux-xfs@oss.sgi.com Mon Sep 10 05:57:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ACv5U14824 for linux-xfs-outgoing; Mon, 10 Sep 2001 05:57:05 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ACuvd14804 for ; Mon, 10 Sep 2001 05:56:57 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id OAA21312; Mon, 10 Sep 2001 14:56:35 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id OAA15236; Mon, 10 Sep 2001 14:56:09 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id A8FAB57306; Mon, 10 Sep 2001 14:55:24 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 6192125835; Mon, 10 Sep 2001 14:55:24 +0200 (CEST) Message-ID: <3B9CB83C.38153FEE@ch.sauter-bc.com> Date: Mon, 10 Sep 2001 14:55:24 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Mike Burger Cc: linux-xfs Subject: Re: Updated quota RPM for RedHat 7.1 References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Mike Burger schrieb: > > Hmm...that probably explains why I can't seem to enable quotas. > > What is the version of the quota package that comes with the XFS install? The RH-7.1XFS 1.0.1 comes with quota-3.01-pre7 Simon > > On Mon, 10 Sep 2001, Simon Matter wrote: > > > I've just checked for updates for RH-7.1 and found a new quota RPM. I > > guess it wouldn't be a good idea to install this one since the quota > > package for XFS is modified. Did I assume right? > > > > Simon > > > > > > From owner-linux-xfs@oss.sgi.com Mon Sep 10 06:06:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AD6pp15270 for linux-xfs-outgoing; Mon, 10 Sep 2001 06:06:51 -0700 Received: from minerva.local.lan (madkiss@pD952C80F.dip.t-dialin.net [217.82.200.15]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AD6ld15249 for ; Mon, 10 Sep 2001 06:06:47 -0700 Received: from minerva.local.lan (madkiss@localhost [127.0.0.1]) by localhost (8.12.0.Beta19/8.12.0.Beta16/Debian 8.12.0.Beta16) with ESMTP id f8AD6K2S002166 for ; Mon, 10 Sep 2001 15:06:21 +0200 Received: (from madkiss@localhost) by minerva.local.lan (8.12.0.Beta19/8.12.0.Beta16/Debian 8.12.0.Beta16) id f8AD6KVm002165 for linux-xfs@oss.sgi.com; Mon, 10 Sep 2001 15:06:20 +0200 From: Martin Loschwitz Date: Mon, 10 Sep 2001 15:06:20 +0200 To: linux-xfs@oss.sgi.com Subject: xfs-cvstree-errors Message-ID: <20010910150620.A2155@Minerva> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello ppl, i downloaded your xfs-cvs-tree for Linux-kernel 2.4. I tried to compile it, but when i do "make dep", it finishs with: udp.c utils.c > .depend make[4]: Leaving directory `/usr/src/linux-2.4-xfs/linux/net/ipv4' make -C ipv4/netfilter fastdep make[4]: Entering directory `/usr/src/linux-2.4-xfs/linux/net/ipv4/netfilter' .depend:12: *** missing separator. Stop. make[4]: Leaving directory `/usr/src/linux-2.4-xfs/linux/net/ipv4/netfilter' make[3]: *** [_sfdep_ipv4/netfilter] Error 2 make[3]: Leaving directory `/usr/src/linux-2.4-xfs/linux/net' make[2]: *** [fastdep] Error 2 make[2]: Leaving directory `/usr/src/linux-2.4-xfs/linux/net' make[1]: *** [_sfdep_net] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4-xfs/linux' make: *** [dep-files] Error 2 is that a bug, and if it's, how to patch? -- greetings, Madkiss "Who cares if it doesn't do anything? It was made with our new Triple-Iso-Bifurcated-Krypton-Gate-MOS process ..." From owner-linux-xfs@oss.sgi.com Mon Sep 10 06:14:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ADE9U15503 for linux-xfs-outgoing; Mon, 10 Sep 2001 06:14:09 -0700 Received: from acmex.gatech.edu (IDENT:root@acmex.gatech.edu [130.207.165.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ADDed15482 for ; Mon, 10 Sep 2001 06:13:40 -0700 Received: from [130.207.197.237] ([130.207.197.237]) by acmex.gatech.edu (8.9.2/8.9.2) with ESMTP id JAA04209 for ; Mon, 10 Sep 2001 09:13:40 -0400 (EDT) Subject: 2.4.9 oops - dual athlon/2gb ram From: Rob Myers To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13.99+cvs.2001.09.08.07.08 (Preview Release) Date: 10 Sep 2001 09:16:35 -0400 Message-Id: <1000127795.10581.13.camel@ransom> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hello i generated an oops after running ctcs (http://sourceforge.net/projects/va-ctcs/) for 5 days. This machine is a dual athlon with 2gb ram and a single scsi disk. Linux version 2.4.9-xfs (root@monsoon) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-85)) #6 SMP Fri Aug 24 00:31:54 EDT 2001 would switching back to kgcc solve this problem? thanks rob. ksymoops 2.4.0 on i686 2.4.9-xfs. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.9-xfs/ (default) -m /boot/System.map-2.4.9-xfs (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Error (regular_file): read_ksyms stat /proc/ksyms failed No modules in ksyms, skipping objects No ksyms, skipping lsmod Sep 10 03:36:30 monsoon kernel: Oops: 0000 Sep 10 03:36:30 monsoon kernel: CPU: 1 Sep 10 03:36:30 monsoon kernel: EIP: 0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 Sep 10 03:36:30 monsoon kernel: EFLAGS: 00010246 Sep 10 03:36:30 monsoon kernel: eax: 00000000 ebx: 00000000 ecx: 00000070 edx: 00000000 Sep 10 03:36:30 monsoon kernel: esi: 00000000 edi: e0eb6ed8 ebp: f7bd7938 esp: f7bd78f4 Sep 10 03:36:30 monsoon kernel: ds: 0018 es: 0018 ss: 0018 Sep 10 03:36:30 monsoon kernel: Process bdflush (pid: 7, stackpage=f7bd7000) Sep 10 03:36:30 monsoon kernel: Stack: e0eb6ed8 00000000 00000000 c01a22ee e0eb6f64 00000001 f7b47800 00000000 Sep 10 03:36:30 monsoon kernel: 00000000 00000001 00000001 00000001 f7711000 00000000 f7bd7958 0001c87d Sep 10 03:36:30 monsoon kernel: 00000009 f7bd7968 c0188935 e0eb6ed8 00000000 f7bd7958 f7bd7958 00000000 Sep 10 03:36:30 monsoon kernel: Call Trace: [] [] [] <4>eth0: card reports no resources. Sep 10 03:36:30 monsoon kernel: [] [] Sep 10 03:36:30 monsoon kernel: [] [] [] [] [] [] Sep 10 03:36:30 monsoon kernel: [] [] [] [] [] [] Sep 10 03:36:30 monsoon kernel: [] [] [] [] [] [] Sep 10 03:36:30 monsoon kernel: [] [] [] [] Sep 10 03:36:30 monsoon kernel: Code: 8b 70 30 50 53 56 57 e8 79 63 01 00 83 c4 1c 85 c0 74 08 e9 >>EIP; c018bf2b <===== Trace; c01a22ee Trace; c0188935 Trace; c01890fe Trace; c0188ba6 Trace; c018acd5 Trace; c0197b96 Trace; c0194254 Trace; c01a1117 Trace; c01a1117 Trace; c019af57 Trace; c0183558 Trace; c01dfa5b Trace; c012bef9 Trace; c01dde4a Trace; c0185f43 <__pb_block_prepare_write_async+d3/270> Trace; c02068b9 Trace; c0185af1 Trace; c01dde00 Trace; c01ddff1 Trace; c01dde00 Trace; c0134691 <_write_buffer+71/d0> Trace; c01348b1 Trace; c0111d80 Trace; c01381f4 Trace; c0105000 <_stext+0/0> Trace; c01055e6 Trace; c0138160 Code; c018bf2b 00000000 <_EIP>: Code; c018bf2b <===== 0: 8b 70 30 mov 0x30(%eax),%esi <===== Code; c018bf2e 3: 50 push %eax Code; c018bf2f 4: 53 push %ebx Code; c018bf30 5: 56 push %esi Code; c018bf31 6: 57 push %edi Code; c018bf32 7: e8 79 63 01 00 call 16385 <_EIP+0x16385> c01a22b0 Code; c018bf37 c: 83 c4 1c add $0x1c,%esp Code; c018bf3a f: 85 c0 test %eax,%eax Code; c018bf3c 11: 74 08 je 1b <_EIP+0x1b> c018bf46 Code; c018bf3e 13: e9 00 00 00 00 jmp 18 <_EIP+0x18> c018bf43 1 warning and 1 error issued. Results may not be reliable. GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... (no debugging symbols found)... (gdb) disass xfs_alloc_lookup Dump of assembler code for function xfs_alloc_lookup: 0xc018be30 : push %ebp 0xc018be31 : mov %esp,%ebp 0xc018be33 : push %edi 0xc018be34 : push %esi 0xc018be35 : xor %esi,%esi 0xc018be37 : push %ebx 0xc018be38 : sub $0x2c,%esp 0xc018be3b : mov 0x8(%ebp),%eax 0xc018be3e : incl 0xc03cd930 0xc018be44 : mov 0x8(%ebp),%edx 0xc018be47 : movl $0x0,0xffffffdc(%ebp) 0xc018be4e : mov 0x8(%ebp),%ecx 0xc018be51 : mov 0x4(%eax),%eax 0xc018be54 : mov %eax,0xffffffd4(%ebp) 0xc018be57 : mov 0x74(%edx),%eax 0xc018be5a : mov 0x30(%eax),%edx 0xc018be5d : mov 0x8(%edx),%eax 0xc018be60 : bswap %eax 0xc018be62 : mov %eax,0xffffffd0(%ebp) 0xc018be65 : mov %eax,0xffffffe4(%ebp) 0xc018be68 : mov 0x70(%ecx),%eax 0xc018be6b : mov 0x10(%edx,%eax,4),%eax 0xc018be6f : bswap %eax 0xc018be71 : mov %eax,0xffffffe8(%ebp) 0xc018be74 : movzbl 0x6c(%ecx),%eax 0xc018be78 : movl $0x1,0xffffffe0(%ebp) 0xc018be7f : dec %eax 0xc018be80 : mov %eax,0xffffffd8(%ebp) 0xc018be83 : js 0xc018c060 0xc018be89 : lea 0x0(%esi,1),%esi 0xc018be90 : mov 0xffffffd4(%ebp),%ecx 0xc018be93 : mov 0xffffffe4(%ebp),%eax 0xc018be96 : mul 0x78(%ecx),%eax 0xc018be99 : movzbl 0x18e(%ecx),%ecx 0xc018bea0 : mov %eax,%ebx 0xc018bea2 : mov 0xffffffe8(%ebp),%eax 0xc018bea5 : mov %edx,%esi 0xc018bea7 : xor %edx,%edx 0xc018bea9 : add %eax,%ebx 0xc018beab : adc %edx,%esi 0xc018bead : xor %edi,%edi 0xc018beaf : mov 0xffffffd8(%ebp),%edx 0xc018beb2 : shld %cl,%ebx,%esi 0xc018beb5 : shl %cl,%ebx 0xc018beb7 : test $0x20,%cl 0xc018beba : mov 0x8(%ebp),%ecx 0xc018bebd : cmovne %ebx,%esi 0xc018bec0 : cmovne %edi,%ebx 0xc018bec3 : mov 0x24(%ecx,%edx,4),%eax 0xc018bec7 : mov %eax,%edi 0xc018bec9 : mov %eax,0xfffffff0(%ebp) 0xc018becc : test %edi,%edi 0xc018bece : je 0xc018bee9 0xc018bed0 : mov 0x18(%edi),%edx 0xc018bed3 : mov 0x14(%edi),%eax 0xc018bed6 : mov %edx,%ecx 0xc018bed8 : xor %esi,%ecx 0xc018beda : xor %ebx,%eax 0xc018bedc : or %eax,%ecx 0xc018bede : je 0xc018bee9 0xc018bee0 : movl $0x0,0xfffffff0(%ebp) 0xc018bee7 : xor %edi,%edi 0xc018bee9 : test %edi,%edi 0xc018beeb : jne 0xc018bf43 0xc018beed : push $0x2 0xc018beef : lea 0xfffffff0(%ebp),%eax 0xc018bef2 : mov 0xffffffe8(%ebp),%esi 0xc018bef5 : push %eax 0xc018bef6 : mov 0xffffffd0(%ebp),%ebx 0xc018bef9 : mov 0x8(%ebp),%edi 0xc018befc : push $0x0 0xc018befe : mov 0xffffffd4(%ebp),%edx 0xc018bf01 : push %esi 0xc018bf02 : push %ebx 0xc018bf03 : mov (%edi),%ecx 0xc018bf05 : push %ecx 0xc018bf06 : push %edx 0xc018bf07 : call 0xc01a2a50 0xc018bf0c : add $0x1c,%esp 0xc018bf0f : test %eax,%eax 0xc018bf11 : jne 0xc018c14c 0xc018bf17 : mov 0xfffffff0(%ebp),%eax 0xc018bf1a : mov 0xffffffd8(%ebp),%esi 0xc018bf1d : push %eax 0xc018bf1e : push %esi 0xc018bf1f : push %edi 0xc018bf20 : call 0xc01a2d90 0xc018bf25 : mov 0xfffffff0(%ebp),%eax 0xc018bf28 : mov 0xffffffd8(%ebp),%ebx 0xc018bf2b : mov 0x30(%eax),%esi 0xc018bf2e : push %eax 0xc018bf2f : push %ebx 0xc018bf30 : push %esi 0xc018bf31 : push %edi 0xc018bf32 : call 0xc01a22b0 0xc018bf37 : add $0x1c,%esp 0xc018bf3a : test %eax,%eax 0xc018bf3c : je 0xc018bf46 0xc018bf3e : jmp 0xc018c14c 0xc018bf43 : mov 0x30(%edi),%esi 0xc018bf46 : mov 0xffffffe0(%ebp),%ecx 0xc018bf49 : test %ecx,%ecx 0xc018bf4b : jne 0xc018bf60 0xc018bf4d : movl $0x1,0xffffffdc(%ebp) 0xc018bf54 : jmp 0xc018c010 0xc018bf59 : lea 0x0(%esi,1),%esi 0xc018bf60 : movl $0x0,0xffffffcc(%ebp) 0xc018bf67 : mov 0xffffffd8(%ebp),%edx 0xc018bf6a : movl $0x0,0xffffffc8(%ebp) 0xc018bf71 : test %edx,%edx 0xc018bf73 : jle 0xc018bf80 0xc018bf75 : lea 0x10(%esi),%eax 0xc018bf78 : mov %eax,0xffffffcc(%ebp) 0xc018bf7b : jmp 0xc018bf86 0xc018bf7d : lea 0x0(%esi),%esi 0xc018bf80 : lea 0x10(%esi),%edx 0xc018bf83 : mov %edx,0xffffffc8(%ebp) 0xc018bf86 : movzwl 0x6(%esi),%eax 0xc018bf8a : mov $0x1,%ebx 0xc018bf8f : xchg %al,%ah 0xc018bf91 : movzwl %ax,%ecx 0xc018bf94 : test %ecx,%ecx 0xc018bf96 : je 0xc018c110 0xc018bf9c : cmp %ecx,%ebx 0xc018bf9e : jg 0xc018c010 0xc018bfa0 : incl 0xc03cd934 0xc018bfa6 : lea (%ecx,%ebx,1),%edi 0xc018bfa9 : mov 0xffffffd8(%ebp),%eax 0xc018bfac : sar %edi 0xc018bfae : mov %edi,0xffffffdc(%ebp) 0xc018bfb1 : test %eax,%eax 0xc018bfb3 : jle 0xc018bfc0 0xc018bfb5 : mov 0xffffffcc(%ebp),%edx 0xc018bfb8 : jmp 0xc018bfc6 0xc018bfba : lea 0x0(%esi),%esi 0xc018bfc0 : mov 0xffffffc8(%ebp),%edx 0xc018bfc3 : mov 0xffffffdc(%ebp),%edi 0xc018bfc6 : lea (%edx,%edi,8),%eax 0xc018bfc9 : mov 0xfffffff8(%eax),%edx 0xc018bfcc : bswap %edx 0xc018bfce : mov 0xfffffffc(%eax),%eax 0xc018bfd1 : bswap %eax 0xc018bfd3 : mov 0x8(%ebp),%edi 0xc018bfd6 : cmpl $0x0,0x70(%edi) 0xc018bfda : je 0xc018bfe7 0xc018bfdc : mov 0x8(%ebp),%edi 0xc018bfdf : sub 0xc(%edi),%eax 0xc018bfe2 : mov %eax,0xffffffe0(%ebp) 0xc018bfe5 : jne 0xc018bfef 0xc018bfe7 : mov 0x8(%edi),%eax 0xc018bfea : sub %eax,%edx 0xc018bfec : mov %edx,0xffffffe0(%ebp) 0xc018bfef : mov 0xffffffe0(%ebp),%eax 0xc018bff2 : test %eax,%eax 0xc018bff4 : jns 0xc018c000 0xc018bff6 : mov 0xffffffdc(%ebp),%ebx 0xc018bff9 : inc %ebx 0xc018bffa : jmp 0xc018bf9c 0xc018bffc : lea 0x0(%esi,1),%esi 0xc018c000 : mov 0xffffffe0(%ebp),%edi 0xc018c003 : test %edi,%edi 0xc018c005 : jle 0xc018c010 0xc018c007 : mov 0xffffffdc(%ebp),%ecx 0xc018c00a : dec %ecx 0xc018c00b : jmp 0xc018bf9c 0xc018c00d : lea 0x0(%esi),%esi 0xc018c010 : mov 0xffffffd8(%ebp),%ebx 0xc018c013 : test %ebx,%ebx 0xc018c015 : jle 0xc018c057 0xc018c017 : mov 0xffffffe0(%ebp),%ecx 0xc018c01a : test %ecx,%ecx 0xc018c01c : jle 0xc018c032 0xc018c01e : decl 0xffffffdc(%ebp) 0xc018c021 : mov $0x1,%eax 0xc018c026 : mov 0xffffffdc(%ebp),%edx 0xc018c029 : test %edx,%edx 0xc018c02b : cmovg 0xffffffdc(%ebp),%eax 0xc018c02f : mov %eax,0xffffffdc(%ebp) 0xc018c032 : mov 0x8(%ebp),%edx 0xc018c035 : mov 0xffffffdc(%ebp),%ecx 0xc018c038 : mov 0xffffffd8(%ebp),%edi 0xc018c03b : mov 0x4(%edx),%eax 0xc018c03e : mov 0x1a4(%eax),%eax 0xc018c044 : shl $0x3,%eax 0xc018c047 : lea (%eax,%ecx,4),%eax 0xc018c04a : mov 0xc(%eax,%esi,1),%eax 0xc018c04e : bswap %eax 0xc018c050 : mov %eax,0xffffffe8(%ebp) 0xc018c053 : mov %ecx,0x44(%edx,%edi,4) 0xc018c057 : decl 0xffffffd8(%ebp) 0xc018c05a : jns 0xc018be90 0xc018c060 : cmpl $0x1,0xc(%ebp) 0xc018c064 : je 0xc018c0d0 0xc018c066 : mov 0xffffffe0(%ebp),%edi 0xc018c069 : test %edi,%edi 0xc018c06b : jns 0xc018c0d0 0xc018c06d : incl 0xffffffdc(%ebp) 0xc018c070 : cmpl $0x2,0xc(%ebp) 0xc018c074 : jne 0xc018c0e5 0xc018c076 : movzwl 0x6(%esi),%eax 0xc018c07a : xchg %al,%ah 0xc018c07c : movzwl %ax,%eax 0xc018c07f : cmp %eax,0xffffffdc(%ebp) 0xc018c082 : jle 0xc018c0e5 0xc018c084 : mov 0xc(%esi),%eax 0xc018c087 : bswap %eax 0xc018c089 : inc %eax 0xc018c08a : je 0xc018c0e5 0xc018c08c : mov 0xffffffdc(%ebp),%eax 0xc018c08f : mov 0x8(%ebp),%edx 0xc018c092 : mov %eax,0x44(%edx) 0xc018c095 : lea 0xffffffec(%ebp),%eax 0xc018c098 : push %eax 0xc018c099 : push $0x0 0xc018c09b : push %edx 0xc018c09c : call 0xc018d230 0xc018c0a1 : add $0xc,%esp 0xc018c0a4 : test %eax,%eax 0xc018c0a6 : jne 0xc018c14c 0xc018c0ac : cmpl $0x1,0xffffffec(%ebp) 0xc018c0b0 : mov $0x3de,%eax 0xc018c0b5 : jne 0xc018c14c 0xc018c0bb : mov 0x10(%ebp),%ecx 0xc018c0be : xor %eax,%eax 0xc018c0c0 : movl $0x1,(%ecx) 0xc018c0c6 : jmp 0xc018c14c 0xc018c0cb : nop 0xc018c0cc : lea 0x0(%esi,1),%esi 0xc018c0d0 : cmpl $0x1,0xc(%ebp) 0xc018c0d4 : jne 0xc018c0e5 0xc018c0d6 : mov 0xffffffdc(%ebp),%eax 0xc018c0d9 : dec %eax 0xc018c0da : cmpl $0x1,0xffffffe0(%ebp) 0xc018c0de : cmovl 0xffffffdc(%ebp),%eax 0xc018c0e2 : mov %eax,0xffffffdc(%ebp) 0xc018c0e5 : mov 0xffffffdc(%ebp),%edi 0xc018c0e8 : mov 0x8(%ebp),%eax 0xc018c0eb : test %edi,%edi 0xc018c0ed : mov %edi,0x44(%eax) 0xc018c0f0 : je 0xc018c0ff 0xc018c0f2 : movzwl 0x6(%esi),%eax 0xc018c0f6 : xchg %al,%ah 0xc018c0f8 : movzwl %ax,%eax 0xc018c0fb : cmp %eax,%edi 0xc018c0fd : jle 0xc018c130 0xc018c0ff : mov 0x10(%ebp),%edx 0xc018c102 : movl $0x0,(%edx) 0xc018c108 : jmp 0xc018c14a 0xc018c10a : lea 0x0(%esi),%esi 0xc018c110 : xor %eax,%eax 0xc018c112 : mov 0x8(%ebp),%ecx 0xc018c115 : cmpl $0x1,0xc(%ebp) 0xc018c119 : setne %al 0xc018c11c : mov %eax,0x44(%ecx) 0xc018c11f : xor %eax,%eax 0xc018c121 : mov 0x10(%ebp),%edi 0xc018c124 : movl $0x0,(%edi) 0xc018c12a : jmp 0xc018c14c 0xc018c12c : lea 0x0(%esi,1),%esi 0xc018c130 : mov 0xc(%ebp),%ebx 0xc018c133 : xor %eax,%eax 0xc018c135 : test %ebx,%ebx 0xc018c137 : jne 0xc018c140 0xc018c139 : mov 0xffffffe0(%ebp),%ecx 0xc018c13c : test %ecx,%ecx 0xc018c13e : jne 0xc018c145 0xc018c140 : mov $0x1,%eax 0xc018c145 : mov 0x10(%ebp),%edx 0xc018c148 : mov %eax,(%edx) 0xc018c14a : xor %eax,%eax 0xc018c14c : lea 0xfffffff4(%ebp),%esp 0xc018c14f : pop %ebx 0xc018c150 : pop %esi 0xc018c151 : pop %edi 0xc018c152 : pop %ebp 0xc018c153 : ret 0xc018c154 : lea 0x0(%esi),%esi 0xc018c15a : lea 0x0(%edi),%edi End of assembler dump. (gdb) From owner-linux-xfs@oss.sgi.com Mon Sep 10 06:37:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ADbdE16045 for linux-xfs-outgoing; Mon, 10 Sep 2001 06:37:39 -0700 Received: from linux.compucomis.net (linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ADZad16000 for ; Mon, 10 Sep 2001 06:37:21 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id D2E9E139DA; Mon, 10 Sep 2001 09:35:07 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id A9E42139D1; Mon, 10 Sep 2001 09:35:07 -0400 (EDT) Date: Mon, 10 Sep 2001 09:35:07 -0400 (EDT) From: Mike Burger To: Simon Matter Cc: linux-xfs Subject: Re: Updated quota RPM for RedHat 7.1 In-Reply-To: <3B9CB83C.38153FEE@ch.sauter-bc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Blarg. I think I might have let up2date update it. Crud...guess I'll have to put the SGI CD back in the system, and see if I can't replace the samba install. On Mon, 10 Sep 2001, Simon Matter wrote: > Mike Burger schrieb: > > > > Hmm...that probably explains why I can't seem to enable quotas. > > > > What is the version of the quota package that comes with the XFS install? > > The RH-7.1XFS 1.0.1 comes with quota-3.01-pre7 > > Simon > > > > > On Mon, 10 Sep 2001, Simon Matter wrote: > > > > > I've just checked for updates for RH-7.1 and found a new quota RPM. I > > > guess it wouldn't be a good idea to install this one since the quota > > > package for XFS is modified. Did I assume right? > > > > > > Simon > > > > > > > > > > > > From owner-linux-xfs@oss.sgi.com Mon Sep 10 06:43:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ADhDa16239 for linux-xfs-outgoing; Mon, 10 Sep 2001 06:43:13 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ADhBd16220 for ; Mon, 10 Sep 2001 06:43:11 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f8ADh5J22396 for ; Mon, 10 Sep 2001 06:43:05 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id AAA04238; Tue, 11 Sep 2001 00:41:48 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id AAA87043; Tue, 11 Sep 2001 00:41:48 +1100 (AEDT) Date: Tue, 11 Sep 2001 00:41:47 +1100 From: Nathan Scott To: Simon Matter Cc: linux-xfs Subject: Re: Updated quota RPM for RedHat 7.1 Message-ID: <20010911004147.A288111@wobbly.melbourne.sgi.com> References: <3B9CAB9D.28502B00@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B9CAB9D.28502B00@ch.sauter-bc.com>; from simon.matter@ch.sauter-bc.com on Mon, Sep 10, 2001 at 02:01:33PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Mon, Sep 10, 2001 at 02:01:33PM +0200, Simon Matter wrote: > I've just checked for updates for RH-7.1 and found a new quota RPM. I > guess it wouldn't be a good idea to install this one since the quota > package for XFS is modified. Did I assume right? With the XFS releases we didn't actually ship a "modified rpm" per-se - we shipped a version of the quota rpm which was ahead of where Redhat was at the time (but it sounds like they are catching up, which is good). I'm pretty sure this new version (as long as its >3.01) will work with XFS quota, but YMMV. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Sep 10 06:45:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ADj8V16409 for linux-xfs-outgoing; Mon, 10 Sep 2001 06:45:08 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ADj5d16390 for ; Mon, 10 Sep 2001 06:45:05 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id PAA09205; Mon, 10 Sep 2001 15:44:44 +0200 (CEST) Message-Id: <4.3.2.7.2.20010910154402.03d952c8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 10 Sep 2001 15:44:42 +0200 To: Rob Myers , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: 2.4.9 oops - dual athlon/2gb ram In-Reply-To: <1000127795.10581.13.camel@ransom> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 09:16 10-9-2001 -0400, Rob Myers wrote: >hello > >i generated an oops after running ctcs >(http://sourceforge.net/projects/va-ctcs/) for 5 days. This machine is >a dual athlon with 2gb ram and a single scsi disk. > >Linux version 2.4.9-xfs (root@monsoon) (gcc version 2.96 20000731 (Red >Hat Linux 7.1 2.96-85)) #6 SMP Fri Aug 24 00:31:54 EDT 2001 > >would switching back to kgcc solve this problem? I think it would. Most "vague" problems solve them selves after recompiling with kgcc. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Sep 10 06:50:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ADou116599 for linux-xfs-outgoing; Mon, 10 Sep 2001 06:50:56 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ADocd16579; Mon, 10 Sep 2001 06:50:38 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8ADodd16580 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 07:23:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AENFh17426 for linux-xfs-outgoing; Mon, 10 Sep 2001 07:23:15 -0700 Received: from linux.compucomis.net (linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AEMpd17406 for ; Mon, 10 Sep 2001 07:22:58 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id E588C139DA; Mon, 10 Sep 2001 10:22:22 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id E2748139D1; Mon, 10 Sep 2001 10:22:22 -0400 (EDT) Date: Mon, 10 Sep 2001 10:22:22 -0400 (EDT) From: Mike Burger To: Nathan Scott Cc: Simon Matter , linux-xfs Subject: Re: Updated quota RPM for RedHat 7.1 In-Reply-To: <20010911004147.A288111@wobbly.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hmm...the version on my 7.1 w/XFS install is 3.00-4. Maybe I'm missing something. I'll have to check the XFS download area, as well as my XFS install CD. On Tue, 11 Sep 2001, Nathan Scott wrote: > hi, > > On Mon, Sep 10, 2001 at 02:01:33PM +0200, Simon Matter wrote: > > I've just checked for updates for RH-7.1 and found a new quota RPM. I > > guess it wouldn't be a good idea to install this one since the quota > > package for XFS is modified. Did I assume right? > > With the XFS releases we didn't actually ship a "modified rpm" > per-se - we shipped a version of the quota rpm which was ahead > of where Redhat was at the time (but it sounds like they are > catching up, which is good). I'm pretty sure this new version > (as long as its >3.01) will work with XFS quota, but YMMV. > > cheers. > > From owner-linux-xfs@oss.sgi.com Mon Sep 10 07:25:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AEPXY17591 for linux-xfs-outgoing; Mon, 10 Sep 2001 07:25:33 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AEPUd17572 for ; Mon, 10 Sep 2001 07:25:30 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8AEPM519178 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Mon, 10 Sep 2001 07:25:22 -0700 Received: from zeus-fddi.americas.sgi.com ([128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA243469 for ; Mon, 10 Sep 2001 16:25:29 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2917057; Mon, 10 Sep 2001 09:24:03 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA08284; Mon, 10 Sep 2001 09:24:03 -0500 (CDT) Message-ID: <3B9CCCE8.BD8396E9@sgi.com> Date: Mon, 10 Sep 2001 09:23:36 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Alan Brown CC: linux-xfs@oss.sgi.com Subject: Re: Patch comments. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Alan Brown wrote: > Also your inclusion of non-related code may interfere with application > of other single patches people may be applying. > Hi Alan - We do have a "clean" set of patches with kdb, lvm, acl/extattr, etc stripped out to make it easy to see "core" XFS. However, even these stripped down patches may not apply cleanly to -ac trees since we do our development against Linus' tree. Also, Alan C. is aware of XFS - although we're not directly submitting to him (I don't think). However, based on some of his diary entries, I'm not sure he's quite ready to take it into his tree either. We'll just keep plugging away... :) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Mon Sep 10 07:30:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AEUK817797 for linux-xfs-outgoing; Mon, 10 Sep 2001 07:30:20 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AEU8d17765 for ; Mon, 10 Sep 2001 07:30:08 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id QAA08103; Mon, 10 Sep 2001 16:29:42 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id QAA22982; Mon, 10 Sep 2001 16:29:16 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id F112057306; Mon, 10 Sep 2001 16:28:16 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id DB96125835; Mon, 10 Sep 2001 16:28:16 +0200 (CEST) Message-ID: <3B9CCE00.D704DC0B@ch.sauter-bc.com> Date: Mon, 10 Sep 2001 16:28:16 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Adrian Head Cc: linux-xfs@oss.sgi.com Subject: Re: Problems with many processes copying large directories acrossan XFS volume. References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Adrian Head schrieb: > > Thanks for your reply Simon > > Yes the softraid was fully synced before I started any test. > > The XFS patch I used to obtain these errors was > patch-2.4.9-xfs-2001-08-19 and the errors were: > Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 > Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device > > When I used a later version of the XFS patch I had more descriptive > errors written to /var/log/messages: > Sep 10 10:14:57 ATLAS kernel: I/O error in filesystem ("md(9,0)") > meta-data dev 0x900 block 0x9802bdc > Sep 10 10:14:57 ATLAS kernel: (xlog_iodone") error 5 buf count 32768 > Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called > from line 940 of file xfs_log.c. Return address - 0xd8cb66f8 > Sep 10 10:14:57 ATLAS kernel: Log I/O Error Detected. Shutting down > filesystem: md(9,0) > Sep 10 10:14:57 ATLAS kernel: Please umount the filesystem, and rectify > the problem(s) > Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called > from line 714 of file xfs_log.c. Return address = 0xd8cb65d3 > Sep 10 10:14:57 ATLAS kernel: attempt to access beyond end of device > Sep 10 10:14:57 ATLAS kernel: 02:82: rw=0, want=1602235696, limit=4 > > I did think at the time that it may have been issues with XFS stomping > all over raid code or raid code stomping all over XFS. Although I not > sure now as the 2.4.10-pre2-xfs-2001-09-02 patch never wrote any errors > out at all. (please see my 2nd post for more info) > > Thanks for taking the time to test this on your own machine. I tried 20, 40 and 80 simultanous cp with no crash. Then I changed the file tree and the new tree has ~280M small files with 100b-50kb size. When using 60 cp jobs the machine died. I could ping it but nothing more. No ssh, no console, no shutdown. I try some more tests tonight. I try the same with ext2 as well to make sure it's XFS and not Softraid. -Simon > > Adrian Head > Bytecomm P/L > > > -----Original Message----- > > From: Simon Matter [SMTP:simon.matter@ch.sauter-bc.com] > > Sent: Monday, 10 September 2001 17:45 > > To: adrian.head@bytecomm.com.au > > Cc: linux-xfs@oss.sgi.com > > Subject: Re: Problems with many processes copying large > > directories across an XFS volume. > > > > Hi Adrian > > > > I did similar tests two months ago. I was having problems as well but > > ufurtunately I don't remember what is was exactly. > > First question: You created Softraid5, was the raid synced when you > > started the tests? > > > > > In the /var/log/messages log around the same time as the copy test I > > get > > > entries like: > > > Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 > > > Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device > > > > This looks interesting. I don't know what this means exactly but it > > looks to me like you managed to create a filesystem bigger than the > > raid > > volume was? I got the very same error when I tried to restore data > > with > > xfsrestore from DAT (xfsrestore from DLT was fine). The issue is still > > open. > > > > I have a test system here with SoftRAID5 on 4 U160 SCSI disks. I'll > > try > > to kill it today with cp jobs. > > > > -Simon > > -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Mon Sep 10 07:32:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AEWG017932 for linux-xfs-outgoing; Mon, 10 Sep 2001 07:32:16 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AEWCd17910 for ; Mon, 10 Sep 2001 07:32:12 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id HAA02153 for ; Mon, 10 Sep 2001 07:32:19 -0700 (PDT) mail_from (ivanr@melbourne.sgi.com) Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id BAA04422; Tue, 11 Sep 2001 01:30:53 +1100 From: ivanr@melbourne.sgi.com (Ivan Rayner) Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id AAA04860; Tue, 11 Sep 2001 00:30:52 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Tue, 11 Sep 2001 00:30:52 +1000 To: Takayuki Sasaki cc: Subject: Re: xfsdump/xfsrestore failed sometimes when running QA suite 022 In-Reply-To: <200109101246.VAA27978@tagajo.bsd.tnes.nec.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 10 Sep 2001, Takayuki Sasaki wrote: > I would like to know that whether it is correct way or > workaround to dump the XFS file system which requires preceding > unmount and mount, not only for QA suite but also on a > production environment. > > Could you explain me about this? For a production environment, it would not be necessary to do the umount and mount to stabilise the filesystem. The fact is that xfsdump must be run on a mounted filesystem, which means there is always the possibility that it will miss files which have been created immediately before the execution of xfsdump and during the execution of xfsdump. These files will be caught in the backup the next time you run xfsdump. There is nothing xfsdump can do to protect against this situation -- it is up to the system administrator to try to run xfsdump when the system is not busy. If the system is always very busy, then the administrator should be sure to run xfsdump on a regular basis. In the QA environment, we create a test filesystem and immediately dump it, so we need to take special steps to ensure the test works as expected. Basically, it's simply a matter of understanding that the backup created by xfsdump is a snapshot of the filesystem as it was 30 seconds ago[1], rather than the moment xfsdump was run. For most people, I would expect this would be fine. Ivan [1] 30 seconds is just an estimate. This is reliant on the new inode data being being flushed to disk ... I'm not sure how long it takes normally. Someone else on the list might have a better idea. -- Ivan Rayner ivanr@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 10 07:42:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AEgJv18281 for linux-xfs-outgoing; Mon, 10 Sep 2001 07:42:19 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AEgGd18262 for ; Mon, 10 Sep 2001 07:42:16 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8AEgB521072 for ; Mon, 10 Sep 2001 07:42:11 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2932867; Mon, 10 Sep 2001 09:40:55 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA48024; Mon, 10 Sep 2001 09:40:51 -0500 (CDT) Message-ID: <3B9CD0D7.9D1B0491@sgi.com> Date: Mon, 10 Sep 2001 09:40:23 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Barrett Gay CC: linux-xfs@oss.sgi.com Subject: Re: Kickstart on Bootable CDROM References: <999975773.3b9a6b5d2b4e0@www.c4solutions.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Barrett - Not sure what to tell you here, I have never tried putting the ks.cfg on the CD itself. Might be one for the Red Hat lists/newsgroups? Or has this worked in the past for you with stock RH Linux 7.1? -Eric Barrett Gay wrote: > > I'm trying to create an automated install using kickstart off a bootable cd. > I specify the install method as "cdrom" in my ks.cfg on the cd. When I boot > the cd, it gives me the error: "No install method specified in Kickstart". > However, if I use the same image (with the same kickstart file) on a floppy, > the install goes fine. Any ideas? Should I specify the install method as > Harddrive and point it to /tmp/cdrom? -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Mon Sep 10 07:43:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AEh8C18407 for linux-xfs-outgoing; Mon, 10 Sep 2001 07:43:08 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AEh4d18388 for ; Mon, 10 Sep 2001 07:43:04 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8AEgx521171 for ; Mon, 10 Sep 2001 07:42:59 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2905964; Mon, 10 Sep 2001 09:41:40 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA15692; Mon, 10 Sep 2001 09:41:39 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f8AEcXo16558; Mon, 10 Sep 2001 09:38:33 -0500 Message-Id: <200109101438.f8AEcXo16558@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Takayuki Sasaki cc: Timothy Shimmin , linux-xfs@oss.sgi.com Subject: Re: xfsdump/xfsrestore failed sometimes when running QA suite 022 In-Reply-To: Message from Takayuki Sasaki of "Mon, 10 Sep 2001 21:46:58 +0900." <200109101246.VAA27978@tagajo.bsd.tnes.nec.co.jp> Date: Mon, 10 Sep 2001 09:38:33 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > xfsdump uses an xfs feature called bulkstat'ing to speed up > > the stat'ing of all the inodes of the file system. > > However, it apparently snapshots the info from the disk blocks > > instead of going through the in-core data structures. > > This means that if this data is not flushed to disk completely > > when xfsdump is running then it won't have the latest stat > > information. > > Hmmm... I see. > I should expand on this one a little. XFS has two copies of the inode, first the in memory inode structure which is used to by most parts of the filesystem, and is the structure modified by most operations and recorded into the log. Second is the on disk inode structure which is held in buffers, this structure is updated asynchronously from the in memory inode and flushed out to disk. It is this second structure which bulkstat reports the contents of and hence the potential time lag between what is visible to xfsdump and what is visible by the regular system call interface. The contents of the inode buffers should not lag behind the in memory inodes by very much - 30 to 60 seconds with the default kupdated configuration. As Ivan pointed out, xfsdump is not an instantanous operation anyway, it takes time to dump a filesystem, and should the filesystem be changing during the dump process there is no guaranteed way to ensure that everything which existed in memory at the time of the end of the dump will be in the dump. However, everything skipped by one dump should be included in the next dump. Steve From owner-linux-xfs@oss.sgi.com Mon Sep 10 07:46:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AEkEb18601 for linux-xfs-outgoing; Mon, 10 Sep 2001 07:46:14 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AEk6d18579 for ; Mon, 10 Sep 2001 07:46:06 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8AEk1521583 for ; Mon, 10 Sep 2001 07:46:01 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2899790; Mon, 10 Sep 2001 09:44:45 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA87030; Mon, 10 Sep 2001 09:44:45 -0500 (CDT) Message-ID: <3B9CD1C2.FB670E59@sgi.com> Date: Mon, 10 Sep 2001 09:44:18 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: damasta@teknospy.com CC: linux-xfs@oss.sgi.com Subject: Re: Mounting onboard raid References: <200109091603.f89G3NM22280@mail21.jump.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Bryan Payne wrote: > I have 3 harddrives. Hda has a swap, an ext2 boot and a xfs root. Hdb is xfs > and Hdg is xfs. If I attempt to mount hdg1, I get the wrong fs type error. Can you look in the system logs and see what they say when you try to mount? /bin/mount's error messages aren't the most helpful. > However, I moved hdg to to hdb and it mounts fine. Is this because of the > highpoint controller? The funny thing is I can mount hdg as vfat. And can you _read_ it, mounted as vfat? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Mon Sep 10 07:56:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AEuBD18850 for linux-xfs-outgoing; Mon, 10 Sep 2001 07:56:11 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AEu9d18831 for ; Mon, 10 Sep 2001 07:56:09 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8AEu3J26089 for ; Mon, 10 Sep 2001 07:56:03 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2931851; Mon, 10 Sep 2001 09:54:48 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA74273; Mon, 10 Sep 2001 09:54:47 -0500 (CDT) Message-ID: <3B9CD41C.89BC0C59@sgi.com> Date: Mon, 10 Sep 2001 09:54:20 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Federico Sevilla III CC: Linux XFS Mailing List Subject: Re: 10minutes for rm -rf on 400MB References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Federico Sevilla III wrote: > > On Sun, 9 Sep 2001 at 13:17, Dirk Wetter wrote: > > a user complained that /rm -rf of 400MB / takes ~10 minutes (!) until > > the command returns, whereas on the systems with reiserfs we have e.g. > > it takes seconds. > > This is expected. XFS does deletes synchronously. Still, 10 minutes is too long, I think. Since you're just guessing about the number of files, though, it's hard to say. If you can find out more about the data, that might offer some hints. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Mon Sep 10 08:03:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AF3bk19124 for linux-xfs-outgoing; Mon, 10 Sep 2001 08:03:37 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AF3Td19097 for ; Mon, 10 Sep 2001 08:03:29 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id IAA18078 for ; Mon, 10 Sep 2001 08:03:33 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id CAA04546; Tue, 11 Sep 2001 02:02:10 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id CAA85507; Tue, 11 Sep 2001 02:02:09 +1100 (AEDT) Date: Tue, 11 Sep 2001 02:02:09 +1100 From: Nathan Scott To: Mike Burger Cc: Simon Matter , linux-xfs Subject: Re: Updated quota RPM for RedHat 7.1 Message-ID: <20010911020209.D288111@wobbly.melbourne.sgi.com> References: <20010911004147.A288111@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mburger@compucomis.net on Mon, Sep 10, 2001 at 10:22:22AM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Mon, Sep 10, 2001 at 10:22:22AM -0400, Mike Burger wrote: > Hmm...the version on my 7.1 w/XFS install is 3.00-4. > > Maybe I'm missing something. > > I'll have to check the XFS download area, as well as my XFS install CD. > [Mike] ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/cmd_rpms/ contains quota-3.01-pre7.src.rpm ... that should be the version the installer provides you too. [Simon] Just checked the Redhat 7.1 updates and they are now using the quota-3.01-pre9 code, which does contain XFS quota support. For the next XFS installer release, we will start using the base Redhat quota rpm. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Sep 10 08:18:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AFIW619489 for linux-xfs-outgoing; Mon, 10 Sep 2001 08:18:32 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AFILd19467 for ; Mon, 10 Sep 2001 08:18:21 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id IAA01356 for ; Mon, 10 Sep 2001 08:16:50 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2936810; Mon, 10 Sep 2001 10:17:04 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA92216; Mon, 10 Sep 2001 10:17:04 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f8AFDwM20002; Mon, 10 Sep 2001 10:13:58 -0500 Message-Id: <200109101513.f8AFDwM20002@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Dirk Wetter cc: "Bernhard R. Erdmann" , Linux XFS Mailing List Subject: Re: 10minutes for rm -rf on 400MB In-Reply-To: Message from Dirk Wetter of "Sun, 09 Sep 2001 20:42:51 EDT." <3B9C0C8B.2070201@rentec.com> Content-Transfer-Encoding: 8bit Date: Mon, 10 Sep 2001 10:13:57 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > hi, > > Bernhard R. Erdmann wrote: > > >>we've been running XFS on the data disks of our HPC Linux cluster since > >>a while. we are quite happy with xfs, thx guys for your work! > >>the setup is: > >> > >>- dual >=1GHZ box, 4GB mem > >>- lvm 0.9beta7, phys. volume size ~140 GB, logical vol for xfs: 100GB > >>- no additional mount options or options for mkfs.xfs were given > >>- kernel 2.4.8pre4-xfs, highly patched SuSE 7.0 (not that it should matter) > >> > > >>a user complained that "rm -rf of 400MB" takes ~10 minutes (!) until > >>the > >>command returns, whereas on the systems with reiserfs we have e.g. it > >>takes seconds. > >> > > > >Some very important data is missing: > >- what's the I/O performance of the disk subsystem? > > > why is that relevant? with reiserfs it takes seconds, so the > disks/controller cannot be the bottleneck. This is because of a fundamental difference between reiserfs operation and xfs operation. reiserfs flushes its log to disk periodically, the log could in theory be very large in memory - a crash will basically undo everything which is in the in memory log. In fact, I have seen reiserfs create and remove 30000 files without doing any disk I/O at all. On the other hand XFS has a small in memory log, 64K is the default, when this is full it must go to disk. The in memory log is built of fixed sized 32K buffers, you can add more with the mount option logbufs=x where x is the number allowed, 8 is the maximum. This translates into the number of log writes which can be in transit at anyone time. This small log means that the amount of metadata which update can be lost at a crash is fairly small. To compound this issue some transactions in XFS are always synchronous, freeing space being one of them. The reason for this is complex, say you free some metadata and then it gets reallocated as data - and the data gets flushed out to disk. If you crash at this point and the removal of the space was in a transaction which did not make it out to disk then you end up with a filesystem which has data in an active metadata block. In order to avoid this situation, XFS flushes the free space operation to disk immediately, an expensive operation which is being done to deal with a very rare set of events. The 'obvious' fix is to not reuse this freed space until its transaction is on disk, or to not flush the reallocation to disk until the transaction is on disk. This fix has been on the TODO list around here for quite a long time - but there is always higher priority work to do. Having said that, all is not right with your system. I have a 2 CPU 450 Mhz PIII using a 7200rpm scsi drive on an Adaptec 7896 controller. On a single partition on this machine I just created 3 complete copies of the xfs tree, (kernel and commands) this consisted of 34549 files occupying 500Mbytes of disk space. In order to clean the cache and force reads from disk in the remove process I unmounted and remounted the filesystem before removing it. It took 65.373 seconds to remove the whole directory tree with a single rm -r -f. Having said that, this filesystem was mounted with 8 log buffers, and has a 16384 block log. The mkfs option for creating a bigger log is: mkfs -t xfs -f -l size=16384b /dev/xxx Steve From owner-linux-xfs@oss.sgi.com Mon Sep 10 08:20:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AFKS819625 for linux-xfs-outgoing; Mon, 10 Sep 2001 08:20:28 -0700 Received: from cis.ohio-state.edu (root@mail.cis.ohio-state.edu [164.107.115.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AFKPd19606 for ; Mon, 10 Sep 2001 08:20:25 -0700 Received: from iota.cis.ohio-state.edu (ramakria@iota.cis.ohio-state.edu [164.107.112.17]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id LAA00699 for ; Mon, 10 Sep 2001 11:20:24 -0400 (EDT) Received: from localhost (ramakria@localhost) by iota.cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id LAA05987 for ; Mon, 10 Sep 2001 11:20:24 -0400 (EDT) X-Authentication-Warning: iota.cis.ohio-state.edu: ramakria owned process doing -bs Date: Mon, 10 Sep 2001 11:20:24 -0400 (EDT) From: Arun Ramakrishnan To: Linux XFS Mailing List Subject: Re: 10minutes for rm -rf on 400MB In-Reply-To: <3B9CD41C.89BC0C59@sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I recently did rm -rf on a directory containing 6 10 GB files and it took a few seconds.I am running the XFS patched 2.4.9 kernel. Cheers, Arun. On Mon, 10 Sep 2001, Eric Sandeen wrote: > Federico Sevilla III wrote: > > > > On Sun, 9 Sep 2001 at 13:17, Dirk Wetter wrote: > > > a user complained that /rm -rf of 400MB / takes ~10 minutes (!) until > > > the command returns, whereas on the systems with reiserfs we have e.g. > > > it takes seconds. > > > > This is expected. XFS does deletes synchronously. > > Still, 10 minutes is too long, I think. Since you're just guessing > about the number of files, though, it's hard to say. If you can find > out more about the data, that might offer some hints. > > -Eric > > -- > Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs > sandeen@sgi.com SGI, Inc. > From owner-linux-xfs@oss.sgi.com Mon Sep 10 08:21:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AFL3019751 for linux-xfs-outgoing; Mon, 10 Sep 2001 08:21:03 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AFKbd19727; Mon, 10 Sep 2001 08:20:37 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8AFKcd19728 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 08:41:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AFfqL20231 for linux-xfs-outgoing; Mon, 10 Sep 2001 08:41:52 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AFfnd20212 for ; Mon, 10 Sep 2001 08:41:49 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8AFfh528112 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Mon, 10 Sep 2001 08:41:43 -0700 Received: from zeus-fddi.americas.sgi.com ([128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id RAA255488 for ; Mon, 10 Sep 2001 17:41:50 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2932434; Mon, 10 Sep 2001 10:40:25 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA80454; Mon, 10 Sep 2001 10:40:24 -0500 (CDT) Message-ID: <3B9CDECC.2EC34A61@sgi.com> Date: Mon, 10 Sep 2001 10:39:56 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Martin Loschwitz CC: linux-xfs@oss.sgi.com Subject: Re: xfs-cvstree-errors References: <20010910150620.A2155@Minerva> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Martin Loschwitz wrote: > > Hello ppl, i downloaded your xfs-cvs-tree for Linux-kernel 2.4. I tried to > compile it, but when i do "make dep", it finishs with: > > (problems) A fresh checkout today Works For Me. You might try a "make mrproper" and give it another shot. Or maybe even try a fresh checkout? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Mon Sep 10 09:02:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AG2C220728 for linux-xfs-outgoing; Mon, 10 Sep 2001 09:02:12 -0700 Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AG29d20709 for ; Mon, 10 Sep 2001 09:02:09 -0700 Received: from scare ([63.231.179.33]) by lips.thebarn.com (8.12.0/8.12.0) with ESMTP id f8AG1uPp028834; Mon, 10 Sep 2001 11:01:56 -0500 (CDT) Subject: Re: ftp.thebarn.com From: Russell Cattelan To: Alan Eldridge Cc: SGI XFS Dev List In-Reply-To: <20010909180634.A14095@wwweasel.geeksrus.net> References: <20010909180634.A14095@wwweasel.geeksrus.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 10 Sep 2001 10:55:15 -0500 Message-Id: <1000137316.29096.4678.camel@scare> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 09 Sep 2001 18:06:34 -0400, Alan Eldridge wrote: > Is Russell's CVSup daemon dead? Or is something else wrong? I can traceroute it > but I can't do a CVSup connect. :( > the system drive failed over the weekend and I was out of town this weekend so I didn't notice the failure till late sunday. I'm working on recovering the configuration give me a few hours. > -- > Alan Eldridge > from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Mon Sep 10 09:34:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AGYXo21343 for linux-xfs-outgoing; Mon, 10 Sep 2001 09:34:33 -0700 Received: from roujin.gargoylecc.com (roujin.gargoylecc.com [65.100.85.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AGYNd21323 for ; Mon, 10 Sep 2001 09:34:24 -0700 Received: from ringram by roujin.gargoylecc.com with local (Exim 3.31 #1) id 15gPWF-0000e8-00 for linux-xfs@oss.sgi.com; Mon, 10 Sep 2001 11:46:27 +0000 Date: Mon, 10 Sep 2001 11:46:27 +0000 To: linux-xfs@oss.sgi.com Subject: xfsdump error question Message-ID: <20010910114627.A1640@roujin.gargoylecc.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline User-Agent: Mutt/1.3.20i From: Russel Ingram Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I'm trying to run a system backup on my Debian based XFS system with xfsdump and keep getting the following error: xfsdump: version 3.0 - Running single-threaded xfsdump: level 0 dump of roujin:/ xfsdump: dump date: Mon Sep 10 09:41:26 2001 xfsdump: session id: 8714af3d-1288-46a3-ac9c-37ed6a33639c xfsdump: session label: "roujin full" xfsdump: ino map phase 1: skipping (no subtrees specified) xfsdump: ino map phase 2: constructing initial dump list xfsdump: ERROR: map_add(5243008, 3): ino(5243008) <= last_ino(5768702) The command I'm using is: xfsdump -l0 -o -E -F -L"roujin full" -M"root" -f /dev/st0 / Can someone tell me what this error means and if its something I'm doing wrong or if its a problem with my filesystem or xfsdump? I've also attached the output from running the same command with -v5. Thanx, Russ -- Russel H. Ingram Gargoyle Computer Consulting (307)742-1361 or (307)760-1317 www.gargoylecc.com --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="xfsdump.err" xfsdump: RLIMIT_AS org cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: RLIMIT_STACK org cur 0x800000 max 0xffffffffffffffff xfsdump: raising stack size soft limit from 0x800000 to 0x2000000 xfsdump: RLIMIT_STACK new cur 0x2000000 max 0xffffffffffffffff xfsdump: RLIMIT_DATA org cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: RLIMIT_FSIZE org cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: RLIMIT_FSIZE now cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: RLIMIT_CPU cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: RLIMIT_CPU now cur 0xffffffffffffffff max 0xffffffffffffffff xfsdump: INTGENMAX == 2147483647 (0x7fffffff) xfsdump: UINTGENMAX == 4294967295 (0xffffffff) xfsdump: OFF64MAX == 9223372036854775807 (0x7fffffffffffffff) xfsdump: OFFMAX == -1 (0x7fffffff) xfsdump: SIZEMAX == 4294967295 (0xffffffff) xfsdump: INOMAX == 4294967295 (0xffffffff) xfsdump: TIMEMAX == 2147483647 (0x7fffffff) xfsdump: SIZE64MAX == 18446744073709551615 (0xffffffffffffffff) xfsdump: INO64MAX == 18446744073709551615 (0xffffffffffffffff) xfsdump: UINT64MAX == 18446744073709551615 (0xffffffffffffffff) xfsdump: INT64MAX == 9223372036854775807 (0x7fffffffffffffff) xfsdump: UINT32MAX == 4294967295 (0xffffffff) xfsdump: INT32MAX == 2147483647 (0x7fffffff) xfsdump: INT16MAX == 32767 (0x7fff) xfsdump: UINT16MAX == 65535 (0xffff) xfsdump: getpagesize( ) returns 4096 xfsdump: parent pid is 1621 xfsdump: effective user id is 0 xfsdump: stack pid 1621: sz 0x2000000 min 0xbdfffbab max 0xbffffbab xfsdump: instantiating drive_scsitape xfsdump: version 3.0 - Running single-threaded xfsdump: fs / uuid [85dc0a65-d803-485b-9142-ef2c75e9dca9] xfsdump: creating directory /var/xfsdump xfsdump: level 0 dump of roujin:/ xfsdump: dump date: Mon Sep 10 11:31:41 2001 xfsdump: session id: 912bd615-dffe-453d-abe2-22e6ae42dbe4 xfsdump: session label: "root" xfsdump: excluding /var/xfsdump from dump xfsdump: excluding /var/xfsdump/inventory from dump xfsdump: excluding /var/xfsdump/inventory/3552fb6a-10ed-48eb-830c-3e32d0ea895c.InvIndex from dump xfsdump: excluding /var/xfsdump/inventory/823b26df-0abb-42d8-9d6b-8cd3fc826936.StObj from dump xfsdump: excluding /var/xfsdump/inventory/fstab from dump xfsdump: ino map phase 1: skipping (no subtrees specified) xfsdump: ino map phase 2: constructing initial dump list xfsdump: bulkstat iteration initiated: start_ino == 0 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 128 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 161396 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 1077258 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 1245314 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 1589835 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 2196064 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 3256808 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 3426415 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 3677526 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 4394016 xfsdump: calling bulkstat xfsdump: bulkstat returns buflen 4096 ino 5282011 xfsdump: ino 5768703 needed second bulkstat xfsdump: ERROR: map_add(5243008, 3): ino(5243008) <= last_ino(5768702) --bg08WKrSYDhXBjb5-- From owner-linux-xfs@oss.sgi.com Mon Sep 10 09:41:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AGfvj21595 for linux-xfs-outgoing; Mon, 10 Sep 2001 09:41:57 -0700 Received: from phobos.pop-star.net (phobos.pop-star.net [64.85.83.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AGfsd21575 for ; Mon, 10 Sep 2001 09:41:54 -0700 Received: from zerowing.pop-star.net ([208.181.22.52]) by phobos.pop-star.net with asmtp (Exim 3.167 #4) id 15gU9q-0000c2-00 for linux-xfs@oss.sgi.com; Mon, 10 Sep 2001 09:43:38 -0700 Subject: Contrib 2.4.10-pre2 RPMS From: Andy Kwong To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13.99+cvs.2001.09.05.07.08 (Preview Release) Date: 10 Sep 2001 09:42:18 -0700 Message-Id: <1000140142.9874.9.camel@zerowing.pop-star.net> Mime-Version: 1.0 X-Authenticated-Sender: andy.kwong@pop-star.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, We are using XFS with RedHat on production systems with highmem. Seems like the 2.4.3 and 2.4.5 had bounce buffer issues. Thus, we made some 2.4.10-pre2 RPMS with lm_sensors support (and the PL2303 patch) for convenience. They are available at - http://rpms.aicompro.net/ These are derived from the 2.4.5 RPM spec file and come in devfs and non-devfs flavors. Cheers, Andy From owner-linux-xfs@oss.sgi.com Mon Sep 10 09:44:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AGi3l21731 for linux-xfs-outgoing; Mon, 10 Sep 2001 09:44:03 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AGhud21712; Mon, 10 Sep 2001 09:43:56 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8AGhvd21713 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 10:50:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AHoiK22767 for linux-xfs-outgoing; Mon, 10 Sep 2001 10:50:44 -0700 Received: from thor.goeci.com (thor.goeci.com [216.181.40.16]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AHoed22748 for ; Mon, 10 Sep 2001 10:50:40 -0700 Received: by THOR with Internet Mail Service (5.5.2650.21) id ; Mon, 10 Sep 2001 13:50:34 -0400 Message-ID: From: Murthy Kambhampaty To: "'linux-xfs@oss.sgi.com'" Subject: Installing on disks connected with 3ware adapter Date: Mon, 10 Sep 2001 13:50:33 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am trying to install from the XFS installer (1.0.1) to a RAID 5 array on the 3ware Escalade 7810 controller. I load the drivers from floppy, but the installer doesn't not see the drives. I do not experience this problem with the stock RedHat installer CD-ROM. Please help. 3ware's installation manual is at: http://www.3ware.com/support/UserDocs/7000UG1.pdf Linux installation directions begin on page 107 3ware's drivers can be downloaded at: http://www.3ware.com/support/swlibrary.asp Thanks for the help. In the meanwhile, I am trying to see if using the older 1.0.0 installer give success. I will e-mail my findings with the subject above preceded by "Follow up:" Murthy S. Murthy Kambhampaty Vice President Glassman-Oliver Economic Consultants, Inc. 1828 L St NW, Suite 405 Washington, DC 20036-5104 Voice (202) 331-1946 Fax (202) 466-3199 From owner-linux-xfs@oss.sgi.com Mon Sep 10 10:57:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AHvuk22976 for linux-xfs-outgoing; Mon, 10 Sep 2001 10:57:56 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AHvqd22942 for ; Mon, 10 Sep 2001 10:57:52 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id 2CBCE139E5; Mon, 10 Sep 2001 13:57:55 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id 29CA1139DA; Mon, 10 Sep 2001 13:57:55 -0400 (EDT) Date: Mon, 10 Sep 2001 13:57:55 -0400 (EDT) From: Mike Burger To: Nathan Scott Cc: Simon Matter , linux-xfs Subject: Re: Updated quota RPM for RedHat 7.1 In-Reply-To: <20010911020209.D288111@wobbly.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Yup...just ran the update. Now, I'm working on creating the quotas...unfortunately, Webmin can't manipulate them...it's looking for quota.user and/or aquota.user, which don't exist in XFS quota support. Webmin thinks that the quota system isn't enabled. Oh, well. On Tue, 11 Sep 2001, Nathan Scott wrote: > hi, > > On Mon, Sep 10, 2001 at 10:22:22AM -0400, Mike Burger wrote: > > Hmm...the version on my 7.1 w/XFS install is 3.00-4. > > > > Maybe I'm missing something. > > > > I'll have to check the XFS download area, as well as my XFS install CD. > > > > [Mike] > ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/cmd_rpms/ > contains quota-3.01-pre7.src.rpm ... that should be the version > the installer provides you too. > > [Simon] > Just checked the Redhat 7.1 updates and they are now using the > quota-3.01-pre9 code, which does contain XFS quota support. > For the next XFS installer release, we will start using the > base Redhat quota rpm. > > cheers. > > From owner-linux-xfs@oss.sgi.com Mon Sep 10 11:02:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AI2Xw23187 for linux-xfs-outgoing; Mon, 10 Sep 2001 11:02:33 -0700 Received: from cis.ohio-state.edu (root@mail.cis.ohio-state.edu [164.107.115.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AI2Sd23168 for ; Mon, 10 Sep 2001 11:02:28 -0700 Received: from iota.cis.ohio-state.edu (ramakria@iota.cis.ohio-state.edu [164.107.112.17]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id OAA28441; Mon, 10 Sep 2001 14:02:27 -0400 (EDT) Received: from localhost (ramakria@localhost) by iota.cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id OAA07330; Mon, 10 Sep 2001 14:02:26 -0400 (EDT) X-Authentication-Warning: iota.cis.ohio-state.edu: ramakria owned process doing -bs Date: Mon, 10 Sep 2001 14:02:26 -0400 (EDT) From: Arun Ramakrishnan To: Murthy Kambhampaty cc: "'linux-xfs@oss.sgi.com'" Subject: Re: Installing on disks connected with 3ware adapter In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I beleive that the 3ware support comes with the 2.4 kernel.I had lot of kernel oopses with the 2.4 kernel and the drivers.So i checked the "3ware kernel switch" while compiling the kernel and it has been working fine. Cheers, Arun On Mon, 10 Sep 2001, Murthy Kambhampaty wrote: > I am trying to install from the XFS installer (1.0.1) to a RAID 5 array on > the 3ware Escalade 7810 controller. I load the drivers from floppy, but the > installer doesn't not see the drives. I do not experience this problem with > the stock RedHat installer CD-ROM. Please help. > > 3ware's installation manual is at: > http://www.3ware.com/support/UserDocs/7000UG1.pdf > Linux installation directions begin on page 107 > > 3ware's drivers can be downloaded at: > http://www.3ware.com/support/swlibrary.asp > > Thanks for the help. In the meanwhile, I am trying to see if using the older > 1.0.0 installer give success. I will e-mail my findings with the subject > above preceded by "Follow up:" > > Murthy > > S. Murthy Kambhampaty > Vice President > Glassman-Oliver Economic Consultants, Inc. > 1828 L St NW, Suite 405 > Washington, DC 20036-5104 > Voice (202) 331-1946 > Fax (202) 466-3199 > From owner-linux-xfs@oss.sgi.com Mon Sep 10 11:07:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AI7cj23366 for linux-xfs-outgoing; Mon, 10 Sep 2001 11:07:38 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AI7Hd23338; Mon, 10 Sep 2001 11:07:17 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8AI7Id23340 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 11:09:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AI9LZ23500 for linux-xfs-outgoing; Mon, 10 Sep 2001 11:09:21 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AI9Dd23481 for ; Mon, 10 Sep 2001 11:09:13 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id LAA04610 for ; Mon, 10 Sep 2001 11:08:44 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2769637; Mon, 10 Sep 2001 13:07:13 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id NAA97787; Mon, 10 Sep 2001 13:07:12 -0500 (CDT) Message-ID: <3B9D0134.CABAF90F@sgi.com> Date: Mon, 10 Sep 2001 13:06:44 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Murthy Kambhampaty CC: "'linux-xfs@oss.sgi.com'" Subject: Re: Installing on disks connected with 3ware adapter References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Murthy Kambhampaty wrote: > > I am trying to install from the XFS installer (1.0.1) to a RAID 5 array on > the 3ware Escalade 7810 controller. I load the drivers from floppy, but the > installer doesn't not see the drives. I do not experience this problem with > the stock RedHat installer CD-ROM. Please help. Hi - I'm not sure how you created the drivers floppy - if it's the same one you used with RH Linux 7.1, it won't work with the XFS installer since we run a different (xfs-capable, 2.4.3-updated) kernel in our installer. You'll need to recompile the driver to be loadable under the 2.4.3-BOOT kernel we use in the installer. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Mon Sep 10 11:17:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AIH1B23790 for linux-xfs-outgoing; Mon, 10 Sep 2001 11:17:01 -0700 Received: from sto-vo-kor.koschikode.com (sto-vo-kor.koschikode.com [195.124.129.42]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AIGwd23771 for ; Mon, 10 Sep 2001 11:16:58 -0700 Received: from warp9.koschikode.com (pD9E0E640.dip.t-dialin.net [217.224.230.64]) by sto-vo-kor.koschikode.com (Postfix) with ESMTP id A0CFCB52B; Mon, 10 Sep 2001 20:16:53 +0200 (CEST) Received: from koschikode.com (kaplah.koschikode.com [192.168.200.15]) by warp9.koschikode.com (Postfix) with ESMTP id 846D7CDF3; Mon, 10 Sep 2001 20:16:42 +0200 (CEST) Message-ID: <3B9D0389.CE17E423@koschikode.com> Date: Mon, 10 Sep 2001 20:16:41 +0200 From: Juri Haberland X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.10-pre4-ext3 i686) X-Accept-Language: en MIME-Version: 1.0 To: Seref Tufan Sen Cc: linux-xfs@oss.sgi.com, Michael Wahlbrink Subject: Re: Problems with many processes copying large directories across an XFS volume.[Offtpic] References: <001201c139f7$5d5b62a0$2c054ba0@aontws4044> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seref Tufan Sen wrote: > > I got 7 copies of this message. Am I the only one with this problem ??? No, same here :-( Michael, it seems to be your message which is repeatedly send (~ ever 90 minutes). Can you have a look whether there's something wrong on your side? TIA, Juri From owner-linux-xfs@oss.sgi.com Mon Sep 10 12:37:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AJbmt25498 for linux-xfs-outgoing; Mon, 10 Sep 2001 12:37:48 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AJbHd25387; Mon, 10 Sep 2001 12:37:17 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8AJbId25398 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 13:35:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AKZgq26807 for linux-xfs-outgoing; Mon, 10 Sep 2001 13:35:42 -0700 Received: from chef.cc.absoval.com (cpe-66-1-218-101.fl.sprintbbd.net [66.1.218.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AKZbd26782 for ; Mon, 10 Sep 2001 13:35:37 -0700 Received: from ieee.org (IDENT:bs@thebs.cc.absoval.com. [192.168.100.89]) by chef.cc.absoval.com (8.9.3/8.9.3) with ESMTP id QAA13446; Mon, 10 Sep 2001 16:35:00 -0400 Message-ID: <3B9D2415.DE0F8347@ieee.org> Date: Mon, 10 Sep 2001 16:35:33 -0400 From: Bryan-TheBS-Smith Organization: SmithConcepts/AbsoluteValueSystems X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: en MIME-Version: 1.0 To: Eric Sandeen CC: Murthy Kambhampaty , "'linux-xfs@oss.sgi.com'" Subject: Re: Installing on disks connected with 3ware adapter References: <3B9D0134.CABAF90F@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > I'm not sure how you created the drivers floppy - if it's the same one > you used with RH Linux 7.1, it won't work with the XFS installer since > we run a different (xfs-capable, 2.4.3-updated) kernel in our > installer. You'll need to recompile the driver to be loadable under the > 2.4.3-BOOT kernel we use in the installer. I had the same issue. This is what I did: - Install RedHat 7.1 + XFS 1.0.1 on a regular drive - Grab the updated firmware and drivers for the 7000 series - Compile the driver module for the kernel, copy to modules directory - Create an initrd (initial root disk) for the kernel with the 3Ware driver - Modify and re-install LILO for the kernel+initrd - Reboot with 3Ware card/drives connected - Transfer over the partitions - Boot the XFS installer into recovery mode - Re-install LILO I found this to be quickest and easiest. -- TheBS -- Bryan "TheBS" Smith mailto:b.j.smith@ieee.org chat:thebs413 Engineer AbsoluteValue Systems, Inc. http://www.linux-wlan.org President SmithConcepts, Inc. http://www.SmithConcepts.com From owner-linux-xfs@oss.sgi.com Mon Sep 10 13:43:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AKhIS27115 for linux-xfs-outgoing; Mon, 10 Sep 2001 13:43:18 -0700 Received: from gateway1.brets.elevating.com (adsl-216-63-236-137.dsl.tulsok.swbell.net [216.63.236.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AKhCd27096 for ; Mon, 10 Sep 2001 13:43:12 -0700 Received: from elevating.com (bretdell.brets.elevating.com [192.168.0.128]) by gateway1.brets.elevating.com (8.9.3/8.8.7) with ESMTP id PAA13696; Mon, 10 Sep 2001 15:43:12 -0500 Message-ID: <3B9D25E0.9483C32A@elevating.com> Date: Mon, 10 Sep 2001 15:43:12 -0500 From: Bret Hughes X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, ja MIME-Version: 1.0 To: linux-xfs Subject: [Fwd: Re: directory cache problems (I think)] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter wrote: > > Hi Bret > > Bret Hughes schrieb: > > > > I have a configuration on 6 boxes, Duron 700 with 128 MB ram and 10GB > > ide harddrives. These machines are all XFS 1.0.1 using the kernel from > > the 1.0.1 RH install iso and most of the RH updates. > > > > They were all placed into service the same day and yesterday 5 days > > after they were turned on they all stopped responding to ssh. A couple > > would still respond to a ping but nothing else. Actually I caough one > > before it quit altogether and rebooted it last night. These machines a > > kiosk type display that scroll html and flash pages using (netscape as > > the browser). There is no user interaction infact not any input device > > at all. A different page is displayed every 10 seconds. > > > > Now, After rebooting them I can get to the sadc data and looking through > > the logs shows really bad stuff happening at 1:00PM yesterday on the one > > machine I have really looked at closely. interrupt 14s out the wazoo > > and what I think must be the cause, the dentunusd goes to 0. Looking > > over the logs of the last few days I can see the dentunusd creeping down > > from the beginning at boot of over 20K to 0. > > > > Since netscape is such a pig I kill it and restart it once an hour and > > restart X once a day. both these events seem to take a tremendous toll > > on this value and never gain it all back. > > > > I don't know if this is an XFS issue or not but I thought that I would > > start here. Any ideas? I can send all the log data anyone might use if > > it would help. Right now I am going to reboot the damn things nightly > > like they were windows machines for Christ's sake. > > > > BTW the same scenario and control scripts run for months on end on RH > > 6.2 using the 2.2.3-16 kernel. > > > > Any tips and or other places to ask are appreciated. > > > > TIA > > > > Bret > > Did you run the RH-6.2 stuff on exactly the same hardware (including > same disks?) No, I have not. The load is really not very high though. I will go ahead and try the 6.2 config on the new hardware. Something is definitely weird. > > What about the disks, are they running with DMA enabled? > Yes. the default was to enable mda and the 32 bit access. I have not increased the bus speed though I plan on testing it. > Over here our mailservers used to be IBM PC's with Fujitsu Harddrives. > After some time of operation they started to slow down and load started > to increase. They even did not respond to ssh sometimes. In the end I > saw that those disks failed under the heavy load of the mailserver and I > replaced them with other disks. We have hundreds of the same disks in > windows desktop PC's with no problem. Linux just pushes the hardware > more. > > Simon Thanks for the thoughts. Bret From owner-linux-xfs@oss.sgi.com Mon Sep 10 14:00:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AL0nv27836 for linux-xfs-outgoing; Mon, 10 Sep 2001 14:00:49 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AL0bd27809; Mon, 10 Sep 2001 14:00:37 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8AL0cd27810 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 15:24:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AMO3L30339 for linux-xfs-outgoing; Mon, 10 Sep 2001 15:24:03 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AMNvd30319; Mon, 10 Sep 2001 15:23:57 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8AMNwd30320 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 15:47:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8AMlph30944 for linux-xfs-outgoing; Mon, 10 Sep 2001 15:47:51 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8AMlOd30919; Mon, 10 Sep 2001 15:47:25 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8AMlPd30920 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 16:42:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ANgIW31884 for linux-xfs-outgoing; Mon, 10 Sep 2001 16:42:18 -0700 Received: from plato.arts.usyd.edu.au (plato.arts.usyd.edu.au [129.78.16.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ANgBd31850 for ; Mon, 10 Sep 2001 16:42:12 -0700 Received: from arts.usyd.edu.au (IDENT:matthew@whitestar.arts.usyd.edu.au [129.78.16.20]) by plato.arts.usyd.edu.au (8.9.3/8.9.3) with ESMTP id JAA00945; Tue, 11 Sep 2001 09:41:24 +1000 (EST) Message-ID: <3B9D5124.3C1F644D@arts.usyd.edu.au> Date: Tue, 11 Sep 2001 09:47:48 +1000 From: Matthew Geier Organization: Arts IT Unit, Sydney University X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i686) X-Accept-Language: en, pdf MIME-Version: 1.0 To: Simon Matter CC: linux-xfs Subject: Re: Updated quota RPM for RedHat 7.1 References: <3B9CAB9D.28502B00@ch.sauter-bc.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms3D1C4854A0DB9000FEF4AFB7" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a cryptographically signed message in MIME format. --------------ms3D1C4854A0DB9000FEF4AFB7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Simon Matter wrote: > > I've just checked for updates for RH-7.1 and found a new quota RPM. I > guess it wouldn't be a good idea to install this one since the quota > package for XFS is modified. Did I assume right? Yes. I accidently did this running the command line 'up2date' which doesn't ask what packages to update, it just 'does it'. Fortunatly I had the XFS source tree including the 'cmd' folder on the system, so I had the XFS versions on hand to put back :-) -- Matthew Geier matthew@arts.usyd.edu.au Arts IT Unit +61 2 9351 4713 Sydney University --------------ms3D1C4854A0DB9000FEF4AFB7 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIH0AYJKoZIhvcNAQcCoIIHwTCCB70CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BbswggKKMIIB86ADAgECAgMFMYswDQYJKoZIhvcNAQECBQAwgZIxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMTA3MDkxOTEyNThaFw0wMjA3MDkxOTEyNTha MEoxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxJzAlBgkqhkiG9w0BCQEWGG1h dHRoZXdAYXJ0cy51c3lkLmVkdS5hdTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA1H+o MQ4xn5lDS/7p9rYboPW7grw13lXOj7Xisip37QttkX7Ga3ITBXnsAKnuFK3Z7GtILACBXil1 BngLBOd0AlW9zqQBXEOP9aODNJzBsTb3+tOHwQo6shcORKQArKEinG00SuwBdzxALU3KWT6E yIUSvoz7q0PN4C8qUF3t00sCAwEAAaM1MDMwIwYDVR0RBBwwGoEYbWF0dGhld0BhcnRzLnVz eWQuZWR1LmF1MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQECBQADgYEAiJu7SNBXsW7I+ZH9 e2+0M47BmR3DxV31VbW9mKcwuamusWSJJEy5MAKZc8b0snRX/XDkCpM+av3VxDJX8T3rxOE0 siyCC6Tclu6wjwjw0goXK4N6Xhsz+qwIfdoclNZkqK5yInEZtc5ijKr0IPRgch79f35WP82C SNHVYApmjzgwggMpMIICkqADAgECAgEMMA0GCSqGSIb3DQEBBAUAMIHRMQswCQYDVQQGEwJa QTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoT EVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERp dmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG 9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDAwODMwMDAwMDAwWhcN MDIwODI5MjM1OTU5WjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTES MBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmlj YXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMw MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMzKmY8cJJUU+0m54J2eBxdqIGYKXDuNE KYpjNSptcDz63K737nRvMLwzkH/5NHGgo22Y8cNPomXbDfpL8dbdYaX5hc1VmjUanZJ1qCeu 2HL5ugL217CR3hzpq+AYA6h8Q0JQUYeDPPA5tJtUihOH/7ObnUlmAC0JieyUa+mhaQIDAQAB o04wTDApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMS0yOTcwEgYDVR0T AQH/BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAcxtvJmWL/xU0 S1liiu1EvknH6A27j7kNaiYqYoQfuIdjdBxtt88aU5FL4c3mONntUPQ6bDSSrOaSnG7BIwHC CafvS65y3QZn9VBvLli4tgvBUFe17BzX7xe21Yibt6KIGu05Wzl9NPy2lhglTWr0ncXDkS+p lrgFPFL83eliA0gxggHdMIIB2QIBATCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNV BAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBS U0EgMjAwMC44LjMwAgMFMYswCQYFKw4DAhoFAKCBmTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0wMTA5MTAyMzQ3NDlaMCMGCSqGSIb3DQEJBDEWBBShRI1k v9L/tOJ1TF7s+C7K5ybQ6TA6BgkqhkiG9w0BCQ8xLTArMAoGCCqGSIb3DQMHMA4GCCqGSIb3 DQMCAgIAgDANBggqhkiG9w0DAgIBQDANBgkqhkiG9w0BAQEFAASBgETvrK6p2jj34wo/jgr5 RxnTJMmuMtyftXprGqE/rBwRTf3hGENNoHi61NnHVIG+632h7e6htqR/QTYSSzUM97/yTacC d8+C9vQOukbVTi959W4zt/rdhTpDPhtnWfHyqsfjIRtEkmIIjS2j24SOQsxU6O2PMt9PLD7J XaOs3Dce --------------ms3D1C4854A0DB9000FEF4AFB7-- From owner-linux-xfs@oss.sgi.com Mon Sep 10 16:42:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ANg9E31844 for linux-xfs-outgoing; Mon, 10 Sep 2001 16:42:09 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ANg3d31823 for ; Mon, 10 Sep 2001 16:42:03 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id QAA01248 for ; Mon, 10 Sep 2001 16:42:07 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA06602; Tue, 11 Sep 2001 10:40:40 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA29557; Tue, 11 Sep 2001 10:40:37 +1100 (AEDT) Date: Tue, 11 Sep 2001 10:40:36 +1100 From: Nathan Scott To: Mike Burger Cc: linux-xfs , jcameron@webmin.com Subject: Re: Updated quota RPM for RedHat 7.1 Message-ID: <20010911104036.B376776@wobbly.melbourne.sgi.com> References: <20010911020209.D288111@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mburger@compucomis.net on Mon, Sep 10, 2001 at 01:57:55PM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Mike, On Mon, Sep 10, 2001 at 01:57:55PM -0400, Mike Burger wrote: > Yup...just ran the update. Now, I'm working on creating the > quotas...unfortunately, Webmin can't manipulate them...it's looking for > quota.user and/or aquota.user, which don't exist in XFS quota support. > Webmin thinks that the quota system isn't enabled. > Hmmm.... I know nothing about Webmin I'm afraid. The quota link from this web page - http://www.webmin.com/webmin/standard.html - suggests its a matter of doing some Perl hacking to make this work. I've CC'd the webmin author - perhaps he can give some additional pointers. I'm guessing there's an assumption in there that for quota to be enabled there must be a [a]quota.[user|group] file in the filesystem root - which is not correct for XFS filesystems. As a reference, there is a "README.quota" file in xfsprogs which discusses the differences between XFS notion of quota and the model used in the two versions of the Linux VFS quota subsystem. Another reference is the code in the current quota package which implements support for all three models of quota in one set of tools. cheers. > > On Tue, 11 Sep 2001, Nathan Scott wrote: > > > hi, > > > > On Mon, Sep 10, 2001 at 10:22:22AM -0400, Mike Burger wrote: > > > Hmm...the version on my 7.1 w/XFS install is 3.00-4. > > > > > > Maybe I'm missing something. > > > > > > I'll have to check the XFS download area, as well as my XFS install CD. > > > > > > > [Mike] > > ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/cmd_rpms/ > > contains quota-3.01-pre7.src.rpm ... that should be the version > > the installer provides you too. > > > > [Simon] > > Just checked the Redhat 7.1 updates and they are now using the > > quota-3.01-pre9 code, which does contain XFS quota support. > > For the next XFS installer release, we will start using the > > base Redhat quota rpm. > > > > cheers. > > > > > -- Nathan From owner-linux-xfs@oss.sgi.com Mon Sep 10 17:02:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B02ur32386 for linux-xfs-outgoing; Mon, 10 Sep 2001 17:02:56 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B02sd32364 for ; Mon, 10 Sep 2001 17:02:54 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id EE74E139EC; Mon, 10 Sep 2001 20:02:57 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id EB857139EA; Mon, 10 Sep 2001 20:02:57 -0400 (EDT) Date: Mon, 10 Sep 2001 20:02:57 -0400 (EDT) From: Mike Burger To: Matthew Geier Cc: Simon Matter , linux-xfs Subject: Re: Updated quota RPM for RedHat 7.1 In-Reply-To: <3B9D5124.3C1F644D@arts.usyd.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 11 Sep 2001, Matthew Geier wrote: > I accidently did this running the command line 'up2date' which doesn't > ask what packages to update, it just 'does it'. > Fortunatly I had the XFS source tree including the 'cmd' folder on the > system, so I had the XFS versions on hand to put back :-) Interesting...usually, when I run "up2date" from the command line, it gives me a menu. I usually have to run "up2date -l" to list the packages that are available, and then "up2date ..." to download and install them. From owner-linux-xfs@oss.sgi.com Mon Sep 10 17:11:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B0BAL32668 for linux-xfs-outgoing; Mon, 10 Sep 2001 17:11:10 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B0Ahd32642; Mon, 10 Sep 2001 17:10:43 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8B0Aid32643 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 18:12:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B1CxB01429 for linux-xfs-outgoing; Mon, 10 Sep 2001 18:12:59 -0700 Received: from alpha.bytecomm.com.au (byt130674-1.gw.connect.com.au [202.21.11.108]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B1Crd01407 for ; Mon, 10 Sep 2001 18:12:53 -0700 Received: (qmail 24466 invoked from network); 11 Sep 2001 01:12:41 -0000 Received: from unknown (HELO herbie.local) (192.168.0.11) by 192.168.0.1 with SMTP; 11 Sep 2001 01:12:41 -0000 Received: by herbie.local with Internet Mail Service (5.5.1960.3) id ; Tue, 11 Sep 2001 11:12:41 +1000 Message-ID: From: Adrian Head To: Simon Matter Cc: linux-xfs@oss.sgi.com Subject: RE: Problems with many processes copying large directories across an XFS volume. Date: Tue, 11 Sep 2001 11:12:35 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Again - thanks Simon for your time. I have done ten's of tests now and I am getting a strong feeling that it is the same problems described here from Steve Lord: http://marc.theaimsgroup.com/?l=linux-xfs&m=99980808004670&w=2 Or the start of the thread: http://marc.theaimsgroup.com/?l=linux-xfs&m=99919025308712&w=2 The reason I am almost convinced it is the same issue is that about every 3 attempts I have only bdflush running and everything else in deadlock. - I will have to follow the instructions and see what output I get from kdb. It appears that although they could only get it to crash with SCSI the problem affects both SCSI & IDE. I was going to short-cut the process and just download the cvs tree - but for some reason the XFS site times-out at the moment. I will try later. When your machine hangs - have you noticed any trends in what processes are left running? Adrian Head P/L > -----Original Message----- > From: Simon Matter [SMTP:simon.matter@ch.sauter-bc.com] > Sent: Tuesday, 11 September 2001 00:28 > To: Adrian Head > Cc: linux-xfs@oss.sgi.com > Subject: Re: Problems with many processes copying large > directories acrossan XFS volume. > > > I tried 20, 40 and 80 simultanous cp with no crash. Then I changed the > file tree and the new tree has ~280M small files with 100b-50kb size. > When using 60 cp jobs the machine died. I could ping it but nothing > more. No ssh, no console, no shutdown. I try some more tests tonight. > I > try the same with ext2 as well to make sure it's XFS and not Softraid. > > -Simon > > From owner-linux-xfs@oss.sgi.com Mon Sep 10 18:31:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B1VTR01898 for linux-xfs-outgoing; Mon, 10 Sep 2001 18:31:29 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B1VPd01872 for ; Mon, 10 Sep 2001 18:31:25 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8B1VKJ03578 for ; Mon, 10 Sep 2001 18:31:20 -0700 Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id SAA61495 for ; Mon, 10 Sep 2001 18:36:35 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 416A915A213 for ; Mon, 10 Sep 2001 18:30:04 -0700 (PDT) Subject: 1.0.1 doesn't work with SGI1100 From: Florin Andrei To: linux-xfs Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 10 Sep 2001 18:30:04 -0700 Message-Id: <1000171804.24471.129.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Guys, Looks like XFS-1.0.1 (the installer from the CD-ROM image) doesn't work with SGI 1100 systems (1x or 2xPIII/800, 1x or 2x18GB IDE). I saw the problem on systems with either one or two IDE drives. It doesn't matter if i install from the CD-ROM or through the network, the result is the same. The installer boots just fine, it does all kind of things, the partitioning is fine, but then, when it tries to mount the newly created filesystems, its solid frozen; nothing works. If i switch to ALT-F4 before it's frozen, i see this: [...] <4>Start mounting filesystem: ide0(3,6) <4>Ending clean XFS mount for filesystem: ide0(3,6) <4>Start mounting filesystem: ide0(3,65) <4>hdb: timeout waiting for DMA <4>ide_dmaproc: chipset supported ide_dma_timeout func only: 14 After the last message, it's dead. :-/ I tried different kernel parameters, like "apic", but nothing helps. It looks like the problem occurs no matter how i partition the disk, as long as i have a large partition. I can reproduce the problem any time you want. I never managed to install XFS-1.0.1 on a SGI 1100 system. The problem doesn't seem to occur with XFS-1.0 Is there any solution for this? (installing 1.0 and upgrading to 1.0.1 is not an option, since i have to create an automatic procedure to install 1.0.1 very fast on many SGI1100s - a kickstart disk - and "install and upgrade" kind of defeats the very idea of kickstart) -- Florin Andrei "Our kernel does have source control: its name is Linus Torvalds, CVS with a brain." - Nicholas Knight From owner-linux-xfs@oss.sgi.com Mon Sep 10 18:34:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B1YPk02040 for linux-xfs-outgoing; Mon, 10 Sep 2001 18:34:25 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B1Y3d02018; Mon, 10 Sep 2001 18:34:04 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8B1Y4d02019 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 18:55:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B1tCC02658 for linux-xfs-outgoing; Mon, 10 Sep 2001 18:55:12 -0700 Received: from mail.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B1tAd02639 for ; Mon, 10 Sep 2001 18:55:10 -0700 Message-Id: <200109110155.f8B1tAd02639@oss.sgi.com> Received: (qmail 2367 invoked from network); 11 Sep 2001 01:55:10 -0000 Received: from unknown (HELO there) ([216.254.50.68]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 11 Sep 2001 01:55:10 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Steven Farrier To: linux-xfs@oss.sgi.com Subject: Shrinking XFS partitions Date: Mon, 10 Sep 2001 18:53:52 -0700 X-Mailer: KMail [version 1.3.1] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I know it is possible to make XFS partitions bigger, but will it ever be possible to shrink them? Steve From owner-linux-xfs@oss.sgi.com Mon Sep 10 18:55:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B1tdp02787 for linux-xfs-outgoing; Mon, 10 Sep 2001 18:55:39 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B1tbd02768 for ; Mon, 10 Sep 2001 18:55:37 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8B1tWJ06419 for ; Mon, 10 Sep 2001 18:55:32 -0700 Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by nodin.corp.sgi.com (8.11.4/8.11.2/nodin-1.0) with ESMTP id f8B1sV540906650; Mon, 10 Sep 2001 18:54:31 -0700 (PDT) Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id F13FB300095; Tue, 11 Sep 2001 11:53:40 +1000 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id BBF41AB; Tue, 11 Sep 2001 11:53:40 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Florin Andrei Cc: linux-xfs Subject: Re: 1.0.1 doesn't work with SGI1100 In-reply-to: Your message of "10 Sep 2001 18:30:04 MST." <1000171804.24471.129.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Sep 2001 11:53:35 +1000 Message-ID: <27500.1000173215@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10 Sep 2001 18:30:04 -0700, Florin Andrei wrote: >Looks like XFS-1.0.1 (the installer from the CD-ROM image) doesn't work >with SGI 1100 systems (1x or 2xPIII/800, 1x or 2x18GB IDE). ><4>Start mounting filesystem: ide0(3,6) ><4>Ending clean XFS mount for filesystem: ide0(3,6) ><4>Start mounting filesystem: ide0(3,65) ><4>hdb: timeout waiting for DMA ><4>ide_dmaproc: chipset supported ide_dma_timeout func only: 14 Does booting with "ide=nodma" help? From owner-linux-xfs@oss.sgi.com Mon Sep 10 18:56:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B1ue002962 for linux-xfs-outgoing; Mon, 10 Sep 2001 18:56:40 -0700 Received: from main.braxis.co.uk (root@main.braxis.co.uk [213.77.40.29]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B1uQd02926 for ; Mon, 10 Sep 2001 18:56:26 -0700 Received: (from kszysiu@localhost) by main.braxis.co.uk (8.11.6/8.11.6) id f8B1uRN02123 for linux-xfs@oss.sgi.com; Tue, 11 Sep 2001 03:56:27 +0200 Date: Tue, 11 Sep 2001 03:56:27 +0200 From: Krzysztof Rusocki To: linux-xfs@oss.sgi.com Subject: linux-2.4.10-pre7-xfs-2001-09-10.patch.bz2 cuts a large number of mips files Message-ID: <20010911035627.A1921@main.braxis.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everybody, I've just noticed that -rw-r--r-- 1 10190 10010 949171 Sep 10 09:08 linux-2.4.10-pre7-xfs-2001-09-10.patch.bz2 obtained by ftp from oss.sgi.com/projects/xfs/download/patches/ erases _a_lot_ of mips related files CVS tree has all of them... so apparently patch-maker had incomplete tree :/ Who's looking after patches/ subdir on oss.sgi.com ? just wondering.... Cheers, Krzysztof From owner-linux-xfs@oss.sgi.com Mon Sep 10 19:07:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B27ve03515 for linux-xfs-outgoing; Mon, 10 Sep 2001 19:07:57 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B27sd03496 for ; Mon, 10 Sep 2001 19:07:54 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8B27nJ06623 for ; Mon, 10 Sep 2001 19:07:49 -0700 Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id TAA82974 for ; Mon, 10 Sep 2001 19:13:04 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 4DD3515A213 for ; Mon, 10 Sep 2001 19:06:32 -0700 (PDT) Subject: Re: 1.0.1 doesn't work with SGI1100 From: Florin Andrei To: linux-xfs In-Reply-To: <27500.1000173215@kao2.melbourne.sgi.com> References: <27500.1000173215@kao2.melbourne.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 10 Sep 2001 19:06:32 -0700 Message-Id: <1000173992.24442.141.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 11 Sep 2001 11:53:35 +1000, Keith Owens wrote: > On 10 Sep 2001 18:30:04 -0700, > Florin Andrei wrote: > >Looks like XFS-1.0.1 (the installer from the CD-ROM image) doesn't work > >with SGI 1100 systems (1x or 2xPIII/800, 1x or 2x18GB IDE). > ><4>Start mounting filesystem: ide0(3,6) > ><4>Ending clean XFS mount for filesystem: ide0(3,6) > ><4>Start mounting filesystem: ide0(3,65) > ><4>hdb: timeout waiting for DMA > ><4>ide_dmaproc: chipset supported ide_dma_timeout func only: 14 > > Does booting with "ide=nodma" help? Ah, right. That solves the problem. Thanks a lot. But why it doesn't work without it anyway? -- Florin Andrei "Our kernel does have source control: its name is Linus Torvalds, CVS with a brain." - Nicholas Knight From owner-linux-xfs@oss.sgi.com Mon Sep 10 19:25:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B2PfE03865 for linux-xfs-outgoing; Mon, 10 Sep 2001 19:25:41 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B2Pbd03846 for ; Mon, 10 Sep 2001 19:25:37 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA05749 for ; Mon, 10 Sep 2001 19:24:07 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id TAA04091 for ; Mon, 10 Sep 2001 19:30:46 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 876A415A213 for ; Mon, 10 Sep 2001 19:24:15 -0700 (PDT) Subject: Re: 1.0.1 doesn't work with SGI1100 From: Florin Andrei To: linux-xfs In-Reply-To: <1000173992.24442.141.camel@stantz.corp.sgi.com> References: <27500.1000173215@kao2.melbourne.sgi.com> <1000173992.24442.141.camel@stantz.corp.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 10 Sep 2001 19:24:15 -0700 Message-Id: <1000175055.23809.155.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10 Sep 2001 19:06:32 -0700, Florin Andrei wrote: > On 11 Sep 2001 11:53:35 +1000, Keith Owens wrote: > > > > Does booting with "ide=nodma" help? > > Ah, right. That solves the problem. Thanks a lot. A quick follow-up: ide=nodma solves the problem for the installer. But, after the install, when the system comes up for the first time, it's the same problem: it's frozen when it tries to mount large partitions. I can add to the kickstart file, to the lilo option, the "--append ide=nodma" string, and it appears to solve the problem. But, still, if i want a high performance from that system (and believe me, i do want that, since it's gonna be a busy mail gateway), not using DMA will hurt performance. Somehow, i believe this problem is specific to the kernel version from 1.0.1, since 1.0 doesn't exhibit the same problem. I'm not sure of that, but i believe the vanilla Red Hat 7.1 doesn't show this problem. So, maybe a kernel upgrade will make it dissapear? I'll try and see what i can do. -- Florin Andrei "Our kernel does have source control: its name is Linus Torvalds, CVS with a brain." - Nicholas Knight From owner-linux-xfs@oss.sgi.com Mon Sep 10 19:35:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B2Zv604106 for linux-xfs-outgoing; Mon, 10 Sep 2001 19:35:57 -0700 Received: from hotmail.com (f113.law7.hotmail.com [216.33.237.113]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B2Ztd04086 for ; Mon, 10 Sep 2001 19:35:55 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 10 Sep 2001 19:35:48 -0700 Received: from 211.99.247.66 by lw7fd.law7.hotmail.msn.com with HTTP; Tue, 11 Sep 2001 02:35:47 GMT X-Originating-IP: [211.99.247.66] From: "Harrison Xing" To: linux-xfs@oss.sgi.com Subject: Memory leak in XFS 1.0.1 ? Just mount and umount Date: Tue, 11 Sep 2001 10:35:47 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 11 Sep 2001 02:35:48.0204 (UTC) FILETIME=[77173AC0:01C13A6A] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, When I mount and umount XFS heavily it seems that there are memory leaks. After about a day, the machine becomes quite slow and there is little free memory left, the buffers and cached memory are almost exhausted. for((i=1;i<10,000,000;i++));do mount -t xfs /dev/hda6 /mnt/xfs umount /mnt/xfs done I use the 2.4.5 kernel with XFS 1.0.1 release. _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp From owner-linux-xfs@oss.sgi.com Mon Sep 10 19:43:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B2h4304284 for linux-xfs-outgoing; Mon, 10 Sep 2001 19:43:04 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B2h2d04265 for ; Mon, 10 Sep 2001 19:43:02 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8B2guJ07292 for ; Mon, 10 Sep 2001 19:42:56 -0700 Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by nodin.corp.sgi.com (8.11.4/8.11.2/nodin-1.0) with ESMTP id f8B2ft541409492; Mon, 10 Sep 2001 19:41:55 -0700 (PDT) Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id 30465300095; Tue, 11 Sep 2001 12:41:05 +1000 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id DA40DAB; Tue, 11 Sep 2001 12:41:05 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Florin Andrei Cc: linux-xfs Subject: Re: 1.0.1 doesn't work with SGI1100 In-reply-to: Your message of "10 Sep 2001 19:24:15 MST." <1000175055.23809.155.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Sep 2001 12:41:00 +1000 Message-ID: <27772.1000176060@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10 Sep 2001 19:24:15 -0700, Florin Andrei wrote: >ide=nodma solves the problem for the installer. But, after the install, >when the system comes up for the first time, it's the same problem: it's >frozen when it tries to mount large partitions. >I can add to the kickstart file, to the lilo option, the "--append >ide=nodma" string, and it appears to solve the problem. But, still, if i >want a high performance from that system (and believe me, i do want >that, since it's gonna be a busy mail gateway), not using DMA will hurt >performance. It is likely to be a chipset problem rather than XFS. RH 7.1 was probably compiled without CONFIG_IDEDMA_PCI_AUTO. From owner-linux-xfs@oss.sgi.com Mon Sep 10 20:04:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B34Ha04636 for linux-xfs-outgoing; Mon, 10 Sep 2001 20:04:17 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B33ud04615; Mon, 10 Sep 2001 20:03:56 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8B33vd04616 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 20:22:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B3MOv04940 for linux-xfs-outgoing; Mon, 10 Sep 2001 20:22:24 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B3M9d04918 for ; Mon, 10 Sep 2001 20:22:09 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id UAA00862 for ; Mon, 10 Sep 2001 20:21:50 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id NAA19611; Tue, 11 Sep 2001 13:21:24 +1000 Date: Tue, 11 Sep 2001 13:21:24 +1000 From: Keith Owens Message-Id: <200109110321.NAA19611@sherman.melbourne.sgi.com> Subject: TAKE - Upgrade to 2.4.10-pre8 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Upgrade to 2.4.10-pre8. Linus has reverted the min/max changes, the functions take two parameters again. However the kernel min/max definitions now warn if the types are different. This take changes MIN/MAX in xfs_linux.h to use the kernel min/max and it highlighted some problems. xfs_ag.h is messy, the macro definitions use the variable types which are typically uint or uint8, returning uint but the equivalent functions are defined with int parameters, returning int. The following warnings need to be fixed by somebody who knows the code better than I. xfs_alloc.c: In function `xfs_alloc_fix_freelist': xfs_alloc.c:1810: warning: comparison of distinct pointer types lacks a cast xfs_alloc.c:1810: warning: comparison of distinct pointer types lacks a cast xfs_bmap.c: In function `xfs_bmap_alloc': xfs_bmap.c:2529: warning: comparison of distinct pointer types lacks a cast xfs_bmap.c:2529: warning: comparison of distinct pointer types lacks a cast xfs_bmap.c: In function `xfs_getbmap': xfs_bmap.c:5600: warning: comparison of distinct pointer types lacks a cast xfs_bmap.c:5715: warning: comparison of distinct pointer types lacks a cast xfs_dir2_leaf.c: In function `xfs_dir2_leaf_getdents': xfs_dir2_leaf.c:841: warning: comparison of distinct pointer types lacks a cast xfs_dir2_leaf.c:994: warning: comparison of distinct pointer types lacks a cast xfs_log_recover.c: In function `xlog_recover_do_buffer_trans': xfs_log_recover.c:1937: warning: comparison of distinct pointer types lacks a cast xfs_mount.c: In function `xfs_mount_common': xfs_mount.c:467: warning: comparison of distinct pointer types lacks a cast xfs_trans.c: In function `xfs_trans_init': xfs_trans.c:74: warning: comparison of distinct pointer types lacks a cast xfs_vnodeops.c: In function `xfs_set_uiosize': xfs_vnodeops.c:4941: warning: comparison of distinct pointer types lacks a cast xfs_vnodeops.c:4952: warning: comparison of distinct pointer types lacks a cast xfs_vnodeops.c:4958: warning: comparison of distinct pointer types lacks a cast xfs_vnodeops.c: In function `xfs_free_file_space': xfs_vnodeops.c:5596: warning: comparison of distinct pointer types lacks a cast Date: Mon Sep 10 20:12:20 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102561a linux/net/x25/af_x25.c - 1.22 linux/net/wanrouter/wanproc.c - 1.18 linux/net/unix/af_unix.c - 1.34 linux/net/sunrpc/xprt.c - 1.18 linux/net/sched/sch_tbf.c - 1.9 linux/net/rose/af_rose.c - 1.20 linux/net/netrom/af_netrom.c - 1.20 linux/net/irda/af_irda.c - 1.24 linux/net/ipx/af_ipx.c - 1.22 linux/net/ipv6/route.c - 1.19 linux/net/ipv6/raw.c - 1.20 linux/net/ipv6/ndisc.c - 1.15 linux/net/ipv6/ipv6_sockglue.c - 1.12 linux/net/ipv6/icmp.c - 1.15 linux/net/ipv4/tcp_timer.c - 1.20 linux/net/ipv4/tcp_output.c - 1.21 linux/net/ipv4/tcp_input.c - 1.28 linux/net/ipv4/tcp.c - 1.30 linux/net/ipv4/route.c - 1.25 linux/net/ipv4/ipmr.c - 1.18 linux/net/ipv4/ip_sockglue.c - 1.15 linux/net/core/iovec.c - 1.9 linux/net/ax25/af_ax25.c - 1.21 linux/net/appletalk/ddp.c - 1.19 linux/mm/slab.c - 1.26 linux/mm/memory.c - 1.58 linux/kernel/ksyms.c - 1.106 linux/kernel/fork.c - 1.35 linux/kernel/exit.c - 1.30 linux/kernel/exec_domain.c - 1.12 linux/kernel/Makefile - 1.24 linux/include/net/tcp.h - 1.24 linux/include/net/sock.h - 1.24 linux/include/linux/sysctl.h - 1.35 linux/include/linux/swap.h - 1.37 linux/include/linux/sched.h - 1.43 linux/include/linux/personality.h - 1.9 linux/include/linux/mm.h - 1.61 linux/include/linux/kernel.h - 1.24 linux/include/linux/fs.h - 1.116 linux/include/asm-i386/uaccess.h - 1.12 linux/include/asm-i386/spinlock.h - 1.20 linux/include/asm-i386/processor.h - 1.26 linux/include/asm-i386/io.h - 1.17 linux/fs/umsdos/inode.c - 1.18 linux/fs/ufs/util.h - 1.6 linux/fs/ufs/util.c - 1.7 linux/fs/ufs/truncate.c - 1.10 linux/fs/ufs/balloc.c - 1.7 linux/fs/sysv/inode.c - 1.24 linux/fs/smbfs/inode.c - 1.23 linux/fs/select.c - 1.18 linux/fs/romfs/inode.c - 1.24 linux/fs/ncpfs/ncpsign_kernel.c - 1.4 linux/fs/ncpfs/ncplib_kernel.c - 1.10 linux/fs/ncpfs/mmap.c - 1.15 linux/fs/ncpfs/ioctl.c - 1.15 linux/fs/ncpfs/inode.c - 1.21 linux/fs/ncpfs/file.c - 1.17 linux/fs/namei.c - 1.36 linux/fs/isofs/rock.c - 1.14 linux/fs/hfs/inode.c - 1.13 linux/fs/hfs/file_cap.c - 1.10 linux/fs/coda/upcall.c - 1.13 linux/fs/buffer.c - 1.81 linux/fs/attr.c - 1.10 linux/fs/adfs/inode.c - 1.17 linux/drivers/usb/uhci.c - 1.47 linux/drivers/scsi/sym53c8xx.h - 1.7 linux/drivers/scsi/sr_ioctl.c - 1.18 linux/drivers/scsi/sd.c - 1.44 linux/drivers/scsi/eata_pio.c - 1.13 linux/drivers/net/hamradio/baycom_epp.c - 1.17 linux/drivers/net/dgrs.c - 1.19 linux/drivers/net/de600.c - 1.15 linux/drivers/net/acenic.c - 1.30 linux/drivers/char/dsp56k.c - 1.17 linux/drivers/char/cyclades.c - 1.19 linux/drivers/block/xd.c - 1.22 linux/drivers/block/rd.c - 1.33 linux/drivers/block/ps2esdi.c - 1.21 linux/drivers/block/paride/pf.c - 1.13 linux/drivers/block/paride/pd.c - 1.17 linux/drivers/block/nbd.c - 1.21 linux/drivers/block/loop.c - 1.35 linux/drivers/block/floppy.c - 1.27 linux/drivers/block/amiflop.c - 1.15 linux/drivers/block/acsi.c - 1.16 linux/drivers/acorn/scsi/acornscsi.c - 1.9 linux/drivers/acorn/block/mfmhd.c - 1.13 linux/arch/sparc64/solaris/timod.c - 1.14 linux/arch/sparc64/solaris/misc.c - 1.19 linux/arch/i386/lib/Makefile - 1.16 linux/arch/i386/kernel/signal.c - 1.18 linux/arch/i386/kernel/i386_ksyms.c - 1.40 linux/arch/arm/kernel/traps.c - 1.21 linux/Makefile - 1.121 linux/Documentation/sysctl/vm.txt - 1.6 linux/fs/hpfs/inode.c - 1.14 linux/drivers/i2o/i2o_block.c - 1.29 linux/drivers/block/blkpg.c - 1.11 linux/arch/arm/kernel/arthur.c - 1.8 linux/drivers/char/ppdev.c - 1.24 linux/drivers/block/cpqarray.c - 1.27 linux/net/khttpd/waitheaders.c - 1.6 linux/net/khttpd/rfc.c - 1.6 linux/net/khttpd/datasending.c - 1.9 linux/drivers/block/DAC960.c - 1.36 linux/drivers/net/wan/cycx_main.c - 1.12 linux/drivers/net/wan/sdla_x25.c - 1.11 linux/drivers/net/wan/sdla_ppp.c - 1.14 linux/drivers/net/wan/sdla_fr.c - 1.15 linux/drivers/net/wan/sbni.c - 1.15 linux/drivers/net/wan/cycx_x25.c - 1.14 linux/drivers/char/agp/agpgart_be.c - 1.22 linux/drivers/sbus/char/jsflash.c - 1.9 linux/drivers/usb/devio.c - 1.18 linux/drivers/net/wan/sdla_chdlc.c - 1.13 linux/drivers/usb/usb-uhci.c - 1.27 linux/drivers/usb/usb-ohci.c - 1.26 linux/include/linux/ac97_codec.h - 1.11 linux/drivers/ide/ide.c - 1.29 linux/drivers/ide/hd.c - 1.12 linux/drivers/net/wan/comx.c - 1.12 linux/drivers/net/wan/comx-proto-lapb.c - 1.7 linux/drivers/net/wan/comx-proto-fr.c - 1.7 linux/drivers/net/wan/comx-hw-mixcom.c - 1.7 linux/drivers/net/wan/comx-hw-locomx.c - 1.5 linux/drivers/net/wan/comx-hw-comx.c - 1.6 linux/net/ipv4/netfilter/ipfwadm_core.c - 1.7 linux/net/ipv4/netfilter/ipchains_core.c - 1.6 linux/drivers/sound/dmasound/dmasound_q40.c - 1.5 linux/drivers/sound/dmasound/dmasound_paula.c - 1.5 linux/drivers/sound/dmasound/dmasound_awacs.c - 1.8 linux/drivers/sound/dmasound/dmasound_atari.c - 1.6 linux/drivers/usb/serial/usbserial.c - 1.20 linux/drivers/usb/serial/visor.c - 1.21 linux/drivers/sound/emu10k1/cardwo.c - 1.6 linux/drivers/sound/emu10k1/cardwi.c - 1.5 linux/drivers/sound/emu10k1/audio.c - 1.12 linux/drivers/usb/serial/digi_acceleport.c - 1.15 linux/drivers/char/rio/riointr.c - 1.5 linux/drivers/s390/net/iucv.c - 1.6 linux/drivers/s390/block/dasd.c - 1.12 linux/fs/xfs/xfs_dir2_trace.c - 1.10 linux/fs/xfs/linux/xfs_lrw.c - 1.108 linux/fs/xfs/linux/xfs_linux.h - 1.54 linux/fs/pagebuf/page_buf_io.c - 1.96 linux/drivers/usb/bluetooth.c - 1.15 linux/fs/jffs/inode-v23.c - 1.11 linux/fs/jffs/intrep.c - 1.7 linux/drivers/mtd/ftl.c - 1.7 linux/drivers/mtd/mtdblock.c - 1.6 linux/net/ipv4/tcp_minisocks.c - 1.8 linux/drivers/md/lvm.c - 1.19 linux/drivers/block/cciss.c - 1.14 linux/drivers/md/lvm-snap.c - 1.6 linux/drivers/md/md.c - 1.22 linux/drivers/usb/serial/empeg.c - 1.11 linux/drivers/s390/net/netiucv.c - 1.6 linux/drivers/s390/block/xpram.c - 1.5 linux/fs/xfs_support/qsort.c - 1.3 linux/drivers/usb/serial/io_usbvend.h - 1.3 linux/drivers/usb/serial/io_edgeport.c - 1.8 linux/drivers/net/wan/wanpipe_multppp.c - 1.6 linux/arch/cris/drivers/usb-host.c - 1.6 linux/drivers/mtd/nftlcore.c - 1.4 linux/drivers/mtd/mtdblock_ro.c - 1.2 linux/drivers/mtd/devices/docecc.c - 1.3 linux/drivers/net/wireless/airo.c - 1.5 linux/drivers/net/sk98lin/skproc.c - 1.7 linux/drivers/usb/storage/jumpshot.c - 1.3 linux/drivers/usb/storage/datafab.c - 1.3 From owner-linux-xfs@oss.sgi.com Mon Sep 10 21:27:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B4RSu06267 for linux-xfs-outgoing; Mon, 10 Sep 2001 21:27:28 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B4RFd06244; Mon, 10 Sep 2001 21:27:16 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8B4RGd06249 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 22:46:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B5kRs07681 for linux-xfs-outgoing; Mon, 10 Sep 2001 22:46:27 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B5kEd07657 for ; Mon, 10 Sep 2001 22:46:14 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id HAA08696; Tue, 11 Sep 2001 07:45:47 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id HAA18259; Tue, 11 Sep 2001 07:44:21 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id EF65757306; Tue, 11 Sep 2001 07:43:47 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id E3E7B25835; Tue, 11 Sep 2001 07:43:47 +0200 (CEST) Message-ID: <3B9DA493.11CD4C16@ch.sauter-bc.com> Date: Tue, 11 Sep 2001 07:43:47 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Adrian Head , linux-xfs@oss.sgi.com Subject: Re: Problems with many processes copying large directories acrossan XFS volume. References: <3B9CCE00.D704DC0B@ch.sauter-bc.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter schrieb: > > Adrian Head schrieb: > > > > Thanks for your reply Simon > > > > Yes the softraid was fully synced before I started any test. > > > > The XFS patch I used to obtain these errors was > > patch-2.4.9-xfs-2001-08-19 and the errors were: > > Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 > > Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device > > > > When I used a later version of the XFS patch I had more descriptive > > errors written to /var/log/messages: > > Sep 10 10:14:57 ATLAS kernel: I/O error in filesystem ("md(9,0)") > > meta-data dev 0x900 block 0x9802bdc > > Sep 10 10:14:57 ATLAS kernel: (xlog_iodone") error 5 buf count 32768 > > Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called > > from line 940 of file xfs_log.c. Return address - 0xd8cb66f8 > > Sep 10 10:14:57 ATLAS kernel: Log I/O Error Detected. Shutting down > > filesystem: md(9,0) > > Sep 10 10:14:57 ATLAS kernel: Please umount the filesystem, and rectify > > the problem(s) > > Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called > > from line 714 of file xfs_log.c. Return address = 0xd8cb65d3 > > Sep 10 10:14:57 ATLAS kernel: attempt to access beyond end of device > > Sep 10 10:14:57 ATLAS kernel: 02:82: rw=0, want=1602235696, limit=4 > > > > I did think at the time that it may have been issues with XFS stomping > > all over raid code or raid code stomping all over XFS. Although I not > > sure now as the 2.4.10-pre2-xfs-2001-09-02 patch never wrote any errors > > out at all. (please see my 2nd post for more info) > > > > Thanks for taking the time to test this on your own machine. > > I tried 20, 40 and 80 simultanous cp with no crash. Then I changed the > file tree and the new tree has ~280M small files with 100b-50kb size. > When using 60 cp jobs the machine died. I could ping it but nothing > more. No ssh, no console, no shutdown. I try some more tests tonight. I > try the same with ext2 as well to make sure it's XFS and not Softraid. Update: I tried the 60 cp jobs on a ext2 filesystem and the system is still alive but 58 of the 60 cp jobs are hanging. Well maybe the 2.4.3 kernel is a bit old now... I'll try some more tests. Simon > > -Simon > > > > > Adrian Head > > Bytecomm P/L > > > > > -----Original Message----- > > > From: Simon Matter [SMTP:simon.matter@ch.sauter-bc.com] > > > Sent: Monday, 10 September 2001 17:45 > > > To: adrian.head@bytecomm.com.au > > > Cc: linux-xfs@oss.sgi.com > > > Subject: Re: Problems with many processes copying large > > > directories across an XFS volume. > > > > > > Hi Adrian > > > > > > I did similar tests two months ago. I was having problems as well but > > > ufurtunately I don't remember what is was exactly. > > > First question: You created Softraid5, was the raid synced when you > > > started the tests? > > > > > > > In the /var/log/messages log around the same time as the copy test I > > > get > > > > entries like: > > > > Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 > > > > Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device > > > > > > This looks interesting. I don't know what this means exactly but it > > > looks to me like you managed to create a filesystem bigger than the > > > raid > > > volume was? I got the very same error when I tried to restore data > > > with > > > xfsrestore from DAT (xfsrestore from DLT was fine). The issue is still > > > open. > > > > > > I have a test system here with SoftRAID5 on 4 U160 SCSI disks. I'll > > > try > > > to kill it today with cp jobs. > > > > > > -Simon > > > From owner-linux-xfs@oss.sgi.com Mon Sep 10 22:50:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B5oh107882 for linux-xfs-outgoing; Mon, 10 Sep 2001 22:50:43 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B5oad07840; Mon, 10 Sep 2001 22:50:36 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8B5obd07841 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Mon Sep 10 22:50:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B5olb07936 for linux-xfs-outgoing; Mon, 10 Sep 2001 22:50:47 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B5ofd07846 for ; Mon, 10 Sep 2001 22:50:41 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id WAA28665 for ; Mon, 10 Sep 2001 22:50:44 -0700 (PDT) mail_from (ivanr@melbourne.sgi.com) Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id QAA08766; Tue, 11 Sep 2001 16:49:20 +1100 From: ivanr@melbourne.sgi.com (Ivan Rayner) Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id PAA24814; Tue, 11 Sep 2001 15:49:19 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Tue, 11 Sep 2001 15:49:18 +1000 To: Russel Ingram cc: Subject: Re: xfsdump error question In-Reply-To: <20010910114627.A1640@roujin.gargoylecc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 10 Sep 2001, Russel Ingram wrote: > xfsdump: calling bulkstat > xfsdump: bulkstat returns buflen 4096 ino 5282011 > xfsdump: ino 5768703 needed second bulkstat > xfsdump: ERROR: map_add(5243008, 3): ino(5243008) <= last_ino(5768702) ... > Can someone tell me what this error means and if its something I'm > doing wrong or if its a problem with my filesystem or xfsdump? > I've also attached the output from running the same command with -v5. When xfsdump does a bulkstat to get the stat information for a whole bunch of files, it can sometimes detect inconsistencies which usually means the inode is or has just been modified. xfsdump will then call bulkstat_single to reget this information. In your case, xfsdump tried to reget the stat information for inode 5768703 but it got back information for inode 5243008. This is a problem. Looking at the code, the bulkstat_single probably would have returned an errno, but xfsdump doesn't check the return value for the ioctl, and it continues to process the stat info, but dies when it realises that it shouldn't have an ino which is out of sequence. So, the question is, is there a problem with your filesystem? Can you do a: # find / -inum 5243008 -o -inum 5768703 to see which files these inode numbers represent? In the xfstests package, there is a program called bstat. It will go through a filesystem comparing what it gets from bulkstat with regular stat information. You should redirect it's output to a file ... there will be alot of it: # bstat -C -l 5243000 > bstat.log When it's done, take a look at the bstat.log to see if there are any inconsistencies with inodes 5243008 and 5768703. It might also be interesting to see the inode information from xfs_db: # xfs_db -r /dev/ xfs_db: inode 5243008 xfs_db: p xfs_db: inode 5768703 xfs_db: p And I suppose you could remount your root filesystem readonly and run xfs_repair and see what it produces. Ivan -- Ivan Rayner ivanr@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 10 23:13:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B6Dnf08612 for linux-xfs-outgoing; Mon, 10 Sep 2001 23:13:49 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B6Dcd08592 for ; Mon, 10 Sep 2001 23:13:38 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA13985; Tue, 11 Sep 2001 08:13:02 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA21193; Tue, 11 Sep 2001 08:12:56 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id D557857306; Tue, 11 Sep 2001 08:11:23 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id C605325835; Tue, 11 Sep 2001 08:11:23 +0200 (CEST) Message-ID: <3B9DAB0B.57915665@ch.sauter-bc.com> Date: Tue, 11 Sep 2001 08:11:23 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Adrian Head Cc: linux-xfs@oss.sgi.com Subject: Re: Problems with many processes copying large directories acrossan XFS volume. References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Adrian Head schrieb: > > Again - thanks Simon for your time. > > I have done ten's of tests now and I am getting a strong feeling that it > is the same problems described here from Steve Lord: > http://marc.theaimsgroup.com/?l=linux-xfs&m=99980808004670&w=2 > > Or the start of the thread: > http://marc.theaimsgroup.com/?l=linux-xfs&m=99919025308712&w=2 > > The reason I am almost convinced it is the same issue is that about > every 3 attempts I have only bdflush running and everything else in > deadlock. - I will have to follow the instructions and see what output I > get from kdb. So do I. > > It appears that although they could only get it to crash with SCSI the > problem affects both SCSI & IDE. > > I was going to short-cut the process and just download the cvs tree - > but for some reason the XFS site times-out at the moment. I will try > later. > > When your machine hangs - have you noticed any trends in what processes > are left running? Unfortunately it disabled kdb and was not able to get a process list. I'm still trying more tests and I will also try a current kernel if time permits. Simon > > Adrian Head P/L > > > -----Original Message----- > > From: Simon Matter [SMTP:simon.matter@ch.sauter-bc.com] > > Sent: Tuesday, 11 September 2001 00:28 > > To: Adrian Head > > Cc: linux-xfs@oss.sgi.com > > Subject: Re: Problems with many processes copying large > > directories acrossan XFS volume. > > > > > > I tried 20, 40 and 80 simultanous cp with no crash. Then I changed the > > file tree and the new tree has ~280M small files with 100b-50kb size. > > When using 60 cp jobs the machine died. I could ping it but nothing > > more. No ssh, no console, no shutdown. I try some more tests tonight. > > I > > try the same with ext2 as well to make sure it's XFS and not Softraid. > > > > -Simon > > > > From owner-linux-xfs@oss.sgi.com Tue Sep 11 00:20:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B7Kd410031 for linux-xfs-outgoing; Tue, 11 Sep 2001 00:20:39 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B7KYd10012; Tue, 11 Sep 2001 00:20:34 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8B7KZd10013 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 01:44:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8B8iYW11569 for linux-xfs-outgoing; Tue, 11 Sep 2001 01:44:34 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8B8hsd11543; Tue, 11 Sep 2001 01:43:54 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8B8hsd11544 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 03:07:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BA7JM13170 for linux-xfs-outgoing; Tue, 11 Sep 2001 03:07:19 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BA7Dd13151; Tue, 11 Sep 2001 03:07:14 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BA7Ed13152 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 04:26:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BBQ6714520 for linux-xfs-outgoing; Tue, 11 Sep 2001 04:26:06 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BBQ1d14501; Tue, 11 Sep 2001 04:26:01 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BBQ2d14502 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 05:04:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BC4u815171 for linux-xfs-outgoing; Tue, 11 Sep 2001 05:04:56 -0700 Received: from hammail1.truenorth.com (h-213.61.138.102.host.de.colt.net [213.61.138.102]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BC4qd15152 for ; Tue, 11 Sep 2001 05:04:52 -0700 Received: from fcb-wilkens.com ([170.200.66.15]) by hammail1.truenorth.com (Netscape Messaging Server 4.15) with ESMTP id GJHYVW00.S95; Tue, 11 Sep 2001 14:04:44 +0200 Message-ID: <3B9DFDDC.C0480DA3@fcb-wilkens.com> Date: Tue, 11 Sep 2001 14:04:44 +0200 From: Harald Wagener Organization: FCB Wilkens X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: stimits@idcomm.com CC: "XFS: linux-xfs@oss.sgi.com" Subject: Re: ".", "..", and cd References: <3B99B55E.CF8F4F16@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" wrote: > > This is probably not an XFS question per se, but might be, I'm not sure. > I use XFS on the root system, and am working on some directory and file > scanning code. One of the banes of this is to scan for files or > directories beginning with ".", without always viewing the current > directory and its parent directory, "..". While doing some testing of > special cases, I discovered that if I look for files in the root > directory "/" (on XFS), through the "glob" function (which presumably is > used in code of some shells for its pattern matching), looking for files > of pattern ".*", then doing so in "/" results in both "/./" (I have the > flag set to append "/" to the end of directory values) and "/../". This > latter entry is a curiosity, seeing as the root partition does not have > a parent. If I cd to "/", and then do "cd ..", there is no error either, > I just end up where I started. If You want to omit this, try to match .??* . > Is this the standard, expected behavior (possibly POSIX or HFS > designated)? Or would different filesystems behave differently, where > some complain about "cd .." when already in the root? At this point it > is really nothing more than a curiosity, but it sticks out during > testing. It is the expected behavior. Regards, Harald -- Harald Wagener | Systemadministrator FCB/Wilkens GmbH | Tel.:+49-40-2881-1252 An der Alster 42 | Fax.:+49-40-2881-1263 20099 Hamburg | http://www.fcb-wilkens.com From owner-linux-xfs@oss.sgi.com Tue Sep 11 05:48:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BCmvo15851 for linux-xfs-outgoing; Tue, 11 Sep 2001 05:48:57 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BCmpd15832; Tue, 11 Sep 2001 05:48:52 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BCmqd15833 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 07:12:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BECKk17579 for linux-xfs-outgoing; Tue, 11 Sep 2001 07:12:20 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BEC9d17557; Tue, 11 Sep 2001 07:12:09 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BECAd17558 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 07:37:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BEb7817942 for linux-xfs-outgoing; Tue, 11 Sep 2001 07:37:07 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BEb5d17923 for ; Tue, 11 Sep 2001 07:37:05 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8BEax513190 for ; Tue, 11 Sep 2001 07:36:59 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2944298; Tue, 11 Sep 2001 09:35:44 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA60505; Tue, 11 Sep 2001 09:35:43 -0500 (CDT) Message-ID: <3B9E211B.43CC31B0@sgi.com> Date: Tue, 11 Sep 2001 09:35:07 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Steven Farrier CC: linux-xfs@oss.sgi.com Subject: Re: Shrinking XFS partitions References: <200109110155.f8B1tAd02639@oss.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steven Farrier wrote: > > I know it is possible to make XFS partitions bigger, but will it ever be > possible to shrink them? Short answer is no, for a longer answer, there is a thread in the archives somewhere. :) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Tue Sep 11 07:38:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BEcfq18074 for linux-xfs-outgoing; Tue, 11 Sep 2001 07:38:41 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BEcdd18055 for ; Tue, 11 Sep 2001 07:38:39 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8BEcY513398 for ; Tue, 11 Sep 2001 07:38:34 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2944594; Tue, 11 Sep 2001 09:37:18 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA55558; Tue, 11 Sep 2001 09:37:18 -0500 (CDT) Message-ID: <3B9E2179.B797CDED@sgi.com> Date: Tue, 11 Sep 2001 09:36:41 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Krzysztof Rusocki CC: linux-xfs@oss.sgi.com Subject: Re: linux-2.4.10-pre7-xfs-2001-09-10.patch.bz2 cuts a large number of mips files References: <20010911035627.A1921@main.braxis.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Krzysztof Rusocki wrote: > Who's looking after patches/ subdir on oss.sgi.com ? just wondering.... I am; I'll take a look. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Tue Sep 11 08:38:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BFcJm19113 for linux-xfs-outgoing; Tue, 11 Sep 2001 08:38:19 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BFbHd19057; Tue, 11 Sep 2001 08:37:17 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BFbId19065 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 09:25:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BGP1S19767 for linux-xfs-outgoing; Tue, 11 Sep 2001 09:25:01 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BGOsd19746 for ; Tue, 11 Sep 2001 09:24:54 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8BGOm523342 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 11 Sep 2001 09:24:48 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id SAA316765 for ; Tue, 11 Sep 2001 18:24:58 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2945380; Tue, 11 Sep 2001 11:23:30 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA45709; Tue, 11 Sep 2001 11:23:29 -0500 (CDT) Message-ID: <3B9E3A5B.8B011E71@sgi.com> Date: Tue, 11 Sep 2001 11:22:51 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Krzysztof Rusocki , linux-xfs@oss.sgi.com Subject: Re: linux-2.4.10-pre7-xfs-2001-09-10.patch.bz2 cuts a large number of mips files References: <20010911035627.A1921@main.braxis.co.uk> <3B9E2179.B797CDED@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > > Krzysztof Rusocki wrote: > > > Who's looking after patches/ subdir on oss.sgi.com ? just wondering.... Ok, the latest patch out there should be OK, I forgot the "-d" on the cvs update script, so new directories were getting lost. Sorry about that, and thanks for the heads up. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Tue Sep 11 09:29:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BGTud19906 for linux-xfs-outgoing; Tue, 11 Sep 2001 09:29:56 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BGTrd19887 for ; Tue, 11 Sep 2001 09:29:53 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f8BGTlw14600 for linux-xfs@oss.sgi.com; Tue, 11 Sep 2001 12:29:47 -0400 Date: Tue, 11 Sep 2001 12:29:47 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: big failure on a scsi driver Message-ID: <20010911122947.A14588@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Time: 2001-09-11 09:04:03 Command: rpm -ba --target i386,i686 kernel-2.4.spec Building target platforms: i386,i686 Building for target i386 [elided] + make -s -j 1 CC=kgcc modules [elided] cpqfcTSinit.c: In function `cpqfcTS_ioctl': cpqfcTSinit.c:662: `SCSI_IOCTL_FC_TARGET_ADDRESS' undeclared (first use in this function) cpqfcTSinit.c:662: (Each undeclared identifier is reported only once cpqfcTSinit.c:662: for each function it appears in.) cpqfcTSinit.c:680: `SCSI_IOCTL_FC_TDR' undeclared (first use in this function) make[2]: *** [cpqfcTSinit.o] Error 1 make[1]: *** [_modsubdir_scsi] Error 2 make: *** [_mod_drivers] Error 2 error: Bad exit status from /home/alane/rpm/tmp/rpm-tmp.52739 (%build) RPM build errors: Bad exit status from /home/alane/rpm/tmp/rpm-tmp.52739 (%build) 1 -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Tue Sep 11 10:00:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BH0hl20488 for linux-xfs-outgoing; Tue, 11 Sep 2001 10:00:43 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BH0ad20469; Tue, 11 Sep 2001 10:00:36 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BH0bd20470 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 10:34:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BHYBv21020 for linux-xfs-outgoing; Tue, 11 Sep 2001 10:34:11 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BHY7d21001 for ; Tue, 11 Sep 2001 10:34:07 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8BHY2528381 for ; Tue, 11 Sep 2001 10:34:02 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2944169; Tue, 11 Sep 2001 12:32:46 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA34158; Tue, 11 Sep 2001 12:32:46 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f8BHTTR03002; Tue, 11 Sep 2001 12:29:29 -0500 Message-Id: <200109111729.f8BHTTR03002@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Alan Eldridge cc: SGI XFS Dev List Subject: Re: big failure on a scsi driver In-Reply-To: Message from Alan Eldridge of "Tue, 11 Sep 2001 12:29:47 EDT." <20010911122947.A14588@wwweasel.geeksrus.net> Date: Tue, 11 Sep 2001 12:29:28 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Time: 2001-09-11 09:04:03 > Command: rpm -ba --target i386,i686 kernel-2.4.spec > Building target platforms: i386,i686 > Building for target i386 > [elided] > + make -s -j 1 CC=kgcc modules > [elided] > cpqfcTSinit.c: In function `cpqfcTS_ioctl': > cpqfcTSinit.c:662: `SCSI_IOCTL_FC_TARGET_ADDRESS' undeclared (first use in th > is function) > cpqfcTSinit.c:662: (Each undeclared identifier is reported only once > cpqfcTSinit.c:662: for each function it appears in.) > cpqfcTSinit.c:680: `SCSI_IOCTL_FC_TDR' undeclared (first use in this function > ) > make[2]: *** [cpqfcTSinit.o] Error 1 > make[1]: *** [_modsubdir_scsi] Error 2 > make: *** [_mod_drivers] Error 2 > error: Bad exit status from /home/alane/rpm/tmp/rpm-tmp.52739 (%build) > > > RPM build errors: > Bad exit status from /home/alane/rpm/tmp/rpm-tmp.52739 (%build) > 1 > First check your tree is fully upto date, then look on linux kernel for a thread about this driver not building. This particular module has not changed in about a month. Steve From owner-linux-xfs@oss.sgi.com Tue Sep 11 10:39:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BHdLJ21165 for linux-xfs-outgoing; Tue, 11 Sep 2001 10:39:21 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BHdJd21146 for ; Tue, 11 Sep 2001 10:39:19 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8BHdDJ30952 for ; Tue, 11 Sep 2001 10:39:13 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2944456; Tue, 11 Sep 2001 12:37:57 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA88687; Tue, 11 Sep 2001 12:37:57 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f8BHYeb03033; Tue, 11 Sep 2001 12:34:40 -0500 Message-Id: <200109111734.f8BHYeb03033@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Harrison Xing" cc: linux-xfs@oss.sgi.com Subject: Re: Memory leak in XFS 1.0.1 ? Just mount and umount In-Reply-To: Message from "Harrison Xing" of "Tue, 11 Sep 2001 10:35:47 +0800." Date: Tue, 11 Sep 2001 12:34:40 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi, > > When I mount and umount XFS heavily it seems that there are memory leaks. > After about a day, the machine becomes quite slow and there is little free > memory left, > the buffers and cached memory are almost exhausted. > > for((i=1;i<10,000,000;i++));do > mount -t xfs /dev/hda6 /mnt/xfs > umount /mnt/xfs > done > > I use the 2.4.5 kernel with XFS 1.0.1 release. There does appear to be a slow leak in the mount/unmount path, I have had the loop running for an hour or so now, and memory does appear to be going somewhere. This is with a tree from yesterday's cvs tree. Steve From owner-linux-xfs@oss.sgi.com Tue Sep 11 11:24:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BIO1h21772 for linux-xfs-outgoing; Tue, 11 Sep 2001 11:24:01 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BINud21752; Tue, 11 Sep 2001 11:23:56 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BINvd21753 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 11:48:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BIm3H22126 for linux-xfs-outgoing; Tue, 11 Sep 2001 11:48:03 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BIlId22099; Tue, 11 Sep 2001 11:47:18 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BIlJd22100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 12:27:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BJRZe22733 for linux-xfs-outgoing; Tue, 11 Sep 2001 12:27:35 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BJRXd22713 for ; Tue, 11 Sep 2001 12:27:33 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8BJRRJ03132 for ; Tue, 11 Sep 2001 12:27:27 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2946800 for ; Tue, 11 Sep 2001 14:26:11 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA81670 for ; Tue, 11 Sep 2001 14:26:10 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f8BJMrq03369; Tue, 11 Sep 2001 14:22:53 -0500 Message-Id: <200109111922.f8BJMrq03369@jen.americas.sgi.com> Date: Tue, 11 Sep 2001 14:22:53 -0500 Subject: TAKE - fix min max typing issues Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Clean up type issues with the new min and max macros in xfs. Date: Tue Sep 11 12:25:00 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102597a linux/fs/xfs/xfs_ag.h - 1.39 linux/fs/xfs/xfs_vnodeops.c - 1.511 linux/fs/xfs/xfs_log_recover.c - 1.211 linux/fs/xfs/xfs_mount.c - 1.261 linux/fs/xfs/xfs_dir2_leaf.c - 1.23 linux/fs/xfs/xfs_trans.h - 1.109 linux/fs/xfs/xfs_bmap.c - 1.271 linux/fs/pagebuf/page_buf_io.c - 1.97 From owner-linux-xfs@oss.sgi.com Tue Sep 11 12:42:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BJg8n23146 for linux-xfs-outgoing; Tue, 11 Sep 2001 12:42:08 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BJg4d23127 for ; Tue, 11 Sep 2001 12:42:04 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id MAA08584 for ; Tue, 11 Sep 2001 12:41:56 -0700 (PDT) mail_from (austin@coremetrics.com) Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id ; Tue, 11 Sep 2001 14:39:16 -0500 Message-ID: <85063BBE668FD411944400D0B744267A888576@AUSMAIL> From: "Gonyou, Austin" To: "'Steve Lord'" , Harrison Xing Cc: linux-xfs@oss.sgi.com Subject: RE: Memory leak in XFS 1.0.1 ? Just mount and umount Date: Tue, 11 Sep 2001 14:39:05 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Perhaps another way to do this is to have several bg processes happen and see if the concurrency makes it any order of magnitude worse? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Steve Lord [mailto:lord@sgi.com] > Sent: Tuesday, September 11, 2001 12:35 PM > To: Harrison Xing > Cc: linux-xfs@oss.sgi.com > Subject: Re: Memory leak in XFS 1.0.1 ? Just mount and umount > > > > Hi, > > > > When I mount and umount XFS heavily it seems that there are > memory leaks. > > After about a day, the machine becomes quite slow and there > is little free > > memory left, > > the buffers and cached memory are almost exhausted. > > > > for((i=1;i<10,000,000;i++));do > > mount -t xfs /dev/hda6 /mnt/xfs > > umount /mnt/xfs > > done > > > > I use the 2.4.5 kernel with XFS 1.0.1 release. > > There does appear to be a slow leak in the mount/unmount > path, I have had the > loop running for an hour or so now, and memory does appear to > be going > somewhere. This is with a tree from yesterday's cvs tree. > > Steve > > > From owner-linux-xfs@oss.sgi.com Tue Sep 11 12:59:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BJx2d23451 for linux-xfs-outgoing; Tue, 11 Sep 2001 12:59:02 -0700 Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BJx0d23432 for ; Tue, 11 Sep 2001 12:59:00 -0700 Received: from scare ([63.231.179.33]) by lips.thebarn.com (8.12.0/8.12.0) with ESMTP id f8BJx6Pp095763 for ; Tue, 11 Sep 2001 14:59:07 -0500 (CDT) Subject: Mandrake RPMs available for testing. From: Russell Cattelan To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 11 Sep 2001 14:52:04 -0500 Message-Id: <1000237926.13368.54.camel@scare> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have placed somewhat current Mandrake rpms on oss. ftp://oss.sgi.com/projects/xfs/download/testing/Mandrake These were compiled with kgcc and should be stable the rpms in RPMSgcc where compiled with: Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/2.96/specs gcc version 2.96 20000731 (Mandrake Linux 8.1 2.96-0.62mdk) Which may or may not be stable. If anybody is willing and has the time to stress test these things it would be really helpful in possibly getting XFS included in the next release of Mandrake. I see today mandrake has a new version of the kernel out, so I will respin the rpms to include the latest updates from mdk. Note the version of XFS is the same as the 2.4.8 snapshot patch. I have yet to determine if the top of tree is stable enough and or compatible with 2.4.8+ac but hopefully it is and the next set of rpms will be the latest and greatest bits. From owner-linux-xfs@oss.sgi.com Tue Sep 11 13:10:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BKAoo23914 for linux-xfs-outgoing; Tue, 11 Sep 2001 13:10:50 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BKAdd23895; Tue, 11 Sep 2001 13:10:39 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BKAed23896 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 14:34:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BLY4w25096 for linux-xfs-outgoing; Tue, 11 Sep 2001 14:34:04 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BLXwd25072; Tue, 11 Sep 2001 14:33:58 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.23]) by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |May 14, 2001) at 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BLXxd25073 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10.09.2001 04:00:30 Adrian Head wrote: [....see subject...] Hi Adrian, I've had a quite similar phenomen last weekend. When copiing with many cp-processes on my xfs-volume i run into io errors or kernel oops. The solution was that the two disks of the Raidsystem are getting to hot when I run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB raid 1 volume). Added another fan and all was fine ;-)........... cu michael From owner-linux-xfs@oss.sgi.com Tue Sep 11 16:08:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BN8Gx26149 for linux-xfs-outgoing; Tue, 11 Sep 2001 16:08:16 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BN8Ce26130 for ; Tue, 11 Sep 2001 16:08:12 -0700 Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id QAA00922 for ; Tue, 11 Sep 2001 16:08:08 -0700 (PDT) mail_from (cattelan@thebarn.com) Received: from scare ([63.231.179.33]) by lips.thebarn.com (8.12.0/8.12.0) with ESMTP id f8BMxkPp004045; Tue, 11 Sep 2001 17:59:47 -0500 (CDT) Subject: Re: Mandrake RPMs available for testing. From: Russell Cattelan To: Russell Cattelan Cc: linux-xfs@oss.sgi.com In-Reply-To: <1000237926.13368.54.camel@scare> References: <1000237926.13368.54.camel@scare> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 11 Sep 2001 17:52:43 -0500 Message-Id: <1000248764.13366.113.camel@scare> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 11 Sep 2001 14:52:04 -0500, Russell Cattelan wrote: > I have placed somewhat current Mandrake rpms on oss. > > ftp://oss.sgi.com/projects/xfs/download/testing/Mandrake > > These were compiled with kgcc and should be stable > the rpms in RPMSgcc where compiled with: > Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/2.96/specs > gcc version 2.96 20000731 (Mandrake Linux 8.1 2.96-0.62mdk) > > Which may or may not be stable. > > If anybody is willing and has the time to stress test these things > it would be really helpful in possibly getting XFS included in the > next release of Mandrake. > > I see today mandrake has a new version of the kernel out, so I will > respin the rpms to include the latest updates from mdk. Ok so I should have actually looked at the latest cooker rpms before I sent this out. XFS is in the latest cooker rpm! yea! > > Note the version of XFS is the same as the 2.4.8 snapshot patch. > I have yet to determine if the top of tree is stable enough and > or compatible with 2.4.8+ac but hopefully it is and the next > set of rpms will be the latest and greatest bits. > From owner-linux-xfs@oss.sgi.com Tue Sep 11 16:15:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BNFTS26366 for linux-xfs-outgoing; Tue, 11 Sep 2001 16:15:29 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BNFRe26346 for ; Tue, 11 Sep 2001 16:15:27 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f8BNFLP31401 for linux-xfs@oss.sgi.com; Tue, 11 Sep 2001 19:15:21 -0400 Date: Tue, 11 Sep 2001 19:15:21 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: cpqfcTSinit.c module build failure Message-ID: <20010911191521.A25147@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have just pulled a fresh CVS copy and the build problem still exists. I'm doing a diff now between my cvs copy from 0908 and today. I tracked it down. Those modules weren't mentioned in the Makefile until now. Bleah. Into my borked-drivers.config file to cut it out of the build. -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Tue Sep 11 17:08:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8C08VK27163 for linux-xfs-outgoing; Tue, 11 Sep 2001 17:08:31 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8C08Te27141 for ; Tue, 11 Sep 2001 17:08:29 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8C08NJ11048 for ; Tue, 11 Sep 2001 17:08:23 -0700 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA35050 for linux-xfs@oss.sgi.com; Wed, 12 Sep 2001 10:07:06 +1000 (EST) Date: Wed, 12 Sep 2001 10:07:06 +1000 (EST) From: Nathan Scott Message-Id: <200109120007.KAA35050@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - install scripts Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Fix a bug from the folks working on XFS support in the Debian boot floppies. Date: Tue Sep 11 17:03:41 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102627a cmd/attr/install-sh - 1.3 cmd/xfsdump/install-sh - 1.4 cmd/xfsprogs/install-sh - 1.4 cmd/xfsprogs/debian/changelog - 1.27 cmd/acl/install-sh - 1.3 cmd/dmapi/install-sh - 1.5 - Make install-sh posix compliant so ash as /bin/sh works. From owner-linux-xfs@oss.sgi.com Tue Sep 11 23:58:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8C6wPQ00952 for linux-xfs-outgoing; Tue, 11 Sep 2001 23:58:25 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8C6wMe00933 for ; Tue, 11 Sep 2001 23:58:22 -0700 Received: from idcomm.com (IDENT:+HVD84Yp2LWUB3ohupymf+Hr+UrVbq2j@x2-pip82.idcomm.com [209.60.72.93]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f8C78uQ01240 for ; Wed, 12 Sep 2001 01:08:56 -0600 Message-ID: <3B9F080B.F0BBB761@idcomm.com> Date: Wed, 12 Sep 2001 01:00:27 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 To: "XFS: linux-xfs@oss.sgi.com" Subject: lock files after crash Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based (root is XFS). I had a crash at the moment I attempted to start login as a regular user (home is also XFS). It seems that ~/.ICEauthority is written each session when gdm/gnome is used for the login session, and that a check is done for whether or not .ICEauthority can be locked. After a crash, the file is empty (this is ok, it's the metadata versus full journal thing, it isn't an issue), since the crash occurs during that file write. However, after coming back up, X11 will fail due to an inability to lock the file. A question occurs here, whether lock data or whatever information is used to determine if a file can be locked, is part of the filesystem journaling? Or is this a separate issue that can't be dealth with by journaling filesystems? Is there any way XFS, coming back after a crash, can remove stale locks or bogus locks? I have no idea if this is entirely just coincidence it occurs, or if XFS itself can help recover under such circumstances. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Wed Sep 12 00:13:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8C7DNe01341 for linux-xfs-outgoing; Wed, 12 Sep 2001 00:13:23 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8C7DJe01320 for ; Wed, 12 Sep 2001 00:13:19 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id JAA01815; Wed, 12 Sep 2001 09:13:09 +0200 (CEST) Message-Id: <4.3.2.7.2.20010912091115.03368618@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 12 Sep 2001 09:13:06 +0200 To: stimits@idcomm.com, "XFS: linux-xfs@oss.sgi.com" From: Seth Mos Subject: Re: lock files after crash In-Reply-To: <3B9F080B.F0BBB761@idcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 01:00 12-9-2001 -0600, D. Stimits wrote: >I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based >(root is XFS). I had a crash at the moment I attempted to start login as >a regular user (home is also XFS). It seems that ~/.ICEauthority is >written each session when gdm/gnome is used for the login session, and >that a check is done for whether or not .ICEauthority can be locked. >After a crash, the file is empty (this is ok, it's the metadata versus >full journal thing, it isn't an issue), since the crash occurs during >that file write. However, after coming back up, X11 will fail due to an >inability to lock the file. A question occurs here, whether lock data or >whatever information is used to determine if a file can be locked, is >part of the filesystem journaling? Or is this a separate issue that >can't be dealth with by journaling filesystems? Is there any way XFS, >coming back after a crash, can remove stale locks or bogus locks? I have >no idea if this is entirely just coincidence it occurs, or if XFS itself >can help recover under such circumstances. Most of the time lock files are just empty files that get removed when they are done. Netscape also used to do this. But since a lock file might have 0 bytes size it will be committed to disk very fast and journaling or not the file will probably survive a reboot. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Sep 12 01:20:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8C8KJY02470 for linux-xfs-outgoing; Wed, 12 Sep 2001 01:20:19 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8C8KEe02451 for ; Wed, 12 Sep 2001 01:20:14 -0700 Received: from idcomm.com (IDENT:BKGLAaeX7S03fXe0P71JKTdOwZwYLTS5@x2-pip20.idcomm.com [209.60.72.31]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f8C8UTQ06166 for ; Wed, 12 Sep 2001 02:30:29 -0600 Message-ID: <3B9F1B27.49261933@idcomm.com> Date: Wed, 12 Sep 2001 02:21:59 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 To: "XFS: linux-xfs@oss.sgi.com" Subject: Re: lock files after crash References: <4.3.2.7.2.20010912091115.03368618@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > > At 01:00 12-9-2001 -0600, D. Stimits wrote: > >I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based > >(root is XFS). I had a crash at the moment I attempted to start login as > >a regular user (home is also XFS). It seems that ~/.ICEauthority is > >written each session when gdm/gnome is used for the login session, and > >that a check is done for whether or not .ICEauthority can be locked. > >After a crash, the file is empty (this is ok, it's the metadata versus > >full journal thing, it isn't an issue), since the crash occurs during > >that file write. However, after coming back up, X11 will fail due to an > >inability to lock the file. A question occurs here, whether lock data or > >whatever information is used to determine if a file can be locked, is > >part of the filesystem journaling? Or is this a separate issue that > >can't be dealth with by journaling filesystems? Is there any way XFS, > >coming back after a crash, can remove stale locks or bogus locks? I have > >no idea if this is entirely just coincidence it occurs, or if XFS itself > >can help recover under such circumstances. > > Most of the time lock files are just empty files that get removed when they > are done. > Netscape also used to do this. But since a lock file might have 0 bytes > size it will be committed to disk very fast and journaling or not the file > will probably survive a reboot. > > Cheers > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. In this case the file is .ICEauthority, not related to Netscape. What I am thinking about is fcntl(). I'm wondering about how these are implemented: F_GETLK, F_SETLK and F_SETLKW. If fcntl locks depend on file structures or metadata, or if the file itself has nothing to do with fcntl? The complaint after failure would seemt to be that it can't set a lock, which is not necessarily the same as file existence. Permissions do not seem to be the problem either. Is the filesystem cooperating with fcntl, and doing the lock storage? Or is this determined in some other way? If the filesystem maintains metadata on locks, then it seems that they should be discarded upon recovery. I'm not concerned with custom schemes like the one you mention (PostgreSQL does this, and it annoys me that after any crash I have to delete the postmaster.pid file...yet "/etc/rc.d/init.d/postgresql status" knows that the "subsystem is locked but postmaster is not running", and it is too stupid to forcibly remove the lock file). D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Wed Sep 12 03:29:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CATDv05022 for linux-xfs-outgoing; Wed, 12 Sep 2001 03:29:13 -0700 Received: from picklock.adams.family ([145.254.147.58]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CAT6e05003 for ; Wed, 12 Sep 2001 03:29:06 -0700 Received: from loewe-komp.de (localhost [127.0.0.1]) by picklock.adams.family (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id f8CATT510196; Wed, 12 Sep 2001 12:29:29 +0200 Message-ID: <3B9F3908.F94E9039@loewe-komp.de> Date: Wed, 12 Sep 2001 12:29:28 +0200 From: Peter =?iso-8859-1?Q?W=E4chtler?= Organization: B16 X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.4.9-ac5 i686) X-Accept-Language: de, en MIME-Version: 1.0 To: Michael Wahlbrink CC: linux-xfs@oss.sgi.com Subject: Re: Problems with many processes copying large directories across an XFSvolume. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Michael Wahlbrink wrote: > > On 10.09.2001 04:00:30 Adrian Head wrote: > [....see subject...] > Hi Adrian, > I've had a quite similar phenomen last weekend. When copiing with many > cp-processes on my xfs-volume i run into io errors or kernel oops. > The solution was that the two disks of the Raidsystem are getting to hot when I > run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB > raid 1 volume). Added another fan and all was fine ;-)........... > Hm, every mail from Michael Wahlbrink arrives _7_times_ at the list. Full header follows (no I have no idea why). Why are you sending to linux-xfs AND owner-linux-xfs? From - Wed Sep 12 12:26:06 2001 X-Sieve: cmu-sieve 2.0 Return-Path: Received: from mail.loewe-komp.de (mail.loewe-komp.de [192.168.169.6]) by noisy.loewe-komp.de (Postfix on SuSE eMail Server 2.0) with ESMTP id 9 for ; Tue, 11 Sep 2001 23:19:48 +0200 (CEST) Received: from oss.sgi.com (oss.sgi.com [216.32.174.27]) by mail.loewe-komp.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id for ; Tue, 11 Sep 2001 19:09:46 +0200 Received: from localhost (mail@localhost) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BH0nJ20501; Tue, 11 Sep 2001 10:00:49 -0700 X-Authentication-Warning: oss.sgi.com: mail owned process doing -bs Received: by oss.sgi.com (bulk_mailer v1.13); Tue, 11 Sep 2001 10:00:43 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8BH0hl20488 for linux-xfs-outgoing; Tue, 11 Sep 2001 10:00:43 -0700 Received: from out-gate.propack-data.de (out-gate.propack-data.de [194.120.230.2] by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BH0ad20469; Tue, 11 Sep 2001 10:00:36 -0700 Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de [10.2.1.2 by out-gate.propack-data.de (Postfix) with ESMTP id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) Subject: Re: Problems with many processes copying large directories across an XFS volume. To: adrian.head@bytecomm.com.au Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Michael Wahlbrink" Date: Mon, 10 Sep 2001 06:56:01 +0200 X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release 5.07a |M 10.09.2001 06:56:03 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8BH0bd2047 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk From owner-linux-xfs@oss.sgi.com Wed Sep 12 04:47:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CBliq07056 for linux-xfs-outgoing; Wed, 12 Sep 2001 04:47:44 -0700 Received: from mel-rti17.wanadoo.fr (smtprt17.wanadoo.fr [193.252.19.228]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CBlfe07030 for ; Wed, 12 Sep 2001 04:47:41 -0700 Received: from citronier.wanadoo.fr (193.252.19.222) by mel-rti17.wanadoo.fr; 12 Sep 2001 13:47:34 +0200 Received: from there (193.248.142.125) by citronier.wanadoo.fr; 12 Sep 2001 13:47:16 +0200 Message-ID: <3b9f4b453c427ad2@citronier.wanadoo.fr> (added by citronier.wanadoo.fr) Content-Type: text/plain; charset="iso-8859-1" From: =?iso-8859-1?q?Fran=E7ois=20Dupoux?= To: linux-xfs@oss.sgi.com Subject: Partition Image 0.6.0-rc3 with XFS support Date: Wed, 12 Sep 2001 13:47:13 +0200 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk HOMEPAGE: http://www.partimage.org/ DOWNLOAD: http://www.partimage.org/download.php3 HANDBOOK: http://www.partimage.org/doc/index.html Partition Image is a Norton Ghost / Drive Image clone for Linux. This uility saves partitions in the ext2, reiserfs, ntfs, hpfs, fat16, fat32, jfs, xfs, hfs filesystems format to an image file. The image file can be compressed in the GZIP/BZIP2 formats to save disk space, and be splitted to be copied on multiple removable floppies On problems, the user just have to restore the partition from the image file, and all the original data are copied. A boot/root and a bootable CD-Rom disk are now provided to run partition image without Linux installed on the hard disk. The new version provides the newtork support. Tested under intel i386+ and PowerPC/iMac The XFS support has just been added in version 0.6.0rc3. It was a little tested with small partitions (300 MB), and large ones (15 GB), but we need more test to be sure this support is stable. Interested users can make tests and send us bug reports. Tests on large and fragmented partitions are very useful, because the support is more complex. You can have details about how to make advanced tests in the handbook. The partimage team. AUTHORS: Franck Ladurelle Francois Dupoux From owner-linux-xfs@oss.sgi.com Wed Sep 12 06:01:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CD1GL08399 for linux-xfs-outgoing; Wed, 12 Sep 2001 06:01:16 -0700 Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.131]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CD1Be08380 for ; Wed, 12 Sep 2001 06:01:11 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id PAA14453; Wed, 12 Sep 2001 15:01:08 +0200 (CEST) Message-Id: <4.3.2.7.2.20010912145644.03309ca8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 12 Sep 2001 15:01:05 +0200 To: =?iso-8859-1?Q?Fran=E7ois?= Dupoux , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Partition Image 0.6.0-rc3 with XFS support In-Reply-To: <3b9f4b453c427ad2@citronier.wanadoo.fr> (added by citronier.wanadoo.fr) Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8CD1Ce08381 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 13:47 12-9-2001 +0200, François Dupoux wrote: >HOMEPAGE: http://www.partimage.org/ >DOWNLOAD: http://www.partimage.org/download.php3 >HANDBOOK: http://www.partimage.org/doc/index.html > >Partition Image is a Norton Ghost / Drive Image clone for Linux. This uility >saves partitions in the ext2, reiserfs, ntfs, hpfs, fat16, fat32, jfs, xfs, >hfs filesystems format to an image file. The image file can be compressed in >the GZIP/BZIP2 formats to save disk space, and be splitted to be copied on >multiple removable floppies On problems, the user just have to restore the >partition from the image file, and all the original data are copied. A >boot/root and a bootable CD-Rom disk are now provided to run partition image >without Linux installed on the hard disk. The new version provides the >newtork support. Tested under intel i386+ and PowerPC/iMac > >The XFS support has just been added in version 0.6.0rc3. It was a little >tested with small partitions (300 MB), and large ones (15 GB), but we need >more test to be sure this support is stable. > >Interested users can make tests and send us bug reports. Tests on large and >fragmented partitions are very useful, because the support is more complex. >You can have details about how to make advanced tests in the handbook. I am testing it now since my linux partition still needed to be moved off my old notebook to my new one. This makes it somewhat easier :-) Does partimage also take things like ACLs and other Extended Attributes into account? It looks good and it works right too, impressive. This will make a fast backup solution if some server takes a dump and it needs to be restored. I will test it with a larger filesystem later from a test server which holds some large databases. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Sep 12 06:19:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CDJKO08960 for linux-xfs-outgoing; Wed, 12 Sep 2001 06:19:20 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CDJGe08941 for ; Wed, 12 Sep 2001 06:19:16 -0700 Received: from fort.demeern.sgi.com (fort.demeern.sgi.com [144.253.208.2]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id GAA11278 for ; Wed, 12 Sep 2001 06:19:20 -0700 (PDT) mail_from (martinh@demeern.sgi.com) Received: from poortvliet.demeern.sgi.com (poortvliet.demeern.sgi.com [144.253.208.34]) by fort.demeern.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF.hoststrip-1.1) via ESMTP id PAA28157; Wed, 12 Sep 2001 15:17:52 +0200 (MDT) Received: (from martinh@localhost) by poortvliet.demeern.sgi.com (SGI-8.9.3/8.9.3) id PAA03806; Wed, 12 Sep 2001 15:17:32 +0200 (MDT) Date: Wed, 12 Sep 2001 15:17:32 +0200 From: Martin Hilgeman To: Keith Owens Cc: Florin Andrei , linux-xfs Subject: Re: 1.0.1 doesn't work with SGI1100 Message-ID: <20010912151731.B3756@poortvliet.demeern.sgi.com> Reply-To: martinh@demeern.sgi.com References: <1000175055.23809.155.camel@stantz.corp.sgi.com> <27772.1000176060@kao2.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <27772.1000176060@kao2.melbourne.sgi.com> User-Agent: Mutt/1.3.22i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tuesday 11 September 2001, at 12:41 +1000, Keith Owens wrote: > On 10 Sep 2001 19:24:15 -0700, > Florin Andrei wrote: > >ide=nodma solves the problem for the installer. But, after the install, > >when the system comes up for the first time, it's the same problem: it's > >frozen when it tries to mount large partitions. > >I can add to the kickstart file, to the lilo option, the "--append > >ide=nodma" string, and it appears to solve the problem. But, still, if i > >want a high performance from that system (and believe me, i do want > >that, since it's gonna be a busy mail gateway), not using DMA will hurt > >performance. > > It is likely to be a chipset problem rather than XFS. RH 7.1 was > probably compiled without CONFIG_IDEDMA_PCI_AUTO. I used to have the same problem on sgi 1100's. The solution is to patch the kernel with Andre Hedrick's IDE patch, which supports the Serverworks 3LE chipset. The patches can be found on: http://www.linux-ide.org With this patch I get ~16 MB/s on a single Seagate Barracuda ST320420A disk drive. Don't forget to tune with hdparm(8) (hdparm -c3 -d1 -A1 -m16 -X66 works best here). Regards, -Martin -- Martin Hilgeman Technical consultant VNET: 955-6885 SGI Mailstop: INL-3650 The Netherlands E-mail: martinh@demeern.sgi.com From owner-linux-xfs@oss.sgi.com Wed Sep 12 09:06:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CG66012153 for linux-xfs-outgoing; Wed, 12 Sep 2001 09:06:06 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CG5se12133 for ; Wed, 12 Sep 2001 09:05:55 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id SAA15539; Wed, 12 Sep 2001 18:05:32 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id SAA09777; Wed, 12 Sep 2001 18:05:21 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 51F4C57306; Wed, 12 Sep 2001 18:04:47 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id F3D9225835; Wed, 12 Sep 2001 18:04:46 +0200 (CEST) Message-ID: <3B9F879E.3FB8976@ch.sauter-bc.com> Date: Wed, 12 Sep 2001 18:04:46 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: stimits@idcomm.com Cc: "XFS: linux-xfs@oss.sgi.com" Subject: Re: lock files after crash References: <4.3.2.7.2.20010912091115.03368618@pop.xs4all.nl> <3B9F1B27.49261933@idcomm.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" schrieb: > > Seth Mos wrote: > > > > At 01:00 12-9-2001 -0600, D. Stimits wrote: > > >I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based > > >(root is XFS). I had a crash at the moment I attempted to start login as > > >a regular user (home is also XFS). It seems that ~/.ICEauthority is > > >written each session when gdm/gnome is used for the login session, and > > >that a check is done for whether or not .ICEauthority can be locked. > > >After a crash, the file is empty (this is ok, it's the metadata versus > > >full journal thing, it isn't an issue), since the crash occurs during > > >that file write. However, after coming back up, X11 will fail due to an > > >inability to lock the file. A question occurs here, whether lock data or > > >whatever information is used to determine if a file can be locked, is > > >part of the filesystem journaling? Or is this a separate issue that > > >can't be dealth with by journaling filesystems? Is there any way XFS, > > >coming back after a crash, can remove stale locks or bogus locks? I have > > >no idea if this is entirely just coincidence it occurs, or if XFS itself > > >can help recover under such circumstances. At least you're not alone, I was having the same problem. Did you really have a kernel crash? I don't rember what happened in my case but I thought I was upgrading some RPM's and when I rebooted next time I just couldn't login. IIRC I did not have a kernel crash. -Simon > > > > Most of the time lock files are just empty files that get removed when they > > are done. > > Netscape also used to do this. But since a lock file might have 0 bytes > > size it will be committed to disk very fast and journaling or not the file > > will probably survive a reboot. > > > > Cheers > > > > -- > > Seth > > Every program has two purposes one for which > > it was written and another for which it wasn't > > I use the last kind. > > In this case the file is .ICEauthority, not related to Netscape. What I > am thinking about is fcntl(). I'm wondering about how these are > implemented: F_GETLK, F_SETLK and F_SETLKW. If fcntl locks depend on > file structures or metadata, or if the file itself has nothing to do > with fcntl? The complaint after failure would seemt to be that it can't > set a lock, which is not necessarily the same as file existence. > Permissions do not seem to be the problem either. Is the filesystem > cooperating with fcntl, and doing the lock storage? Or is this > determined in some other way? If the filesystem maintains metadata on > locks, then it seems that they should be discarded upon recovery. I'm > not concerned with custom schemes like the one you mention (PostgreSQL > does this, and it annoys me that after any crash I have to delete the > postmaster.pid file...yet "/etc/rc.d/init.d/postgresql status" knows > that the "subsystem is locked but postmaster is not running", and it is > too stupid to forcibly remove the lock file). > > D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Wed Sep 12 09:12:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CGCuI12410 for linux-xfs-outgoing; Wed, 12 Sep 2001 09:12:56 -0700 Received: from bassia.wanadoo.fr (smtp-rt-5.wanadoo.fr [193.252.19.159]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CGCpe12348 for ; Wed, 12 Sep 2001 09:12:53 -0700 Received: from amyris.wanadoo.fr (193.252.19.150) by bassia.wanadoo.fr; 12 Sep 2001 18:12:42 +0200 Received: from there (193.248.253.129) by amyris.wanadoo.fr; 12 Sep 2001 18:12:37 +0200 Message-ID: <3b9f89763bea14e4@amyris.wanadoo.fr> (added by amyris.wanadoo.fr) Content-Type: text/plain; charset="iso-8859-1" From: =?iso-8859-1?q?Fran=E7ois=20Dupoux?= To: linux-xfs@oss.sgi.com Subject: Re: Partition Image 0.6.0-rc3 with XFS support Date: Wed, 12 Sep 2001 17:15:06 +0200 X-Mailer: KMail [version 1.3] References: <4.3.2.7.2.20010912145644.03309ca8@pop.xs4all.nl> In-Reply-To: <4.3.2.7.2.20010912145644.03309ca8@pop.xs4all.nl> Cc: Seth Mos MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I am testing it now since my linux partition still needed to be moved off > my old notebook to my new one. This makes it somewhat easier :-) > > Does partimage also take things like ACLs and other Extended Attributes > into account? partimage makes a physical copy of the partition. It's not a simple "tar.gz" of files. In other words, it does the same work than dd does, but it forget to copy all free blocks in order to save space and time. Then everything is kept (bootsector informations, all attributes that can exist, ...) It even keeps location of files on the disk, then the vmlinuz file won't be moved, and LILO will continue to work. regards francois dupoux From owner-linux-xfs@oss.sgi.com Wed Sep 12 09:23:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CGNiF12758 for linux-xfs-outgoing; Wed, 12 Sep 2001 09:23:44 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CGNfe12738 for ; Wed, 12 Sep 2001 09:23:41 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id SAA19882; Wed, 12 Sep 2001 18:23:29 +0200 (CEST) Message-Id: <4.3.2.7.2.20010912182157.03348b00@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 12 Sep 2001 18:23:14 +0200 To: =?iso-8859-1?Q?Fran=E7ois?= Dupoux , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Partition Image 0.6.0-rc3 with XFS support In-Reply-To: <3b9f89763bea14e4@amyris.wanadoo.fr> (added by amyris.wanadoo.fr) References: <4.3.2.7.2.20010912145644.03309ca8@pop.xs4all.nl> <4.3.2.7.2.20010912145644.03309ca8@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8CGNge12739 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:15 12-9-2001 +0200, François Dupoux wrote: > > I am testing it now since my linux partition still needed to be moved off > > my old notebook to my new one. This makes it somewhat easier :-) > > > > Does partimage also take things like ACLs and other Extended Attributes > > into account? >partimage makes a physical copy of the partition. It's not a simple "tar.gz" >of files. In other words, it does the same work than dd does, but it forget >to copy all free blocks in order to save space and time. Then everything is >kept (bootsector informations, all attributes that can exist, ...) It even >keeps location of files on the disk, then the vmlinuz file won't be moved, >and LILO will continue to work. Cool! I will add it to the FAQ after helping out my sister who is moving. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Sep 12 11:19:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CIJ8Z15182 for linux-xfs-outgoing; Wed, 12 Sep 2001 11:19:08 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CIJ2e15163 for ; Wed, 12 Sep 2001 11:19:02 -0700 Received: from idcomm.com (IDENT:18XRkvuzMpCdka/rSOw35tKpuP1+ZImA@x2-pip12.idcomm.com [209.60.72.23]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f8CITcQ20932 for ; Wed, 12 Sep 2001 12:29:38 -0600 Message-ID: <3B9FA793.FCCBC231@idcomm.com> Date: Wed, 12 Sep 2001 12:21:07 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: Problems with many processes copying large directories across an XFSvolume. References: <3B9F3908.F94E9039@loewe-komp.de> Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by mailhost.idcomm.com id f8CITcQ20932 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8CIJ2e15164 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Peter Wächtler wrote: > > Michael Wahlbrink wrote: > > > > On 10.09.2001 04:00:30 Adrian Head wrote: > > [....see subject...] > > Hi Adrian, > > I've had a quite similar phenomen last weekend. When copiing with many > > cp-processes on my xfs-volume i run into io errors or kernel oops. > > The solution was that the two disks of the Raidsystem are getting to hot when I > > run these extensive tests (30cp processes and 15 tar processes on thesame 60 GB > > raid 1 volume). Added another fan and all was fine ;-)........... > > > > Hm, every mail from Michael Wahlbrink arrives _7_times_ at the list. > > Full header follows (no I have no idea why). Why are you sending > to linux-xfs AND owner-linux-xfs? I have the same question. Only I wonder if it is *more* than 7 times each. D. Stimits, stimits@idcomm.com > > >From - Wed Sep 12 12:26:06 2001 > X-Sieve: cmu-sieve 2.0 > Return-Path: > Received: from mail.loewe-komp.de (mail.loewe-komp.de [192.168.169.6]) > by noisy.loewe-komp.de (Postfix on SuSE eMail Server 2.0) with > ESMTP id 9 > for ; Tue, 11 Sep 2001 23:19:48 +0200 > (CEST) > Received: from oss.sgi.com (oss.sgi.com [216.32.174.27]) > by mail.loewe-komp.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with > ESMTP id > for ; Tue, 11 Sep 2001 19:09:46 +0200 > Received: from localhost (mail@localhost) > by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BH0nJ20501; > Tue, 11 Sep 2001 10:00:49 -0700 > X-Authentication-Warning: oss.sgi.com: mail owned process doing -bs > Received: by oss.sgi.com (bulk_mailer v1.13); Tue, 11 Sep 2001 10:00:43 > -0700 > Received: (from majordomo@localhost) > by oss.sgi.com (8.11.2/8.11.3) id f8BH0hl20488 > for linux-xfs-outgoing; Tue, 11 Sep 2001 10:00:43 -0700 > Received: from out-gate.propack-data.de (out-gate.propack-data.de > [194.120.230.2] > by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8BH0ad20469; > Tue, 11 Sep 2001 10:00:36 -0700 > Received: from pegasus.propack-data.de (pddeka-s0008.ka.propack-data.de > [10.2.1.2 > by out-gate.propack-data.de (Postfix) with ESMTP > id CF7C567041; Mon, 10 Sep 2001 06:56:02 +0200 (CEST) > Subject: Re: Problems with many processes copying large directories > across an XFS volume. > To: adrian.head@bytecomm.com.au > Cc: linux-xfs@oss.sgi.com, owner-linux-xfs@oss.sgi.com > X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 > Message-ID: > From: "Michael Wahlbrink" > Date: Mon, 10 Sep 2001 06:56:01 +0200 > X-MIMETrack: Serialize by Router on Pegasus/KA/Propack Data GmbH(Release > 5.07a |M 10.09.2001 06:56:03 > MIME-Version: 1.0 > Content-type: text/plain; charset=iso-8859-1 > Content-Transfer-Encoding: 8bit > X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id > f8BH0bd2047 > Sender: owner-linux-xfs@oss.sgi.com > Precedence: bulk From owner-linux-xfs@oss.sgi.com Wed Sep 12 11:27:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CIRRW15414 for linux-xfs-outgoing; Wed, 12 Sep 2001 11:27:27 -0700 Received: from phobos.pop-star.net (phobos.pop-star.net [64.85.83.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CIRNe15394 for ; Wed, 12 Sep 2001 11:27:23 -0700 Received: from zerowing.pop-star.net ([208.181.22.52]) by phobos.pop-star.net with asmtp (Exim 3.167 #4) id 15hEl5-00014d-00; Wed, 12 Sep 2001 11:29:11 -0700 Subject: Re: 1.0.1 doesn't work with SGI1100 From: Andy Kwong To: martinh@demeern.sgi.com Cc: linux-xfs In-Reply-To: <20010912151731.B3756@poortvliet.demeern.sgi.com> References: <1000175055.23809.155.camel@stantz.corp.sgi.com> <27772.1000176060@kao2.melbourne.sgi.com> <20010912151731.B3756@poortvliet.demeern.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13.99+cvs.2001.09.05.07.08 (Preview Release) Date: 12 Sep 2001 11:27:48 -0700 Message-Id: <1000319272.14789.3.camel@zerowing.pop-star.net> Mime-Version: 1.0 X-Authenticated-Sender: andy.kwong@pop-star.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk And you might want to check out the contrib RPMS at http://rpms.aicompro.net As the newer kernels contains serverworks support. These RPMS also have lm_sensors support for hardware monitoring. --Andy On Wed, 2001-09-12 at 06:17, Martin Hilgeman wrote: > On Tuesday 11 September 2001, at 12:41 +1000, Keith Owens wrote: > > On 10 Sep 2001 19:24:15 -0700, > > Florin Andrei wrote: > > >ide=nodma solves the problem for the installer. But, after the install, > > >when the system comes up for the first time, it's the same problem: it's > > >frozen when it tries to mount large partitions. > > >I can add to the kickstart file, to the lilo option, the "--append > > >ide=nodma" string, and it appears to solve the problem. But, still, if i > > >want a high performance from that system (and believe me, i do want > > >that, since it's gonna be a busy mail gateway), not using DMA will hurt > > >performance. > > > > It is likely to be a chipset problem rather than XFS. RH 7.1 was > > probably compiled without CONFIG_IDEDMA_PCI_AUTO. > > I used to have the same problem on sgi 1100's. The solution is to patch > the kernel with Andre Hedrick's IDE patch, which supports the > Serverworks 3LE chipset. > > The patches can be found on: http://www.linux-ide.org > > With this patch I get ~16 MB/s on a single Seagate Barracuda ST320420A > disk drive. Don't forget to tune with hdparm(8) (hdparm -c3 -d1 -A1 -m16 > -X66 works best here). > > Regards, > > -Martin > From owner-linux-xfs@oss.sgi.com Wed Sep 12 14:05:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CL5Ye19348 for linux-xfs-outgoing; Wed, 12 Sep 2001 14:05:34 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CL5Ve19326 for ; Wed, 12 Sep 2001 14:05:31 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8CL5P500581 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Wed, 12 Sep 2001 14:05:26 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id XAA398548 for ; Wed, 12 Sep 2001 23:05:23 +0200 (CEST) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id OAA84297 for ; Wed, 12 Sep 2001 14:10:38 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 890F915A213 for ; Wed, 12 Sep 2001 14:04:06 -0700 (PDT) Subject: Re: 1.0.1 doesn't work with SGI1100 From: Florin Andrei To: linux-xfs In-Reply-To: <20010912151731.B3756@poortvliet.demeern.sgi.com> References: <1000175055.23809.155.camel@stantz.corp.sgi.com> <27772.1000176060@kao2.melbourne.sgi.com> <20010912151731.B3756@poortvliet.demeern.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 12 Sep 2001 14:04:06 -0700 Message-Id: <1000328646.1469.5.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 12 Sep 2001 15:17:32 +0200, Martin Hilgeman wrote: > > Don't forget to tune with hdparm(8) (hdparm -c3 -d1 -A1 -m16 > -X66 works best here). Those parameters are tuned for an 1100? -- Florin Andrei "Our kernel does have source control: its name is Linus Torvalds, CVS with a brain." - Nicholas Knight From owner-linux-xfs@oss.sgi.com Wed Sep 12 14:07:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CL78j19491 for linux-xfs-outgoing; Wed, 12 Sep 2001 14:07:08 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CL76e19468 for ; Wed, 12 Sep 2001 14:07:06 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id OAA01445 for ; Wed, 12 Sep 2001 14:05:38 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id OAA40570 for ; Wed, 12 Sep 2001 14:12:21 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 82E1A15A213 for ; Wed, 12 Sep 2001 14:05:49 -0700 (PDT) Subject: Re: 1.0.1 doesn't work with SGI1100 From: Florin Andrei To: linux-xfs In-Reply-To: <1000319272.14789.3.camel@zerowing.pop-star.net> References: <1000175055.23809.155.camel@stantz.corp.sgi.com> <27772.1000176060@kao2.melbourne.sgi.com> <20010912151731.B3756@poortvliet.demeern.sgi.com> <1000319272.14789.3.camel@zerowing.pop-star.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 12 Sep 2001 14:05:49 -0700 Message-Id: <1000328749.1586.9.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 12 Sep 2001 11:27:48 -0700, Andy Kwong wrote: > And you might want to check out the contrib RPMS at > > http://rpms.aicompro.net Cool! I tried those RPMS and they work fine on a SGI1100 without turning off DMA, which is great. Thanks, -- Florin Andrei "Our kernel does have source control: its name is Linus Torvalds, CVS with a brain." - Nicholas Knight From owner-linux-xfs@oss.sgi.com Wed Sep 12 14:16:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CLGTm19799 for linux-xfs-outgoing; Wed, 12 Sep 2001 14:16:29 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CLGQe19777 for ; Wed, 12 Sep 2001 14:16:26 -0700 Received: from idcomm.com (IDENT:ZYqZt4fqjKgeyXSHkuBSnutcYN4V75Q/@x2-pip16.idcomm.com [209.60.72.27]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f8CLR3Q30131 for ; Wed, 12 Sep 2001 15:27:04 -0600 Message-ID: <3B9FD128.AFD7CB83@idcomm.com> Date: Wed, 12 Sep 2001 15:18:32 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 To: "XFS: linux-xfs@oss.sgi.com" Subject: Re: lock files after crash References: <3B9F080B.F0BBB761@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" wrote: > > I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based > (root is XFS). I had a crash at the moment I attempted to start login as > a regular user (home is also XFS). It seems that ~/.ICEauthority is > written each session when gdm/gnome is used for the login session, and > that a check is done for whether or not .ICEauthority can be locked. > After a crash, the file is empty (this is ok, it's the metadata versus > full journal thing, it isn't an issue), since the crash occurs during > that file write. However, after coming back up, X11 will fail due to an > inability to lock the file. A question occurs here, whether lock data or > whatever information is used to determine if a file can be locked, is > part of the filesystem journaling? Or is this a separate issue that > can't be dealth with by journaling filesystems? Is there any way XFS, > coming back after a crash, can remove stale locks or bogus locks? I have > no idea if this is entirely just coincidence it occurs, or if XFS itself > can help recover under such circumstances. > > D. Stimits, stimits@idcomm.com Since nobody has said anything, let me rephrase the question. There are custom lock file schemes, which I am not interested in. There *is* fcntl to perform locking. Ignoring lock files, is there any metadata or filesystem data that is altered when using fcntl to lock? If so, it is a "bad thing" to preserve locked status upon recovery...it should be cleared, else the file can't be reopened and locked. During recovery, it can be assumed that the original application no longer should have a lock...it's long dead. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Wed Sep 12 14:29:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CLTwf20120 for linux-xfs-outgoing; Wed, 12 Sep 2001 14:29:58 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CLTte20101 for ; Wed, 12 Sep 2001 14:29:55 -0700 Received: from clink-eth.americas.sgi.com (clink-eth.americas.sgi.com [128.162.2.8]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8CLTn502437 for ; Wed, 12 Sep 2001 14:29:49 -0700 Received: (from roehrich@localhost) by clink-eth.americas.sgi.com (SGI-8.9.3/8.9.3) id QAA67782 for linux-xfs@oss.sgi.com; Wed, 12 Sep 2001 16:28:31 -0500 (CDT) Date: Wed, 12 Sep 2001 16:28:31 -0500 (CDT) From: Dean Roehrich Message-Id: <200109122128.QAA67782@clink-eth.americas.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - put LGPL copyright on cmd/dmapi stuff. Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Wed Sep 12 14:28:18 PDT 2001 Workarea: clink-eth.americas.sgi.com:/data/clink/a67/roehrich/2.4.x-xfsA The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102694a cmd/dmapi/libdm/dm_session.c - 1.3 cmd/dmapi/libdm/dm_right.c - 1.3 cmd/dmapi/libdm/dm_region.c - 1.3 cmd/dmapi/libdm/dm_rdwr.c - 1.3 cmd/dmapi/libdm/dm_mountinfo.c - 1.3 cmd/dmapi/libdm/dm_hole.c - 1.3 cmd/dmapi/libdm/dm_handle2path.c - 1.6 cmd/dmapi/libdm/dm_handle.c - 1.3 cmd/dmapi/libdm/dm_event.c - 1.3 cmd/dmapi/libdm/dm_dmattr.c - 1.3 cmd/dmapi/libdm/dm_config.c - 1.3 cmd/dmapi/libdm/dm_bulkattr.c - 1.3 cmd/dmapi/libdm/dm_attr.c - 1.3 cmd/dmapi/libdm/dmapi_lib.c - 1.5 cmd/dmapi/libdm/dmapi_lib.h - 1.2 cmd/dmapi/debian/copyright - 1.2 - No Message Supplied From owner-linux-xfs@oss.sgi.com Wed Sep 12 14:32:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CLW3V20281 for linux-xfs-outgoing; Wed, 12 Sep 2001 14:32:03 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CLW1e20260 for ; Wed, 12 Sep 2001 14:32:01 -0700 Received: from clink-eth.americas.sgi.com (clink-eth.americas.sgi.com [128.162.2.8]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8CLVt502613 for ; Wed, 12 Sep 2001 14:31:56 -0700 Received: (from roehrich@localhost) by clink-eth.americas.sgi.com (SGI-8.9.3/8.9.3) id QAA03997 for linux-xfs@oss.sgi.com; Wed, 12 Sep 2001 16:30:36 -0500 (CDT) Date: Wed, 12 Sep 2001 16:30:36 -0500 (CDT) From: Dean Roehrich Message-Id: <200109122130.QAA03997@clink-eth.americas.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - put LGPL copyright on cmd/xfsprogs/libhandle Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Wed Sep 12 14:30:26 PDT 2001 Workarea: clink-eth.americas.sgi.com:/data/clink/a67/roehrich/2.4.x-xfsA The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102695a cmd/xfsprogs/libhandle/handle.c - 1.6 cmd/xfsprogs/libhandle/jdm.c - 1.3 cmd/xfsprogs/doc/COPYING - 1.2 - No Message Supplied From owner-linux-xfs@oss.sgi.com Wed Sep 12 15:31:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CMVja21494 for linux-xfs-outgoing; Wed, 12 Sep 2001 15:31:45 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CMVee21475 for ; Wed, 12 Sep 2001 15:31:40 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8CMVYJ20675 for ; Wed, 12 Sep 2001 15:31:35 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2943147; Wed, 12 Sep 2001 17:30:18 -0500 (CDT) Received: from lord.americas.sgi.com (lord.americas.sgi.com [128.162.187.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA83758; Wed, 12 Sep 2001 17:30:18 -0500 (CDT) Received: from lord.americas.sgi.com by lord.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f8CMUGv02195; Wed, 12 Sep 2001 17:30:16 -0500 Message-Id: <200109122230.f8CMUGv02195@lord.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: stimits@idcomm.com cc: "XFS: linux-xfs@oss.sgi.com" Subject: Re: lock files after crash In-Reply-To: Message from "D. Stimits" of "Wed, 12 Sep 2001 15:18:32 MDT." <3B9FD128.AFD7CB83@idcomm.com> Date: Wed, 12 Sep 2001 17:30:16 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > "D. Stimits" wrote: > > > > I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based > > (root is XFS). I had a crash at the moment I attempted to start login as > > a regular user (home is also XFS). It seems that ~/.ICEauthority is > > written each session when gdm/gnome is used for the login session, and > > that a check is done for whether or not .ICEauthority can be locked. > > After a crash, the file is empty (this is ok, it's the metadata versus > > full journal thing, it isn't an issue), since the crash occurs during > > that file write. However, after coming back up, X11 will fail due to an > > inability to lock the file. A question occurs here, whether lock data or > > whatever information is used to determine if a file can be locked, is > > part of the filesystem journaling? Or is this a separate issue that > > can't be dealth with by journaling filesystems? Is there any way XFS, > > coming back after a crash, can remove stale locks or bogus locks? I have > > no idea if this is entirely just coincidence it occurs, or if XFS itself > > can help recover under such circumstances. > > > > D. Stimits, stimits@idcomm.com > > Since nobody has said anything, let me rephrase the question. There are > custom lock file schemes, which I am not interested in. There *is* fcntl > to perform locking. Ignoring lock files, is there any metadata or > filesystem data that is altered when using fcntl to lock? If so, it is a > "bad thing" to preserve locked status upon recovery...it should be > cleared, else the file can't be reopened and locked. During recovery, it > can be assumed that the original application no longer should have a > lock...it's long dead. I did respond - twice, but I am operating on a temporary workstation here due to a head crash and my mail setup appears not to be all it could be. In my first message I said: >> Usually part of the start up process of a system should be to clean up >> the junk left behind by the last shutdown/crash/power outage. I >> suspect this is really a case of the cleanup not being there, or of >> the logic in X being a little flakey, the file exists, ergo.... >> >> The only part a filesystem plays in file locking in linux is to store >> the bit in the mode word of the inode that mandatory locking should be >> used, all the rest of the code is above the filesystem level. In my second response, I looked more closely at the code and wrote this: >> There appears to be no filesystem involvement in file locks via fcntl, >> there is no call into filesystem code from the file locking fcntl, so >> I do not see an XFS issue here. Steve > > D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Wed Sep 12 16:47:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8CNluu23234 for linux-xfs-outgoing; Wed, 12 Sep 2001 16:47:56 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8CNlpe23188 for ; Wed, 12 Sep 2001 16:47:51 -0700 Received: from idcomm.com (IDENT:qtuklYToD4LsI97eoHHQWvfJU36y0gct@x2-pip67.idcomm.com [209.60.72.78]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f8CNwSQ29476 for ; Wed, 12 Sep 2001 17:58:29 -0600 Message-ID: <3B9FF4A5.353C87C5@idcomm.com> Date: Wed, 12 Sep 2001 17:49:57 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: "XFS: linux-xfs@oss.sgi.com" Subject: Re: lock files after crash References: <200109122230.f8CMUGv02195@lord.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: > > > "D. Stimits" wrote: > > > > > > I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based > > > (root is XFS). I had a crash at the moment I attempted to start login as > > > a regular user (home is also XFS). It seems that ~/.ICEauthority is > > > written each session when gdm/gnome is used for the login session, and > > > that a check is done for whether or not .ICEauthority can be locked. > > > After a crash, the file is empty (this is ok, it's the metadata versus > > > full journal thing, it isn't an issue), since the crash occurs during > > > that file write. However, after coming back up, X11 will fail due to an > > > inability to lock the file. A question occurs here, whether lock data or > > > whatever information is used to determine if a file can be locked, is > > > part of the filesystem journaling? Or is this a separate issue that > > > can't be dealth with by journaling filesystems? Is there any way XFS, > > > coming back after a crash, can remove stale locks or bogus locks? I have > > > no idea if this is entirely just coincidence it occurs, or if XFS itself > > > can help recover under such circumstances. > > > > > > D. Stimits, stimits@idcomm.com > > > > Since nobody has said anything, let me rephrase the question. There are > > custom lock file schemes, which I am not interested in. There *is* fcntl > > to perform locking. Ignoring lock files, is there any metadata or > > filesystem data that is altered when using fcntl to lock? If so, it is a > > "bad thing" to preserve locked status upon recovery...it should be > > cleared, else the file can't be reopened and locked. During recovery, it > > can be assumed that the original application no longer should have a > > lock...it's long dead. > > I did respond - twice, but I am operating on a temporary workstation here > due to a head crash and my mail setup appears not to be all it could be. > > In my first message I said: > > >> Usually part of the start up process of a system should be to clean up > >> the junk left behind by the last shutdown/crash/power outage. I > >> suspect this is really a case of the cleanup not being there, or of > >> the logic in X being a little flakey, the file exists, ergo.... > >> > >> The only part a filesystem plays in file locking in linux is to store > >> the bit in the mode word of the inode that mandatory locking should be > >> used, all the rest of the code is above the filesystem level. > > In my second response, I looked more closely at the code and wrote this: > > >> There appears to be no filesystem involvement in file locks via fcntl, > >> there is no call into filesystem code from the file locking fcntl, so > >> I do not see an XFS issue here. > > Steve > > > > > D. Stimits, stimits@idcomm.com Is it safe then to say that "...mode word of the inode that mandatory locking should be used..." does not actually get preserved in the metadata? It could be apples and oranges comparison, that mandatory locking should be used, versus actual storage of a bit that says locking has occurred...therefore is it correct that the mandatory locking bit does not actually preserve the idea that a file is currently locked or not locked? If it does preserve anything about the currently locked state, it should probably be cleared after a recovery (it's hard to have a file locked during a recovery...it would be fairly safe to assume no process is actually locking it). D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Wed Sep 12 17:59:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D0xsV24662 for linux-xfs-outgoing; Wed, 12 Sep 2001 17:59:54 -0700 Received: from shakti.rupa.com (cx838204-a.alsv1.occa.home.com [24.16.83.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D0xle24642 for ; Wed, 12 Sep 2001 17:59:48 -0700 Received: by shakti.rupa.com (Postfix, from userid 500) id 92804C0098; Wed, 12 Sep 2001 17:59:41 -0700 (PDT) To: linux-xfs@oss.sgi.com Subject: Unable to mount crashed RAID1: bad clientid From: Rupa Schomaker Mail-Copies-To: never Date: Wed, 12 Sep 2001 17:59:41 -0700 Message-ID: Lines: 43 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- After a hard crash under heavy read IO (write to tape) I was unable to mount my /home filesystem (not where the heavy IO was happending). System: Athlon system with VIA motherboard (maybe the root cause of my problems) 4 maxtor 40G drives in two RAID1 40G mirrors. LVM with 1 volume group that spans the two RAID1 slices. /home is in one of the logical volumes in the volume group. Kernel: Debian 2.4.5 + xfs 1.0.1 patches. My kern.log shows: Sep 12 17:07:08 shakti kernel: Starting XFS recovery on filesystem: lvm(58,1) (d ev: 58/1) Sep 12 17:07:08 shakti kernel: XFS: xlog_recover_process_data: bad clientid Sep 12 17:07:08 shakti kernel: XFS: log mount/recovery failed Sep 12 17:07:08 shakti kernel: XFS: log mount failed I "fixed" this by doing a xfs_repair in single user mode. - -- - -rupa -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv Comment: Processed by Mailcrypt 3.5.6, an Emacs/PGP interface iQEVAwUBO6AE9nHDM4ucEopdAQGtrQf/TyvOJPXQq401SZZ54geg31x2Lxkg8kyD Vafi23bxP69TLUTyMN4wydayYX04OEIM6rb6rLsIS0I9qiDz7bvxTzoYAh3C/eGv 1c7hQ+R6sN4Ei4g+A0Y5UpzyqrNRkD0pmuELkyU3xM2G5dS4zbRAtRuPNwUo2q65 TNk22lynfMI8wEjfkYCvnejDkZsw3drVyb2mFGpcscKQtOn+D5J7RWW0lpxe2mwB 0mjJ3MMXqST9PmqTL403w4Hz/yQRRFPdza0HiaySO42SvtAqvdpzMNfiMdHw46I9 9ainap6B3qg3bVqDh3Wz8o+Qovo/RQAvdordqtQLJcq0MahmJpCr8Q== =ZjJ4 -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Wed Sep 12 21:55:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D4tLl28132 for linux-xfs-outgoing; Wed, 12 Sep 2001 21:55:21 -0700 Received: from aquaman.rsp.com.au (unused.rsp.com.au [150.101.94.74] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D4tHe28113 for ; Wed, 12 Sep 2001 21:55:17 -0700 Received: from [10.5.0.31] (borat.rsp.com.au [10.5.0.31]) by aquaman.rsp.com.au (8.11.2/8.11.2) with ESMTP id f8D4tAq03953 for ; Thu, 13 Sep 2001 14:25:10 +0930 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Thu, 13 Sep 2001 14:25:11 +0930 Subject: RH 7.1 & XFS 1.0.1 on SGI 1200 (AIC7xxx hang) From: Tony Clark To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, I've seen mention of this a number of times on the list, but haven't managed to dig up a solution. Please excuse my repetition of the issue. I have a stack of SGI 1200's with 2 x P3 cpus. I can successfully use the XFS 1.0 install disk, but the 1.0.1 disk hangs at the AIC7xxx point. Is there actually a way to make it move past this point using options in lilo, or should I abandon ship and use the 1.0 installer. Thanks, Tony -- Tony Clark e: tony@rsp.com.au Rising Sun Pictures t: +61 8 8364 6074 Adelaide / Sydney f: +61 8 8364 6075 Australia w: http://www.rsp.com.au/ From owner-linux-xfs@oss.sgi.com Wed Sep 12 21:58:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D4wEh28333 for linux-xfs-outgoing; Wed, 12 Sep 2001 21:58:14 -0700 Received: from sa-bwmail1.storageapps.com (smtp.storageapps.com [63.101.83.13]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D4wAe28313 for ; Wed, 12 Sep 2001 21:58:10 -0700 Received: by SA-BWMAIL1 with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Sep 2001 00:56:38 -0400 Message-ID: <23D04BDBA646D411BDDD00D0B774B53902963E49@SA-BWMAIL1> From: "Christian, Chip" To: "Linux XFS (E-mail)" Subject: xfs_repair problems Date: Thu, 13 Sep 2001 00:56:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk All, I'm having trouble at a customer site, where they run RedHat Linux 7.1, XFS 1.0.1 2.4.3 kernel, mounting through RedHat's multipath driver. Linux nas1 2.4.3-SGI_XFS_1.0.1 #1 SMP Thu Aug 30 15:50:24 EDT 2001 i686 unknown Two things happened tonight, not sure yet what was done to cause it, but: the box was refusing to mount three filesystems, claiming duplicate UUIDs. solved this by running xfs_admin -U generate one of the filesystems has a corrupt lost+found; xfs_repair can't fix it: [root@nas2 /]# ls -l /nas2/disk211 ls: /nas2/disk211/lost+found: No such file or directory ls: /nas2/disk211/lost+found: No such file or directory total 12 dr-xr-xr-x 28 root root 4096 Sep 12 09:41 admin drwxr-xr-x 3 root bin 22 Jul 30 10:39 home ... [root@nas2 /]# xfs_repair /dev/md30 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 imap claims a free inode 5700 is in use, correcting imap and clearing inode - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - clear lost+found (if it exists) ... - clearing existing "lost+found" inode - deleting existing "lost+found" entry - clearing existing "lost+found" inode - deleting existing "lost+found" entry xfs_repair: phase4.c:1022: delete_orphanage: Assertion `(res == 0 && dirty == 0) || (res == 1 && dirty == 1)' failed. Aborted (core dumped) From owner-linux-xfs@oss.sgi.com Wed Sep 12 22:08:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D580G28597 for linux-xfs-outgoing; Wed, 12 Sep 2001 22:08:00 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D57ve28578 for ; Wed, 12 Sep 2001 22:07:57 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8D57q525688 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Wed, 12 Sep 2001 22:07:52 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id WAA48200 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Wed, 12 Sep 2001 22:07:51 -0700 (PDT) Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id HAA429579 for ; Thu, 13 Sep 2001 07:07:46 +0200 (CEST) mail_from (ajag@snort.melbourne.sgi.com) Received: (from ajag@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id PAA00706 for linux-xfs@oss.sgi.com; Thu, 13 Sep 2001 15:06:30 +1000 (EST) Date: Thu, 13 Sep 2001 15:06:30 +1000 (EST) From: Andrew Gildfind Message-Id: <200109130506.PAA00706@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - Improvement request for xfsdump/xfsrestore exit codes Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Incorporate irix6.5f-melb:eoe:06423a from IRIX... Date: Wed Sep 12 22:05:22 PDT 2001 Workarea: snort.melbourne.sgi.com:/home/ajag/isms/slinx The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102719a cmd/xfsdump/common/stream.c - 1.5 - remove MLOG_BARE flags to mlog() cmd/xfsdump/common/qlock.c - 1.3 - change getpid's back to get_pid, remove MLOG_BARE flags, fix mlog_get_hint assert for single-stream/miniroot cmd/xfsdump/common/mlog.c - 1.5 - remove locking from stream_getix, cleanup, comments From owner-linux-xfs@oss.sgi.com Wed Sep 12 22:29:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D5T0q28966 for linux-xfs-outgoing; Wed, 12 Sep 2001 22:29:00 -0700 Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.133]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D5Sve28946 for ; Wed, 12 Sep 2001 22:28:57 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp7.xs4all.nl (8.9.3/8.9.3) with ESMTP id HAA04644; Thu, 13 Sep 2001 07:27:17 +0200 (CEST) Message-Id: <4.3.2.7.2.20010913072344.04338058@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 13 Sep 2001 07:26:53 +0200 To: Tony Clark , From: Seth Mos Subject: Re: RH 7.1 & XFS 1.0.1 on SGI 1200 (AIC7xxx hang) In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 14:25 13-9-2001 +0930, Tony Clark wrote: >Hello, > >I've seen mention of this a number of times on the list, but haven't managed >to dig up a solution. Please excuse my repetition of the issue. > >I have a stack of SGI 1200's with 2 x P3 cpus. I can successfully use the >XFS 1.0 install disk, but the 1.0.1 disk hangs at the AIC7xxx point. IIRC you should use the update disk that is available on the ftp site. >Is there actually a way to make it move past this point using options in >lilo, or should I abandon ship and use the 1.0 installer. Hmm, it might be related the noapic option although I don't remember the exact syntax. Head on over to the FAQ or the mailinglist page, there is a link to a searchable mail archive there. I think searching for this type of machine in the list will turn op some results. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Sep 12 22:37:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D5bSn29230 for linux-xfs-outgoing; Wed, 12 Sep 2001 22:37:28 -0700 Received: from aquaman.rsp.com.au (unused.rsp.com.au [150.101.94.74] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D5bNe29210 for ; Wed, 12 Sep 2001 22:37:23 -0700 Received: from [10.5.0.31] (borat.rsp.com.au [10.5.0.31]) by aquaman.rsp.com.au (8.11.2/8.11.2) with ESMTP id f8D5b9q04241; Thu, 13 Sep 2001 15:07:09 +0930 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Thu, 13 Sep 2001 15:07:09 +0930 Subject: Re: RH 7.1 & XFS 1.0.1 on SGI 1200 (AIC7xxx hang) From: Tony Clark To: Seth Mos , Message-ID: In-Reply-To: <4.3.2.7.2.20010913072344.04338058@pop.xs4all.nl> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk on 13/9/01 2:56 PM, Seth Mos at knuffie@xs4all.nl wrote: > At 14:25 13-9-2001 +0930, Tony Clark wrote: >> Hello, >> >> I've seen mention of this a number of times on the list, but haven't managed >> to dig up a solution. Please excuse my repetition of the issue. >> >> I have a stack of SGI 1200's with 2 x P3 cpus. I can successfully use the >> XFS 1.0 install disk, but the 1.0.1 disk hangs at the AIC7xxx point. > > IIRC you should use the update disk that is available on the ftp site. I tried, but it never gets to the point where it loads the update disk, and hangs at the point of loading the aic7xxx driver. > >> Is there actually a way to make it move past this point using options in >> lilo, or should I abandon ship and use the 1.0 installer. > > Hmm, it might be related the noapic option although I don't remember the > exact syntax. > Head on over to the FAQ or the mailinglist page, there is a link to a > searchable mail archive there. > > I think searching for this type of machine in the list will turn op some > results. > Hmmm... This was posted: On 18 Jul 2001 15:46:48 -0400, Doug Ledford wrote: > > When using my boot disk, you have to use the "apic" option, not the "noapic" > option. but with no mention of how to use this option. I'll try a little more and see if anything can be made to happen. If anyone who knows how to make this go away, I'd appreciate the assistance. Thanks, Tony From owner-linux-xfs@oss.sgi.com Wed Sep 12 23:02:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D62Df29678 for linux-xfs-outgoing; Wed, 12 Sep 2001 23:02:13 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D627e29658 for ; Wed, 12 Sep 2001 23:02:07 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8D620527473 for ; Wed, 12 Sep 2001 23:02:00 -0700 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id QAA90272; Thu, 13 Sep 2001 16:00:38 +1000 (EST) Date: Thu, 13 Sep 2001 16:00:38 +1000 (EST) From: Nathan Scott Message-Id: <200109130600.QAA90272@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Cc: ag@bestbits.at Subject: TAKE - attr Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a work in progress and is not useful to anyone yet (unless your name is Andreas or Nathan). Eventually this will become the new EA userspace, but there's plenty to be done yet. No kernel support is being made available at this stage as its not all done. cheers. Date: Wed Sep 12 22:53:23 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/attr-linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102721a cmd/attr2/Makefile - 1.1 cmd/attr2/Makepkgs - 1.1 cmd/attr2/README - 1.1 cmd/attr2/VERSION - 1.1 cmd/attr2/attr/Makefile - 1.1 cmd/attr2/attr/attr.c - 1.1 cmd/attr2/build/Makefile - 1.1 cmd/attr2/build/rpm/Makefile - 1.1 cmd/attr2/build/rpm/attr.spec.in - 1.1 cmd/attr2/build/rpm/macros.template - 1.1 cmd/attr2/build/rpm/rpm-2.rc.template - 1.1 cmd/attr2/build/tar/Makefile - 1.1 cmd/attr2/configure.in - 1.1 cmd/attr2/debian/Makefile - 1.1 cmd/attr2/debian/changelog - 1.1 cmd/attr2/debian/control - 1.1 cmd/attr2/debian/copyright - 1.1 cmd/attr2/debian/rules - 1.1 cmd/attr2/doc/CHANGES - 1.1 cmd/attr2/doc/COPYING - 1.1 cmd/attr2/doc/INSTALL - 1.1 cmd/attr2/doc/Makefile - 1.1 cmd/attr2/doc/PORTING - 1.1 cmd/attr2/getfattr/Makefile - 1.1 cmd/attr2/getfattr/getfattr.c - 1.1 cmd/attr2/getfattr/walk_tree.c - 1.1 cmd/attr2/getfattr/walk_tree.h - 1.1 cmd/attr2/include/Makefile - 1.1 cmd/attr2/include/attributes.h - 1.1 cmd/attr2/include/builddefs.in - 1.1 cmd/attr2/include/buildrules - 1.1 cmd/attr2/include/extattr.h - 1.1 cmd/attr2/include/syscalls.h - 1.1 cmd/attr2/install-sh - 1.1 cmd/attr2/libattr/Makefile - 1.1 cmd/attr2/libattr/libattr.c - 1.1 cmd/attr2/man/Makefile - 1.1 cmd/attr2/man/man1/Makefile - 1.1 cmd/attr2/man/man1/attr.1 - 1.1 cmd/attr2/man/man1/getfattr.1 - 1.1 cmd/attr2/man/man1/setfattr.1 - 1.1 cmd/attr2/man/man2/Makefile - 1.1 cmd/attr2/man/man2/extattr.2 - 1.1 cmd/attr2/man/man3/Makefile - 1.1 cmd/attr2/man/man3/attr_get.3 - 1.1 cmd/attr2/man/man3/attr_list.3 - 1.1 cmd/attr2/man/man3/attr_multi.3 - 1.1 cmd/attr2/man/man3/attr_remove.3 - 1.1 cmd/attr2/man/man3/attr_set.3 - 1.1 cmd/attr2/setfattr/Makefile - 1.1 cmd/attr2/setfattr/setfattr.c - 1.1 - temporary development version of the extended attribute code. From owner-linux-xfs@oss.sgi.com Thu Sep 13 00:56:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D7uHt31306 for linux-xfs-outgoing; Thu, 13 Sep 2001 00:56:17 -0700 Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D7uEe31287 for ; Thu, 13 Sep 2001 00:56:14 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.195]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8D7u5Q22251 for ; Thu, 13 Sep 2001 16:56:05 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8D7u3c23833 for ; Thu, 13 Sep 2001 16:56:03 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id f8D7u2F05006 for ; Thu, 13 Sep 2001 16:56:02 +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 AAA280 for ; Thu, 13 Sep 2001 16:56:01 +0900 Received: FROM mailsv.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Thu Sep 13 16:56:00 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by mailsv.tnes.nec.co.jp (8.9.3/3.7W01031510) with ESMTP id QAA96932 for ; Thu, 13 Sep 2001 16:56:01 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f8D7u0L17955 for ; Thu, 13 Sep 2001 16:56:00 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id QAA08490; Thu, 13 Sep 2001 16:56:00 +0900 (JST) Message-Id: <200109130756.QAA08490@tagajo.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: xfs_estimate Date: Thu, 13 Sep 2001 16:56:00 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi there, First of all, thank you for your time to explain xfsdump. I am happy to know about it. Thanks. Today, I have a little question - the default log size of xfs_estimate. The man data of xfs_estimate says it is 10MB, but "xfs_estimate -v foo" says it is 4096000. Which is correct? Cheers. Takayuki From owner-linux-xfs@oss.sgi.com Thu Sep 13 01:36:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D8aAT32035 for linux-xfs-outgoing; Thu, 13 Sep 2001 01:36:10 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D8a8e32016 for ; Thu, 13 Sep 2001 01:36:08 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f8D8a2505920 for ; Thu, 13 Sep 2001 01:36:02 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA22700; Thu, 13 Sep 2001 19:34:44 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA10274; Thu, 13 Sep 2001 18:34:44 +1000 (AEDT) Date: Thu, 13 Sep 2001 18:34:43 +1000 From: Nathan Scott To: Takayuki Sasaki Cc: linux-xfs@oss.sgi.com Subject: Re: xfs_estimate Message-ID: <20010913183443.A332417@wobbly.melbourne.sgi.com> References: <200109130756.QAA08490@tagajo.bsd.tnes.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109130756.QAA08490@tagajo.bsd.tnes.nec.co.jp>; from sasaki@bsd.tnes.nec.co.jp on Thu, Sep 13, 2001 at 04:56:00PM +0900 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Sep 13, 2001 at 04:56:00PM +0900, Takayuki Sasaki wrote: > Hi there, > > First of all, thank you for your time to explain xfsdump. > I am happy to know about it. Thanks. > > Today, I have a little question - the default log size of > xfs_estimate. The man data of xfs_estimate says it is 10MB, but > "xfs_estimate -v foo" says it is 4096000. Which is correct? > >From a quick look in the code, it seems the man page is incorrect - the default logsize is 4096 (default blksize) multiplied by 1000 (default log length). xfs_estimate -v -i 4000k xxx ... seems to confirm this. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 13 01:39:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D8dhf32194 for linux-xfs-outgoing; Thu, 13 Sep 2001 01:39:43 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D8dee32175 for ; Thu, 13 Sep 2001 01:39:40 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f8D8dYJ01222 for ; Thu, 13 Sep 2001 01:39:34 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA22710; Thu, 13 Sep 2001 19:38:18 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA57053; Thu, 13 Sep 2001 18:38:17 +1000 (AEDT) Date: Thu, 13 Sep 2001 18:38:16 +1000 From: Nathan Scott To: "Christian, Chip" Cc: "Linux XFS (E-mail)" Subject: Re: xfs_repair problems Message-ID: <20010913183816.B332417@wobbly.melbourne.sgi.com> References: <23D04BDBA646D411BDDD00D0B774B53902963E49@SA-BWMAIL1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <23D04BDBA646D411BDDD00D0B774B53902963E49@SA-BWMAIL1>; from chip.christian@storageapps.com on Thu, Sep 13, 2001 at 12:56:38AM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Thu, Sep 13, 2001 at 12:56:38AM -0400, Christian, Chip wrote: > All, > > xfs_repair: phase4.c:1022: delete_orphanage: Assertion `(res == 0 && dirty == 0) > || (res == 1 && dirty == 1)' failed. > Aborted (core dumped) > Its not immediately obvious what the problem is - any chance you can send me me the core file and your xfs_repair binary? (or put them somewhere I can download them?) That'll provide some more clues. thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 13 01:42:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D8gKf32346 for linux-xfs-outgoing; Thu, 13 Sep 2001 01:42:20 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D8gGe32326 for ; Thu, 13 Sep 2001 01:42:17 -0700 Received: from yavin (yavin.pdc.kth.se [130.237.221.61]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id BAA01006 for ; Thu, 13 Sep 2001 01:42:09 -0700 (PDT) mail_from (nico@pdc.kth.se) Received: from nico by yavin with local (Exim 3.33 #1 (Debian)) id 15hRuk-0006ux-00 for ; Thu, 13 Sep 2001 10:32:02 +0200 Date: Thu, 13 Sep 2001 10:32:02 +0200 To: linux-xfs@oss.sgi.com Subject: lots of inodes... Message-ID: <20010913103202.F26100@yavin.pdc.kth.se> Reply-To: nico@pdc.kth.se Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.20i From: Niklas Jakobsson Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello! I have been testing xfs for linux a couple of day now and I'm quite happy with it, I have a couple of questions though. I ran a test program, a small hack that creates 128000 1K files. After a while it crashed when it could to create any more files. loon:/mnt/scr2/pek/files2>time ./inodemauler 131072 1024 inodemauler : Could not create file: Illegal seek The filesystem looked like this right after I ran the program. loon:/mnt/scr2/pek/files2>df -i . Filesystem Inodes IUsed IFree IUse% Mounted on /dev/hdc1 69104 68864 240 100% /mnt/scr2 I then waited a while and then I suddenly had a _lot_ of inodes: loon# df -i /mnt/scr2/ Filesystem Inodes IUsed IFree IUse% Mounted on /dev/hdc1 75068224 46765 75021459 1% /mnt/scr2 It looks like it has maxed out the number of inodes, 256 bytes/inode * 75000000 =~ 25 % of my 75 Gb filesystem. So there are two questions: 1. Shouldn't it block the program until it has created more inodes? 2. Why did it create so many inodes? Shouldn't it have taken smaller steps? /Nico From owner-linux-xfs@oss.sgi.com Thu Sep 13 01:46:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D8kQM32548 for linux-xfs-outgoing; Thu, 13 Sep 2001 01:46:26 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D8kCe32523 for ; Thu, 13 Sep 2001 01:46:13 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id KAA03690; Thu, 13 Sep 2001 10:45:35 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id KAA12219; Thu, 13 Sep 2001 10:45:06 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id D14B257306; Thu, 13 Sep 2001 10:44:28 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id C88C525835; Thu, 13 Sep 2001 10:44:28 +0200 (CEST) Message-ID: <3BA071EC.D9BE8E22@ch.sauter-bc.com> Date: Thu, 13 Sep 2001 10:44:28 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Adrian Head , linux-xfs@oss.sgi.com Subject: Re: Problems with many processes copying large directories acrossan XFS volume. References: <3B9CCE00.D704DC0B@ch.sauter-bc.com> <3B9DA493.11CD4C16@ch.sauter-bc.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter schrieb: > > Simon Matter schrieb: > > > > Adrian Head schrieb: > > > > > > Thanks for your reply Simon > > > > > > Yes the softraid was fully synced before I started any test. > > > > > > The XFS patch I used to obtain these errors was > > > patch-2.4.9-xfs-2001-08-19 and the errors were: > > > Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 > > > Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device > > > > > > When I used a later version of the XFS patch I had more descriptive > > > errors written to /var/log/messages: > > > Sep 10 10:14:57 ATLAS kernel: I/O error in filesystem ("md(9,0)") > > > meta-data dev 0x900 block 0x9802bdc > > > Sep 10 10:14:57 ATLAS kernel: (xlog_iodone") error 5 buf count 32768 > > > Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called > > > from line 940 of file xfs_log.c. Return address - 0xd8cb66f8 > > > Sep 10 10:14:57 ATLAS kernel: Log I/O Error Detected. Shutting down > > > filesystem: md(9,0) > > > Sep 10 10:14:57 ATLAS kernel: Please umount the filesystem, and rectify > > > the problem(s) > > > Sep 10 10:14:57 ATLAS kernel: xfs_force_shutdown(md(9,0),0x2) called > > > from line 714 of file xfs_log.c. Return address = 0xd8cb65d3 > > > Sep 10 10:14:57 ATLAS kernel: attempt to access beyond end of device > > > Sep 10 10:14:57 ATLAS kernel: 02:82: rw=0, want=1602235696, limit=4 > > > > > > I did think at the time that it may have been issues with XFS stomping > > > all over raid code or raid code stomping all over XFS. Although I not > > > sure now as the 2.4.10-pre2-xfs-2001-09-02 patch never wrote any errors > > > out at all. (please see my 2nd post for more info) > > > > > > Thanks for taking the time to test this on your own machine. > > > > I tried 20, 40 and 80 simultanous cp with no crash. Then I changed the > > file tree and the new tree has ~280M small files with 100b-50kb size. > > When using 60 cp jobs the machine died. I could ping it but nothing > > more. No ssh, no console, no shutdown. I try some more tests tonight. I > > try the same with ext2 as well to make sure it's XFS and not Softraid. > > Update: I tried the 60 cp jobs on a ext2 filesystem and the system is > still alive but 58 of the 60 cp jobs are hanging. Well maybe the 2.4.3 > kernel is a bit old now... I'll try some more tests. I have just installed the 2.4.10-pre2 kernel from http://rpms.aicompro.net/ and tried my stresstest with 60 instances of cp and it has crashed as well. Not good. I'm not sure whether kdb is in those RPMS but when the machine hung I couldn't get into kdb (sysctl switch was on). Usually you can unblank the console by pressing shift or numlock but this time it was really dead. I'm now right now trying the same test on a non raid partition. Simon > > Simon > > > > > -Simon > > > > > > > > Adrian Head > > > Bytecomm P/L > > > > > > > -----Original Message----- > > > > From: Simon Matter [SMTP:simon.matter@ch.sauter-bc.com] > > > > Sent: Monday, 10 September 2001 17:45 > > > > To: adrian.head@bytecomm.com.au > > > > Cc: linux-xfs@oss.sgi.com > > > > Subject: Re: Problems with many processes copying large > > > > directories across an XFS volume. > > > > > > > > Hi Adrian > > > > > > > > I did similar tests two months ago. I was having problems as well but > > > > ufurtunately I don't remember what is was exactly. > > > > First question: You created Softraid5, was the raid synced when you > > > > started the tests? > > > > > > > > > In the /var/log/messages log around the same time as the copy test I > > > > get > > > > > entries like: > > > > > Sep 9 05:13:46 ATLAS kernel: 02:86: rw=0, want=156092516, limit=360 > > > > > Sep 9 05:13:46 ATLAS kernel: attempt to access beyond end of device > > > > > > > > This looks interesting. I don't know what this means exactly but it > > > > looks to me like you managed to create a filesystem bigger than the > > > > raid > > > > volume was? I got the very same error when I tried to restore data > > > > with > > > > xfsrestore from DAT (xfsrestore from DLT was fine). The issue is still > > > > open. > > > > > > > > I have a test system here with SoftRAID5 on 4 U160 SCSI disks. I'll > > > > try > > > > to kill it today with cp jobs. > > > > > > > > -Simon > > > > -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Thu Sep 13 01:53:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D8rMD00355 for linux-xfs-outgoing; Thu, 13 Sep 2001 01:53:22 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D8rKe00336 for ; Thu, 13 Sep 2001 01:53:20 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id BAA04966 for ; Thu, 13 Sep 2001 01:53:23 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA59565 for linux-xfs@oss.sgi.com; Thu, 13 Sep 2001 18:52:02 +1000 (EST) Date: Thu, 13 Sep 2001 18:52:02 +1000 (EST) From: Nathan Scott Message-Id: <200109130852.SAA59565@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - man page Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Fix typo. Date: Thu Sep 13 01:49:50 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102722a cmd/xfsdump/man/man8/xfs_estimate.8 - 1.2 - fix several typos and formatting problems. From owner-linux-xfs@oss.sgi.com Thu Sep 13 02:11:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D9BV201014 for linux-xfs-outgoing; Thu, 13 Sep 2001 02:11:31 -0700 Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D9BQe00995 for ; Thu, 13 Sep 2001 02:11:27 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.197]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8D9BPQ10801 for ; Thu, 13 Sep 2001 18:11:25 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8D9BOZ14181 for ; Thu, 13 Sep 2001 18:11:24 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id f8D9BOF29307 for ; Thu, 13 Sep 2001 18:11:24 +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 AAA302 for ; Thu, 13 Sep 2001 18:11:22 +0900 Received: FROM noshiro.bsd.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Thu Sep 13 18:11:21 2001 +0900 Received: from localhost (localhost [127.0.0.1]) by noshiro.bsd.tnes.nec.co.jp (Postfix) with ESMTP id A4DB5660C for ; Thu, 13 Sep 2001 18:11:21 +0900 (JST) To: linux-xfs@oss.sgi.com Subject: XFS ACL with NFS X-Mailer: Mew version 1.94.2 on XEmacs 21.4 (Artificial Intelligence) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010913181121F.masano@tnes.nec.co.jp> Date: Thu, 13 Sep 2001 18:11:21 +0900 (JST) From: ASANO Masahiro X-Dispatcher: imput version 20000228(IM140) Lines: 42 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Does acl of XFS work with NFS? I tested it but encountered the any of the following situations: 1. I/O error occured with a console message. 2. Permission denied error occured with a console message. 3. ACL was ignored. Any of them was not result as I expected, or am I wrong? Thanks in advance, Environment: Kernel: linux-2.4.10-pre8-xfs (20010912 CVS Tree) gcc: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) /mnt/xfs xfs (rw,biosize=16,usrquota,grpquota) /mnt/nfs localhost:/mnt/xfs on /mnt/nfs type nfs (rw,intr,nfsvers=3,addr=127.0.0.1) Results: user1$ chacl -l /mnt/xfs/aclfile /mnt/xfs/aclfile [u::rw-,g::rw-,o::rw-,m::rw-,u:user1:---] user1$ cat /mnt/xfs/aclfile cat: /mnt/xfs/aclfile: Permission denied user1$ cat /mnt/nfs/aclfile ... 1 fh_verify: //aclfile permission failure, acc=44, error=13 cat: /mnt/nfs/aclfile: Input/output error user1$ cat /mnt/nfs/aclfile ... 2 fh_verify: //aclfile permission failure, acc=44, error=13 cat: /mnt/nfs/aclfile: Permission denied user1$ su user2 user2$ cat /mnt/nfs/aclfile access ok user2$ exit exit user1$ cat /mnt/nfs/aclfile ... 3 access ok -- Masahiro Asano From owner-linux-xfs@oss.sgi.com Thu Sep 13 02:20:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D9KHT01289 for linux-xfs-outgoing; Thu, 13 Sep 2001 02:20:17 -0700 Received: from sa-bwmail1.storageapps.com (smtp.storageapps.com [63.101.83.13]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D9KAe01263 for ; Thu, 13 Sep 2001 02:20:10 -0700 Received: by SA-BWMAIL1 with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Sep 2001 05:18:38 -0400 Message-ID: <23D04BDBA646D411BDDD00D0B774B53902963E50@SA-BWMAIL1> From: "Christian, Chip" To: Nathan Scott Cc: "Linux XFS (E-mail)" Subject: RE: xfs_repair problems Date: Thu, 13 Sep 2001 05:18:37 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Cores sent in another message to Nathan... Furthermore, an hour or so later, they got the following Oops on the same box. They called me an hour after that. I have since rebooted. All filesystems are NFS exported sync,nowdelay. Sep 13 01:14:14 nas2 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000008 Sep 13 01:14:14 nas2 kernel: 801e9395 Sep 13 01:14:14 nas2 kernel: Oops: 0000 Sep 13 01:14:14 nas2 kernel: CPU: 0 Sep 13 01:14:14 nas2 kernel: EIP: 0010:[xfs_syncsub+2261/2976] Sep 13 01:14:14 nas2 kernel: EIP: 0010:[<801e9395>] Using defaults from ksymoops -t elf32-i386 -a i386 Sep 13 01:14:14 nas2 kernel: EFLAGS: 00010246 Sep 13 01:14:14 nas2 kernel: eax: bce0bbc0 ebx: a0ccc514 ecx: 00000000 edx: 00000000 Sep 13 01:14:14 nas2 kernel: esi: 00000000 edi: bce0bbc0 ebp: a0ccc514 esp: bfff5f00 Sep 13 01:14:14 nas2 kernel: ds: 0018 es: 0018 ss: 0018 Sep 13 01:14:14 nas2 kernel: Process kupdated (pid: 6, stackpage=bfff5000) Sep 13 01:14:14 nas2 kernel: Stack: a0ccc514 00000000 00000000 00000001 00000008 00000008 00000040 00000000 Sep 13 01:14:14 nas2 kernel: 00000000 00000000 00000001 bcd144a0 8252e108 00000246 803109e0 8252e000 Sep 13 01:14:14 nas2 kernel: 82585200 80239036 82585200 00000000 8034c800 80316360 80316000 bfff4000 Sep 13 01:14:14 nas2 kernel: Call Trace: [AAC_QueueCommand+22/48] [xfs_sync+21/32] [linvfs_write_super+39/48] [sync_supers+141/208] [schedule_timeout+139/176] Sep 13 01:14:14 nas2 kernel: Call Trace: [<80239036>] [<801e8ab5>] [<801f9197>][<801373ad>] [<8011178b>] Sep 13 01:14:14 nas2 kernel: [<8013625a>] [] [] [<8013659 8>] [<80105000>] [<801055a6>] Sep 13 01:14:14 nas2 kernel: [<80136480>] Sep 13 01:14:14 nas2 kernel: Code: 39 56 08 0f 85 42 f8 ff ff 8b 44 24 74 05 1401 00 00 50 e8 >>EIP; 801e9395 <===== Trace; 80239036 Trace; 801e8ab5 Trace; 801f9197 Trace; 801373ad <__wait_on_super+11d/160> Trace; 8011178b Trace; 8013625a Trace; ffff0018 Trace; ffff0018 Trace; 80136598 Trace; 80105000 Trace; 801055a6 Trace; 80136480 Code; 801e9395 00000000 <_EIP>: Code; 801e9395 <===== 0: 39 56 08 cmp %edx,0x8(%esi) <===== Code; 801e9398 3: 0f 85 42 f8 ff ff jne fffff84b <_EIP+0xfffff84b> 801e8be0 Code; 801e939e 9: 8b 44 24 74 mov 0x74(%esp,1),%eax Code; 801e93a2 d: 05 14 01 00 00 add $0x114,%eax Code; 801e93a7 12: 50 push %eax Code; 801e93a8 13: e8 00 00 00 00 call 18 <_EIP+0x18> 801e93ad 1 warning and 1 error issued. Results may not be reliable. -----Original Message----- From: Nathan Scott [mailto:nathans@sgi.com] Sent: Thursday, September 13, 2001 4:38 To: Christian, Chip Cc: Linux XFS (E-mail) Subject: Re: xfs_repair problems hi, On Thu, Sep 13, 2001 at 12:56:38AM -0400, Christian, Chip wrote: > All, > > xfs_repair: phase4.c:1022: delete_orphanage: Assertion `(res == 0 && dirty == 0) > || (res == 1 && dirty == 1)' failed. > Aborted (core dumped) > Its not immediately obvious what the problem is - any chance you can send me me the core file and your xfs_repair binary? (or put them somewhere I can download them?) That'll provide some more clues. thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 13 02:45:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8D9juH02026 for linux-xfs-outgoing; Thu, 13 Sep 2001 02:45:56 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8D9jke02007 for ; Thu, 13 Sep 2001 02:45:47 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id LAA27155 for ; Thu, 13 Sep 2001 11:45:25 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id LAA21742 for linux-xfs@oss.sgi.com; Thu, 13 Sep 2001 11:45:12 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id C5D6D57306 for ; Thu, 13 Sep 2001 11:44:36 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id AD98B25835 for ; Thu, 13 Sep 2001 11:44:36 +0200 (CEST) Message-ID: <3BA08004.A2FBC956@ch.sauter-bc.com> Date: Thu, 13 Sep 2001 11:44:36 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: Problems with many processes copying directories on XFS Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Can someone confirm what Adrian Head and me discussed in a previous thread? Im using the following script to reproduce crashes on 2.4.3-XFS-1.0.1 and on 2.4.10-pre2: #!/bin/sh max=$1 cnt=1 # count while [ $cnt -le $max ]; do # fill number if [ $cnt -ge 100 ]; then strcnt=$cnt fill="" elif [ $cnt -ge 10 ]; then strcnt=0$cnt fill=" " else strcnt=00$cnt fill=" " fi # do something cp -r src $strcnt & # tar cf $strcnt.tar src & # increment cnt=$[ cnt + 1 ] done I invoke it with './mkstress 60' to get 60 cp processes. The directory 'src' has 746 dirs with 30070 files. du -sm src gives 229M. File sizes are ~100b - 50k. Directory depth is 4 dirs max. I was having src on XFS on Softraid5 and on plain partition. No difference. It will just crash sooner or later. -Simon From owner-linux-xfs@oss.sgi.com Thu Sep 13 03:23:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DAN1v02747 for linux-xfs-outgoing; Thu, 13 Sep 2001 03:23:01 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DAMwe02728 for ; Thu, 13 Sep 2001 03:22:58 -0700 Received: from exocore.com ([202.4.185.25]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id DAA03481 for ; Thu, 13 Sep 2001 03:22:45 -0700 (PDT) mail_from (shanu@exocore.com) Received: (from shanu@localhost) by exocore.com (8.11.6/8.11.6) id f8DAHuk08326 for linux-xfs@oss.sgi.com; Thu, 13 Sep 2001 15:47:56 +0530 Date: Thu, 13 Sep 2001 15:47:56 +0530 From: Shanker Balan To: Linux-XFS Subject: XFS + EXt2 + ACL Message-ID: <20010913154756.A8265@exocore.com> Reply-To: Shanker Balan Mail-Followup-To: Linux-XFS Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organisation: Exocore Consulting (P) Ltd Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello: I have both ext2 and XFS partitions on my workstation and want to patch my XFS enabled kernel with the Bestbits Extended Attributes ACL patches for the ext2 file system. I am at http://acl.bestbits.at/download.html ATM and am uncertain as to what all i need to patch my XFS kernel with. If there is someone running Ext2+XFS+ACL with kernel 2.4.9, i would love to hear from you. Thank you for your time. -- Princess Leia: I'll be back. From owner-linux-xfs@oss.sgi.com Thu Sep 13 03:38:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DAc9Y03064 for linux-xfs-outgoing; Thu, 13 Sep 2001 03:38:09 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DAc5e03044 for ; Thu, 13 Sep 2001 03:38:05 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id A974263922 for ; Thu, 13 Sep 2001 11:34:33 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 13 Sep 2001 12:09:52 UT MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: XFS + EXt2 + ACL X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message Date: Thu, 13 Sep 2001 11:34:06 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: XFS + EXt2 + ACL Thread-Index: AcE8PiR+MBmbv/dNSZOfIp/2LsCtUwAAMlpw From: "Juer Lee" To: "Linux-XFS" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8DAc6e03045 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Shanker, I think you can't do that, I tried it here, there were many conflicts when patching them. And, I think the reason is: Check the code of /linux/fs/ext_attr.*, both EXT2 and XFS need to use it, so if you really want to use both of them, maybe you have to look into all the code :) Juer >-----Original Message----- >From: Shanker Balan [mailto:shanu@exocore.com] >Sent: 13 September 2001 11:18 >To: Linux-XFS >Subject: XFS + EXt2 + ACL > > >Hello: > >I have both ext2 and XFS partitions on my workstation and want to patch >my XFS enabled kernel with the Bestbits Extended Attributes ACL patches >for the ext2 file system. > >I am at http://acl.bestbits.at/download.html ATM and am uncertain as to >what all i need to patch my XFS kernel with. > >If there is someone running Ext2+XFS+ACL with kernel 2.4.9, i >would love >to hear from you. > >Thank you for your time. > >-- >Princess Leia: > I'll be back. > > From owner-linux-xfs@oss.sgi.com Thu Sep 13 03:39:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DAdFk03201 for linux-xfs-outgoing; Thu, 13 Sep 2001 03:39:15 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DAdCe03181 for ; Thu, 13 Sep 2001 03:39:12 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id DAA04997 for ; Thu, 13 Sep 2001 03:39:09 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id VAA23210; Thu, 13 Sep 2001 21:37:46 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id UAA83952; Thu, 13 Sep 2001 20:37:46 +1000 (AEDT) Date: Thu, 13 Sep 2001 20:37:45 +1000 From: Nathan Scott To: Shanker Balan Cc: Linux-XFS , Andreas Gruenbacher Subject: Re: XFS + EXt2 + ACL Message-ID: <20010913203745.B409120@wobbly.melbourne.sgi.com> References: <20010913154756.A8265@exocore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010913154756.A8265@exocore.com>; from shanu@exocore.com on Thu, Sep 13, 2001 at 03:47:56PM +0530 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Thu, Sep 13, 2001 at 03:47:56PM +0530, Shanker Balan wrote: > Hello: > > I have both ext2 and XFS partitions on my workstation and want to patch > my XFS enabled kernel with the Bestbits Extended Attributes ACL patches > for the ext2 file system. > > I am at http://acl.bestbits.at/download.html ATM and am uncertain as to > what all i need to patch my XFS kernel with. > > If there is someone running Ext2+XFS+ACL with kernel 2.4.9, i would love > to hear from you. I am currently running just such a beast. You do not want to go there ... its a little bit hairy. Wait for a couple of weeks or so - Andreas and I are busily working on consolidating our code bases even as we speak - and at the end of that process you will be able to mix and match our two sets of patches much more easily (and the user code will actually work with both, not one or the other). cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 13 03:44:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DAiTM03388 for linux-xfs-outgoing; Thu, 13 Sep 2001 03:44:29 -0700 Received: from exocore.com ([202.4.185.25]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DAiFe03369 for ; Thu, 13 Sep 2001 03:44:23 -0700 Received: (from shanu@localhost) by exocore.com (8.11.6/8.11.6) id f8DAid308611 for linux-xfs@oss.sgi.com; Thu, 13 Sep 2001 16:14:39 +0530 Date: Thu, 13 Sep 2001 16:14:39 +0530 From: Shanker Balan To: Linux-XFS Subject: Re: XFS + EXt2 + ACL Message-ID: <20010913161439.A8390@exocore.com> Reply-To: Shanker Balan Mail-Followup-To: Linux-XFS References: <20010913154756.A8265@exocore.com> <20010913203745.B409120@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010913203745.B409120@wobbly.melbourne.sgi.com>; from nathans@sgi.com on Thu, Sep 13, 2001 at 08:37:45PM +1000 Organisation: Exocore Consulting (P) Ltd Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello: Nathan Scott wrote, > I am currently running just such a beast. You do not want to > go there ... its a little bit hairy. LOL, i tried applying the patches, none applied cleanly! :) > Wait for a couple of weeks or so - Andreas and I are busily working on > consolidating our code bases even as we speak - and at the end of that > process you will be able to mix and match our two sets of patches much > more easily (and the user code will actually work with both, not one > or the other). I'll wait. :) Will this include GNU fileutils and other supporting programs or just the stuff in the kernel? -- Princess Leia: I'll be back. From owner-linux-xfs@oss.sgi.com Thu Sep 13 04:00:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DB0Hl03856 for linux-xfs-outgoing; Thu, 13 Sep 2001 04:00:17 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DB0Ee03837 for ; Thu, 13 Sep 2001 04:00:14 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id EAA11608 for ; Thu, 13 Sep 2001 04:00:18 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id VAA23288; Thu, 13 Sep 2001 21:58:56 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id UAA36430; Thu, 13 Sep 2001 20:58:56 +1000 (AEDT) Date: Thu, 13 Sep 2001 20:58:55 +1000 From: Nathan Scott To: Shanker Balan Cc: Linux-XFS Subject: Re: XFS + EXt2 + ACL Message-ID: <20010913205855.C409120@wobbly.melbourne.sgi.com> References: <20010913154756.A8265@exocore.com> <20010913203745.B409120@wobbly.melbourne.sgi.com> <20010913161439.A8390@exocore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010913161439.A8390@exocore.com>; from shanu@exocore.com on Thu, Sep 13, 2001 at 04:14:39PM +0530 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Thu, Sep 13, 2001 at 04:14:39PM +0530, Shanker Balan wrote: > Hello: > > Nathan Scott wrote, > > I am currently running just such a beast. You do not want to > > go there ... its a little bit hairy. > > LOL, i tried applying the patches, none applied cleanly! :) > > > Wait for a couple of weeks or so - Andreas and I are busily working on > > consolidating our code bases even as we speak - and at the end of that > > process you will be able to mix and match our two sets of patches much > > more easily (and the user code will actually work with both, not one > > or the other). > > I'll wait. :) > > Will this include GNU fileutils and other supporting programs or just > the stuff in the kernel? > Andreas' GNU fileutils patches will work for both ext2 and XFS after this. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 13 05:31:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DCVA705350 for linux-xfs-outgoing; Thu, 13 Sep 2001 05:31:10 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DCUxe05327 for ; Thu, 13 Sep 2001 05:30:59 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id OAA15827 for ; Thu, 13 Sep 2001 14:30:33 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id OAA05307 for linux-xfs@oss.sgi.com; Thu, 13 Sep 2001 14:30:07 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 536BF57306 for ; Thu, 13 Sep 2001 14:29:46 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 36AB525835 for ; Thu, 13 Sep 2001 14:29:46 +0200 (CEST) Message-ID: <3BA0A6BA.84D64FE1@ch.sauter-bc.com> Date: Thu, 13 Sep 2001 14:29:46 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: Re: Problems with many processes copying directories on XFS References: <3BA08004.A2FBC956@ch.sauter-bc.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter schrieb: > > Can someone confirm what Adrian Head and me discussed in a previous > thread? > > Im using the following script to reproduce crashes on 2.4.3-XFS-1.0.1 > and on 2.4.10-pre2: > > #!/bin/sh > > max=$1 > > cnt=1 > # count > while [ $cnt -le $max ]; do > # fill number > if [ $cnt -ge 100 ]; then > strcnt=$cnt > fill="" > elif [ $cnt -ge 10 ]; then > strcnt=0$cnt > fill=" " > else > strcnt=00$cnt > fill=" " > fi > # do something > cp -r src $strcnt & > # tar cf $strcnt.tar src & > # increment > cnt=$[ cnt + 1 ] > done > > I invoke it with './mkstress 60' to get 60 cp processes. The directory > 'src' has 746 dirs with 30070 files. du -sm src gives 229M. File sizes > are ~100b - 50k. Directory depth is 4 dirs max. > I was having src on XFS on Softraid5 and on plain partition. No > difference. It will just crash sooner or later. > > -Simon Well since nobody seems interested I'm replying myself. I didn't realize that I created a filesystem with more than 1.8 mio files with my 'stress test'. Is it dangerous? I mean if I reach any limit the machine should not crash or hang but should say something like 'can not allocate ...'? Well I tried with XFS on Softraid and without Raid, I tried the same with ext2 and did not get a kernel crash but 58 hanging cp processes. I now tried the same on my laptop with kernel 2.2.19 on ReiserFS and I was surprised: The copy went quite fast and everything semmed fine. Then I tried 'diff -r src 065' and got 3 differing files. I tried other dirs and the same. Okay something goes wrong here as well but now I want to see the ReiserFS deletion speed. 'rm -rf 0*' should go fast but - surprise - it took more than 30min! At the moment I quite confused. I tried the same test on different hardware, different kernels, different disks, different filesystems and _all_ tests without success! -Simon From owner-linux-xfs@oss.sgi.com Thu Sep 13 06:49:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DDng706787 for linux-xfs-outgoing; Thu, 13 Sep 2001 06:49:42 -0700 Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DDnce06763 for ; Thu, 13 Sep 2001 06:49:38 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.197]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8DDnaQ21306 for ; Thu, 13 Sep 2001 22:49:36 +0900 (JST) Received: from mailsv.nec.co.jp (mailgate51.nec.co.jp [10.7.69.196]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8DDnaZ14534 for ; Thu, 13 Sep 2001 22:49:36 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv.nec.co.jp (8.11.6/3.7W-MAILSV-NEC) with ESMTP id f8DDnal15869 for ; Thu, 13 Sep 2001 22:49:36 +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 AAA451 for ; Thu, 13 Sep 2001 22:49:33 +0900 Received: FROM noshiro.bsd.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Thu Sep 13 22:49:32 2001 +0900 Received: from localhost (localhost [127.0.0.1]) by noshiro.bsd.tnes.nec.co.jp (Postfix) with ESMTP id 34C01660C for ; Thu, 13 Sep 2001 22:49:33 +0900 (JST) To: linux-xfs@oss.sgi.com Subject: cannot mount snapshot X-Mailer: Mew version 1.94.2 on XEmacs 21.4 (Artificial Intelligence) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010913224933W.masano@tnes.nec.co.jp> Date: Thu, 13 Sep 2001 22:49:33 +0900 (JST) From: ASANO Masahiro X-Dispatcher: imput version 20000228(IM140) Lines: 26 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I cannot mount the snapshot filesystem of the XFS filesystem. To make the snapshot, I used xfs_freeze. Why it couldn't be mounted? # lvcreate -L 132m -n masano1 vg0 # mkfs.xfs /dev/vg0/masano1 # mount -t xfs /dev/vg0/masano1 /mnt/masano1 # xfs_freeze -f /mnt/masano1 # lvcreate -L 60m -n masano2 -s /dev/vg0/masano1 # xfs_freeze -u /mnt/masano1 # mount -t xfs -o ro,nouuid /dev/vg0/masano2 /mnt/masano2 XFS mounting filesystem lvm(58,1) XFS: WARNING: recovery required on readonly filesystem. XFS: write access unavailable, cannot proceed. XFS: log mount/recovery failed XFS: log mount failed I noticed this may be occurred from "8/28 Merge irix6.5f:irix:101630a". Any comments and suggestions are welcome. Cheers. -- masano From owner-linux-xfs@oss.sgi.com Thu Sep 13 08:03:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DF32e08303 for linux-xfs-outgoing; Thu, 13 Sep 2001 08:03:02 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DF2xe08284 for ; Thu, 13 Sep 2001 08:02:59 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA26573 for ; Thu, 13 Sep 2001 08:03:03 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2958893; Thu, 13 Sep 2001 10:01:42 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA34765; Thu, 13 Sep 2001 10:01:42 -0500 (CDT) Message-ID: <3BA0CA59.F18A0E14@sgi.com> Date: Thu, 13 Sep 2001 10:01:45 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.10-pre8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Simon Matter CC: linux-xfs Subject: Re: Problems with many processes copying directories on XFS References: <3BA08004.A2FBC956@ch.sauter-bc.com> <3BA0A6BA.84D64FE1@ch.sauter-bc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter wrote: > Well since nobody seems interested I'm replying myself. Sorry; we're interested, we're also quite busy. :) I can try this a bit today. Not sure what to tell you about reiserfs, might be one for the reiserfs list. :) > I > tried the same test on different hardware, different kernels, different > disks, different filesystems and _all_ tests without success! Well, sounds like a generic kernel problem, then, although XFS should handle this gracefully if possible. I'll take a look. Thanks, -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Sep 13 13:52:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DKquu13714 for linux-xfs-outgoing; Thu, 13 Sep 2001 13:52:56 -0700 Received: from HAL.vedge.net (extern164.atou.qc.ca [207.96.201.164]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DKqpe13694 for ; Thu, 13 Sep 2001 13:52:51 -0700 Received: by atou.qc.ca via sendmail from stdin id (Debian Smail3.2.0.111) for linux-xfs@oss.sgi.com; Thu, 13 Sep 2001 16:52:15 -0400 (EDT) Date: Thu, 13 Sep 2001 16:52:14 -0400 From: Jean-Francois Landry To: Simon Matter Cc: linux-xfs Subject: Re: Problems with many processes copying directories on XFS Message-ID: <20010913165214.A4685@atou.qc.ca> Reply-To: jflandry@atou.qc.ca References: <3BA08004.A2FBC956@ch.sauter-bc.com> <3BA0A6BA.84D64FE1@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <3BA0A6BA.84D64FE1@ch.sauter-bc.com>; from simon.matter@ch.sauter-bc.com on Thu, Sep 13, 2001 at 02:29:46PM +0200 X-Operating-System: Debian GNU/Linux testing/unstable with kernel 2.4.7 i586 X-Uptime: 4:43pm up 1 day, 1:22, 4 users, load average: 1.75, 1.45, 1.56 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Sep 13, 2001 at 02:29:46PM +0200, Simon Matter wrote: > Well since nobody seems interested I'm replying myself. I didn't realize > that I created a filesystem with more than 1.8 mio files with my 'stress > test'. >Okay something goes wrong here as well but now I want to > see the ReiserFS deletion speed. 'rm -rf 0*' should go fast but - > surprise - it took more than 30min! >-Simon OK, this is kind of off-topic, but that behavior is to be expected if your ReiserFS fs (hmm, can I say that?) uses the tea hash. Since you mention a 2.2 kernel it's quite possible your fs was created while the tea hash was the default. You might want to retry with the r5 hash, since tea bogs down after say, about 500k files or so. For more info on this, search the reiserfs-list archives for a thread by me concerning freedb. I seem to have accidentaly "rediscovered" this bug while testing deletion speeds :) The thread is a couple of months old. Hope this helps, Jean-Francois Landry -- So many lusers, so little ammunition. -- From owner-linux-xfs@oss.sgi.com Thu Sep 13 14:12:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DLCL214217 for linux-xfs-outgoing; Thu, 13 Sep 2001 14:12:21 -0700 Received: from outcast.rsp.com.au (outcast.rsp.com.au [203.32.218.129]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DLCHe14197 for ; Thu, 13 Sep 2001 14:12:17 -0700 Received: from [10.5.100.1] (tc-pc.rsp.com.au [10.5.100.1]) by outcast.rsp.com.au (8.9.3/8.9.3) with SMTP id GAA14796 for ; Fri, 14 Sep 2001 06:41:51 +0930 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Fri, 14 Sep 2001 06:41:54 +0930 Subject: SGI 1200, 1.0.1 - No Gigabit ethernet? From: Tony Clark To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello again, And I thought it was going so well... After advancing with the install last night, the machine now boots quite happily. Thanks to all who contributed suggestions. Now though, the gigabit ethernet no longer wants to work. The box is as follows: SGI 1200, 1GB Ram, 2 x 800Mhz P3 Netgear GA620T Gigabit ethernet (acenic drivers) Adaptec 29160 SCSI controller (talking to an Exabyte LTO tape library) 1 x internal scsi disk, 4 x external SCSI disks The card has negotiated with the switch properly (it previously worked just fine under 1.0 XFS and RH 7.0), and looking at netstat -i i can see incoming and outgoing packet counts that are very low, but they are being counted. No ping or any IP traffic is working. I've switched over to the internal 10/100, which works just fine. I'd love my gigabit back; any thoughts out there? Thanks, Tony From owner-linux-xfs@oss.sgi.com Thu Sep 13 14:39:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DLdYx14985 for linux-xfs-outgoing; Thu, 13 Sep 2001 14:39:34 -0700 Received: from llonchj.atcubic.com ([213.98.165.125]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DLdUe14963 for ; Thu, 13 Sep 2001 14:39:31 -0700 Received: from atCUBIC.com (localhost.localdomain [127.0.0.1]) by llonchj.atcubic.com (8.11.2/8.11.2) with ESMTP id f8DLjTT13735 for ; Thu, 13 Sep 2001 23:45:30 +0200 Message-ID: <3BA128F9.6010607@atCUBIC.com> Date: Thu, 13 Sep 2001 23:45:29 +0200 From: Jordi Llonch User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010808 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS and Firebird Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, I'm a Linux user. Recentlly, i've installed from scratch 2 machines with XFS filesystem. With this 2 machines i'm having problems with Firebird 0.9.4.p1 (Interbase). I cannot connect to any database, local or remote (using TCP/IP). Can you help me? Thanks in advance, -- Jordi Llonch From owner-linux-xfs@oss.sgi.com Thu Sep 13 16:23:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DNNaE16756 for linux-xfs-outgoing; Thu, 13 Sep 2001 16:23:36 -0700 Received: from ukproxy1.emrsn.co.uk (smtpmail.emrsn.co.uk [194.202.166.141]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DNNVe16737 for ; Thu, 13 Sep 2001 16:23:31 -0700 Received: from viruswall1.emrsn.co.uk (viruswall1.emrsn.co.uk [129.254.5.225] (may be forged)) by ukproxy1.emrsn.co.uk (8.9.3/8.9.3) with SMTP id WAA31550 for ; Thu, 13 Sep 2001 22:54:36 +0200 Received: from 129.254.5.5 by viruswall1.emrsn.co.uk (InterScan E-Mail VirusWall NT); Fri, 14 Sep 2001 00:21:07 +0100 (GMT Daylight Time) Received: from mxsemeacn1.emrsn.co.uk (mxsemeacn1.emrsn.co.uk [129.254.5.202]) by etsdns2.emrsn.co.uk (8.9.3/8.9.3) with ESMTP id AAA10283 for ; Fri, 14 Sep 2001 00:24:17 GMT Received: by mxsemeacn1.emrsn.co.uk with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Sep 2001 00:22:53 +0100 Message-ID: <7F0147C496F3D411813C0002B32BF1CC0125AFD0@eesekkex001.kkekant.ericsson.se> From: "Michels, Gustavo [EES/BR]" To: linux-xfs@oss.sgi.com Subject: Quotas on XFS Date: Fri, 14 Sep 2001 00:23:20 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Sorry if my problem has been addressed before, but I really can't find anything related in the archives. My setup: Red Hat Linux 7.1. I got the 2.4.9 kernel from kernel.org, applied the XFS patch and it is currently working. Then I created a XFS filesystem under /xfs/emerson (mkfs -t xfs -l size=32768b -f /dev/sda6). The root filesystem is ext2. In /etc/fstab: /dev/sda6 /xfs/emerson xfs rw,usrquota,logbufs=8,logbsize=32768 0 0 Here is what happens when I try to set quotas for an user (testuser): [root@splus001 /]# mount /dev/sda1 on / type ext2 (rw) none on /proc type proc (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda6 on /xfs/emerson type xfs (rw,usrquota,logbufs=8,logbsize=32768) [root@splus001 /]# setquota testuser 600 800 15 20 /xfs/emerson [root@splus001 /]# repquota /xfs/emerson *** Report for user quotas on device /dev/sda6 Block grace time: 7days; Inode grace time: 7days Block limits File limits User used soft hard grace used soft hard grace ---------------------------------------------------------------------- root -- 0 0 0 3 0 0 [root@splus001 /]# I don't have a clue how to get it working... Anyone could give me a hand? Currently using: - XFS CVS source from today. Built and installed all RPMs (including devel ones) under cmd, except attr2. (I didn't use the already patched kernel from SGI because I have hardware raid devices that are not supported under the latest unstable kernel, 2.4.10-pre8 I guess). - installed quota-3.01pre9-0.7.1.i386.rpm (I first uninstalled the default quota package that comes with RH 7.1) Cheers Gustavo From owner-linux-xfs@oss.sgi.com Thu Sep 13 16:28:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DNSHS16937 for linux-xfs-outgoing; Thu, 13 Sep 2001 16:28:17 -0700 Received: from vertigo.incyte.com (master.incyte.com [198.31.37.253]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DNSEe16918 for ; Thu, 13 Sep 2001 16:28:14 -0700 Received: from vertigo.incyte.com (wfrancis@localhost) by vertigo.incyte.com (8.11.0/8.11.0) with ESMTP id f8DNRsK17669; Thu, 13 Sep 2001 16:27:54 -0700 Message-Id: <200109132327.f8DNRsK17669@vertigo.incyte.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Tony Clark cc: Seth Mos , linux-xfs@oss.sgi.com Subject: Re: RH 7.1 & XFS 1.0.1 on SGI 1200 (AIC7xxx hang) In-Reply-To: Message from Tony Clark of "Thu, 13 Sep 2001 15:07:09 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Sep 2001 16:27:54 -0700 From: Will Francis Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hmmm... This was posted: > > On 18 Jul 2001 15:46:48 -0400, Doug Ledford wrote: > > > > When using my boot disk, you have to use the "apic" option, not the "noapic" > > option. > > but with no mention of how to use this option. I'll try a little more and > see if anything can be made to happen. If anyone who knows how to make this > go away, I'd appreciate the assistance. in your syslinux.cfg file on your boot floppy, simply add "apic" to your append line. For example, my entire syslinux.cfg file looks like this: default ks prompt 1 timeout 1 display boot.msg label linux kernel vmlinuz append initrd=initrd.img label ks kernel vmlinuz append apic ks=floppy initrd=initrd.img ramdisk_size=8192 (the ramdisk_size=8192 is needed if you do a FTP (or HTTP) based install, ignore otherwise) From owner-linux-xfs@oss.sgi.com Thu Sep 13 16:39:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8DNdXF17211 for linux-xfs-outgoing; Thu, 13 Sep 2001 16:39:33 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8DNdSe17192 for ; Thu, 13 Sep 2001 16:39:28 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f8DNdM520624 for ; Thu, 13 Sep 2001 16:39:22 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA26677; Fri, 14 Sep 2001 10:37:55 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA94049; Fri, 14 Sep 2001 10:37:54 +1100 (AEDT) Date: Fri, 14 Sep 2001 10:37:54 +1100 From: Nathan Scott To: "Michels, Gustavo [EES/BR]" Cc: linux-xfs@oss.sgi.com Subject: Re: Quotas on XFS Message-ID: <20010914103754.B410868@wobbly.melbourne.sgi.com> References: <7F0147C496F3D411813C0002B32BF1CC0125AFD0@eesekkex001.kkekant.ericsson.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <7F0147C496F3D411813C0002B32BF1CC0125AFD0@eesekkex001.kkekant.ericsson.se>; from gustavo.michels@emersonenergy.com on Fri, Sep 14, 2001 at 12:23:20AM +0100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Fri, Sep 14, 2001 at 12:23:20AM +0100, Michels, Gustavo [EES/BR] wrote: > Hi, > > Sorry if my problem has been addressed before, but I really can't find > anything related in the archives. > > My setup: Red Hat Linux 7.1. I got the 2.4.9 kernel from kernel.org, applied > the XFS patch and it is currently working. Then I created a XFS filesystem > under /xfs/emerson (mkfs -t xfs -l size=32768b -f /dev/sda6). The root > filesystem is ext2. > > In /etc/fstab: > > /dev/sda6 /xfs/emerson xfs rw,usrquota,logbufs=8,logbsize=32768 > 0 0 Your setup looks correct. > > Here is what happens when I try to set quotas for an user (testuser): > > [root@splus001 /]# mount > /dev/sda1 on / type ext2 (rw) > none on /proc type proc (rw) > none on /dev/pts type devpts (rw,gid=5,mode=620) > /dev/sda6 on /xfs/emerson type xfs (rw,usrquota,logbufs=8,logbsize=32768) > [root@splus001 /]# setquota testuser 600 800 15 20 /xfs/emerson > [root@splus001 /]# repquota /xfs/emerson > *** Report for user quotas on device /dev/sda6 > Block grace time: 7days; Inode grace time: 7days > Block limits File limits > User used soft hard grace used soft hard grace > ---------------------------------------------------------------------- > root -- 0 0 0 3 0 0 > > [root@splus001 /]# > Does user "testuser" have any files or blocks allocated? what does the "quota testuser" command say at this point? Off the top of my head, I'm not sure if repquota will report anything if no space/inodes are used by a user. If you "su testuser" and "touch foo" on the filesystem, repquota should show something for testuser. If so, I can see the justification for this (filesystems with many thousands of users) - I just have not looked at this code for awhile, so canna remember if thats it. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 13 17:16:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8E0G9l17895 for linux-xfs-outgoing; Thu, 13 Sep 2001 17:16:09 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8E0G4e17875 for ; Thu, 13 Sep 2001 17:16:04 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8E0Fv522381 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Thu, 13 Sep 2001 17:15:58 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id CAA515437 for ; Fri, 14 Sep 2001 02:15:52 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id LAA26917; Fri, 14 Sep 2001 11:14:31 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA93360; Fri, 14 Sep 2001 11:14:30 +1100 (AEDT) Date: Fri, 14 Sep 2001 11:14:30 +1100 From: Nathan Scott To: ASANO Masahiro Cc: linux-xfs@oss.sgi.com Subject: Re: cannot mount snapshot Message-ID: <20010914111429.E410868@wobbly.melbourne.sgi.com> References: <20010913224933W.masano@tnes.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010913224933W.masano@tnes.nec.co.jp>; from masano@tnes.nec.co.jp on Thu, Sep 13, 2001 at 10:49:33PM +0900 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Thu, Sep 13, 2001 at 10:49:33PM +0900, ASANO Masahiro wrote: > Hi, > > I cannot mount the snapshot filesystem of the XFS filesystem. > To make the snapshot, I used xfs_freeze. Why it couldn't be mounted? > > # lvcreate -L 132m -n masano1 vg0 > # mkfs.xfs /dev/vg0/masano1 > # mount -t xfs /dev/vg0/masano1 /mnt/masano1 > # xfs_freeze -f /mnt/masano1 > # lvcreate -L 60m -n masano2 -s /dev/vg0/masano1 > # xfs_freeze -u /mnt/masano1 > # mount -t xfs -o ro,nouuid /dev/vg0/masano2 /mnt/masano2 > > XFS mounting filesystem lvm(58,1) > XFS: WARNING: recovery required on readonly filesystem. > XFS: write access unavailable, cannot proceed. For some reason the block device beneath the filesystem is marked as readonly, and XFS cannot do anything about that. In particular - the "write access unavailable" message comes from fs/xfs/linux/xfs_lrw.c in the xfs_is_read_only() routine. This routine uses the block devices is_read_only() routine in drivers/block/ll_rw_blk.c to see if the device is going to allow writes. In your case, it seems the driver has marked /dev/vg0/masano1 as readonly (I don't know why that would be - looks like LVM). Which means XFS cannot proceed because it cannot do recovery on a readonly device. Hope this helps. > XFS: log mount/recovery failed > XFS: log mount failed > > I noticed this may be occurred from "8/28 Merge irix6.5f:irix:101630a". > Any comments and suggestions are welcome. > > Cheers. > > -- > masano > -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 13 18:59:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8E1xDO19383 for linux-xfs-outgoing; Thu, 13 Sep 2001 18:59:13 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8E1xBe19364 for ; Thu, 13 Sep 2001 18:59:11 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8E1x5J12531 for ; Thu, 13 Sep 2001 18:59:05 -0700 Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id LAA13225; Fri, 14 Sep 2001 11:58:04 +1000 Date: Fri, 14 Sep 2001 11:58:04 +1000 From: Keith Owens Message-Id: <200109140158.LAA13225@sherman.melbourne.sgi.com> Subject: TAKE - IA64 changes Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Three source files are patched by both XFS and the IA64 patch. To minimize the differences between XFS and IA64, I have included the IA64 patches in the XFS tree. The changes do not affect other architectures, it still compiles for i386. Eventually these IA64 patches will appear in Linus's tree. Date: Thu Sep 13 18:54:07 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102798a linux/kernel/ksyms.c - 1.107 linux/include/linux/mm.h - 1.62 linux/fs/inode.c - 1.49 From owner-linux-xfs@oss.sgi.com Thu Sep 13 20:40:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8E3eM321109 for linux-xfs-outgoing; Thu, 13 Sep 2001 20:40:22 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8E3dse21083 for ; Thu, 13 Sep 2001 20:39:54 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id UAA05339 for ; Thu, 13 Sep 2001 20:39:50 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id NAA11552; Fri, 14 Sep 2001 13:38:47 +1000 Date: Fri, 14 Sep 2001 13:38:47 +1000 From: Keith Owens Message-Id: <200109140338.NAA11552@sherman.melbourne.sgi.com> Subject: TAKE - Upgrade to 2.4.10-pre9 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Upgrade to 2.4.10-pre9 Date: Thu Sep 13 20:35:16 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102803a linux/drivers/parport/parport_cs.c - 1.1 linux/Documentation/input/cs461x.txt - 1.1 linux/Documentation/input/ff.txt - 1.1 linux/Documentation/input/gameport-programming.txt - 1.1 linux/Documentation/input/input-programming.txt - 1.1 linux/Documentation/input/input.txt - 1.1 linux/Documentation/input/joystick-api.txt - 1.1 linux/Documentation/input/joystick-parport.txt - 1.1 linux/Documentation/input/joystick.txt - 1.1 linux/drivers/usb/hid-core.c - 1.1 linux/drivers/usb/hid-input.c - 1.1 linux/drivers/usb/hiddev.c - 1.1 linux/Documentation/usb/hiddev.txt - 1.1 linux/drivers/char/joystick/emu10k1-gp.c - 1.1 linux/include/linux/dp83840.h - 1.1 linux/include/linux/eeprom.h - 1.1 linux/include/linux/hiddev.h - 1.1 linux/include/linux/ite_gpio.h - 1.1 linux/net/irda/irsysctl.c - 1.6 linux/net/irda/irlmp_frame.c - 1.8 linux/net/irda/irlmp_event.c - 1.11 linux/net/irda/irlmp.c - 1.13 linux/net/irda/irlap_event.c - 1.15 linux/net/irda/irlap.c - 1.13 linux/net/irda/irias_object.c - 1.10 linux/net/irda/iriap.c - 1.11 linux/net/irda/af_irda.c - 1.25 linux/net/ipx/af_spx.c - 1.15 linux/net/ipx/af_ipx.c - 1.23 linux/net/ax25/af_ax25.c - 1.22 linux/lib/vsprintf.c - 1.13 linux/kernel/sysctl.c - 1.40 linux/kernel/sys.c - 1.24 linux/kernel/module.c - 1.24 linux/kernel/ksyms.c - 1.108 linux/include/video/fbcon.h - 1.11 linux/include/net/irda/irlmp.h - 1.7 linux/include/net/irda/irlap.h - 1.12 linux/include/net/irda/irias_object.h - 1.7 linux/include/linux/wait.h - 1.11 linux/include/linux/sysctl.h - 1.36 linux/include/linux/quotaops.h - 1.10 linux/include/linux/mount.h - 1.17 linux/include/linux/module.h - 1.22 linux/include/linux/kernel.h - 1.25 linux/include/linux/irda.h - 1.9 linux/include/linux/fs.h - 1.117 linux/include/linux/amigaffs.h - 1.5 linux/include/asm-ppc/uaccess.h - 1.10 linux/include/asm-i386/uaccess.h - 1.13 linux/include/asm-i386/semaphore.h - 1.15 linux/include/asm-alpha/smp.h - 1.17 linux/include/asm-alpha/pgtable.h - 1.28 linux/include/asm-alpha/machvec.h - 1.12 linux/include/asm-alpha/keyboard.h - 1.7 linux/include/asm-alpha/jensen.h - 1.5 linux/include/asm-alpha/io.h - 1.15 linux/include/asm-alpha/core_tsunami.h - 1.12 linux/include/asm-alpha/core_t2.h - 1.7 linux/include/asm-alpha/core_polaris.h - 1.8 linux/include/asm-alpha/core_mcpcia.h - 1.9 linux/include/asm-alpha/core_lca.h - 1.8 linux/include/asm-alpha/core_cia.h - 1.9 linux/include/asm-alpha/core_apecs.h - 1.7 linux/fs/ufs/balloc.c - 1.8 linux/fs/super.c - 1.54 linux/fs/stat.c - 1.21 linux/fs/ntfs/support.c - 1.11 linux/fs/ntfs/fs.c - 1.31 linux/fs/ntfs/dir.c - 1.9 linux/fs/ntfs/Makefile - 1.12 linux/fs/namei.c - 1.37 linux/fs/locks.c - 1.18 linux/fs/inode.c - 1.50 linux/fs/hfs/inode.c - 1.14 linux/fs/fat/inode.c - 1.26 linux/fs/ext2/ialloc.c - 1.17 linux/fs/exec.c - 1.45 linux/fs/dquot.c - 1.37 linux/fs/binfmt_elf.c - 1.31 linux/fs/binfmt_aout.c - 1.22 linux/fs/affs/super.c - 1.12 linux/fs/affs/namei.c - 1.14 linux/fs/affs/file.c - 1.19 linux/fs/affs/dir.c - 1.11 linux/fs/affs/amigaffs.c - 1.8 linux/fs/affs/Changes - 1.7 linux/drivers/video/virgefb.c - 1.12 linux/drivers/video/vgacon.c - 1.16 linux/drivers/video/vfb.c - 1.10 linux/drivers/video/valkyriefb.c - 1.12 linux/drivers/video/tgafb.c - 1.15 linux/drivers/video/tcxfb.c - 1.7 linux/drivers/video/skeletonfb.c - 1.8 linux/drivers/video/sbusfb.c - 1.18 linux/drivers/video/retz3fb.c - 1.12 linux/drivers/video/q40fb.c - 1.9 linux/drivers/video/pm2fb.c - 1.11 linux/drivers/video/platinumfb.c - 1.11 linux/drivers/video/mdacon.c - 1.10 linux/drivers/video/macfb.c - 1.10 linux/drivers/video/leofb.c - 1.7 linux/drivers/video/imsttfb.c - 1.16 linux/drivers/video/igafb.c - 1.13 linux/drivers/video/hpfb.c - 1.11 linux/drivers/video/g364fb.c - 1.10 linux/drivers/video/fm2fb.c - 1.9 linux/drivers/video/fbcon-vga.c - 1.4 linux/drivers/video/fbcon-mfb.c - 1.5 linux/drivers/video/fbcon-mac.c - 1.7 linux/drivers/video/fbcon-iplan2p8.c - 1.6 linux/drivers/video/fbcon-iplan2p4.c - 1.6 linux/drivers/video/fbcon-iplan2p2.c - 1.6 linux/drivers/video/fbcon-ilbm.c - 1.5 linux/drivers/video/fbcon-cfb8.c - 1.5 linux/drivers/video/fbcon-cfb4.c - 1.5 linux/drivers/video/fbcon-cfb32.c - 1.5 linux/drivers/video/fbcon-cfb24.c - 1.5 linux/drivers/video/fbcon-cfb2.c - 1.5 linux/drivers/video/fbcon-cfb16.c - 1.5 linux/drivers/video/fbcon-afb.c - 1.5 linux/drivers/video/dnfb.c - 1.11 linux/drivers/video/cyberfb.c - 1.12 linux/drivers/video/creatorfb.c - 1.10 linux/drivers/video/controlfb.c - 1.15 linux/drivers/video/chipsfb.c - 1.15 linux/drivers/video/cgthreefb.c - 1.8 linux/drivers/video/cgsixfb.c - 1.9 linux/drivers/video/cgfourteenfb.c - 1.10 linux/drivers/video/bwtwofb.c - 1.9 linux/drivers/video/atafb.c - 1.12 linux/drivers/video/amifb.c - 1.18 linux/drivers/video/acornfb.c - 1.18 linux/drivers/video/S3triofb.c - 1.10 linux/drivers/usb/Makefile - 1.42 linux/drivers/sound/wavfront.c - 1.19 linux/drivers/scsi/Makefile - 1.28 linux/drivers/net/strip.c - 1.14 linux/drivers/net/irda/w83977af_ir.c - 1.19 linux/drivers/net/irda/irtty.c - 1.22 linux/drivers/net/irda/irport.c - 1.22 linux/drivers/net/hamradio/scc.c - 1.21 linux/drivers/net/hamradio/mkiss.c - 1.12 linux/drivers/net/hamradio/bpqether.c - 1.17 linux/drivers/net/hamradio/6pack.c - 1.12 linux/drivers/net/ewrk3.c - 1.18 linux/drivers/net/eql.c - 1.14 linux/drivers/net/Space.c - 1.32 linux/drivers/char/synclink.c - 1.17 linux/drivers/char/stallion.c - 1.16 linux/drivers/char/specialix.c - 1.11 linux/drivers/char/serial167.c - 1.9 linux/drivers/char/serial.c - 1.47 linux/drivers/char/rocket.c - 1.13 linux/drivers/char/riscom8.c - 1.13 linux/drivers/char/pcxx.c - 1.14 linux/drivers/char/pcwd.c - 1.15 linux/drivers/char/nvram.c - 1.16 linux/drivers/char/n_hdlc.c - 1.11 linux/drivers/char/msbusmouse.c - 1.7 linux/drivers/char/lp.c - 1.23 linux/drivers/char/joystick/Makefile - 1.8 linux/drivers/char/joystick/Config.in - 1.8 linux/drivers/char/isicom.c - 1.14 linux/drivers/char/h8.c - 1.11 linux/drivers/char/ftape/zftape/zftape-init.c - 1.10 linux/drivers/char/ftape/lowlevel/ftape-init.c - 1.5 linux/drivers/char/ftape/compressor/zftape-compress.c - 1.4 linux/drivers/char/esp.c - 1.12 linux/drivers/char/dtlk.c - 1.14 linux/drivers/char/amigamouse.c - 1.10 linux/drivers/char/adbmouse.c - 1.14 linux/drivers/char/acquirewdt.c - 1.12 linux/drivers/block/z2ram.c - 1.12 linux/drivers/block/xd.c - 1.23 linux/drivers/block/ataflop.c - 1.14 linux/drivers/block/amiflop.c - 1.16 linux/drivers/block/acsi.c - 1.17 linux/drivers/acorn/scsi/queue.c - 1.5 linux/drivers/acorn/scsi/powertec.c - 1.9 linux/drivers/acorn/scsi/oak.c - 1.5 linux/drivers/acorn/scsi/msgqueue.c - 1.5 linux/drivers/acorn/scsi/fas216.c - 1.10 linux/drivers/acorn/scsi/eesox.c - 1.8 linux/drivers/acorn/scsi/ecoscsi.c - 1.5 linux/drivers/acorn/scsi/cumana_2.c - 1.8 linux/drivers/acorn/scsi/cumana_1.c - 1.5 linux/drivers/acorn/scsi/acornscsi.c - 1.10 linux/drivers/acorn/net/etherh.c - 1.12 linux/drivers/acorn/net/ether3.c - 1.12 linux/drivers/acorn/net/ether1.c - 1.13 linux/drivers/acorn/char/serial-card.c - 1.6 linux/drivers/acorn/block/mfmhd.c - 1.14 linux/arch/sparc64/solaris/fs.c - 1.13 linux/arch/m68k/amiga/config.c - 1.10 linux/arch/i386/defconfig - 1.68 linux/arch/i386/boot/compressed/misc.c - 1.11 linux/arch/i386/boot/compressed/Makefile - 1.7 linux/arch/alpha/kernel/traps.c - 1.14 linux/arch/alpha/kernel/sys_jensen.c - 1.10 linux/arch/alpha/kernel/smp.c - 1.25 linux/arch/alpha/kernel/core_cia.c - 1.19 linux/arch/alpha/kernel/alpha_ksyms.c - 1.26 linux/Makefile - 1.122 linux/Documentation/joystick.txt - 1.7 linux/Documentation/joystick-parport.txt - 1.7 linux/Documentation/joystick-api.txt - 1.8 linux/Documentation/filesystems/ntfs.txt - 1.10 linux/drivers/video/vga16fb.c - 1.11 linux/drivers/video/fbcon-vga-planes.c - 1.4 linux/drivers/video/cyber2000fb.c - 1.24 linux/drivers/net/irda/toshoboe.c - 1.25 linux/drivers/acorn/scsi/arxescsi.c - 1.8 linux/drivers/char/ppdev.c - 1.25 linux/drivers/block/cpqarray.c - 1.28 linux/drivers/parport/Makefile - 1.8 linux/drivers/parport/Config.in - 1.13 linux/drivers/net/hamradio/yam.c - 1.15 linux/drivers/char/logibusmouse.c - 1.5 linux/drivers/char/generic_serial.c - 1.12 linux/drivers/net/fc/iph5526.c - 1.15 linux/drivers/char/ip2main.c - 1.11 linux/drivers/char/ip2.c - 1.6 linux/drivers/atm/zatm.c - 1.11 linux/drivers/atm/uPD98402.c - 1.7 linux/drivers/atm/suni.c - 1.7 linux/drivers/atm/nicstar.c - 1.16 linux/drivers/atm/horizon.c - 1.10 linux/drivers/atm/eni.c - 1.11 linux/drivers/atm/atmtcp.c - 1.8 linux/drivers/atm/ambassador.h - 1.5 linux/drivers/atm/ambassador.c - 1.13 linux/arch/alpha/kernel/pci_impl.h - 1.9 linux/arch/alpha/kernel/pci.c - 1.16 linux/arch/alpha/kernel/machvec_impl.h - 1.8 linux/drivers/char/n_r3964.c - 1.11 linux/drivers/char/applicom.c - 1.10 linux/drivers/net/wan/cycx_main.c - 1.13 linux/drivers/net/wan/cosa.c - 1.21 linux/drivers/net/tokenring/olympic.c - 1.15 linux/drivers/net/tokenring/ibmtr.c - 1.18 linux/drivers/net/ncr885e.c - 1.11 linux/drivers/net/wan/x25_asy.c - 1.8 linux/drivers/net/wan/syncppp.c - 1.13 linux/drivers/net/wan/sdlamain.c - 1.10 linux/drivers/net/wan/sdladrv.c - 1.8 linux/drivers/net/wan/sdla_x25.c - 1.12 linux/drivers/net/wan/sdla_ppp.c - 1.15 linux/drivers/net/wan/sdla_fr.c - 1.16 linux/drivers/net/wan/sdla.c - 1.12 linux/drivers/net/wan/lapbether.c - 1.9 linux/drivers/net/wan/dlci.c - 1.8 linux/drivers/net/tokenring/tms380tr.c - 1.17 linux/drivers/net/pcmcia/xirc2ps_cs.c - 1.14 linux/fs/proc/kcore.c - 1.11 linux/drivers/char/pcmcia/serial_cs.c - 1.7 linux/arch/alpha/kernel/core_irongate.c - 1.7 linux/include/asm-alpha/hw_irq.h - 1.4 linux/include/asm-alpha/core_irongate.h - 1.6 linux/include/linux/ixjuser.h - 1.4 linux/include/linux/input.h - 1.14 linux/drivers/usb/hid.h - 1.12 linux/drivers/usb/hid.c - 1.26 linux/drivers/usb/hid-debug.h - 1.6 linux/drivers/net/tokenring/smctr.c - 1.14 linux/drivers/char/mxser.c - 1.11 linux/drivers/net/wan/sdla_chdlc.c - 1.14 linux/drivers/net/tokenring/tmspci.c - 1.6 linux/drivers/net/tokenring/madgemc.c - 1.5 linux/drivers/net/tokenring/abyss.c - 1.6 linux/drivers/char/mixcomwd.c - 1.8 linux/drivers/video/dn_cfb8.c - 1.5 linux/drivers/video/dn_cfb4.c - 1.5 linux/drivers/net/irda/nsc-ircc.c - 1.15 linux/drivers/char/efirtc.c - 1.7 linux/drivers/atm/idt77105.c - 1.5 linux/arch/alpha/kernel/pci_iommu.c - 1.14 linux/drivers/char/amiserial.c - 1.9 linux/drivers/net/ioc3-eth.c - 1.14 linux/drivers/char/nwflash.c - 1.8 linux/drivers/char/ds1620.c - 1.5 linux/drivers/atm/fore200e.c - 1.12 linux/drivers/video/hgafb.c - 1.7 linux/drivers/video/fbcon-hga.c - 1.3 linux/drivers/ide/via82cxxx.c - 1.19 linux/drivers/ide/buddha.c - 1.7 linux/drivers/net/wan/comx.c - 1.13 linux/drivers/net/wan/comx-proto-ppp.c - 1.4 linux/drivers/net/wan/comx-proto-lapb.c - 1.8 linux/drivers/net/wan/comx-proto-fr.c - 1.8 linux/drivers/net/wan/comx-hw-mixcom.c - 1.8 linux/drivers/net/wan/comx-hw-locomx.c - 1.6 linux/drivers/net/wan/comx-hw-comx.c - 1.7 linux/Documentation/usb/input.txt - 1.5 linux/drivers/video/sa1100fb.c - 1.8 linux/drivers/usb/serial/usbserial.c - 1.21 linux/drivers/usb/serial/visor.c - 1.22 linux/drivers/net/wan/lmc/lmc_main.c - 1.8 linux/drivers/usb/serial/digi_acceleport.c - 1.16 linux/drivers/char/joystick/turbografx.c - 1.2 linux/drivers/char/joystick/tmdc.c - 1.4 linux/drivers/char/joystick/spaceorb.c - 1.3 linux/drivers/char/joystick/spaceball.c - 1.5 linux/drivers/char/joystick/sidewinder.c - 1.6 linux/drivers/char/joystick/serport.c - 1.3 linux/drivers/char/joystick/serio.c - 1.3 linux/drivers/char/joystick/pcigame.c - 1.3 linux/drivers/char/joystick/ns558.c - 1.7 linux/drivers/char/joystick/magellan.c - 1.3 linux/drivers/char/joystick/lightning.c - 1.3 linux/drivers/char/joystick/interact.c - 1.3 linux/drivers/char/joystick/grip.c - 1.3 linux/drivers/char/joystick/gf2k.c - 1.3 linux/drivers/char/joystick/gameport.c - 1.4 linux/drivers/char/joystick/gamecon.c - 1.4 linux/drivers/char/joystick/db9.c - 1.3 linux/drivers/char/joystick/cobra.c - 1.4 linux/drivers/char/joystick/analog.c - 1.4 linux/drivers/char/joystick/amijoy.c - 1.4 linux/drivers/char/joystick/adi.c - 1.5 linux/drivers/char/joystick/a3d.c - 1.3 linux/drivers/char/joystick/warrior.c - 1.3 linux/drivers/char/hp600_keyb.c - 1.5 linux/drivers/video/hitfb.c - 1.5 linux/drivers/char/sbc60xxwdt.c - 1.10 linux/drivers/acpi/os.c - 1.7 linux/drivers/usb/bluetooth.c - 1.16 linux/drivers/ieee1394/video1394.c - 1.10 linux/include/linux/gameport.h - 1.3 linux/include/asm-alpha/core_wildfire.h - 1.2 linux/include/asm-alpha/core_titan.h - 1.2 linux/drivers/media/video/saa7185.c - 1.4 linux/drivers/media/video/saa7111.c - 1.4 linux/drivers/isdn/eicon/Divas_mod.c - 1.5 linux/drivers/input/mousedev.c - 1.5 linux/drivers/input/keybdev.c - 1.5 linux/drivers/input/input.c - 1.4 linux/drivers/input/evdev.c - 1.4 linux/drivers/input/Config.in - 1.2 linux/drivers/char/serial_21285.c - 1.4 linux/drivers/char/joystick/iforce.c - 1.6 linux/drivers/char/i810-tco.c - 1.8 linux/drivers/block/cciss.c - 1.15 linux/drivers/char/serial_amba.c - 1.4 linux/drivers/char/toshiba.c - 1.3 linux/include/asm-ia64/module.h - 1.4 linux/include/asm-alpha/module.h - 1.2 linux/net/irda/irnet/irnet_ppp.c - 1.5 linux/net/irda/irnet/irnet_irda.c - 1.5 linux/net/irda/irnet/irnet.h - 1.5 linux/include/asm-arm/module.h - 1.2 linux/include/asm-i386/module.h - 1.2 linux/include/asm-m68k/module.h - 1.2 linux/include/asm-ppc/module.h - 1.3 linux/include/asm-s390/module.h - 1.2 linux/include/asm-sh/module.h - 1.2 linux/include/asm-sparc/module.h - 1.2 linux/include/asm-sparc64/module.h - 1.2 linux/drivers/video/fbcon-sti.c - 1.3 linux/drivers/video/sticon-bmode.c - 1.4 linux/drivers/video/sticore.c - 1.4 linux/drivers/usb/serial/empeg.c - 1.12 linux/drivers/atm/firestream.c - 1.6 linux/include/asm-s390x/module.h - 1.2 linux/arch/alpha/kernel/pci-noop.c - 1.3 linux/drivers/net/tokenring/tmsisa.c - 1.4 linux/include/asm-cris/module.h - 1.2 linux/drivers/usb/serial/io_usbvend.h - 1.4 linux/drivers/usb/serial/io_edgeport.c - 1.9 linux/drivers/net/wan/n2.c - 1.2 linux/drivers/net/wan/hdlc.c - 1.4 linux/drivers/net/wan/dscc4.c - 1.4 linux/drivers/net/wan/c101.c - 1.2 linux/drivers/net/sungem.c - 1.7 linux/drivers/char/machzwd.c - 1.5 linux/drivers/char/advantechwdt.c - 1.3 linux/drivers/net/wan/sdla_ft1.c - 1.4 linux/drivers/net/wan/wanpipe_multppp.c - 1.7 linux/drivers/video/epson1355fb.c - 1.3 linux/drivers/video/maxinefb.c - 1.3 linux/drivers/char/joystick/stinger.c - 1.2 linux/drivers/char/joystick/cs461x.c - 1.2 linux/drivers/char/ec3104_keyb.c - 1.2 linux/drivers/net/irda/irda-usb.c - 1.6 linux/drivers/net/wireless/airport.c - 1.4 linux/include/net/irda/irda-usb.h - 1.2 linux/drivers/mtd/chips/amd_flash.c - 1.2 linux/drivers/acpi/ospm/ec/ec_osl.c - 1.2 linux/drivers/acpi/ospm/button/bn_osl.c - 1.2 linux/drivers/acpi/ospm/busmgr/bm_osl.c - 1.2 linux/drivers/acpi/ospm/battery/bt_osl.c - 1.2 linux/drivers/acpi/ospm/system/sm_osl.c - 1.2 linux/drivers/acpi/ospm/thermal/tz_osl.c - 1.2 linux/drivers/net/wireless/airo_cs.c - 1.2 linux/drivers/acpi/ospm/processor/pr_osl.c - 1.2 linux/drivers/acpi/ospm/ac_adapter/ac_osl.c - 1.2 linux/drivers/net/irda/ali-ircc.c - 1.4 linux/drivers/char/ser_a2232.c - 1.3 linux/drivers/char/w83877f_wdt.c - 1.3 linux/drivers/video/aty/atyfb_base.c - 1.4 linux/drivers/char/drm/drm_context.h - 1.3 linux/drivers/net/irda/vlsi_ir.c - 1.2 From owner-linux-xfs@oss.sgi.com Thu Sep 13 20:45:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8E3jK621299 for linux-xfs-outgoing; Thu, 13 Sep 2001 20:45:20 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8E3jGe21280 for ; Thu, 13 Sep 2001 20:45:16 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id UAA20267 for ; Thu, 13 Sep 2001 20:45:19 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id NAA12739; Fri, 14 Sep 2001 13:44:12 +1000 Date: Fri, 14 Sep 2001 13:44:12 +1000 From: Keith Owens Message-Id: <200109140344.NAA12739@sherman.melbourne.sgi.com> Subject: TAKE - Add CONFIG_XFS_RT=n to defconfig Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Add CONFIG_XFS_RT=n to defconfig to avoid autobuild asking questions. Date: Thu Sep 13 20:42:33 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102804a linux/arch/sparc64/defconfig - 1.48 linux/arch/sparc/defconfig - 1.25 linux/arch/ppc/defconfig - 1.34 linux/arch/mips/defconfig - 1.20 linux/arch/m68k/defconfig - 1.11 linux/arch/i386/defconfig - 1.69 linux/arch/arm/defconfig - 1.18 linux/arch/alpha/defconfig - 1.19 linux/arch/sh/defconfig - 1.16 linux/arch/ppc/configs/walnut_defconfig - 1.14 linux/arch/ppc/configs/oak_defconfig - 1.14 linux/arch/ppc/configs/mbx_defconfig - 1.9 linux/arch/ppc/configs/gemini_defconfig - 1.16 linux/arch/ppc/configs/common_defconfig - 1.22 linux/arch/ppc/configs/apus_defconfig - 1.10 linux/arch/ia64/defconfig - 1.9 linux/arch/mips64/defconfig - 1.16 linux/arch/s390/defconfig - 1.7 linux/arch/ppc/configs/rpxlite_defconfig - 1.9 linux/arch/ppc/configs/rpxcllf_defconfig - 1.10 linux/arch/ppc/configs/est8260_defconfig - 1.10 linux/arch/ppc/configs/bseip_defconfig - 1.9 linux/arch/parisc/defconfig - 1.3 linux/arch/ppc/configs/power3_defconfig - 1.7 linux/arch/ppc/configs/ibmchrp_defconfig - 1.7 linux/arch/cris/defconfig - 1.6 linux/arch/s390x/defconfig - 1.5 linux/arch/ppc/configs/TQM860L_defconfig - 1.7 linux/arch/ppc/configs/TQM850L_defconfig - 1.7 linux/arch/ppc/configs/TQM823L_defconfig - 1.7 linux/arch/ppc/configs/SPD823TS_defconfig - 1.7 linux/arch/ppc/configs/SM850_defconfig - 1.7 linux/arch/ppc/configs/IVMS8_defconfig - 1.7 From owner-linux-xfs@oss.sgi.com Thu Sep 13 23:05:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8E65DF23222 for linux-xfs-outgoing; Thu, 13 Sep 2001 23:05:13 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8E653e23203 for ; Thu, 13 Sep 2001 23:05:03 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA11050; Fri, 14 Sep 2001 08:04:26 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA13905; Fri, 14 Sep 2001 08:04:05 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 6665F57306; Fri, 14 Sep 2001 08:03:32 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id B6D2025835; Fri, 14 Sep 2001 08:03:21 +0200 (CEST) Message-ID: <3BA19DA9.E5B81574@ch.sauter-bc.com> Date: Fri, 14 Sep 2001 08:03:21 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: jflandry@atou.qc.ca Cc: linux-xfs Subject: Re: Problems with many processes copying directories on XFS References: <3BA08004.A2FBC956@ch.sauter-bc.com> <3BA0A6BA.84D64FE1@ch.sauter-bc.com> <20010913165214.A4685@atou.qc.ca> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jean-Francois Landry schrieb: > > On Thu, Sep 13, 2001 at 02:29:46PM +0200, Simon Matter wrote: > > > Well since nobody seems interested I'm replying myself. I didn't realize > > that I created a filesystem with more than 1.8 mio files with my 'stress > > test'. > > > >Okay something goes wrong here as well but now I want to > > see the ReiserFS deletion speed. 'rm -rf 0*' should go fast but - > > surprise - it took more than 30min! > > >-Simon > > OK, this is kind of off-topic, but that behavior is to be expected if > your ReiserFS fs (hmm, can I say that?) uses the tea hash. Since you > mention a 2.2 kernel it's quite possible your fs was created while the > tea hash was the default. You might want to retry with the r5 hash, > since tea bogs down after say, about 500k files or so. > More OT: dmesg says Checking ReiserFS transaction log (device ... Using r5 hash to sort names It tells me r5 whenever a filesystem gets mounted so it is r5. The point is that XFS is known to be weak when deleting files but in my test ReiserFS was even slower. > For more info on this, search the reiserfs-list archives for a thread by > me concerning freedb. I seem to have accidentaly "rediscovered" this > bug while testing deletion speeds :) The thread is a couple of months > old. > > Hope this helps, > Jean-Francois Landry > -- > So many lusers, so little ammunition. > -- From owner-linux-xfs@oss.sgi.com Thu Sep 13 23:54:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8E6s4c24289 for linux-xfs-outgoing; Thu, 13 Sep 2001 23:54:04 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8E6s1e24270 for ; Thu, 13 Sep 2001 23:54:01 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA27634; Fri, 14 Sep 2001 08:53:56 +0200 (CEST) Message-Id: <4.3.2.7.2.20010914085131.033466a0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 14 Sep 2001 08:53:49 +0200 To: Jordi Llonch , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: XFS and Firebird In-Reply-To: <3BA128F9.6010607@atCUBIC.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 23:45 13-9-2001 +0200, Jordi Llonch wrote: >Hello, > >I'm a Linux user. Recentlly, i've installed from scratch 2 machines with >XFS filesystem. With this 2 machines i'm having problems with Firebird >0.9.4.p1 (Interbase). I doubt this is because of XFS, you would better check with the redhat mailinglists. >I cannot connect to any database, local or remote (using TCP/IP). If you can ping the server and the server is otherwise still alive I would suspect a interbase problem. If you can find some logs of this and they say it can't start up because the fs please post them here. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Sep 13 23:57:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8E6vFp24450 for linux-xfs-outgoing; Thu, 13 Sep 2001 23:57:15 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8E6vBe24424 for ; Thu, 13 Sep 2001 23:57:11 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA12089; Fri, 14 Sep 2001 08:56:23 +0200 (CEST) Message-Id: <4.3.2.7.2.20010914085517.03346490@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 14 Sep 2001 08:56:16 +0200 To: Simon Matter , jflandry@atou.qc.ca From: Seth Mos Subject: Re: Problems with many processes copying directories on XFS Cc: linux-xfs In-Reply-To: <3BA19DA9.E5B81574@ch.sauter-bc.com> References: <3BA08004.A2FBC956@ch.sauter-bc.com> <3BA0A6BA.84D64FE1@ch.sauter-bc.com> <20010913165214.A4685@atou.qc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 08:03 14-9-2001 +0200, Simon Matter wrote: >Jean-Francois Landry schrieb: > > > > On Thu, Sep 13, 2001 at 02:29:46PM +0200, Simon Matter wrote: > > > > > Well since nobody seems interested I'm replying myself. I didn't realize > > > that I created a filesystem with more than 1.8 mio files with my 'stress > > > test'. > > > > > > >Okay something goes wrong here as well but now I want to > > > see the ReiserFS deletion speed. 'rm -rf 0*' should go fast but - > > > surprise - it took more than 30min! > > > > >-Simon > > > > OK, this is kind of off-topic, but that behavior is to be expected if > > your ReiserFS fs (hmm, can I say that?) uses the tea hash. Since you > > mention a 2.2 kernel it's quite possible your fs was created while the > > tea hash was the default. You might want to retry with the r5 hash, > > since tea bogs down after say, about 500k files or so. > > >More OT: dmesg says >Checking ReiserFS transaction log (device ... >Using r5 hash to sort names > >It tells me r5 whenever a filesystem gets mounted so it is r5. The point >is that XFS is known to be weak when deleting files but in my test >ReiserFS was even slower. Weird, better tell them on the reiserfs list what is happening with detail which will help them. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Sep 14 00:28:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8E7SrE25019 for linux-xfs-outgoing; Fri, 14 Sep 2001 00:28:53 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8E7Sne25000 for ; Fri, 14 Sep 2001 00:28:49 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id AAA01878 for ; Fri, 14 Sep 2001 00:28:52 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA38090; Fri, 14 Sep 2001 18:27:27 +1100 (EDT) Date: Fri, 14 Sep 2001 18:27:27 +1100 From: Timothy Shimmin To: ASANO Masahiro Cc: linux-xfs@oss.sgi.com Subject: Re: XFS ACL with NFS Message-ID: <20010914182727.E128646@boing.melbourne.sgi.com> References: <20010913181121F.masano@tnes.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20010913181121F.masano@tnes.nec.co.jp>; from masano@tnes.nec.co.jp on Thu, Sep 13, 2001 at 06:11:21PM +0900 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Sep 13, 2001 at 06:11:21PM +0900, ASANO Masahiro wrote: > Hi Masahiro, > > Does acl of XFS work with NFS? I wouldn't think so. We've never tried to get it going. After the ACL/XFS and ACL/EXT2 reconciliation that is going on with Andreas and Nathan is done, there will probably be a greater chance that this situation will be rectified. --Tim From owner-linux-xfs@oss.sgi.com Fri Sep 14 04:00:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8EB0Cg29757 for linux-xfs-outgoing; Fri, 14 Sep 2001 04:00:12 -0700 Received: from seralph5.essex.ac.uk (seralph5.essex.ac.uk [155.245.240.155]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8EB00e29697 for ; Fri, 14 Sep 2001 04:00:05 -0700 Received: from sernt14.essex.ac.uk ([155.245.240.183]) by seralph5.essex.ac.uk with esmtp (Exim 3.13 #1) id 15hqhG-0002NV-00 for linux-xfs@oss.sgi.com; Fri, 14 Sep 2001 11:59:46 +0100 Received: by sernt14.essex.ac.uk with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Sep 2001 11:57:13 +0100 Message-ID: <7AC902A40BEDD411A3A800D0B7847B66088377@sernt14.essex.ac.uk> From: "Giddings, Bret" To: linux-xfs@oss.sgi.com Subject: NFS Issues with filesystem migration Date: Fri, 14 Sep 2001 11:57:12 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk We are looking to migrate some existing advfs partitions on Compaq Tru64 Unix 4.0e to xfs partitions on linux and have observed extremely weird problems in copying the files. The different scenarios and outcomes are outlined below. Test environment Linux Server: Dell PowerEdge 4400 with hardware RAID on aacraid driver. OS RedHat71. Tried with both SGI supplied kernels and 2.4.9 kernels. Alpha Server: AlphaStation 200, Compaq Tru64 4.0e Tar: Gnu tar on both systems (sym link on linux to /bin/tar to provide same calling convention). Test data: ex-users data - contains mix of usual stuff TEST 1 - XFS The xfs file system is NFS mounted on Alpha (push from the Alpha) # cd /Ufs/servbg/users # /bin/gnutar cfS - test | (cd /mnt/users; /bin/gnutar xpfS - ) Result: test directory expands from 21987 on advfs to 86224 on xfs (also, the size of the data is initially higher and drops to this value a short time after the copy is finished). TEST 2 - XFS The advfs file system on the Alpha is NFS mounted on the Linux machine (pull from the Linux box). # cd /mnt/users # /bin/gnutar cfS - test | (cd /Ufs/servb00/users; /bin/gnutar xpfS -) Result: test directory expands from 21987 on advfs to 23860 on local xfs partition /Ufs/servb00 - this is probably a result of the differing block sizes so OK. TEST 3 - EXT2 The ext2 file system is NFS mounted on Alpha (push from the Alpha) # cd /Ufs/servbg/users # /bin/gnutar cfs - test | (cd /mnt; /bin/gnutar xpfS - ) Result : test directory contracts from 21987 on advfs to 21714 on ext2 TEST 4 - EXT2 The advfs file system on the Alpha is NFS mounted on the Linux machine (pull from the Linux box). # cd /mnt/users # /bin/gnutar cfS - test | (cd /tmp; /bin/gnutar xpfS -) Result: test directory contracts from 21987 on advfs to 21313 on ext2 PROBLEMS: The most worrying problem for us is that remotely mounting an XFS directory to a non-linux machines appears to result in quite excessive use of diskspace. Looking at the test data, we found that (for example), a .netscape/cache directory would grow from 9M to 33M. Is this type of behaviour a known problem and is it likely to bite during normal operation of the filesystem when nfs-mounted. The usage reported by du on the linux server for the test directory shows erratic value. During the copy, it rises to a higher value and then decreases a bit - this seems counter intuitive. Indeed, different runs with the same test data would show slight variations in resultant disk space used for TEST 1. thanks in advance, Bret -- Bret Giddings, Systems Manager, Computing Service, University of Essex Tel: (01206) 872577 Email: bret@essex.ac.uk Fax: (01206) 860585 From owner-linux-xfs@oss.sgi.com Fri Sep 14 05:44:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ECij231533 for linux-xfs-outgoing; Fri, 14 Sep 2001 05:44:45 -0700 Received: from ukproxy1.emrsn.co.uk (smtpmail.emrsn.co.uk [194.202.166.141]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ECice31514 for ; Fri, 14 Sep 2001 05:44:38 -0700 Received: from viruswall1.emrsn.co.uk (viruswall1.emrsn.co.uk [129.254.5.225] (may be forged)) by ukproxy1.emrsn.co.uk (8.9.3/8.9.3) with SMTP id MAA24673; Fri, 14 Sep 2001 12:15:40 +0200 Received: from 129.254.5.5 by viruswall1.emrsn.co.uk (InterScan E-Mail VirusWall NT); Fri, 14 Sep 2001 13:42:13 +0100 (GMT Daylight Time) Received: from mxsemeacn2.emrsn.co.uk (mxsemeacn2.emrsn.co.uk [129.254.5.203]) by etsdns2.emrsn.co.uk (8.9.3/8.9.3) with ESMTP id NAA28219; Fri, 14 Sep 2001 13:45:19 GMT Received: by mxsemeacn2.emrsn.co.uk with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Sep 2001 13:45:13 +0100 Message-ID: <7F0147C496F3D411813C0002B32BF1CC0125B11E@eesekkex001.kkekant.ericsson.se> From: "Michels, Gustavo [EES/BR]" To: Nathan Scott Cc: linux-xfs@oss.sgi.com Subject: RE: Quotas on XFS Date: Fri, 14 Sep 2001 13:08:00 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello Nathan, Right on the spot. Testuser didn't had any files and after I created something, repquota showed the quota values for the user. Thanks for the help! Cheers Gustavo -----Original Message----- From: Nathan Scott [mailto:nathans@sgi.com] Sent: quinta-feira, 13 de setembro de 2001 20:38 To: Michels, Gustavo [EES/BR] Cc: linux-xfs@oss.sgi.com Subject: Re: Quotas on XFS hi, On Fri, Sep 14, 2001 at 12:23:20AM +0100, Michels, Gustavo [EES/BR] wrote: > Hi, > > Sorry if my problem has been addressed before, but I really can't find > anything related in the archives. > > My setup: Red Hat Linux 7.1. I got the 2.4.9 kernel from kernel.org, applied > the XFS patch and it is currently working. Then I created a XFS filesystem > under /xfs/emerson (mkfs -t xfs -l size=32768b -f /dev/sda6). The root > filesystem is ext2. > > In /etc/fstab: > > /dev/sda6 /xfs/emerson xfs rw,usrquota,logbufs=8,logbsize=32768 > 0 0 Your setup looks correct. > > Here is what happens when I try to set quotas for an user (testuser): > > [root@splus001 /]# mount > /dev/sda1 on / type ext2 (rw) > none on /proc type proc (rw) > none on /dev/pts type devpts (rw,gid=5,mode=620) > /dev/sda6 on /xfs/emerson type xfs (rw,usrquota,logbufs=8,logbsize=32768) > [root@splus001 /]# setquota testuser 600 800 15 20 /xfs/emerson > [root@splus001 /]# repquota /xfs/emerson > *** Report for user quotas on device /dev/sda6 > Block grace time: 7days; Inode grace time: 7days > Block limits File limits > User used soft hard grace used soft hard grace > ---------------------------------------------------------------------- > root -- 0 0 0 3 0 0 > > [root@splus001 /]# > Does user "testuser" have any files or blocks allocated? what does the "quota testuser" command say at this point? Off the top of my head, I'm not sure if repquota will report anything if no space/inodes are used by a user. If you "su testuser" and "touch foo" on the filesystem, repquota should show something for testuser. If so, I can see the justification for this (filesystems with many thousands of users) - I just have not looked at this code for awhile, so canna remember if thats it. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Fri Sep 14 06:23:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8EDN3B09394 for linux-xfs-outgoing; Fri, 14 Sep 2001 06:23:03 -0700 Received: from ukproxy1.emrsn.co.uk (smtpmail.emrsn.co.uk [194.202.166.141]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8EDMue09327 for ; Fri, 14 Sep 2001 06:22:56 -0700 Received: from viruswall1.emrsn.co.uk (viruswall1.emrsn.co.uk [129.254.5.225] (may be forged)) by ukproxy1.emrsn.co.uk (8.9.3/8.9.3) with SMTP id MAA27259; Fri, 14 Sep 2001 12:54:00 +0200 Received: from 129.254.5.5 by viruswall1.emrsn.co.uk (InterScan E-Mail VirusWall NT); Fri, 14 Sep 2001 14:20:34 +0100 (GMT Daylight Time) Received: from mxsemeacn2.emrsn.co.uk (mxsemeacn2.emrsn.co.uk [129.254.5.203]) by etsdns2.emrsn.co.uk (8.9.3/8.9.3) with ESMTP id OAA00822; Fri, 14 Sep 2001 14:23:40 GMT Received: by mxsemeacn2.emrsn.co.uk with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Sep 2001 14:23:34 +0100 Message-ID: <7F0147C496F3D411813C0002B32BF1CC0125B148@eesekkex001.kkekant.ericsson.se> From: "Michels, Gustavo [EES/BR]" To: Nathan Scott Cc: linux-xfs@oss.sgi.com Subject: RE: Quotas on XFS Date: Fri, 14 Sep 2001 13:36:05 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Just another question, I can't find anything about it also... How do I set quota defaults for all users (created and to be created)? What is the 'protouser' in setquota? Probably dumb questions, but I really can't figure out... Cheers Gustavo -----Original Message----- From: Nathan Scott [mailto:nathans@sgi.com] Sent: quinta-feira, 13 de setembro de 2001 20:38 To: Michels, Gustavo [EES/BR] Cc: linux-xfs@oss.sgi.com Subject: Re: Quotas on XFS hi, On Fri, Sep 14, 2001 at 12:23:20AM +0100, Michels, Gustavo [EES/BR] wrote: > Hi, > > Sorry if my problem has been addressed before, but I really can't find > anything related in the archives. > > My setup: Red Hat Linux 7.1. I got the 2.4.9 kernel from kernel.org, applied > the XFS patch and it is currently working. Then I created a XFS filesystem > under /xfs/emerson (mkfs -t xfs -l size=32768b -f /dev/sda6). The root > filesystem is ext2. > > In /etc/fstab: > > /dev/sda6 /xfs/emerson xfs rw,usrquota,logbufs=8,logbsize=32768 > 0 0 Your setup looks correct. > > Here is what happens when I try to set quotas for an user (testuser): > > [root@splus001 /]# mount > /dev/sda1 on / type ext2 (rw) > none on /proc type proc (rw) > none on /dev/pts type devpts (rw,gid=5,mode=620) > /dev/sda6 on /xfs/emerson type xfs (rw,usrquota,logbufs=8,logbsize=32768) > [root@splus001 /]# setquota testuser 600 800 15 20 /xfs/emerson > [root@splus001 /]# repquota /xfs/emerson > *** Report for user quotas on device /dev/sda6 > Block grace time: 7days; Inode grace time: 7days > Block limits File limits > User used soft hard grace used soft hard grace > ---------------------------------------------------------------------- > root -- 0 0 0 3 0 0 > > [root@splus001 /]# > Does user "testuser" have any files or blocks allocated? what does the "quota testuser" command say at this point? Off the top of my head, I'm not sure if repquota will report anything if no space/inodes are used by a user. If you "su testuser" and "touch foo" on the filesystem, repquota should show something for testuser. If so, I can see the justification for this (filesystems with many thousands of users) - I just have not looked at this code for awhile, so canna remember if thats it. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Fri Sep 14 07:03:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8EE3PR20714 for linux-xfs-outgoing; Fri, 14 Sep 2001 07:03:25 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8EE3He20678 for ; Fri, 14 Sep 2001 07:03:17 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8EE3A504612 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Fri, 14 Sep 2001 07:03:10 -0700 Received: from zeus-fddi.americas.sgi.com ([128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA562928 for ; Fri, 14 Sep 2001 16:03:05 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2969620; Fri, 14 Sep 2001 09:01:51 -0500 (CDT) Received: from lord.americas.sgi.com (lord.americas.sgi.com [128.162.187.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA02433; Fri, 14 Sep 2001 09:01:50 -0500 (CDT) Received: from lord.americas.sgi.com by lord.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f8EE1W105179; Fri, 14 Sep 2001 09:01:32 -0500 Message-Id: <200109141401.f8EE1W105179@lord.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Giddings, Bret" cc: linux-xfs@oss.sgi.com Subject: Re: NFS Issues with filesystem migration In-Reply-To: Message from "Giddings, Bret" of "Fri, 14 Sep 2001 11:57:12 BST." <7AC902A40BEDD411A3A800D0B7847B66088377@sernt14.essex.ac.uk> Date: Fri, 14 Sep 2001 09:01:32 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > We are looking to migrate some existing advfs partitions on Compaq Tru64 > Unix 4.0e to xfs partitions on linux and have observed extremely weird > problems in copying the files. The different scenarios and outcomes are > outlined below. > > Test environment > > Linux Server: Dell PowerEdge 4400 with hardware RAID on aacraid driver. OS > RedHat71. Tried with both SGI supplied kernels and 2.4.9 kernels. > > Alpha Server: AlphaStation 200, Compaq Tru64 4.0e > > Tar: Gnu tar on both systems (sym link on linux to /bin/tar to provide same > calling convention). > > Test data: ex-users data - contains mix of usual stuff > > TEST 1 - XFS > > The xfs file system is NFS mounted on Alpha (push from the Alpha) > > # cd /Ufs/servbg/users > # /bin/gnutar cfS - test | (cd /mnt/users; /bin/gnutar xpfS - ) > > Result: test directory expands from 21987 on advfs to 86224 on xfs (also, > the size of the data is initially higher and drops to this value a short > time after the copy is finished). This is caused by something called the NFS reference cache within XFS, basically XFS allocated more space than you ask for in anticipation of future writes. The excess space is cleaned up at close time in the normal case. NFS effectively does an open/close around each write and this leads to truncation of the excess space at the end of each write. Because of this XFS keeps a cache of files on which NFS writes have been performed, the reference count on these is kept high. Entries are purged from the cache as new files are written and also over time. I suspect that the latter half of the cache flushing is not working on Linux, especially after recent kernel changes. If you unmounted and remounted the filesystem the space would be recovered. We will look into the cache code, it does sound broken. The du space reporting is being influenced by the same cache. Steve p.s. trust me you do want the cache, adding it increased XFS performance under NFS on linux by about an order of magnitude. > > TEST 2 - XFS > > The advfs file system on the Alpha is NFS mounted on the Linux machine (pull > from the Linux box). > > # cd /mnt/users > # /bin/gnutar cfS - test | (cd /Ufs/servb00/users; /bin/gnutar xpfS -) > > Result: test directory expands from 21987 on advfs to 23860 on local xfs > partition /Ufs/servb00 - this is probably a result of the differing block > sizes so OK. > > TEST 3 - EXT2 > > The ext2 file system is NFS mounted on Alpha (push from the Alpha) > > # cd /Ufs/servbg/users > # /bin/gnutar cfs - test | (cd /mnt; /bin/gnutar xpfS - ) > > Result : test directory contracts from 21987 on advfs to 21714 on ext2 > > TEST 4 - EXT2 > > The advfs file system on the Alpha is NFS mounted on the Linux machine (pull > from the Linux box). > > # cd /mnt/users > # /bin/gnutar cfS - test | (cd /tmp; /bin/gnutar xpfS -) > > Result: test directory contracts from 21987 on advfs to 21313 on ext2 > > PROBLEMS: > > The most worrying problem for us is that remotely mounting an XFS directory > to a non-linux machines appears to result in quite excessive use of > diskspace. Looking at the test data, we found that (for example), a > .netscape/cache directory would grow from 9M to 33M. Is this type of > behaviour a known problem and is it likely to bite during normal operation > of the filesystem when nfs-mounted. > > The usage reported by du on the linux server for the test directory shows > erratic value. During the copy, it rises to a higher value and then > decreases a bit - this seems counter intuitive. Indeed, different runs with > the same test data would show slight variations in resultant disk space used > for TEST 1. > > thanks in advance, > > Bret > -- > Bret Giddings, Systems Manager, Computing Service, University of Essex > Tel: (01206) 872577 Email: bret@essex.ac.uk Fax: (01206) 860585 From owner-linux-xfs@oss.sgi.com Fri Sep 14 12:31:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8EJVlC02891 for linux-xfs-outgoing; Fri, 14 Sep 2001 12:31:47 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8EJVie02871 for ; Fri, 14 Sep 2001 12:31:44 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA00652 for ; Fri, 14 Sep 2001 12:30:18 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA91668 for ; Fri, 14 Sep 2001 12:36:56 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 8B0E715A213 for ; Fri, 14 Sep 2001 12:30:22 -0700 (PDT) Subject: Re: RH 7.1 & XFS 1.0.1 on SGI 1200 (AIC7xxx hang) From: Florin Andrei To: linux-xfs In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 14 Sep 2001 12:30:22 -0700 Message-Id: <1000495822.12129.31.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 2001-09-12 at 22:37, Tony Clark wrote: > > Hmmm... This was posted: > > On 18 Jul 2001 15:46:48 -0400, Doug Ledford wrote: > > > > When using my boot disk, you have to use the "apic" option, not the "noapic" > > option. > > but with no mention of how to use this option. I'll try a little more and > see if anything can be made to happen. If anyone who knows how to make this > go away, I'd appreciate the assistance. When the install floppy boots up, you get a prompt, right? At that prompt, just write "linux apic" and hit Enter. Or "text apic" if you prefer a text-mode installation (i do). -- Florin Andrei "Our kernel does have source control: its name is Linus Torvalds, CVS with a brain." - Nicholas Knight From owner-linux-xfs@oss.sgi.com Fri Sep 14 14:23:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ELNUL05121 for linux-xfs-outgoing; Fri, 14 Sep 2001 14:23:30 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ELNQe05102 for ; Fri, 14 Sep 2001 14:23:26 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8ELNA510631 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Fri, 14 Sep 2001 14:23:10 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id XAA583843 for ; Fri, 14 Sep 2001 23:23:05 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id IAA02883; Sat, 15 Sep 2001 08:21:38 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id HAA96171; Sat, 15 Sep 2001 07:21:38 +1000 (AEDT) Date: Sat, 15 Sep 2001 07:21:37 +1000 From: Nathan Scott To: "Michels, Gustavo [EES/BR]" Cc: linux-xfs@oss.sgi.com Subject: Re: Quotas on XFS Message-ID: <20010915072137.B376594@wobbly.melbourne.sgi.com> References: <7F0147C496F3D411813C0002B32BF1CC0125B148@eesekkex001.kkekant.ericsson.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <7F0147C496F3D411813C0002B32BF1CC0125B148@eesekkex001.kkekant.ericsson.se>; from gustavo.michels@emersonenergy.com on Fri, Sep 14, 2001 at 01:36:05PM +0100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Fri, Sep 14, 2001 at 01:36:05PM +0100, Michels, Gustavo [EES/BR] wrote: > Hi, > > Just another question, I can't find anything about it also... > > How do I set quota defaults for all users (created and to be created)? What > is the 'protouser' in setquota? > This is a prototypical user - the idea being you set up the quota for one user and then basically copy the limits for the rest from that first one. You cannot set default quotas for more than one user at a time (you could write a script which uses setquota in a loop of course), and you can't set quota for users that don't exist (urm - that may not be true if you use numeric IDs directly actually, instead of usernames). cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Fri Sep 14 17:19:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8F0JdG08000 for linux-xfs-outgoing; Fri, 14 Sep 2001 17:19:39 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8F0Jbe07981 for ; Fri, 14 Sep 2001 17:19:37 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id RAA01816 for ; Fri, 14 Sep 2001 17:19:24 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id RAA39844 for ; Fri, 14 Sep 2001 17:24:29 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id D3F6515A213 for ; Fri, 14 Sep 2001 17:17:55 -0700 (PDT) Subject: CPU usage From: Florin Andrei To: linux-xfs Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 14 Sep 2001 17:17:55 -0700 Message-Id: <1000513075.12917.104.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've heard someone complaining about high CPU usage with XFS, especially on low-clocked machines. Someone told me that, on some PII at 266 and 400 MHz, running Linux on XFS, CPU usage is 10-15% all the time, even when the machine is supposed to be idle. I find this hard to believe, since on a lowly Indy, at 180 MHz, CPU usage is 0.00% when the machine is idle. Any idea?... -- Florin Andrei "Our kernel does have source control: its name is Linus Torvalds, CVS with a brain." - Nicholas Knight From owner-linux-xfs@oss.sgi.com Fri Sep 14 18:36:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8F1aaO09009 for linux-xfs-outgoing; Fri, 14 Sep 2001 18:36:36 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8F1aXe08990 for ; Fri, 14 Sep 2001 18:36:33 -0700 Received: from idcomm.com (IDENT:+9ikyfVIqZu9kVwahCzhSjaQGfr3lHZi@x2-pip90.idcomm.com [209.60.72.101]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f8F1lPQ17629 for ; Fri, 14 Sep 2001 19:47:25 -0600 Message-ID: <3BA2B125.E6801644@idcomm.com> Date: Fri, 14 Sep 2001 19:38:45 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs Subject: Re: CPU usage References: <1000513075.12917.104.camel@stantz.corp.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Florin Andrei wrote: > > I've heard someone complaining about high CPU usage with XFS, especially > on low-clocked machines. > Someone told me that, on some PII at 266 and 400 MHz, running Linux on > XFS, CPU usage is 10-15% all the time, even when the machine is supposed > to be idle. > I find this hard to believe, since on a lowly Indy, at 180 MHz, CPU > usage is 0.00% when the machine is idle. > Any idea?... > > -- > Florin Andrei > > "Our kernel does have source control: its name is > Linus Torvalds, CVS with a brain." - Nicholas Knight Maybe an IDE drive is being used without DMA. That forces cpu use for quite a few disk operations. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Sat Sep 15 00:17:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8F7HDN13438 for linux-xfs-outgoing; Sat, 15 Sep 2001 00:17:13 -0700 Received: from mailhost.mil.ameritech.net (mpdr0.milwaukee.wi.ameritech.net [206.141.239.126]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8F7H9e13418 for ; Sat, 15 Sep 2001 00:17:09 -0700 Received: from there ([64.108.134.148]) by mailhost.mil.ameritech.net (InterMail v4.01.01.07 201-229-111-110) with SMTP id <20010915071702.KMGK24877.mailhost.mil.ameritech.net@there>; Sat, 15 Sep 2001 02:17:02 -0500 Content-Type: text/plain; charset="iso-8859-1" From: James To: Florin Andrei Subject: Re: CPU usage Date: Sat, 15 Sep 2001 02:10:48 -0500 X-Mailer: KMail [version 1.3] References: <1000513075.12917.104.camel@stantz.corp.sgi.com> In-Reply-To: <1000513075.12917.104.camel@stantz.corp.sgi.com> Cc: linux-xfs MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20010915071702.KMGK24877.mailhost.mil.ameritech.net@there> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Friday 14 September 2001 07:17 pm, you wrote: > I've heard someone complaining about high CPU usage with XFS, especially > on low-clocked machines. > Someone told me that, on some PII at 266 and 400 MHz, running Linux on > XFS, CPU usage is 10-15% all the time, even when the machine is supposed > to be idle. > I find this hard to believe, since on a lowly Indy, at 180 MHz, CPU > usage is 0.00% when the machine is idle. > Any idea?... runs okay on my 6x86mmx-233 usually 0.00 unless i have top running or doing something on the machine, even while serving mp3's to my main machine. Even running a lot of NFS off a XFS produces at max 15% load not bad considering it serving too both a 100mbit link and a 10meg link at the same time 2-3 clients requesting data.... Linux magic 2.4.9-xfs #1 Sat Aug 25 11:19:10 CDT 2001 i686 unknown 12:57am up 20 days, 14:07, 10 users, load average: 0.04, 0.01, 0.00 keep up the good work James From owner-linux-xfs@oss.sgi.com Sat Sep 15 01:06:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8F86Bf14030 for linux-xfs-outgoing; Sat, 15 Sep 2001 01:06:11 -0700 Received: from porgy.srv.nld.sonera.net (mbox-01.soneraplaza.nl [195.66.15.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8F867e14011 for ; Sat, 15 Sep 2001 01:06:07 -0700 Received: from qn-213-73-192-55.quicknet.nl ([213.73.192.55]:62082 "EHLO et.schoenmakerstraat.org") by soneramail.nl with ESMTP id ; Sat, 15 Sep 2001 09:48:02 +0200 Received: from localhost ([127.0.0.1] helo=dds.nl) by et.schoenmakerstraat.org with esmtp (Exim 3.12 #1 (Debian)) id 15iABr-0000Pt-00 for ; Sat, 15 Sep 2001 09:48:39 +0200 Message-ID: <3BA307D7.3035CE55@dds.nl> Date: Sat, 15 Sep 2001 09:48:39 +0200 From: Ries van twisk Reply-To: rvt@dds.nl X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.9 i586) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs Subject: Re: CPU usage References: <1000513075.12917.104.camel@stantz.corp.sgi.com> <20010915071702.KMGK24877.mailhost.mil.ameritech.net@there> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit To: unlisted-recipients:; (no To-header on input) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk James wrote: > > On Friday 14 September 2001 07:17 pm, you wrote: > > I've heard someone complaining about high CPU usage with XFS, especially > > on low-clocked machines. > > Someone told me that, on some PII at 266 and 400 MHz, running Linux on > > XFS, CPU usage is 10-15% all the time, even when the machine is supposed > > to be idle. > > I find this hard to believe, since on a lowly Indy, at 180 MHz, CPU > > usage is 0.00% when the machine is idle. > > Any idea?... > No by default CPU usage. Everything is nearly at 0%. Three 4Gb XFS partitions on a PII 266/128Mb ram. Kernel is a 2.4.9-xfs kernel patched myself. Other system: Dell PE2550 PIII 1Ghz. 512MbRAM also 2.4.9-xfs kernel on three partitions. Everything is in hardware mirror. Also is nearly at 0%. I can use this system to do some thest if you like. It's not yet a production system so I can play around. Ries From owner-linux-xfs@oss.sgi.com Sat Sep 15 05:10:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8FCAN117561 for linux-xfs-outgoing; Sat, 15 Sep 2001 05:10:23 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8FCALe17539 for ; Sat, 15 Sep 2001 05:10:21 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id AF8A0139D6; Sat, 15 Sep 2001 08:10:22 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: Hard drive light won't go off? Message-Id: <20010915121022.AF8A0139D6@linux.compucomis.net> Date: Sat, 15 Sep 2001 08:10:22 -0400 (EDT) From: mburger@compucomis.net (Mike Burger) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I do have one other minor concern. This only seems to happen on the system on which I'm running XFS. The hard drive light will not turn off...it's like something is constantly running the hard drive(s) on my system. It looked like it had stopped, at one point, when I had a 3 drive combo going. I replaced two drives with a single large drive (1 swap partition, 2 XFS partitions for /var and /home), and the hard drive light just stays on, steady. Now, before anyone says it's got to be a matter of the wire being incorrectly installed, the thing flashes just fine during the normal boot process. It doesn't stay on steady until the thing is fully booted. Is there something in the XFS code that does some sort of major league consistency checking over a period of time? This system is barely in use, yet...only 3 users, of which I'm the only one doing anything, yet. Thanks. From owner-linux-xfs@oss.sgi.com Sat Sep 15 05:25:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8FCPKL17893 for linux-xfs-outgoing; Sat, 15 Sep 2001 05:25:20 -0700 Received: from sto-vo-kor.koschikode.com (sto-vo-kor.koschikode.com [195.124.129.42]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8FCPGe17874 for ; Sat, 15 Sep 2001 05:25:16 -0700 Received: from warp9.koschikode.com (pD9517F0B.dip.t-dialin.net [217.81.127.11]) by sto-vo-kor.koschikode.com (Postfix) with ESMTP id A978BB522; Sat, 15 Sep 2001 14:25:12 +0200 (CEST) Received: from koschikode.com (kaplah.koschikode.com [192.168.200.15]) by warp9.koschikode.com (Postfix) with ESMTP id 0EAD5CED5; Sat, 15 Sep 2001 14:24:58 +0200 (CEST) Message-ID: <3BA3489A.D992BEF1@koschikode.com> Date: Sat, 15 Sep 2001 14:24:58 +0200 From: Juri Haberland X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.10-pre4-ext3 i686) X-Accept-Language: en MIME-Version: 1.0 To: Mike Burger Cc: linux-xfs@oss.sgi.com Subject: Re: Hard drive light won't go off? References: <20010915121022.AF8A0139D6@linux.compucomis.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Mike Burger wrote: > > I do have one other minor concern. > > This only seems to happen on the system on which I'm running XFS. > > The hard drive light will not turn off...it's like something is constantly > running the hard drive(s) on my system. Unusual. > It looked like it had stopped, at one point, when I had a 3 drive combo > going. I replaced two drives with a single large drive (1 swap partition, 2 > XFS partitions for /var and /home), and the hard drive light just stays > on, steady. > > Now, before anyone says it's got to be a matter of the wire being incorrectly > installed, the thing flashes just fine during the normal boot process. It > doesn't stay on steady until the thing is fully booted. > > Is there something in the XFS code that does some sort of major league > consistency checking over a period of time? This system is barely in use, > yet...only 3 users, of which I'm the only one doing anything, yet. Any logging going to syslog constantly? Are running a RAID which might sync in the background? Juri From owner-linux-xfs@oss.sgi.com Sat Sep 15 05:57:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8FCvoY18328 for linux-xfs-outgoing; Sat, 15 Sep 2001 05:57:50 -0700 Received: from mel-rti18.wanadoo.fr ([193.252.19.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8FCvle18309 for ; Sat, 15 Sep 2001 05:57:48 -0700 Received: from antholoma.wanadoo.fr (193.252.19.153) by mel-rti18.wanadoo.fr; 15 Sep 2001 14:57:41 +0200 Received: from serveur.guile.prv (217.128.51.97) by antholoma.wanadoo.fr; 15 Sep 2001 14:57:35 +0200 Received: from guile by serveur.guile.prv with local (Exim 3.22 #1 (Debian)) id 15iF0l-0001EG-00 for ; Sat, 15 Sep 2001 14:57:31 +0200 Date: Sat, 15 Sep 2001 14:57:31 +0200 From: Guillaume Lefevre To: linux-xfs@oss.sgi.com Subject: Re: Hard drive light won't go off? Message-ID: <20010915145731.A2724@serveur.guile.prv> References: <20010915121022.AF8A0139D6@linux.compucomis.net> <3BA3489A.D992BEF1@koschikode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BA3489A.D992BEF1@koschikode.com>; from juri@koschikode.com on Sat, Sep 15, 2001 at 02:24:58PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Mike Burger wrote: > I do have one other minor concern. > > This only seems to happen on the system on which I'm running XFS. > > The hard drive light will not turn off...it's like something is constantly > running the hard drive(s) on my system. not to worry its a motherboard issue. -- From owner-linux-xfs@oss.sgi.com Sat Sep 15 07:28:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8FESbf19608 for linux-xfs-outgoing; Sat, 15 Sep 2001 07:28:37 -0700 Received: from tux.rsn.bth.se (root@tux.rsn.bth.se [194.47.143.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8FESWe19589 for ; Sat, 15 Sep 2001 07:28:33 -0700 Received: from localhost (gandalf@localhost [127.0.0.1]) by localhost (8.12.0.Beta19/8.12.0.Beta19/Debian 8.12.0.Beta19) with ESMTP id f8FEQNCN025797; Sat, 15 Sep 2001 16:26:23 +0200 Date: Sat, 15 Sep 2001 16:26:23 +0200 (CEST) From: Martin Josefsson X-Sender: gandalf@tux.rsn.bth.se To: Mike Burger cc: linux-xfs@oss.sgi.com Subject: Re: Hard drive light won't go off? In-Reply-To: <20010915121022.AF8A0139D6@linux.compucomis.net> Message-ID: X-message-flag: Get yourself a real mail client! http://www.washington.edu/pine/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 15 Sep 2001, Mike Burger wrote: > I do have one other minor concern. > > This only seems to happen on the system on which I'm running XFS. > > The hard drive light will not turn off...it's like something is constantly > running the hard drive(s) on my system. > > It looked like it had stopped, at one point, when I had a 3 drive combo > going. I replaced two drives with a single large drive (1 swap partition, 2 > XFS partitions for /var and /home), and the hard drive light just stays > on, steady. > > Now, before anyone says it's got to be a matter of the wire being incorrectly > installed, the thing flashes just fine during the normal boot process. It > doesn't stay on steady until the thing is fully booted. > > Is there something in the XFS code that does some sort of major league > consistency checking over a period of time? This system is barely in use, > yet...only 3 users, of which I'm the only one doing anything, yet. I've seen this behaviour once, the light works as it should during boot but when something touches the cdrom it stays on constantly. No performance loss or anything, the same thing happand on that system in win98 and Linux so it's not a Linux issue. /Martin From owner-linux-xfs@oss.sgi.com Sat Sep 15 09:27:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8FGR8521228 for linux-xfs-outgoing; Sat, 15 Sep 2001 09:27:08 -0700 Received: from fe010.worldonline.dk (fe010.worldonline.dk [212.54.64.195]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8FGR2e21209 for ; Sat, 15 Sep 2001 09:27:02 -0700 Received: (qmail 16295 invoked by uid 0); 15 Sep 2001 16:26:55 -0000 Received: from 213.237.17.187.adsl.arc.worldonline.dk (HELO Jekaterina) (213.237.17.187) by fe010.worldonline.dk with SMTP; 15 Sep 2001 16:26:55 -0000 Message-ID: <005701c13e4e$a9dc41c0$8ae2fea9@Jekaterina> From: =?iso-8859-1?Q?Sune_M=F8lgaard?= To: Subject: Mount fails Date: Sat, 15 Sep 2001 18:26:51 -0700 Organization: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi. The other night, I suddenly found myself looking at the kernel debugger, which I must say, I don't like looking at. Not knowing what to do, I rebooted, and was quite sorry to see the following: ... dma_intr: status=0x51 {DriveReady SeekComplete Error} dma_intr: error=0x40 {UncorrectableError} LBAsect = 20078068, sector = 2059056 end_request: I/O error, dev 21:03 (hde), sector 2059056 I/O error in filesystem ("ide2(33,3)") meta-data dev 0x2103 block 0x1f6b30: xlog_recover_do(read) XFS: log mount/recovery failed XFS: log mount failed Kernel panic: VFS: Unable to mount root fs on 21:03 Kernel is 2.4.5 with SGI's XFS. Same day, I had added 512Mb ram and a DiskOnKey. can that have something to do with the matter? Is there anything to do in order to save my data? Best regards, Sune Mølgaard From owner-linux-xfs@oss.sgi.com Sat Sep 15 10:00:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8FH03321701 for linux-xfs-outgoing; Sat, 15 Sep 2001 10:00:03 -0700 Received: from sto-vo-kor.koschikode.com (sto-vo-kor.koschikode.com [195.124.129.42]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8FGxwe21650 for ; Sat, 15 Sep 2001 09:59:58 -0700 Received: from warp9.koschikode.com (pD9517F0B.dip.t-dialin.net [217.81.127.11]) by sto-vo-kor.koschikode.com (Postfix) with ESMTP id D8DA2B52B; Sat, 15 Sep 2001 18:59:54 +0200 (CEST) Received: from koschikode.com (kaplah.koschikode.com [192.168.200.15]) by warp9.koschikode.com (Postfix) with ESMTP id 3D90FCDF7; Sat, 15 Sep 2001 18:59:34 +0200 (CEST) Message-ID: <3BA388F3.ADD87809@koschikode.com> Date: Sat, 15 Sep 2001 18:59:31 +0200 From: Juri Haberland X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.10-pre4-ext3 i686) X-Accept-Language: en MIME-Version: 1.0 To: Sune =?iso-8859-1?Q?M=F8lgaard?= Cc: linux-xfs@oss.sgi.com Subject: Re: Mount fails References: <005701c13e4e$a9dc41c0$8ae2fea9@Jekaterina> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sune Mølgaard wrote: > > Hi. > > The other night, I suddenly found myself looking at the kernel debugger, > which I must say, I don't like looking at. Not knowing what to do, I > rebooted, and was quite sorry to see the following: > > ... > dma_intr: status=0x51 {DriveReady SeekComplete Error} > dma_intr: error=0x40 {UncorrectableError} LBAsect = 20078068, sector = > 2059056 > end_request: I/O error, dev 21:03 (hde), sector 2059056 > I/O error in filesystem ("ide2(33,3)") meta-data dev 0x2103 block 0x1f6b30: > xlog_recover_do(read) > XFS: log mount/recovery failed > XFS: log mount failed > Kernel panic: VFS: Unable to mount root fs on 21:03 > > Kernel is 2.4.5 with SGI's XFS. Same day, I had added 512Mb ram and a > DiskOnKey. can that have something to do with the matter? > Is there anything to do in order to save my data? I'd say your drive is broken :( Juri From owner-linux-xfs@oss.sgi.com Sat Sep 15 13:28:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8FKSZx24472 for linux-xfs-outgoing; Sat, 15 Sep 2001 13:28:35 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8FKSWe24453 for ; Sat, 15 Sep 2001 13:28:32 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id 5F172139D6; Sat, 15 Sep 2001 16:28:37 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id 5C188139D5; Sat, 15 Sep 2001 16:28:37 -0400 (EDT) Date: Sat, 15 Sep 2001 16:28:37 -0400 (EDT) From: Mike Burger To: Juri Haberland Cc: Subject: Re: Hard drive light won't go off? In-Reply-To: <3BA3489A.D992BEF1@koschikode.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 15 Sep 2001, Juri Haberland wrote: > > It looked like it had stopped, at one point, when I had a 3 drive combo > > going. I replaced two drives with a single large drive (1 swap partition, 2 > > XFS partitions for /var and /home), and the hard drive light just stays > > on, steady. > > > > Now, before anyone says it's got to be a matter of the wire being incorrectly > > installed, the thing flashes just fine during the normal boot process. It > > doesn't stay on steady until the thing is fully booted. > > > > Is there something in the XFS code that does some sort of major league > > consistency checking over a period of time? This system is barely in use, > > yet...only 3 users, of which I'm the only one doing anything, yet. > > Any logging going to syslog constantly? > Are running a RAID which might sync in the background? No RAID, and nothing really happening on the system to be logged, just yet. From owner-linux-xfs@oss.sgi.com Sat Sep 15 13:29:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8FKTKd24531 for linux-xfs-outgoing; Sat, 15 Sep 2001 13:29:20 -0700 Received: from linux.compucomis.net (IDENT:postfix@linux.CompuComIS.net [216.140.122.75]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8FKTIe24509 for ; Sat, 15 Sep 2001 13:29:18 -0700 Received: by linux.compucomis.net (Postfix, from userid 501) id 0E151139D6; Sat, 15 Sep 2001 16:29:24 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by linux.compucomis.net (Postfix) with ESMTP id 0B2DD139D5; Sat, 15 Sep 2001 16:29:24 -0400 (EDT) Date: Sat, 15 Sep 2001 16:29:23 -0400 (EDT) From: Mike Burger To: Guillaume Lefevre Cc: Subject: Re: Hard drive light won't go off? In-Reply-To: <20010915145731.A2724@serveur.guile.prv> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 15 Sep 2001, Guillaume Lefevre wrote: > Mike Burger wrote: > > I do have one other minor concern. > > > > This only seems to happen on the system on which I'm running XFS. > > > > The hard drive light will not turn off...it's like something is constantly > > running the hard drive(s) on my system. > not to worry its a motherboard issue. No...it's not a motherboard issue. From owner-linux-xfs@oss.sgi.com Sat Sep 15 13:32:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8FKWIq24739 for linux-xfs-outgoing; Sat, 15 Sep 2001 13:32:18 -0700 Received: from fe010.worldonline.dk (fe010.worldonline.dk [212.54.64.195]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8FKWFe24720 for ; Sat, 15 Sep 2001 13:32:16 -0700 Received: (qmail 15407 invoked by uid 0); 15 Sep 2001 20:32:09 -0000 Received: from 213.237.17.187.adsl.arc.worldonline.dk (HELO Jekaterina) (213.237.17.187) by fe010.worldonline.dk with SMTP; 15 Sep 2001 20:32:09 -0000 Message-ID: <007c01c13e70$ed5a1e50$8ae2fea9@Jekaterina> From: =?iso-8859-1?Q?Sune_M=F8lgaard?= To: References: <005701c13e4e$a9dc41c0$8ae2fea9@Jekaterina> <3BA388F3.ADD87809@koschikode.com> Subject: Re: Mount fails Date: Sat, 15 Sep 2001 22:32:08 -0700 Organization: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I'd say your drive is broken :( > > Juri > That's what I feared, but is there a way to restore at least some of the data? From owner-linux-xfs@oss.sgi.com Sat Sep 15 13:53:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8FKrXo25128 for linux-xfs-outgoing; Sat, 15 Sep 2001 13:53:33 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8FKrUe25109 for ; Sat, 15 Sep 2001 13:53:30 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15iMRN-0002ph-00; Sat, 15 Sep 2001 16:53:29 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f8FKrQA04225; Sat, 15 Sep 2001 16:53:26 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Sune =?iso-8859-1?q?M=F8lgaard?= Cc: Subject: Re: Mount fails References: <005701c13e4e$a9dc41c0$8ae2fea9@Jekaterina> <3BA388F3.ADD87809@koschikode.com> <007c01c13e70$ed5a1e50$8ae2fea9@Jekaterina> From: "Martin K. Petersen" Organization: mkp.net Date: 15 Sep 2001 16:53:26 -0400 In-Reply-To: <007c01c13e70$ed5a1e50$8ae2fea9@Jekaterina> Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >> I'd say your drive is broken :( Sune> That's what I feared, but is there a way to restore at least Sune> some of the data? Turn off any hdparm tunings you may have in your config files. Reboot. Then do an xfs_repair -n /dev/ And if that succeeds, xfs_repair /dev/ -- Martin K. Petersen Cereal Bowl Engineer, Linuxcare, Inc. http://mkp.net/ SGI XFS, Linux/PA-RISC, GNOME From owner-linux-xfs@oss.sgi.com Sun Sep 16 02:18:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8G9IhQ02201 for linux-xfs-outgoing; Sun, 16 Sep 2001 02:18:43 -0700 Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8G9Ice02182 for ; Sun, 16 Sep 2001 02:18:39 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.197]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8G9IXQ03281 for ; Sun, 16 Sep 2001 18:18:33 +0900 (JST) Received: from mailsv.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8G9IWZ25486 for ; Sun, 16 Sep 2001 18:18:33 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv.nec.co.jp (8.11.6/3.7W-MAILSV-NEC) with ESMTP id f8G9IWl11791 for ; Sun, 16 Sep 2001 18:18:32 +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 AAA483 for ; Sun, 16 Sep 2001 18:18:31 +0900 Received: FROM noshiro.bsd.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Sun Sep 16 18:18:29 2001 +0900 Received: from localhost (localhost [127.0.0.1]) by noshiro.bsd.tnes.nec.co.jp (Postfix) with ESMTP id 7450D660C; Sun, 16 Sep 2001 18:18:29 +0900 (JST) To: nathans@sgi.com, linux-xfs@oss.sgi.com Subject: Re: cannot mount snapshot In-Reply-To: <20010914111429.E410868@wobbly.melbourne.sgi.com> References: <20010913224933W.masano@tnes.nec.co.jp> <20010914111429.E410868@wobbly.melbourne.sgi.com> X-Mailer: Mew version 1.94.2 on XEmacs 21.4 (Artificial Intelligence) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010916181829U.masano@tnes.nec.co.jp> Date: Sun, 16 Sep 2001 18:18:29 +0900 (JST) From: ASANO Masahiro X-Dispatcher: imput version 20000228(IM140) Lines: 43 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 14 Sep 2001 11:14:30 +1100, Nathan Scott wrote: > hi, > > On Thu, Sep 13, 2001 at 10:49:33PM +0900, ASANO Masahiro wrote: > > Hi, > > > > I cannot mount the snapshot filesystem of the XFS filesystem. > > To make the snapshot, I used xfs_freeze. Why it couldn't be mounted? > > > > # lvcreate -L 132m -n masano1 vg0 > > # mkfs.xfs /dev/vg0/masano1 > > # mount -t xfs /dev/vg0/masano1 /mnt/masano1 > > # xfs_freeze -f /mnt/masano1 > > # lvcreate -L 60m -n masano2 -s /dev/vg0/masano1 > > # xfs_freeze -u /mnt/masano1 > > # mount -t xfs -o ro,nouuid /dev/vg0/masano2 /mnt/masano2 > > > > XFS mounting filesystem lvm(58,1) > > XFS: WARNING: recovery required on readonly filesystem. > > XFS: write access unavailable, cannot proceed. > In your case, it seems the driver has marked /dev/vg0/masano1 > as readonly (I don't know why that would be - looks like LVM). Nope. The readonly error occurred on "/dev/vg0/masano2" (snapshot side). I tried to mount /dev/vg0/masano2 with "-o ro", so it is readonly. "/dev/vg0/masano1" seems writable. lvm(58,0) >> /dev/vg0/masano1 >> original fs lvm(58,1) >> /dev/vg0/masano2 >> snapshot (ro) But the snapshot could be mounted with this sequence before 28th Aug. > > I noticed this may be occurred from "8/28 Merge irix6.5f:irix:101630a". I looked into xfs_recover() and found that the condition "(tail_blk != head_blk)" in xfs_recover() at fs/xfs/xfs_log_recover.c changed to true with adding xfs_fs_log_dummy() at fs/xfs/xfs_fsops.c. Is it right? -- masano From owner-linux-xfs@oss.sgi.com Sun Sep 16 03:06:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GA6IG03027 for linux-xfs-outgoing; Sun, 16 Sep 2001 03:06:18 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GA6Ae03008 for ; Sun, 16 Sep 2001 03:06:11 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 5F734C00B61 for ; Sun, 16 Sep 2001 18:06:02 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id BBC2DC00B60 for ; Sun, 16 Sep 2001 18:06:00 +0800 (PHT) Date: Sun, 16 Sep 2001 18:06:00 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Snapshotting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, To prevent against human error, I currently have a nightly script that does daily and weekly "snapshots" of a filesystem using tar + gzip. I end up with one "as of last night" set of tar.gz's, and one "as of last Sunday" set of tar.gz's that I access when things go wrong (user side, not machine failure). Agreeably this takes quite awhile to finish (luckily activity at night isn't significant), plus it takes up a lot of disk space. I've just been reading posts about snapshotting, and was wondering where I could get more information about this. In particular I wonder if the snapshotting of XFS (?) will help me save space, and will be faster. Also, my tar + gzip solution won't preserve ACLs anymore when I implement them (I'll probably wait for the major revamping of the code to more or less settle down before I do this). Note that I don't have LVM. I'm I reading snapshotting all wrong? Or perhaps is there some other alternative solution to my requirement? Thanks in advance, everyone! :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Sun Sep 16 03:06:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GA6ju03063 for linux-xfs-outgoing; Sun, 16 Sep 2001 03:06:45 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GA6de03044 for ; Sun, 16 Sep 2001 03:06:39 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id DAA10681 for ; Sun, 16 Sep 2001 03:06:42 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id VAA08831; Sun, 16 Sep 2001 21:05:21 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id UAA26104; Sun, 16 Sep 2001 20:05:20 +1000 (AEDT) Date: Sun, 16 Sep 2001 20:05:20 +1000 From: Nathan Scott To: ASANO Masahiro , sandeen@sgi.com Cc: linux-xfs@oss.sgi.com Subject: Re: cannot mount snapshot Message-ID: <20010916200520.A292893@wobbly.melbourne.sgi.com> References: <20010913224933W.masano@tnes.nec.co.jp> <20010914111429.E410868@wobbly.melbourne.sgi.com> <20010916181829U.masano@tnes.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010916181829U.masano@tnes.nec.co.jp>; from masano@tnes.nec.co.jp on Sun, Sep 16, 2001 at 06:18:29PM +0900 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Sun, Sep 16, 2001 at 06:18:29PM +0900, ASANO Masahiro wrote: > On Fri, 14 Sep 2001 11:14:30 +1100, Nathan Scott wrote: > > On Thu, Sep 13, 2001 at 10:49:33PM +0900, ASANO Masahiro wrote: > > > I cannot mount the snapshot filesystem of the XFS filesystem. > > > To make the snapshot, I used xfs_freeze. Why it couldn't be mounted? > > > > > > # lvcreate -L 132m -n masano1 vg0 > > > # mkfs.xfs /dev/vg0/masano1 > > > # mount -t xfs /dev/vg0/masano1 /mnt/masano1 > > > # xfs_freeze -f /mnt/masano1 > > > # lvcreate -L 60m -n masano2 -s /dev/vg0/masano1 > > > # xfs_freeze -u /mnt/masano1 > > > # mount -t xfs -o ro,nouuid /dev/vg0/masano2 /mnt/masano2 > > > > > > XFS mounting filesystem lvm(58,1) > > > XFS: WARNING: recovery required on readonly filesystem. > > > XFS: write access unavailable, cannot proceed. > > > In your case, it seems the driver has marked /dev/vg0/masano1 > > as readonly (I don't know why that would be - looks like LVM). > > Nope. The readonly error occurred on "/dev/vg0/masano2" (snapshot > side). Sorry - my mistake - thats what I meant (the snapshot). > I tried to mount /dev/vg0/masano2 with "-o ro", so it is > readonly. No, that doesn't mark the _device_ readonly it marks the _filesystem_ readonly. Journaling filesystems override this temporarily during mount if the log must be replayed. But if the device is readonly (as is the case with a snap- shot), then that overriding cannot happen, the log cannot be replayed, and so the filesystem cannot be mounted. It sounds like the problem is that the log was not dirty previous to this mod, but it is now still dirty on the snapshot (and it shouldn't be). > "/dev/vg0/masano1" seems writable. > > lvm(58,0) >> /dev/vg0/masano1 >> original fs > lvm(58,1) >> /dev/vg0/masano2 >> snapshot (ro) > > But the snapshot could be mounted with this sequence before 28th Aug. > > > > I noticed this may be occurred from "8/28 Merge irix6.5f:irix:101630a". > > I looked into xfs_recover() and found that the condition > "(tail_blk != head_blk)" in xfs_recover() at fs/xfs/xfs_log_recover.c > changed to true with adding xfs_fs_log_dummy() at fs/xfs/xfs_fsops.c. > Is it right? That condition basically equates to "do I need to do recovery". Sounds like previously (and correctly I think) this would have been false on the snapshot, but now it is true (ie. the snapshot has a dirty log - bad). Eric? Sounds like this mod may have introduced an XFS bug in Linux... thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Sep 16 03:20:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GAKGY03448 for linux-xfs-outgoing; Sun, 16 Sep 2001 03:20:16 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GAKEe03429 for ; Sun, 16 Sep 2001 03:20:14 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 39B601E09C; Sun, 16 Sep 2001 12:20:08 +0200 (MEST) Date: Sun, 16 Sep 2001 12:20:00 +0200 From: Andi Kleen To: Nathan Scott Cc: ASANO Masahiro , linux-xfs@oss.sgi.com Subject: Re: cannot mount snapshot Message-ID: <20010916122000.A13240@gruyere.muc.suse.de> References: <20010913224933W.masano@tnes.nec.co.jp> <20010914111429.E410868@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010914111429.E410868@wobbly.melbourne.sgi.com>; from nathans@sgi.com on Fri, Sep 14, 2001 at 11:14:30AM +1100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Sep 14, 2001 at 11:14:30AM +1100, Nathan Scott wrote: > In your case, it seems the driver has marked /dev/vg0/masano1 > as readonly (I don't know why that would be - looks like LVM). LVM snapshots are always read-only unless you add special patches. LVM only does block COW for writes to the original block device, not for the snapshot. While it is possible to patch it to do COW for snapshots also it is probably unsafe (LVM data structures are not journaled etc.) To handle such an unpatched LVM xfs_freeze would need to flush the log so that no recovery is needed. I actually though it did so already, but it seems that was mistaken. -Andi From owner-linux-xfs@oss.sgi.com Sun Sep 16 03:21:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GALTF03530 for linux-xfs-outgoing; Sun, 16 Sep 2001 03:21:29 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GALRe03499 for ; Sun, 16 Sep 2001 03:21:27 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 860C21E09F; Sun, 16 Sep 2001 12:21:21 +0200 (MEST) Date: Sun, 16 Sep 2001 12:21:18 +0200 From: Andi Kleen To: Federico Sevilla III Cc: Linux XFS Mailing List Subject: Re: Snapshotting Message-ID: <20010916122118.B13240@gruyere.muc.suse.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jijo@leathercollection.ph on Sun, Sep 16, 2001 at 06:06:00PM +0800 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Sep 16, 2001 at 06:06:00PM +0800, Federico Sevilla III wrote: > I've just been reading posts about snapshotting, and was wondering where I > could get more information about this. In particular I wonder if the > snapshotting of XFS (?) will help me save space, and will be faster. Also, LVM snapshots currently are not persistent, so they would be all gone after an reboot. -Andi From owner-linux-xfs@oss.sgi.com Sun Sep 16 07:06:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GE6bC11654 for linux-xfs-outgoing; Sun, 16 Sep 2001 07:06:37 -0700 Received: from athena (jcb.yi.org [80.65.224.59]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GE6Xe11633 for ; Sun, 16 Sep 2001 07:06:34 -0700 Received: by zeus (Postfix, from userid 1000) id 019FA12A1; Sun, 16 Sep 2001 16:03:16 +0200 (CEST) Date: Sun, 16 Sep 2001 16:03:16 +0200 From: Jean-charles To: linux-xfs@oss.sgi.com Subject: mainstream Message-ID: <20010916160316.A1643@zeus.jcb.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.20i X-Location: home Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, when will the the mainstream kernel have xfs support ? From owner-linux-xfs@oss.sgi.com Sun Sep 16 09:19:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GGJqE13495 for linux-xfs-outgoing; Sun, 16 Sep 2001 09:19:52 -0700 Received: from burgers (IDENT:postfix@burgers.bubbanfriends.org [216.140.122.113]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GGJoe13476 for ; Sun, 16 Sep 2001 09:19:50 -0700 Received: by burgers (Postfix, from userid 500) id 898274001BA; Sun, 16 Sep 2001 12:19:54 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by burgers (Postfix) with ESMTP id 87C142400219; Sun, 16 Sep 2001 12:19:54 -0400 (EDT) Date: Sun, 16 Sep 2001 12:19:54 -0400 (EDT) From: Mike Burger To: Jean-charles Cc: Subject: Re: mainstream In-Reply-To: <20010916160316.A1643@zeus.jcb.yi.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 16 Sep 2001, Jean-charles wrote: > hi, > > when will the the mainstream kernel have xfs support ? When Linus Torvalds and the folks who maintain the mainstream kernel decide that they want to include it. From owner-linux-xfs@oss.sgi.com Sun Sep 16 09:29:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GGTNW13694 for linux-xfs-outgoing; Sun, 16 Sep 2001 09:29:23 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GGTLe13675 for ; Sun, 16 Sep 2001 09:29:21 -0700 Received: from lock.thedot.net (grapefruit.iasi.rdsnet.ro [217.156.28.35]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id JAB01183 for ; Sun, 16 Sep 2001 09:27:15 -0700 (PDT) mail_from (laur@grapefruitdesign.com) Received: from smith.thedot.net (IDENT:laur@smith.thedot.net [217.156.29.18]) by lock.thedot.net (8.11.2/8.11.2) with ESMTP id f8GGLFd25646 for ; Sun, 16 Sep 2001 19:21:15 +0300 Subject: how to resize a XFS partition From: Laurian Gridinoc To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12.99+cvs.2001.08.21.23.41 (Preview Release) Date: 16 Sep 2001 19:21:12 +0300 Message-Id: <1000657272.8633.80.camel@smith.thedot.net> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello there, Is there a way to resize [grow] a XFS partition? Thank you, -- Laurian Gridinoc Chief Web Developer GRAPEFRUIT DESIGN ---------------------------------------------------------------------- e-mail: laur@grapefruitdesign.com ICQ: 73831683 mobile: +40 95 304379 voice/fax: (032) 233068 (Romania) voice/fax: (646) 349-2916 (United States) voice/fax: (0845) 127-5996 (UK) web: www.grapefruitdesign.com ---------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Sun Sep 16 09:40:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GGe7913976 for linux-xfs-outgoing; Sun, 16 Sep 2001 09:40:07 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GGe4e13957 for ; Sun, 16 Sep 2001 09:40:04 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15iexf-0005n7-00; Sun, 16 Sep 2001 12:40:03 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f8GGe2B25828; Sun, 16 Sep 2001 12:40:02 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Laurian Gridinoc Cc: linux-xfs@oss.sgi.com Subject: Re: how to resize a XFS partition References: <1000657272.8633.80.camel@smith.thedot.net> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 16 Sep 2001 12:40:02 -0400 In-Reply-To: <1000657272.8633.80.camel@smith.thedot.net> Message-ID: Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Laurian" == Laurian Gridinoc writes: Laurian> Is there a way to resize [grow] a XFS partition? man xfs_growfs -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Sun Sep 16 11:21:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GILg415157 for linux-xfs-outgoing; Sun, 16 Sep 2001 11:21:42 -0700 Received: from europa.cox-internet.com (europa-cox.cox-internet.com [208.180.118.40]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GILde15138 for ; Sun, 16 Sep 2001 11:21:39 -0700 Received: from moe ([208.180.28.9]) by europa.cox-internet.com (InterMail vK.4.02.00.10 201-232-116-110 license dd72657b95c070b1853187e4f5a0d6a7) with SMTP id <20010916181835.LTPC24301.europa@moe> for ; Sun, 16 Sep 2001 13:18:35 -0500 Message-ID: <000701c13edc$bcb091a0$0201a8c0@moe> From: "Stephen Parker" To: Subject: question concerning upgrades Date: Sun, 16 Sep 2001 13:23:46 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk In the event that Redhat goes to another version number, will I be able to upgrade redhat using their cd? As opposed to waiting for an xfs install cd from SGI? -sp From owner-linux-xfs@oss.sgi.com Sun Sep 16 11:24:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GIOKT15308 for linux-xfs-outgoing; Sun, 16 Sep 2001 11:24:20 -0700 Received: from smtp-20v.tesionmail.de (smtp-20v.tesionmail.de [213.182.133.8] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GIOHe15289 for ; Sun, 16 Sep 2001 11:24:18 -0700 Received: from tesionmail.de ([195.226.100.18]) by smtp-20v.tesionmail.de (Netscape Messaging Server 4.15) with ESMTP id GJRPM300.9QR for ; Sun, 16 Sep 2001 20:20:27 +0200 Message-ID: <3BA4EE49.6090006@tesionmail.de> Date: Sun, 16 Sep 2001 20:24:09 +0200 From: Gerd Bitzer User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Integration of xfs into actual kernels Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ladies and Gentlemen, I'd like to use XFS frequently, and preferably for my /boot and /root slices. But it is always a circumstance to stay in sync with the actual kernel release, first one has to grab the actual kernel or the kernelpatch, then one has to wait until you have also released a patch and also has to patch it into the kernel tree (and also one has to preserver an unpatched kernelsourcetree which first could be patched up to the next release, before your patches could also be patched in), and then the recompilation (which sometimes also offers some surprises). Hopefully XFS would be integrated into the standard kernel tree as soon as possible, to ease this boring process. Could you please tell me when this may be happening ? From owner-linux-xfs@oss.sgi.com Sun Sep 16 11:28:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GIS7S15487 for linux-xfs-outgoing; Sun, 16 Sep 2001 11:28:07 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GIS5e15468 for ; Sun, 16 Sep 2001 11:28:05 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 69CCB1AB11 for ; Sun, 16 Sep 2001 14:28:04 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 9E3FA132C; Sun, 16 Sep 2001 14:28:03 -0400 (EDT) Date: Sun, 16 Sep 2001 14:28:03 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: Mount fails Message-ID: <20010916142803.B13794@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <005701c13e4e$a9dc41c0$8ae2fea9@Jekaterina> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <005701c13e4e$a9dc41c0$8ae2fea9@Jekaterina> User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, Sep 15, 2001 at 06:26:51PM -0700, Sune Mølgaard wrote: > Kernel is 2.4.5 with SGI's XFS. Same day, I had added 512Mb > ram and a DiskOnKey. can that have something to do with the > matter? Is there anything to do in order to save my data? Don't forget to double check all your cables, just in case... Andrew Klaassen From owner-linux-xfs@oss.sgi.com Sun Sep 16 12:01:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GJ1RW16082 for linux-xfs-outgoing; Sun, 16 Sep 2001 12:01:27 -0700 Received: from vitelus.com (vitelus.com [64.81.243.207]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GJ1Oe16062 for ; Sun, 16 Sep 2001 12:01:24 -0700 Received: from aaronl by vitelus.com with local (Exim 3.32 #1 (Debian)) id 15ihAR-00008J-00; Sun, 16 Sep 2001 12:01:23 -0700 Date: Sun, 16 Sep 2001 12:01:23 -0700 From: Aaron Lehmann To: linux-xfs@oss.sgi.com Subject: Bizarre in-memory corruption when deleting files in certain dir Message-ID: <20010916120123.A417@vitelus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I've been using XFS for quite awhile, and it's worked flawlessly. Until recently. I've had the peculiar problem that when I delete a file in ~/mail, the system often gives the following message: xfs_force_shutdown(ide1(22,65),0x8) called from line 4072 of file xfs_bmap.c. Return address = 0xc01928a8 Corruption of in-memory data detected. Shutting down filesystem: ide1(22,65) Please umount the filesystem, and rectify the problem(s) I can usually trigger the problem by deleting 3 or 4 files in ~/mail. I'm doing this as an unpriviledged user, which is scary. After this occurs, /home is shown to be mounted, but to userspace it looks empty. lsing any dir that i'm already cd'd into shows no files. To fix this, I have to reboot, since /home is typically "in use" and umount won't let me unmount it. Once I reboot, I usually get the same message and effects when it tries to mount the drive. HOWEVER, if I unmount /home immediately and then remount it, all the files are back. What can I do? Please help me ;-). I'm running linux 2.4.9-xfs from maybe a month ago, but the problem has persisted in a few previous versions. Is the "stable" tree any better? From owner-linux-xfs@oss.sgi.com Sun Sep 16 12:20:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GJKWS16499 for linux-xfs-outgoing; Sun, 16 Sep 2001 12:20:32 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GJKTe16480 for ; Sun, 16 Sep 2001 12:20:29 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA18745; Sun, 16 Sep 2001 21:20:19 +0200 (CEST) Message-Id: <4.3.2.7.2.20010916211729.03dc45a0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 16 Sep 2001 21:19:50 +0200 To: Aaron Lehmann , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Bizarre in-memory corruption when deleting files in certain dir In-Reply-To: <20010916120123.A417@vitelus.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 12:01 16-9-2001 -0700, Aaron Lehmann wrote: >Hi, > >I've been using XFS for quite awhile, and it's worked flawlessly. >Until recently. I've had the peculiar problem that when I delete a >file in ~/mail, the system often gives the following message: Have you repaired the fs with xfs_repair? -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Sep 16 12:29:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GJT7316708 for linux-xfs-outgoing; Sun, 16 Sep 2001 12:29:07 -0700 Received: from vitelus.com (vitelus.com [64.81.243.207]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GJT6e16689 for ; Sun, 16 Sep 2001 12:29:06 -0700 Received: from aaronl by vitelus.com with local (Exim 3.32 #1 (Debian)) id 15ihbD-00007T-00; Sun, 16 Sep 2001 12:29:03 -0700 Date: Sun, 16 Sep 2001 12:29:03 -0700 From: Aaron Lehmann To: Seth Mos Cc: linux-xfs@oss.sgi.com Subject: Re: Bizarre in-memory corruption when deleting files in certain dir Message-ID: <20010916122903.A451@vitelus.com> References: <20010916120123.A417@vitelus.com> <4.3.2.7.2.20010916211729.03dc45a0@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.3.2.7.2.20010916211729.03dc45a0@pop.xs4all.nl> User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Sep 16, 2001 at 09:19:50PM +0200, Seth Mos wrote: > At 12:01 16-9-2001 -0700, Aaron Lehmann wrote: > >Hi, > > > >I've been using XFS for quite awhile, and it's worked flawlessly. > >Until recently. I've had the peculiar problem that when I delete a > >file in ~/mail, the system often gives the following message: > > Have you repaired the fs with xfs_repair? After doing so, I can't reproduce the problem. Thanks. From owner-linux-xfs@oss.sgi.com Sun Sep 16 13:55:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GKt1o17882 for linux-xfs-outgoing; Sun, 16 Sep 2001 13:55:01 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GKsve17862 for ; Sun, 16 Sep 2001 13:54:58 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA17276; Sun, 16 Sep 2001 22:54:53 +0200 (CEST) Message-Id: <4.3.2.7.2.20010916225342.03db62f8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 16 Sep 2001 22:54:39 +0200 To: Aaron Lehmann From: Seth Mos Subject: Re: Bizarre in-memory corruption when deleting files in certain dir Cc: linux-xfs@oss.sgi.com In-Reply-To: <20010916122903.A451@vitelus.com> References: <4.3.2.7.2.20010916211729.03dc45a0@pop.xs4all.nl> <20010916120123.A417@vitelus.com> <4.3.2.7.2.20010916211729.03dc45a0@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 12:29 16-9-2001 -0700, Aaron Lehmann wrote: >On Sun, Sep 16, 2001 at 09:19:50PM +0200, Seth Mos wrote: > > At 12:01 16-9-2001 -0700, Aaron Lehmann wrote: > > >Hi, > > > > > >I've been using XFS for quite awhile, and it's worked flawlessly. > > >Until recently. I've had the peculiar problem that when I delete a > > >file in ~/mail, the system often gives the following message: > > > > Have you repaired the fs with xfs_repair? > >After doing so, I can't reproduce the problem. Thanks. If you don't fix an error it will haunt you. The fs was shutdown because it detected an error and implies that you should run xfs_repair. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Sep 16 13:57:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GKvRA18027 for linux-xfs-outgoing; Sun, 16 Sep 2001 13:57:27 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GKvOe18008 for ; Sun, 16 Sep 2001 13:57:24 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15iiyh-00069N-00; Sun, 16 Sep 2001 16:57:23 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f8GKvMn26109; Sun, 16 Sep 2001 16:57:22 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: "Stephen Parker" Cc: Subject: Re: question concerning upgrades References: <000701c13edc$bcb091a0$0201a8c0@moe> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 16 Sep 2001 16:57:22 -0400 In-Reply-To: <000701c13edc$bcb091a0$0201a8c0@moe> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Stephen" == Stephen Parker writes: Stephen> In the event that Redhat goes to another version number, will Stephen> I be able to upgrade redhat using their cd? As opposed to Stephen> waiting for an xfs install cd from SGI? No, because the Red Hat kernel doesn't support XFS so you can't read and write your filesystems. But you can do a `manual' upgrade by installing the new Red Hat RPMs, of course. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Sun Sep 16 13:59:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GKxB718172 for linux-xfs-outgoing; Sun, 16 Sep 2001 13:59:11 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GKx7e18153 for ; Sun, 16 Sep 2001 13:59:07 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15ij0M-00069X-00; Sun, 16 Sep 2001 16:59:06 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f8GKx6526112; Sun, 16 Sep 2001 16:59:06 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Gerd Bitzer Cc: linux-xfs@oss.sgi.com Subject: Re: Integration of xfs into actual kernels References: <3BA4EE49.6090006@tesionmail.de> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 16 Sep 2001 16:59:06 -0400 In-Reply-To: <3BA4EE49.6090006@tesionmail.de> Message-ID: Lines: 28 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Gerd" == Gerd Bitzer writes: Gerd> I'd like to use XFS frequently, and preferably for my /boot and Gerd> /root slices. But it is always a circumstance to stay in sync Gerd> with the actual kernel release, first one has to grab the actual Gerd> kernel or the kernelpatch, then one has to wait until you have Gerd> also released a patch and also has to patch it into the kernel Gerd> tree (and also one has to preserver an unpatched Gerd> kernelsourcetree which first could be patched up to the next Gerd> release, before your patches could also be patched in), and then Gerd> the recompilation (which sometimes also offers some Gerd> surprises). Or you can simply use our development CVS tree which is almost always up to date. Gerd> Hopefully XFS would be integrated into the standard kernel tree Gerd> as soon as possible, to ease this boring process. Gerd> Could you please tell me when this may be happening ? Whenever Linus feels like it... -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Sun Sep 16 14:06:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GL6a018406 for linux-xfs-outgoing; Sun, 16 Sep 2001 14:06:36 -0700 Received: from burgers (IDENT:postfix@burgers.bubbanfriends.org [216.140.122.113]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GL6Xe18387 for ; Sun, 16 Sep 2001 14:06:33 -0700 Received: by burgers (Postfix, from userid 500) id 34AC64001BA; Sun, 16 Sep 2001 17:06:39 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by burgers (Postfix) with ESMTP id 2C9122400219; Sun, 16 Sep 2001 17:06:39 -0400 (EDT) Date: Sun, 16 Sep 2001 17:06:39 -0400 (EDT) From: Mike Burger To: "Martin K. Petersen" Cc: Stephen Parker , Subject: Re: question concerning upgrades In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Of course, you can also wait, after the next Red Hat release, for the XFS crew to put together a new installer CD to go with it...and then go to town. On 16 Sep 2001, Martin K. Petersen wrote: > >>>>> "Stephen" == Stephen Parker writes: > > Stephen> In the event that Redhat goes to another version number, will > Stephen> I be able to upgrade redhat using their cd? As opposed to > Stephen> waiting for an xfs install cd from SGI? > > No, because the Red Hat kernel doesn't support XFS so you can't read > and write your filesystems. > > But you can do a `manual' upgrade by installing the new Red Hat RPMs, > of course. > > From owner-linux-xfs@oss.sgi.com Sun Sep 16 14:17:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GLHNA18651 for linux-xfs-outgoing; Sun, 16 Sep 2001 14:17:23 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GLHJe18629 for ; Sun, 16 Sep 2001 14:17:19 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15ijHw-0006B3-00; Sun, 16 Sep 2001 17:17:16 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f8GLHGV26139; Sun, 16 Sep 2001 17:17:16 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Mike Burger Cc: Stephen Parker , Subject: Re: question concerning upgrades References: From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 16 Sep 2001 17:17:16 -0400 In-Reply-To: Message-ID: Lines: 20 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Mike" == Mike Burger writes: Mike> Of course, you can also wait, after the next Red Hat release, Mike> for the XFS crew to put together a new installer CD to go with Mike> it...and then go to town. Yes. FWIW, I've already taken a few initial stabs at it. The new Red Hat installer has better support for handling multiple filesystems, so it is easier to deal with than 7.1 was. We usually have an installer out within a few days of a RH release. Whether it will happen this time depends on a lot of things. But we're trying... -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Sun Sep 16 14:18:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GLINF18777 for linux-xfs-outgoing; Sun, 16 Sep 2001 14:18:23 -0700 Received: from TDN.TelDa.Net (GEOV11.TelDa.Net [193.96.236.53]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GLIDe18756 for ; Sun, 16 Sep 2001 14:18:14 -0700 Received: from profimail.de 217.1.158.171 by TDN.TelDa.Net; Sun, 16 Sep 2001 23:17:34 +0200 Message-ID: <3BA51722.4DE70A6A@profimail.de> Date: Sun, 16 Sep 2001 23:18:26 +0200 From: Bernd Birkholz X-Mailer: Mozilla 4.75C-SGI [en] (X11; I; IRIX 6.5 IP22) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Problems with driver disk Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, I did want to use xfs on my new server system because I learnt to appreciate this filesystem under IRIX. So I downloaded your installer iso image and burnt it on CD. Since the RAID driver in RedHat 7.1 for my RAID-Controller was corrupt I got a driver disk. This one was working correctly with RedHat's original install CD. After using your installer CD in expert mode with driver disk I got unfortunately the following error. After choosing "custom installation" this message occurs: No Drives Found An error has occured - no valid devices were found on which to create new filesystems. Please check your hardware for the cause of this problem. Perhaps you have an idea to solve this...... Kind regards Bernd Birkholz From owner-linux-xfs@oss.sgi.com Sun Sep 16 14:27:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8GLRSv19004 for linux-xfs-outgoing; Sun, 16 Sep 2001 14:27:28 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8GLROe18982 for ; Sun, 16 Sep 2001 14:27:25 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15ijRi-0006CI-00; Sun, 16 Sep 2001 17:27:22 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f8GLRLs26257; Sun, 16 Sep 2001 17:27:21 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Bernd Birkholz Cc: linux-xfs@oss.sgi.com Subject: Re: Problems with driver disk References: <3BA51722.4DE70A6A@profimail.de> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 16 Sep 2001 17:27:21 -0400 In-Reply-To: <3BA51722.4DE70A6A@profimail.de> Message-ID: Lines: 24 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Bernd" == Bernd Birkholz writes: Bernd> Hello, I did want to use xfs on my new server system because I Bernd> learnt to appreciate this filesystem under IRIX. So I Bernd> downloaded your installer iso image and burnt it on CD. Since Bernd> the RAID driver in RedHat 7.1 for my RAID-Controller was Bernd> corrupt I got a driver disk. This one was working correctly Bernd> with RedHat's original install CD. After using your installer Bernd> CD in expert mode with driver disk I got unfortunately the Bernd> following error. After choosing "custom installation" this Bernd> message occurs: Bernd> No Drives Found An error has occured - no valid devices were Bernd> found on which to create new filesystems. Please check your Bernd> hardware for the cause of this problem. Well. You can't use a device driver compiled against Red Hat's kernel. Which RAID controller are you using? -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Sun Sep 16 17:31:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8H0VcU21861 for linux-xfs-outgoing; Sun, 16 Sep 2001 17:31:38 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8H0VZe21842 for ; Sun, 16 Sep 2001 17:31:35 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 045FFC00B61 for ; Mon, 17 Sep 2001 08:31:33 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 7A2C0C00B60 for ; Mon, 17 Sep 2001 08:31:31 +0800 (PHT) Date: Mon, 17 Sep 2001 08:31:31 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Re: mainstream In-Reply-To: <20010916160316.A1643@zeus.jcb.yi.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 16 Sep 2001 at 16:03, Jean-charles wrote: > when will the the mainstream kernel have xfs support ? is perhaps the best answer to that. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Sun Sep 16 19:15:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8H2FxS23575 for linux-xfs-outgoing; Sun, 16 Sep 2001 19:15:59 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8H2Fge23554 for ; Sun, 16 Sep 2001 19:15:42 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8H2Fa515584 for ; Sun, 16 Sep 2001 19:15:36 -0700 Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id MAA01886; Mon, 17 Sep 2001 12:15:31 +1000 Date: Mon, 17 Sep 2001 12:15:31 +1000 From: Keith Owens Message-Id: <200109170215.MAA01886@sherman.melbourne.sgi.com> Subject: TAKE - Upgrade to 2.4.10-pre10 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Upgrade to 2.4.10-pre10 Date: Sun Sep 16 19:09:52 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102868a linux/drivers/usb/serial/xircom_pgs.S - 1.1 linux/drivers/usb/serial/xircom_pgs_fw.h - 1.1 linux/fs/jffs2/Makefile - 1.1 linux/fs/jffs2/TODO - 1.1 linux/fs/jffs2/background.c - 1.1 linux/fs/jffs2/build.c - 1.1 linux/fs/jffs2/compr.c - 1.1 linux/fs/jffs2/compr_rtime.c - 1.1 linux/fs/jffs2/compr_rubin.c - 1.1 linux/fs/jffs2/compr_rubin.h - 1.1 linux/fs/jffs2/compr_zlib.c - 1.1 linux/fs/jffs2/comprtest.c - 1.1 linux/fs/jffs2/crc32.c - 1.1 linux/fs/jffs2/crc32.h - 1.1 linux/fs/jffs2/dir.c - 1.1 linux/fs/jffs2/erase.c - 1.1 linux/fs/jffs2/file.c - 1.1 linux/fs/jffs2/gc.c - 1.1 linux/fs/jffs2/histo.h - 1.1 linux/fs/jffs2/histo_mips.h - 1.1 linux/fs/jffs2/ioctl.c - 1.1 linux/fs/jffs2/malloc.c - 1.1 linux/fs/jffs2/nodelist.c - 1.1 linux/fs/jffs2/nodelist.h - 1.1 linux/fs/jffs2/nodemgmt.c - 1.1 linux/fs/jffs2/pushpull.c - 1.1 linux/fs/jffs2/pushpull.h - 1.1 linux/fs/jffs2/read.c - 1.1 linux/include/linux/raid/multipath.h - 1.1 linux/fs/jffs2/readinode.c - 1.1 linux/fs/jffs2/scan.c - 1.1 linux/fs/jffs2/super.c - 1.1 linux/fs/jffs2/symlink.c - 1.1 linux/fs/jffs2/write.c - 1.1 linux/fs/jffs2/zlib.c - 1.1 linux/fs/jffs2/zlib.h - 1.1 linux/include/linux/jffs2_fs_sb.h - 1.1 linux/include/linux/jffs2_fs_i.h - 1.1 linux/drivers/md/multipath.c - 1.1 linux/include/linux/i2c-algo-ite.h - 1.1 linux/include/linux/jffs2.h - 1.1 linux/scripts/mkdep.c - 1.13 linux/net/unix/af_unix.c - 1.35 linux/net/sunrpc/sched.c - 1.18 linux/net/irda/af_irda.c - 1.26 linux/mm/vmscan.c - 1.73 linux/mm/swapfile.c - 1.36 linux/mm/mmap.c - 1.39 linux/mm/memory.c - 1.59 linux/mm/filemap.c - 1.85 linux/kernel/fork.c - 1.36 linux/ipc/shm.c - 1.49 linux/ipc/msg.c - 1.12 linux/include/linux/swap.h - 1.38 linux/include/linux/nfsd/nfsd.h - 1.14 linux/include/linux/mm.h - 1.63 linux/include/linux/genhd.h - 1.15 linux/include/linux/fs.h - 1.118 linux/include/asm-i386/ptrace.h - 1.8 linux/include/asm-i386/processor.h - 1.27 linux/include/asm-alpha/processor.h - 1.12 linux/fs/nfsd/vfs.c - 1.36 linux/fs/nfsd/nfssvc.c - 1.14 linux/fs/nfsd/nfsproc.c - 1.17 linux/fs/nfsd/nfsctl.c - 1.21 linux/fs/nfsd/lockd.c - 1.7 linux/fs/lockd/svc.c - 1.10 linux/fs/inode.c - 1.51 linux/fs/exec.c - 1.46 linux/fs/autofs/root.c - 1.15 linux/drivers/video/offb.c - 1.17 linux/drivers/video/newport_con.c - 1.8 linux/drivers/video/fbmem.c - 1.38 linux/drivers/video/Makefile - 1.33 linux/drivers/video/Config.in - 1.28 linux/drivers/sound/sonicvibes.c - 1.34 linux/drivers/sound/gus_wave.c - 1.8 linux/drivers/sound/es1371.c - 1.34 linux/drivers/sound/es1370.c - 1.33 linux/drivers/sound/Makefile - 1.32 linux/drivers/sound/Config.in - 1.28 linux/drivers/scsi/sym53c8xx_defs.h - 1.10 linux/drivers/scsi/sg.c - 1.21 linux/drivers/scsi/seagate.c - 1.13 linux/drivers/scsi/NCR53C9x.h - 1.6 linux/drivers/isdn/sc/debug.c - 1.5 linux/drivers/isdn/isdnloop/isdnloop.c - 1.9 linux/drivers/isdn/isdn_net.c - 1.24 linux/drivers/isdn/isdn_common.c - 1.28 linux/drivers/isdn/icn/icn.c - 1.16 linux/drivers/isdn/hisax/l3dss1.c - 1.12 linux/drivers/fc4/socal.c - 1.9 linux/drivers/fc4/soc.c - 1.8 linux/drivers/fc4/fc.c - 1.7 linux/drivers/char/tty_io.c - 1.35 linux/drivers/char/tpqic02.c - 1.15 linux/drivers/char/synclink.c - 1.18 linux/drivers/char/serial167.c - 1.10 linux/drivers/char/random.c - 1.17 linux/drivers/char/nvram.c - 1.17 linux/drivers/char/mem.c - 1.39 linux/drivers/char/lp.c - 1.24 linux/drivers/char/ftape/lowlevel/ftape-calibr.c - 1.4 linux/drivers/char/cyclades.c - 1.20 linux/drivers/char/atixlmouse.c - 1.8 linux/drivers/char/atarimouse.c - 1.8 linux/drivers/char/Config.in - 1.48 linux/drivers/block/ps2esdi.c - 1.22 linux/drivers/block/Config.in - 1.34 linux/arch/i386/kernel/time.c - 1.16 linux/arch/i386/kernel/signal.c - 1.19 linux/arch/i386/kernel/ptrace.c - 1.16 linux/arch/i386/defconfig - 1.70 linux/arch/i386/boot/install.sh - 1.3 linux/arch/i386/boot/bootsect.S - 1.13 linux/Makefile - 1.123 linux/MAINTAINERS - 1.72 linux/Documentation/Configure.help - 1.98 linux/drivers/video/cyber2000fb.c - 1.25 linux/drivers/usb/acm.c - 1.40 linux/drivers/isdn/hisax/hfc_pci.c - 1.19 linux/drivers/isdn/divert/isdn_divert.c - 1.7 linux/drivers/isdn/divert/divert_procfs.c - 1.14 linux/drivers/isdn/divert/divert_init.c - 1.5 linux/drivers/atm/zatm.c - 1.12 linux/drivers/atm/eni.c - 1.12 linux/drivers/net/wan/sbni.c - 1.16 linux/drivers/net/wan/cycx_x25.c - 1.15 linux/drivers/video/tdfxfb.c - 1.12 linux/drivers/usb/dc2xx.c - 1.21 linux/include/linux/agp_backend.h - 1.12 linux/drivers/char/agp/agpgart_be.c - 1.23 linux/drivers/char/agp/agp.h - 1.15 linux/drivers/i2c/Config.in - 1.4 linux/drivers/usb/dabusb.c - 1.13 linux/drivers/usb/usbmouse.c - 1.13 linux/drivers/usb/usbkbd.c - 1.18 linux/drivers/usb/ov511.c - 1.26 linux/drivers/usb/usb-ohci.c - 1.27 linux/drivers/char/vme_scc.c - 1.6 linux/include/linux/raid/md_u.h - 1.6 linux/include/linux/raid/md_k.h - 1.13 linux/include/linux/raid/md_compatible.h - 1.5 linux/drivers/char/amiserial.c - 1.10 linux/drivers/isdn/hisax/hfc_sx.c - 1.9 linux/arch/i386/kernel/microcode.c - 1.10 linux/fs/devfs/base.c - 1.19 linux/drivers/video/matrox/matroxfb_base.h - 1.7 linux/drivers/net/tulip/tulip_core.c - 1.28 linux/drivers/char/nwbutton.c - 1.6 linux/include/linux/brlock.h - 1.5 linux/drivers/usb/rio500.c - 1.14 linux/drivers/usb/pegasus.c - 1.21 linux/drivers/video/hgafb.c - 1.8 linux/drivers/char/sh-sci.c - 1.14 linux/drivers/usb/serial/usb-serial.h - 1.14 linux/drivers/usb/serial/Makefile - 1.15 linux/net/ipv4/netfilter/ipchains_core.c - 1.7 linux/net/ipv4/netfilter/ip_tables.c - 1.10 linux/net/ipv4/netfilter/ip_queue.c - 1.10 linux/net/ipv4/netfilter/ip_fw_compat_masq.c - 1.6 linux/net/ipv4/netfilter/ip_conntrack_standalone.c - 1.9 linux/drivers/net/pcmcia/xircom_tulip_cb.c - 1.13 linux/drivers/usb/serial/keyspan_pda.c - 1.16 linux/drivers/usb/serial/ftdi_sio.c - 1.21 linux/drivers/usb/serial/usbserial.c - 1.22 linux/drivers/usb/serial/whiteheat.c - 1.17 linux/drivers/usb/serial/visor.c - 1.23 linux/drivers/usb/serial/omninet.c - 1.15 linux/drivers/usb/serial/digi_acceleport.c - 1.17 linux/drivers/char/rio/riotable.c - 1.5 linux/drivers/char/joystick/gameport.c - 1.5 linux/drivers/char/joystick/analog.c - 1.5 linux/drivers/usb/storage/usb.c - 1.12 linux/drivers/usb/storage/transport.c - 1.13 linux/drivers/usb/storage/scsiglue.c - 1.14 linux/drivers/usb/serial/keyspan.c - 1.13 linux/drivers/usb/microtek.c - 1.10 linux/drivers/usb/bluetooth.c - 1.17 linux/fs/jffs/inode-v23.c - 1.12 linux/fs/jffs/intrep.c - 1.8 linux/fs/jffs/jffs_fm.c - 1.5 linux/include/linux/mtd/doc2000.h - 1.4 linux/drivers/usb/storage/sddr09.c - 1.10 linux/drivers/isdn/hisax/l3ni1.c - 1.5 linux/drivers/isdn/eicon/uxio.h - 1.4 linux/drivers/isdn/eicon/linio.c - 1.4 linux/drivers/char/serial_amba.c - 1.5 linux/drivers/md/Config.in - 1.3 linux/drivers/md/Makefile - 1.5 linux/drivers/md/md.c - 1.23 linux/drivers/net/winbond-840.c - 1.11 linux/drivers/usb/serial/belkin_sa.c - 1.10 linux/drivers/video/sis/sis_main.c - 1.5 linux/include/asm-i386/xor.h - 1.2 linux/Documentation/parisc/registers - 1.2 linux/drivers/usb/serial/mct_u232.c - 1.9 linux/drivers/usb/serial/empeg.c - 1.13 linux/drivers/usb/serial/Config.in - 1.8 linux/drivers/char/drm/radeon_cp.c - 1.5 linux/fs/reiserfs/namei.c - 1.7 linux/fs/reiserfs/inode.c - 1.11 linux/drivers/usb/serial/io_edgeport.c - 1.10 linux/drivers/scsi/aic7xxx_old.c - 1.6 linux/drivers/scsi/aic7xxx/aic7xxx_osm.h - 1.5 linux/drivers/video/pmag-ba-fb.c - 1.2 linux/drivers/video/pmagb-b-fb.c - 1.2 linux/drivers/net/fealnx.c - 1.5 linux/arch/cris/drivers/parport.c - 1.5 linux/drivers/usb/pwc.h - 1.5 linux/drivers/usb/pwc-misc.c - 1.3 linux/drivers/usb/pwc-ioctl.h - 1.2 linux/drivers/usb/pwc-if.c - 1.5 linux/drivers/usb/pwc-ctrl.c - 1.4 linux/drivers/mtd/devices/docprobe.c - 1.2 linux/drivers/usb/catc.c - 1.2 linux/drivers/net/wireless/airo.c - 1.6 linux/drivers/usb/se401.c - 1.5 linux/drivers/usb/serial/cyberjack.c - 1.3 linux/drivers/usb/serial/pl2303.c - 1.3 linux/drivers/usb/usb-skeleton.c - 1.3 linux/drivers/video/pvr2fb.c - 1.2 linux/drivers/net/dl2k.c - 1.3 linux/drivers/usb/storage/jumpshot.c - 1.4 linux/drivers/usb/storage/isd200.c - 1.2 linux/drivers/char/drm/drm_drv.h - 1.2 linux/drivers/char/drm/ati_pcigart.h - 1.4 linux/drivers/sound/emu10k1/passthrough.c - 1.2 linux/drivers/net/irda/vlsi_ir.c - 1.3 linux/drivers/usb/kaweth.c - 1.4 linux/drivers/usb/usbnet.c - 1.2 linux/drivers/usb/hid-core.c - 1.2 From owner-linux-xfs@oss.sgi.com Sun Sep 16 22:09:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8H59Hd26260 for linux-xfs-outgoing; Sun, 16 Sep 2001 22:09:17 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8H59Ee26241 for ; Sun, 16 Sep 2001 22:09:14 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8H598519980 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Sun, 16 Sep 2001 22:09:08 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id HAA668610 for ; Mon, 17 Sep 2001 07:09:02 +0200 (CEST) mail_from (ivanr@snort.melbourne.sgi.com) Received: (from ivanr@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id PAA32300 for linux-xfs@oss.sgi.com; Mon, 17 Sep 2001 15:07:42 +1000 (EST) Date: Mon, 17 Sep 2001 15:07:42 +1000 (EST) From: Ivan Rayner Message-Id: <200109170507.PAA32300@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - linux-xfs, handle bulkstat_single failure in xfsdump Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This will allow xfsdump to gracefully handle bulkstat_single failures. Ie. if a bulkstat_single call fails or returns an invalid inode, xfsdump will output a warning, but continue on dumping the rest of the filesystem. Ivan Date: Sun Sep 16 22:01:13 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build6/ivanr/isms/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102869a cmd/xfsdump/dump/content.c - 1.11 cmd/xfsdump/common/util.c - 1.5 - check return code for bulkstat_single call From owner-linux-xfs@oss.sgi.com Sun Sep 16 23:24:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8H6OTv27535 for linux-xfs-outgoing; Sun, 16 Sep 2001 23:24:29 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8H6OPe27514 for ; Sun, 16 Sep 2001 23:24:25 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA06078; Mon, 17 Sep 2001 08:24:06 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA27990; Mon, 17 Sep 2001 08:24:06 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 566BB57306; Mon, 17 Sep 2001 08:24:00 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id D67C025835; Mon, 17 Sep 2001 08:23:59 +0200 (CEST) Message-ID: <3BA596FF.1A5C3FDA@ch.sauter-bc.com> Date: Mon, 17 Sep 2001 08:23:59 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Florin Andrei Cc: linux-xfs Subject: Re: CPU usage References: <1000513075.12917.104.camel@stantz.corp.sgi.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Florin Andrei schrieb: > > I've heard someone complaining about high CPU usage with XFS, especially > on low-clocked machines. > Someone told me that, on some PII at 266 and 400 MHz, running Linux on > XFS, CPU usage is 10-15% all the time, even when the machine is supposed > to be idle. > I find this hard to believe, since on a lowly Indy, at 180 MHz, CPU > usage is 0.00% when the machine is idle. > Any idea?... I have been running Linux on XFS on a Pentium 200 with 64Mb Ram, four IDE disks with Software Raid5 and LVM. This system was not so fast but when there was no load CPU usage almost 0%. I guess there is something else wrong with your systems. -Simon > > -- > Florin Andrei > > "Our kernel does have source control: its name is > Linus Torvalds, CVS with a brain." - Nicholas Knight From owner-linux-xfs@oss.sgi.com Sun Sep 16 23:33:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8H6XmT27764 for linux-xfs-outgoing; Sun, 16 Sep 2001 23:33:48 -0700 Received: from alaska.net (sephiroth.nwc.alaska.net [209.112.130.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8H6Xie27744 for ; Sun, 16 Sep 2001 23:33:44 -0700 Received: from erbenson.alaska.net (73-pm18.nwc.alaska.net [209.112.142.73]) by alaska.net (8.11.5/8.11.5) with ESMTP id f8H6XeE26085 for ; Sun, 16 Sep 2001 22:33:41 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 851413978 for ; Sun, 16 Sep 2001 22:33:38 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 373451022E; Sun, 16 Sep 2001 22:33:38 -0800 (AKDT) Date: Sun, 16 Sep 2001 22:33:37 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: xfsdump with rmt Message-ID: <20010916223337.J2522@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n8884J15jRwcBTvu" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --n8884J15jRwcBTvu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Is anyone else using xfsdump with remote tapes/files? ive reread the man page and don't see what im missing, with ext2fs dump i set RSH=3D/usr/bin/ssh and set the tape to dump@hostname:/path/name=20 with xfsdump i am using: /sbin/xfsdump -F -o -l 0 -f dump@host:/path/name /home and i get a No such file or directory immediatly, strace reveals its never even attempting to run ssh, it just tries to open() dump@host:/path/name same with simply hostname:/path/name. is there something obvious i am missing here? this same setup works perfectly with ext2 dump (only difference is command line args). --=20 Ethan Benson http://www.alaska.net/~erbenson/ --n8884J15jRwcBTvu 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 iEYEARECAAYFAjulmUEACgkQJKx7GixEevzVvACffdaQa+S7gMF1oMUxdtOTS89X ZFEAnif6rWSCVr5rFmm1gyf7MYUMLp1V =IRNw -----END PGP SIGNATURE----- --n8884J15jRwcBTvu-- From owner-linux-xfs@oss.sgi.com Sun Sep 16 23:53:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8H6rnI28197 for linux-xfs-outgoing; Sun, 16 Sep 2001 23:53:49 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8H6rje28178 for ; Sun, 16 Sep 2001 23:53:45 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f8H6rd523425 for ; Sun, 16 Sep 2001 23:53:39 -0700 Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id RAA13839; Mon, 17 Sep 2001 17:52:16 +1100 From: ivanr@sgi.com Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id QAA57524; Mon, 17 Sep 2001 16:52:15 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Mon, 17 Sep 2001 16:52:15 +1000 X-X-Sender: ivanr@omen.melbourne.sgi.com To: Ethan Benson cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump with rmt In-Reply-To: <20010916223337.J2522@plato.local.lan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 16 Sep 2001, Ethan Benson wrote: > Is anyone else using xfsdump with remote tapes/files? > > ive reread the man page and don't see what im missing, with ext2fs > dump i set RSH=/usr/bin/ssh and set the tape to > dump@hostname:/path/name > > with xfsdump i am using: > > /sbin/xfsdump -F -o -l 0 -f dump@host:/path/name /home > > and i get a No such file or directory immediatly, strace reveals its > never even attempting to run ssh, it just tries to open() > dump@host:/path/name same with simply hostname:/path/name. > > is there something obvious i am missing here? this same setup works > perfectly with ext2 dump (only difference is command line args). Normally this should work, however, it's a little hard to guess what's happening without the real commands you are running, and without the output from xfsdump. One thing though ... is "/path/name" actually "/dev/tape" or some other "/dev" device? xfsdump does a little sanity check on the path, and it expects to see "/dev/". You could try adding '-v5' to xfsdump to get lots of debug output, also try setting the "RMTDEBUG" environment variable to "2" to get librmt debug output. Ivan -- Ivan Rayner ivanr@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 17 00:08:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8H78T228614 for linux-xfs-outgoing; Mon, 17 Sep 2001 00:08:29 -0700 Received: from alaska.net (sephiroth.nwc.alaska.net [209.112.130.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8H78Me28595 for ; Mon, 17 Sep 2001 00:08:22 -0700 Received: from erbenson.alaska.net (73-pm18.nwc.alaska.net [209.112.142.73]) by alaska.net (8.11.5/8.11.5) with ESMTP id f8H77uE00847 for ; Sun, 16 Sep 2001 23:08:03 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 2966D3978 for ; Sun, 16 Sep 2001 23:07:30 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 650751022E; Sun, 16 Sep 2001 23:07:30 -0800 (AKDT) Date: Sun, 16 Sep 2001 23:07:30 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: xfsdump with rmt Message-ID: <20010916230730.K2522@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010916223337.J2522@plato.local.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2WS97oupGEGbYNpW" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ivanr@sgi.com on Mon, Sep 17, 2001 at 04:52:15PM +1000 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --2WS97oupGEGbYNpW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 17, 2001 at 04:52:15PM +1000, ivanr@sgi.com wrote: >=20 > Normally this should work, however, it's a little hard to guess what's > happening without the real commands you are running, and without the > output from xfsdump. root@dilbert /etc/dump# ./dumpscript 0 /sbin/xfsdump: ERROR: unable to open dump@socrates.local.lan:/local/backup/= dump/dilbert-home.dump.0: No such file or directory root@dilbert /etc/dump# the command the script runs is: /sbin/xfsdump -F -o -l $1 -f "$TAPE" /home TAPE=3D"dump@socrates.local.lan:/local/backup/dump/dilbert-home.dump.$1" i don't have a tape drive so a regular file is the only option, this works fine with ext2 dump and as far as i can tell from the docs it should work with xfsdump as well. =20 > One thing though ... is "/path/name" actually "/dev/tape" or some other > "/dev" device? xfsdump does a little sanity check on the path, and it > expects to see "/dev/". that is not possible, unless i do something hideous like create symlinks in /dev to the regular files in /local. i shouldn't have to do that. > You could try adding '-v5' to xfsdump to get lots of debug output, also > try setting the "RMTDEBUG" environment variable to "2" to get librmt debug > output. root@dilbert /etc/dump# RMTDEBUG=3D2 ./dumpscript 0 /sbin/xfsdump: RLIMIT_AS org cur 0xffffffffffffffff max 0xffffffffffffffff /sbin/xfsdump: RLIMIT_STACK org cur 0x800000 max 0xffffffffffffffff /sbin/xfsdump: raising stack size soft limit from 0x800000 to 0x2000000 /sbin/xfsdump: RLIMIT_STACK new cur 0x2000000 max 0xffffffffffffffff /sbin/xfsdump: RLIMIT_DATA org cur 0xffffffffffffffff max 0xffffffffffffffff /sbin/xfsdump: RLIMIT_FSIZE org cur 0xffffffffffffffff max 0xffffffffffffff= ff /sbin/xfsdump: RLIMIT_FSIZE now cur 0xffffffffffffffff max 0xffffffffffffff= ff /sbin/xfsdump: RLIMIT_CPU cur 0xffffffffffffffff max 0xffffffffffffffff /sbin/xfsdump: RLIMIT_CPU now cur 0xffffffffffffffff max 0xffffffffffffffff /sbin/xfsdump: INTGENMAX =3D=3D 2147483647 (0x7fffffff) /sbin/xfsdump: UINTGENMAX =3D=3D 4294967295 (0xffffffff) /sbin/xfsdump: OFF64MAX =3D=3D 9223372036854775807 (0x7fffffffffffffff) /sbin/xfsdump: OFFMAX =3D=3D -1 (0x7fffffff) /sbin/xfsdump: SIZEMAX =3D=3D 4294967295 (0xffffffff) /sbin/xfsdump: INOMAX =3D=3D 4294967295 (0xffffffff) /sbin/xfsdump: TIMEMAX =3D=3D 2147483647 (0x7fffffff) /sbin/xfsdump: SIZE64MAX =3D=3D 18446744073709551615 (0xffffffffffffffff) /sbin/xfsdump: INO64MAX =3D=3D 18446744073709551615 (0xffffffffffffffff) /sbin/xfsdump: UINT64MAX =3D=3D 18446744073709551615 (0xffffffffffffffff) /sbin/xfsdump: INT64MAX =3D=3D 9223372036854775807 (0x7fffffffffffffff) /sbin/xfsdump: UINT32MAX =3D=3D 4294967295 (0xffffffff) /sbin/xfsdump: INT32MAX =3D=3D 2147483647 (0x7fffffff) /sbin/xfsdump: INT16MAX =3D=3D 32767 (0x7fff) /sbin/xfsdump: UINT16MAX =3D=3D 65535 (0xffff) /sbin/xfsdump: getpagesize( ) returns 4096 /sbin/xfsdump: parent pid is 16742 /sbin/xfsdump: effective user id is 0 /sbin/xfsdump: stack pid 16742: sz 0x2000000 min 0xbdfff93b max 0xbffff93b /sbin/xfsdump: instantiating drive_simple /sbin/xfsdump: ERROR: unable to open dump@socrates.local.lan:/local/backup/= dump/dilbert-home.dump.0: No such file or directory --=20 Ethan Benson http://www.alaska.net/~erbenson/ --2WS97oupGEGbYNpW 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 iEYEARECAAYFAjuloTIACgkQJKx7GixEevzAXgCbBAjDB0Vy28jngWnP0ylj38E9 SOcAn1mvTqQ4Pg2FiW7ub+1DwfryhMMv =eUcS -----END PGP SIGNATURE----- --2WS97oupGEGbYNpW-- From owner-linux-xfs@oss.sgi.com Mon Sep 17 00:22:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8H7M6828951 for linux-xfs-outgoing; Mon, 17 Sep 2001 00:22:06 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8H7M2e28932 for ; Mon, 17 Sep 2001 00:22:02 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f8H7LrJ14797 for ; Mon, 17 Sep 2001 00:21:53 -0700 Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id SAA14016; Mon, 17 Sep 2001 18:20:32 +1100 From: ivanr@sgi.com Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id RAA58872; Mon, 17 Sep 2001 17:20:31 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Mon, 17 Sep 2001 17:20:31 +1000 X-X-Sender: ivanr@omen.melbourne.sgi.com To: Ethan Benson cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump with rmt In-Reply-To: <20010916230730.K2522@plato.local.lan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 16 Sep 2001, Ethan Benson wrote: > TAPE="dump@socrates.local.lan:/local/backup/dump/dilbert-home.dump.$1" > > i don't have a tape drive so a regular file is the only option, this > works fine with ext2 dump and as far as i can tell from the docs it > should work with xfsdump as well. > > > One thing though ... is "/path/name" actually "/dev/tape" or some other > > "/dev" device? xfsdump does a little sanity check on the path, and it > > expects to see "/dev/". > > that is not possible, unless i do something hideous like create > symlinks in /dev to the regular files in /local. i shouldn't have to > do that. Unfortunately, as it stands, xfsdump will not write to an arbitrary, remote file -- it must be in /dev. I'm not sure of the reason for this, but you can work around the problem fairly easily, eg: xfsdump -f - /home | rsh socrates.local.lan -l dump dd of=/local/backup/dump/dilbert-home.dump.$1 or another example, this time from socrates: rsh othermachine "xfsdump -f - /home" > /local/backup/dump/dilbert-home.dump.$1 If you'd rather fix the source, check cmd/xfsdump/librmt/rmtopen.c line 80. Ivan -- Ivan Rayner ivanr@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 17 02:17:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8H9HM131069 for linux-xfs-outgoing; Mon, 17 Sep 2001 02:17:22 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8H9HKe31049 for ; Mon, 17 Sep 2001 02:17:20 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8H9HDJ16929 for ; Mon, 17 Sep 2001 02:17:13 -0700 Received: (from tes@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id TAA64043 for linux-xfs@oss.sgi.com; Mon, 17 Sep 2001 19:15:54 +1000 (EST) Date: Mon, 17 Sep 2001 19:15:54 +1000 (EST) From: Timothy Shimmin Message-Id: <200109170915.TAA64043@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump/librmt Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Adopted Ivan's suggestion which will allow rmt file specifications to work (as well as rmt tapes) for xfsdump. This does, however, use rmt(8) not for its intended purpose. Tried it out and it worked for me on Linux. (for IRIX I needed to create the remote irix file first) --Tim Date: Mon Sep 17 02:12:08 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/tes/slinx-xfs-acl The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102872a cmd/xfsdump/librmt/rmtopen.c - 1.6 - Allow remote paths without /dev in their name. From owner-linux-xfs@oss.sgi.com Mon Sep 17 02:37:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8H9bmd31524 for linux-xfs-outgoing; Mon, 17 Sep 2001 02:37:48 -0700 Received: from alaska.net (kitsune.nwc.alaska.net [209.112.130.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8H9bge31504 for ; Mon, 17 Sep 2001 02:37:42 -0700 Received: from erbenson.alaska.net (177-pm19.nwc.alaska.net [209.112.142.177]) by alaska.net (8.9.1/8.9.1) with ESMTP id BAA09446 for ; Mon, 17 Sep 2001 01:37:39 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 5101F3978 for ; Mon, 17 Sep 2001 01:37:27 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id E80D21022E; Mon, 17 Sep 2001 01:37:26 -0800 (AKDT) Date: Mon, 17 Sep 2001 01:37:26 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: xfsdump with rmt Message-ID: <20010917013726.M2522@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010916230730.K2522@plato.local.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SEFvVLxbW/dEDtN8" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ivanr@sgi.com on Mon, Sep 17, 2001 at 05:20:31PM +1000 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --SEFvVLxbW/dEDtN8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 17, 2001 at 05:20:31PM +1000, ivanr@sgi.com wrote: >=20 > Unfortunately, as it stands, xfsdump will not write to an arbitrary, > remote file -- it must be in /dev. I'm not sure of the reason for this, if nobody can state why then why not remove this silly limitation. unix device nodes can be anywhere, they are just placed in /dev by convention, besides that there shouldn't be any limitation against using regular files, thats the only backup option in some cases. > but you can work around the problem fairly easily, eg: >=20 > xfsdump -f - /home | rsh socrates.local.lan -l dump dd of=3D/local/back= up/dump/dilbert-home.dump.$1 i suppose that will do, but this limitation should really be fixed, or at the very least documented. =20 > or another example, this time from socrates: >=20 > rsh othermachine "xfsdump -f - /home" > /local/backup/dump/dilbert-home= .dump.$1 >=20 > If you'd rather fix the source, check cmd/xfsdump/librmt/rmtopen.c line > 80. actually that code looks fine, its the _rmt_dev function that is broken, here is a patch: --- rmtdev.c.orig Sun Sep 16 23:41:28 2001 +++ rmtdev.c Sun Sep 16 23:42:34 2001 @@ -41,7 +41,7 @@ =20 /* * Test pathname to see if it is local or remote. A remote device - * is any string that contains ":/dev/". Returns 1 if remote, + * is any string that contains ":/". Returns 1 if remote, * 0 otherwise. */ =20 @@ -50,7 +50,7 @@ { if ((path =3D strchr (path, ':')) !=3D (char *)0) { - if (strncmp (path + 1, "/dev/", 5) =3D=3D 0) + if (strncmp (path + 1, "/", 1) =3D=3D 0) { return (1); } i have tested it and it seems to work.. another question, why is xfsdump trying to call `rsh hostname uname' ?=20 AFAICT from a brief look at the code it checks whether the remote host is either IRIX or Linux and if niether it warns and continues anyway? whats the point? --=20 Ethan Benson http://www.alaska.net/~erbenson/ --SEFvVLxbW/dEDtN8 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 iEYEARECAAYFAjulxFYACgkQJKx7GixEevyoTwCffG3pvU40aqP7SQomeCuZFYyn i2IAmgJ07RGT+65uxfKgdNj9PnTVp59+ =cQVX -----END PGP SIGNATURE----- --SEFvVLxbW/dEDtN8-- From owner-linux-xfs@oss.sgi.com Mon Sep 17 03:00:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HA0ku32074 for linux-xfs-outgoing; Mon, 17 Sep 2001 03:00:46 -0700 Received: from alaska.net (sephiroth.nwc.alaska.net [209.112.130.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HA0ge32055 for ; Mon, 17 Sep 2001 03:00:42 -0700 Received: from erbenson.alaska.net (177-pm19.nwc.alaska.net [209.112.142.177]) by alaska.net (8.11.5/8.11.5) with ESMTP id f8HA0eE17105 for ; Mon, 17 Sep 2001 02:00:40 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 900AF3978 for ; Mon, 17 Sep 2001 02:00:35 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 821211022E; Mon, 17 Sep 2001 02:00:35 -0800 (AKDT) Date: Mon, 17 Sep 2001 02:00:35 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: xfsdump with rmt Message-ID: <20010917020035.N2522@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010916230730.K2522@plato.local.lan> <20010917013726.M2522@plato.local.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KCXyoJ//PRyfzsc9" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010917013726.M2522@plato.local.lan>; from erbenson@alaska.net on Mon, Sep 17, 2001 at 01:37:26AM -0800 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --KCXyoJ//PRyfzsc9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 17, 2001 at 01:37:26AM -0800, Ethan Benson wrote: >=20 > another question, why is xfsdump trying to call `rsh hostname uname' ?=20 >=20 > AFAICT from a brief look at the code it checks whether the remote host > is either IRIX or Linux and if niether it warns and continues anyway? > whats the point? ok looking further i found where this is used in rmtioctl.c. i just worked around it by creating an rsh wrapper that echos `Linux' when its given the uname command. =20 that code probably should not hard code rsh though, it should use $RSH if its set. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --KCXyoJ//PRyfzsc9 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 iEYEARECAAYFAjulycMACgkQJKx7GixEevxPnwCgkBbMVi/WVOC0wt5o4C0wUcML MO8AoJ3Hmvro436LWfQGbwHJOBxg3JN7 =tPJo -----END PGP SIGNATURE----- --KCXyoJ//PRyfzsc9-- From owner-linux-xfs@oss.sgi.com Mon Sep 17 03:06:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HA63T32302 for linux-xfs-outgoing; Mon, 17 Sep 2001 03:06:03 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HA61e32283 for ; Mon, 17 Sep 2001 03:06:01 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 746CA1E260; Mon, 17 Sep 2001 12:05:55 +0200 (MEST) Date: Mon, 17 Sep 2001 12:05:54 +0200 From: Andi Kleen To: Timothy Shimmin Cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - xfsdump/librmt Message-ID: <20010917120554.A26170@gruyere.muc.suse.de> References: <200109170915.TAA64043@snort.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109170915.TAA64043@snort.melbourne.sgi.com>; from tes@snort.melbourne.sgi.com on Mon, Sep 17, 2001 at 07:15:54PM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Sep 17, 2001 at 07:15:54PM +1000, Timothy Shimmin wrote: > Adopted Ivan's suggestion which will allow rmt file specifications > to work (as well as rmt tapes) for xfsdump. > This does, however, use rmt(8) not for its intended purpose. > Tried it out and it worked for me on Linux. > (for IRIX I needed to create the remote irix file first) AFAIK the linux rmts are normally not LFS aware so that'll likely have a 2GB limit. -Andi From owner-linux-xfs@oss.sgi.com Mon Sep 17 04:23:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HBN6B01648 for linux-xfs-outgoing; Mon, 17 Sep 2001 04:23:06 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HBN1e01627 for ; Mon, 17 Sep 2001 04:23:01 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f8HBMsJ18683 for ; Mon, 17 Sep 2001 04:22:55 -0700 Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id WAA14918; Mon, 17 Sep 2001 22:21:38 +1100 From: ivanr@sgi.com Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id VAA56865; Mon, 17 Sep 2001 21:21:37 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Mon, 17 Sep 2001 21:21:36 +1000 X-X-Sender: ivanr@omen.melbourne.sgi.com To: Ethan Benson cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump with rmt In-Reply-To: <20010917013726.M2522@plato.local.lan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 17 Sep 2001, Ethan Benson wrote: > > If you'd rather fix the source, check cmd/xfsdump/librmt/rmtopen.c line > > 80. > > actually that code looks fine, its the _rmt_dev function that is > broken, here is a patch: Well, I probably would've removed the call to rmt_dev, as Tim did did -- no point having a function called rmt_dev if it doesn't have anything to do with devices or /dev. > i have tested it and it seems to work.. Good. I assume error conditions such as no space left or insufficient permissions to write will work too... Also, it would also be a good idea to test xfsrestore. Although, I suppose Tim must've checked this stuff before checking in the change, right Tim? :) Ivan -- Ivan Rayner ivanr@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 17 04:33:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HBX7Z01911 for linux-xfs-outgoing; Mon, 17 Sep 2001 04:33:07 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HBX3e01881 for ; Mon, 17 Sep 2001 04:33:03 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id EAA25573 for ; Mon, 17 Sep 2001 04:33:06 -0700 (PDT) mail_from (ivanr@sgi.com) From: ivanr@sgi.com Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id WAA14971; Mon, 17 Sep 2001 22:31:45 +1100 Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id VAA55057; Mon, 17 Sep 2001 21:31:45 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Mon, 17 Sep 2001 21:31:44 +1000 X-X-Sender: ivanr@omen.melbourne.sgi.com To: Ethan Benson cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump with rmt In-Reply-To: <20010917020035.N2522@plato.local.lan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 17 Sep 2001, Ethan Benson wrote: > On Mon, Sep 17, 2001 at 01:37:26AM -0800, Ethan Benson wrote: > > > > another question, why is xfsdump trying to call `rsh hostname uname' ? > > > > AFAICT from a brief look at the code it checks whether the remote host > > is either IRIX or Linux and if niether it warns and continues anyway? > > whats the point? Linux's MT commands are sufficiently different from IRIX (and other UNIXes) that we need to know what OS is running on the remote machine, and how we are to translate commands and responses. If xfsdump can't work out what the remote machine is, it'll continue in the hope that it's talking to a compatible system. > ok looking further i found where this is used in rmtioctl.c. i just > worked around it by creating an rsh wrapper that echos `Linux' when > its given the uname command. > > that code probably should not hard code rsh though, it should use $RSH > if its set. You're right of course. One of us will fix it tomorrow. Ivan -- Ivan Rayner ivanr@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 17 05:10:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HCAl402687 for linux-xfs-outgoing; Mon, 17 Sep 2001 05:10:47 -0700 Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HCAhe02668 for ; Mon, 17 Sep 2001 05:10:43 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.193]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8HCAgQ07564 for ; Mon, 17 Sep 2001 21:10:42 +0900 (JST) Received: from mailsv.nec.co.jp (mailgate51.nec.co.jp [10.7.69.196]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8HCAfI15787 for ; Mon, 17 Sep 2001 21:10:41 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv.nec.co.jp (8.11.6/3.7W-MAILSV-NEC) with ESMTP id f8HCAel05967 for ; Mon, 17 Sep 2001 21:10:40 +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 AAA435 for ; Mon, 17 Sep 2001 21:10:39 +0900 Received: FROM mailsv.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Mon Sep 17 21:10:38 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by mailsv.tnes.nec.co.jp (8.9.3/3.7W01031510) with ESMTP id VAA01325 for ; Mon, 17 Sep 2001 21:10:39 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f8HCAZL21286 for ; Mon, 17 Sep 2001 21:10:38 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id VAA18856; Mon, 17 Sep 2001 21:10:32 +0900 (JST) Message-Id: <200109171210.VAA18856@tagajo.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: XFS + quota-3.01-pre9 + LVM ( QA suite 050 ) Date: Mon, 17 Sep 2001 21:10:32 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi there, I try to run QA suite 050, and noticed that the following kernel message is displayed on console: lvm -- lvm_blk_ioctl: unknown command 0xc0105865 I checked 050 and found that it was caused by "quot /dev/vg0/foo". quot calls ioctl(XFS_IOC_FSBULKSTAT). However, if I try same thing on another box, it is OK. The difference of these boxes are the revision of quota-tools. One is the latest quota-tools quota-3.01-pre9 and the another is quota-3.01-pre?. ( sorry, I cannot find out exactry revision ...) To get the mount point of the filesystem, the old quot calls getmntent() in mounttable() and it works ( ie. it returns "/mnt/foo"). The new ( 3.01-pre9 ) quot calls get_next_mount() which is in quotasys.c, but it not seems to work ( ie. it returns "/dev/vg0/foo"). Has anyone met the same problem before? Thanks in advance, Takayuki From owner-linux-xfs@oss.sgi.com Mon Sep 17 06:41:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HDfME04357 for linux-xfs-outgoing; Mon, 17 Sep 2001 06:41:22 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HDfJe04337 for ; Mon, 17 Sep 2001 06:41:19 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8HDfB518995 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Mon, 17 Sep 2001 06:41:12 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id PAA694470 for ; Mon, 17 Sep 2001 15:41:06 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2976353; Mon, 17 Sep 2001 08:39:42 -0500 (CDT) Received: from lord.americas.sgi.com (lord.americas.sgi.com [128.162.187.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA31428; Mon, 17 Sep 2001 08:39:37 -0500 (CDT) Received: from lord.americas.sgi.com by lord.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f8HDcmb18212; Mon, 17 Sep 2001 08:38:49 -0500 Message-Id: <200109171338.f8HDcmb18212@lord.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andi Kleen cc: Nathan Scott , ASANO Masahiro , linux-xfs@oss.sgi.com Subject: Re: cannot mount snapshot In-Reply-To: Message from Andi Kleen of "Sun, 16 Sep 2001 12:20:00 +0200." <20010916122000.A13240@gruyere.muc.suse.de> Date: Mon, 17 Sep 2001 08:38:48 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Fri, Sep 14, 2001 at 11:14:30AM +1100, Nathan Scott wrote: > > In your case, it seems the driver has marked /dev/vg0/masano1 > > as readonly (I don't know why that would be - looks like LVM). > > LVM snapshots are always read-only unless you add special patches. LVM > only does block COW for writes to the original block device, not for the > snapshot. While it is possible to patch it to do COW for snapshots also > it is probably unsafe (LVM data structures are not journaled etc.) > > To handle such an unpatched LVM xfs_freeze would need to flush the log so > that no recovery is needed. I actually though it did so already, but it seems > that was mistaken. > > -Andi I think a merge of the Irix version of this code has changed the situation, and it is now attempting to replay the log. It should be fairly simple to back out this part of the change. Steve From owner-linux-xfs@oss.sgi.com Mon Sep 17 08:35:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HFZbR06756 for linux-xfs-outgoing; Mon, 17 Sep 2001 08:35:37 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HFZYe06737 for ; Mon, 17 Sep 2001 08:35:34 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8HFZL531418 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Mon, 17 Sep 2001 08:35:21 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id RAA707909 for ; Mon, 17 Sep 2001 17:35:15 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2971893; Mon, 17 Sep 2001 10:34:03 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA82755; Mon, 17 Sep 2001 10:34:01 -0500 (CDT) Message-ID: <3BA617E1.6D756750@sgi.com> Date: Mon, 17 Sep 2001 10:33:53 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Bernd Birkholz CC: linux-xfs@oss.sgi.com Subject: Re: Problems with driver disk References: <3BA51722.4DE70A6A@profimail.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Bernd Birkholz wrote: > > Hello, > > I did want to use xfs on my new server system because I learnt to > appreciate this filesystem under IRIX. So I downloaded your installer > iso image and burnt it on CD. Since the RAID driver in RedHat 7.1 for my > RAID-Controller was corrupt I got a driver disk. Like Martin said, you can't use a driver compiled for Red Hat's kernel with the XFS kernel (more generally, you can't use reliably use drivers across kernel versions, in most cases.) On the other hand, we have a newer kernel than in the original Red Hat 7.1 release - perhaps your issue has been resolved in this kernel. Have you tried installing without using any driver disk? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Mon Sep 17 10:27:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HHR7V08802 for linux-xfs-outgoing; Mon, 17 Sep 2001 10:27:07 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HHR4e08783 for ; Mon, 17 Sep 2001 10:27:04 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id KAA00144 for ; Mon, 17 Sep 2001 10:25:40 -0700 (PDT) mail_from (eric@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2825608 for ; Mon, 17 Sep 2001 12:25:46 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA10614 for ; Mon, 17 Sep 2001 12:25:46 -0500 (CDT) Received: by stout.americas.sgi.com (8.11.2/SGI-client-1.7) id f8HHPcY23825; Mon, 17 Sep 2001 12:25:38 -0500 Message-Id: <200109171725.f8HHPcY23825@stout.americas.sgi.com> Date: Mon, 17 Sep 2001 12:25:38 -0500 From: Eric Sandeen Subject: TAKE - Fix read-only mount of LVM snapshots. Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk A dummy log entry was added to xfs_fs_freeze, to ensure that unlinked files got processed on an otherwise clean filesystem that was shut down with umount -i (an irix fix). Dirtying the log in xfs_fs_freeze, though, affects snapshotting such that the snapshot can't be mounted read-only. For now, just don't dirty the log with a dummy transaction in xfs_fs_freeze(). Date: Mon Sep 17 10:20:15 PDT 2001 Workarea: stout.americas.sgi.com:/localhome/eric/2.4.x-xfs/workarea-clean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102882a linux/fs/xfs/xfs_fsops.c - 1.69 - Back out part of irix6.5f:irix:101630a mrege Don't dirty log in xfs_fs_freeze(), as this affects more than just umount -k In Irix this will probably move to xfs_goingdown() From owner-linux-xfs@oss.sgi.com Mon Sep 17 13:18:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HKIjq12041 for linux-xfs-outgoing; Mon, 17 Sep 2001 13:18:45 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HKIge12022 for ; Mon, 17 Sep 2001 13:18:42 -0700 Received: from idcomm.com (IDENT:VNGA7LFPs+I9wDOWvo8JHyWwCQ8awg2e@x2-pip56.idcomm.com [209.60.72.67]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f8HKTpQ32537 for ; Mon, 17 Sep 2001 14:29:52 -0600 Message-ID: <3BA65B2B.AC2DEFA6@idcomm.com> Date: Mon, 17 Sep 2001 14:20:59 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 To: "XFS: linux-xfs@oss.sgi.com" Subject: possible future legal problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Please don't add too much about this on the XFS list, but I am giving some links that might be important to anyone developing on linux or open source in general. If it seems important to you, talk about it with your company or local linux group. The ramifications of these legal problems looking for a place to happen are at: http://slashdot.org/articles/01/09/08/0238200.shtml http://www.wired.com/news/politics/0,1283,46655,00.html http://www.wired.com/news/politics/0,1283,46671,00.html D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Mon Sep 17 14:03:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HL3Rp12972 for linux-xfs-outgoing; Mon, 17 Sep 2001 14:03:27 -0700 Received: from localhost.localdomain (wet-pants.ximian.com [141.154.95.105]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HL3Oe12951 for ; Mon, 17 Sep 2001 14:03:24 -0700 Received: (from jacob@localhost) by localhost.localdomain (8.11.6/8.11.6) id f8I144o07914; Mon, 17 Sep 2001 21:04:04 -0400 X-Authentication-Warning: localhost.localdomain: jacob set sender to jacob@ximian.com using -f Subject: Re: Bizarre in-memory corruption when deleting files in certain dir From: jacob berkman To: linux-xfs@oss.sgi.com In-Reply-To: <20010916120123.A417@vitelus.com> References: <20010916120123.A417@vitelus.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13.99 (Preview Release) Date: 17 Sep 2001 21:04:04 -0400 Message-Id: <1000775044.6089.3.camel@wet-pants> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 2001-09-16 at 15:01, Aaron Lehmann wrote: > Hi, > > I've been using XFS for quite awhile, and it's worked flawlessly. > Until recently. I've had the peculiar problem that when I delete a > file in ~/mail, the system often gives the following message: i also got this on my old / partition today, and after running xfs_repair on it everything is "gone" as in it is in lost+found and renamed to funky numbers fortunately, i had installed rh 7.2 beta over the weekend, and didn't lose anything important. i still have the trashed fs - if there's any debugging stuff i can get for you guys let me know. jacob -- "It drains me, and it shakes me, and hurts like hell everytime I play it, looking out at thousands of people cheering and smiling, oblivious to the tragedy of it's meaning, like when you're going to have your dog put down and it's wagging it's tail on the way there." - Thom Yorke From owner-linux-xfs@oss.sgi.com Mon Sep 17 16:09:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HN9Nj16169 for linux-xfs-outgoing; Mon, 17 Sep 2001 16:09:23 -0700 Received: from shakti.rupa.com (cx838204-a.alsv1.occa.home.com [24.16.83.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HN9Ge16148 for ; Mon, 17 Sep 2001 16:09:16 -0700 Received: by shakti.rupa.com (Postfix, from userid 500) id C1D2DC009C; Mon, 17 Sep 2001 16:09:15 -0700 (PDT) To: linux-xfs@oss.sgi.com Subject: OOPS: 2.4.5 + 1.0.1 patches From: Rupa Schomaker Mail-Copies-To: never Date: Mon, 17 Sep 2001 16:09:15 -0700 Message-ID: Lines: 85 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk While using apt to update pidentd, I got the following error: Unpacking replacement pidentd ... E: Sub-process /usr/bin/dpkg received a segmentation fault. I then retried the install, and this time the process hung writing to a file. I tried to ls in the directory that the file was hung in, no output of data. Attemping to strace the process results in the strace process hanging. I've had some squirly stuff happen recently (one file system gave IO errors until I ran xfs_repair). I think it might be time to boot from recovery and xfs_repair everything... Maybe... The oops data: Sep 17 15:55:38 shakti kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000008 Sep 17 15:55:38 shakti kernel: printing eip: Sep 17 15:55:38 shakti kernel: c01d4543 Sep 17 15:55:38 shakti kernel: *pde = 00000000 Sep 17 15:55:38 shakti kernel: Oops: 0000 Sep 17 15:55:38 shakti kernel: CPU: 0 Sep 17 15:55:38 shakti kernel: EIP: 0010:[xfs_itobp+291/448] Sep 17 15:55:38 shakti kernel: EFLAGS: 00010256 Sep 17 15:55:38 shakti kernel: eax: 00000000 ebx: 00000000 ecx: 00000008 edx: 00000000 Sep 17 15:55:38 shakti kernel: esi: c5b649e4 edi: c1900000 ebp: 00000000 esp: c5723d58 Sep 17 15:55:38 shakti kernel: ds: 0018 es: 0018 ss: 0018 Sep 17 15:55:38 shakti kernel: Process dpkg (pid: 28253, stackpage=c5723000) Sep 17 15:55:38 shakti kernel: Stack: 00500034 00000000 c1900000 c5b649e4 001d4c20 00000000 00000000 00000000 Sep 17 15:55:38 shakti kernel: 001d4c10 00000000 00000010 00000002 14000014 c01d55c0 c1900000 00000000 Sep 17 15:55:38 shakti kernel: c5b649e4 c5723dc8 c5723dcc 00000000 00000000 c18b7b60 00000004 000007f0 Sep 17 15:55:38 shakti kernel: Call Trace: [xfs_iread+112/464] [xfs_iget_core+546/1392] [xfs_iget+117/272] [xfs_dir_lookup_int+300/6 72] [xfs_lookup+151/272] [linvfs_lookup+101/192] [] Sep 17 15:55:38 shakti kernel: [real_lookup+122/288] [path_walk+1545/2128] [getname+90/160] [] [__user_walk+60/96] [sys_lstat64+22/112] [system_call+51/56] Sep 17 15:55:38 shakti kernel: Sep 17 15:55:38 shakti kernel: Code: f6 42 08 04 74 07 8b 52 30 01 c2 eb 0c 50 52 e8 39 54 fb ff The same run through ksymoops: Warning (compare_maps): ksyms_base symbol __VERSIONED_SYMBOL(shmem_file_setup) not found in System.map. Ignoring ksyms_base entry Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c029ccf0, System.map says c0155670. Ignoring ksyms_base entry Unable to handle kernel NULL pointer dereference at virtual address 00000008 c01d4543 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[xfs_itobp+291/448] EFLAGS: 00010256 eax: 00000000 ebx: 00000000 ecx: 00000008 edx: 00000000 esi: c5b649e4 edi: c1900000 ebp: 00000000 esp: c5723d58 ds: 0018 es: 0018 ss: 0018 Process dpkg (pid: 28253, stackpage=c5723000) Stack: 00500034 00000000 c1900000 c5b649e4 001d4c20 00000000 00000000 00000000 001d4c10 00000000 00000010 00000002 14000014 c01d55c0 c1900000 00000000 c5b649e4 c5723dc8 c5723dcc 00000000 00000000 c18b7b60 00000004 000007f0 Call Trace: [xfs_iread+112/464] [xfs_iget_core+546/1392] [xfs_iget+117/272] [xfs_dir_lookup_int+300/672] [xfs_lookup+151/272] [linvfs_lookup+101/192] [] Code: f6 42 08 04 74 07 8b 52 30 01 c2 eb 0c 50 52 e8 39 54 fb ff Using defaults from ksymoops -t elf32-i386 -a i386 Code; 00000000 Before first symbol 00000000 <_EIP>: Code; 00000000 Before first symbol 0: f6 42 08 04 testb $0x4,0x8(%edx) Code; 00000004 Before first symbol 4: 74 07 je d <_EIP+0xd> 0000000d Before first symbol Code; 00000006 Before first symbol 6: 8b 52 30 mov 0x30(%edx),%edx Code; 00000009 Before first symbol 9: 01 c2 add %eax,%edx Code; 0000000b Before first symbol b: eb 0c jmp 19 <_EIP+0x19> 00000019 Before first symbol Code; 0000000d Before first symbol d: 50 push %eax Code; 0000000e Before first symbol e: 52 push %edx Code; 0000000f Before first symbol f: e8 39 54 fb ff call fffb544d <_EIP+0xfffb544d> fffb544d -- -rupa From owner-linux-xfs@oss.sgi.com Mon Sep 17 16:08:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8HN8Xg16103 for linux-xfs-outgoing; Mon, 17 Sep 2001 16:08:33 -0700 Received: from ptialaska.net (garza.acsalaska.net [209.193.61.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8HN8Te16084 for ; Mon, 17 Sep 2001 16:08:29 -0700 Received: from erbenson.alaska.net (96-pm18.nwc.alaska.net [209.112.142.96]) by ptialaska.net (8.11.1/8.11.1) with ESMTP id f8HN8R325089 for ; Mon, 17 Sep 2001 15:08:27 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 3A3123939 for ; Mon, 17 Sep 2001 15:08:26 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id D63481022F; Mon, 17 Sep 2001 15:08:25 -0800 (AKDT) Date: Mon, 17 Sep 2001 15:08:25 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: xfsdump with rmt Message-ID: <20010917150825.S2522@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010917013726.M2522@plato.local.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Sr/1Pkwuhjf1+ztR" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ivanr@sgi.com on Mon, Sep 17, 2001 at 09:21:36PM +1000 X-OS: Debian GNU Mail-Copies-To: nobody Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --Sr/1Pkwuhjf1+ztR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 17, 2001 at 09:21:36PM +1000, ivanr@sgi.com wrote: > On Mon, 17 Sep 2001, Ethan Benson wrote: >=20 > > > If you'd rather fix the source, check cmd/xfsdump/librmt/rmtopen.c li= ne > > > 80. > > > > actually that code looks fine, its the _rmt_dev function that is > > broken, here is a patch: >=20 > Well, I probably would've removed the call to rmt_dev, as Tim did > did -- no point having a function called rmt_dev if it doesn't have > anything to do with devices or /dev. well it looked to me like rmt_dev was what was figuring out whether the pathname given was a remotehost:/path or a local pathname. but again i am not familier with this code at all. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --Sr/1Pkwuhjf1+ztR 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 iEYEARECAAYFAjumgmkACgkQJKx7GixEevwOrgCeI+XzyUGOCP3vjhZWS1bKeba4 oHEAn1vbglVtGZsJLcgi2PjebV0nM3WE =kn3l -----END PGP SIGNATURE----- --Sr/1Pkwuhjf1+ztR-- From owner-linux-xfs@oss.sgi.com Mon Sep 17 17:20:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8I0KBE17341 for linux-xfs-outgoing; Mon, 17 Sep 2001 17:20:11 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8I0Jwe17318 for ; Mon, 17 Sep 2001 17:19:58 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id RAA06761 for ; Mon, 17 Sep 2001 17:19:28 -0700 (PDT) mail_from (ivanr@sgi.com) Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id LAA18485; Tue, 18 Sep 2001 11:18:15 +1100 From: ivanr@sgi.com Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id KAA33538; Tue, 18 Sep 2001 10:18:14 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Tue, 18 Sep 2001 10:18:14 +1000 X-X-Sender: ivanr@omen.melbourne.sgi.com To: Ethan Benson cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump with rmt In-Reply-To: <20010917150825.S2522@plato.local.lan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 17 Sep 2001, Ethan Benson wrote: > On Mon, Sep 17, 2001 at 09:21:36PM +1000, ivanr@sgi.com wrote: > > On Mon, 17 Sep 2001, Ethan Benson wrote: > > > > > > If you'd rather fix the source, check cmd/xfsdump/librmt/rmtopen.c line > > > > 80. > > > > > > actually that code looks fine, its the _rmt_dev function that is > > > broken, here is a patch: > > > > Well, I probably would've removed the call to rmt_dev, as Tim did > > did -- no point having a function called rmt_dev if it doesn't have > > anything to do with devices or /dev. > > well it looked to me like rmt_dev was what was figuring out whether > the pathname given was a remotehost:/path or a local pathname. but > again i am not familier with this code at all. Yes, it does do that ... but it only does it by checking to see if there's a ':' in the name. You'll note that Tim simply replaced the call to rmt_dev with a call to strchr. There really isn't much point in keeping rmt_dev if it's only function is to call strchr, and if it has nothing to do with checking whether the path is a device. But still, we're quibbling over details -- your main point that xfsdump shouldn't be restricted to remote devices seems valid and unless we discover an unexpected problem, we're happy to remove that restriction. (Although, I must admit, Tim was the one who wanted to change it and I originally wanted to keep the status quo ... :) Ivan -- Ivan Rayner ivanr@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 17 19:43:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8I2h1t19485 for linux-xfs-outgoing; Mon, 17 Sep 2001 19:43:01 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8I2gue19466 for ; Mon, 17 Sep 2001 19:42:56 -0700 Received: from there (localhost.localdomain [127.0.0.1]) by wwweasel.geeksrus.net (8.11.6/8.11.6) with SMTP id f8I2gmN08653; Mon, 17 Sep 2001 22:42:48 -0400 Message-Id: <200109180242.f8I2gmN08653@wwweasel.geeksrus.net> Content-Type: text/plain; charset="iso-8859-1" From: Alan Eldridge Reply-To: alane@geeksrus.net Organization: a local lack of entropy To: Andy Kwong Subject: Found bug preventing CPQFC driver from building Date: Mon, 17 Sep 2001 22:42:47 -0400 X-Mailer: KMail [version 1.3.1] References: <20010915131859.A8702@wwweasel.geeksrus.net> <20010917180503.A10536@wwweasel.geeksrus.net> <1000770384.14257.29.camel@zerowing.pop-star.net> In-Reply-To: <1000770384.14257.29.camel@zerowing.pop-star.net> Cc: XFS list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Monday September 17 2001 19:46, you wrote: > Yup, that's right in B.C. So how are doing out there right now? Is > everything back to normal for you? Reasonably so. I'll go into the office again for the first time tomorrow. Subways are running at about 80% normal, which means just a bit more fucked up than usual. At least now they're being honest about it being fucked up. Didn't lose anyone in the disaster. That's a blessing. Life will be running a bit slower than normal for a good while here, I think. That's not bad ... NYC needs to relax a bit. Now... I found the bug. Somebody deleted two #defines from linux/include/scsi/scsi.h, that cpqfc needs in order to build. (That was smart.) ---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<--- --- linux/include/scsi/scsi.h.ioctl_fc Wed May 2 02:22:13 2001 +++ linux/include/scsi/scsi.h Mon Sep 17 20:41:38 2001 @@ -214,6 +214,14 @@ /* Used to get the PCI location of a device */ #define SCSI_IOCTL_GET_PCI 0x5387 +#ifndef NO_IOCTL_FC +/* These got removed somehow and broke the CPQFC driver */ +/* Used to get Fibre Channel WWN and port_id from device */ +#define SCSI_IOCTL_FC_TARGET_ADDRESS 0x5387 +/* Used to invoke Target Defice Reset for Fibre Channel */ +#define SCSI_IOCTL_FC_TDR 0x5388 +#endif /* ifndef NO_IOCTL_FC */ + /* * Overrides for Emacs so that we follow Linus's tabbing style. * Emacs will notice this stuff at the end of the file and automatically ---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<--- I'll let you know when it's building everything correctly. -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Mon Sep 17 19:49:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8I2n5X19672 for linux-xfs-outgoing; Mon, 17 Sep 2001 19:49:05 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8I2n3e19653 for ; Mon, 17 Sep 2001 19:49:03 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f8I2mwR10799 for linux-xfs@oss.sgi.com; Mon, 17 Sep 2001 22:48:58 -0400 Date: Mon, 17 Sep 2001 22:48:58 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: sorry bout the language Message-ID: <20010917224858.A10401@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sorry for the language in the post i copied to the list. I didn't think about that until about 2 seconds after it had gone out. :( -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Mon Sep 17 19:56:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8I2ueS19922 for linux-xfs-outgoing; Mon, 17 Sep 2001 19:56:40 -0700 Received: from afara-gw.afara.com (mx1.afara.com [63.113.218.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8I2uce19903 for ; Mon, 17 Sep 2001 19:56:39 -0700 Received: from tduffy-lnx.afara.com ([10.2.4.191]) by afara-gw.afara.com with Microsoft SMTPSVC(5.0.2195.1600); Mon, 17 Sep 2001 19:56:29 -0700 Subject: Re: sorry bout the language From: Thomas Duffy To: Alan Eldridge Cc: SGI XFS Dev List In-Reply-To: <20010917224858.A10401@wwweasel.geeksrus.net> References: <20010917224858.A10401@wwweasel.geeksrus.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13.99+cvs.2001.09.17.18.33 (Preview Release) Date: 17 Sep 2001 19:55:01 -0700 Message-Id: <1000781701.3192.15.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 X-OriginalArrivalTime: 18 Sep 2001 02:56:29.0403 (UTC) FILETIME=[83CB6AB0:01C13FED] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 2001-09-17 at 19:48, Alan Eldridge wrote: > Sorry for the language in the post i copied to the list. I didn't think > about that until about 2 seconds after it had gone out. :( we're all adults here, well sorta. I can't imagine anyone caring or complaining... :) -tduffy From owner-linux-xfs@oss.sgi.com Mon Sep 17 20:05:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8I35Mt20188 for linux-xfs-outgoing; Mon, 17 Sep 2001 20:05:22 -0700 Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8I35Fe20169 for ; Mon, 17 Sep 2001 20:05:16 -0700 Received: from walt400.localhost (user-uini6rr.dsl.mindspring.com [165.121.27.123]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA31039; Mon, 17 Sep 2001 23:05:10 -0400 (EDT) Received: from mindspring.com (localhost.localdomain [127.0.0.1]) by walt400.localhost (Postfix) with ESMTP id 97610798C; Mon, 17 Sep 2001 20:06:58 -0700 (PDT) Message-ID: <3BA6BA52.6050002@mindspring.com> Date: Mon, 17 Sep 2001 20:06:58 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913 X-Accept-Language: en-us MIME-Version: 1.0 To: Alan Eldridge Cc: SGI XFS Dev List Subject: Re: sorry bout the language References: <20010917224858.A10401@wwweasel.geeksrus.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk No problem for me. It's completely understandable. Everybody needs to vent a bit I think. Take care and God bless. Or, if you're not into that, I love ya anyway :) Thanks to you and all involved in XFS, the rest of us are getting a great FS and I for one really appreciate the hard work, especially given the circumstances of late. Thanks, -Walt Alan Eldridge wrote: > Sorry for the language in the post i copied to the list. I didn't think > about that until about 2 seconds after it had gone out. :( > > From owner-linux-xfs@oss.sgi.com Mon Sep 17 21:42:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8I4g1f21656 for linux-xfs-outgoing; Mon, 17 Sep 2001 21:42:01 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8I4fxe21637 for ; Mon, 17 Sep 2001 21:41:59 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f8I4frb27964 for linux-xfs@oss.sgi.com; Tue, 18 Sep 2001 00:41:53 -0400 Date: Tue, 18 Sep 2001 00:41:52 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: Weird message in kernel build Message-ID: <20010918004152.A27704@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Anybody know the story on this little gem: md5sum: WARNING: 4 of 13 computed checksums did NOT match It occurs several places, including (lastly) during make modules_install. -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Mon Sep 17 22:38:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8I5cFU22285 for linux-xfs-outgoing; Mon, 17 Sep 2001 22:38:15 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8I5cBe22266 for ; Mon, 17 Sep 2001 22:38:11 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id WAA22144 for ; Mon, 17 Sep 2001 22:38:11 -0700 (PDT) mail_from (tes@snort.melbourne.sgi.com) Received: (from tes@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id PAA94853 for linux-xfs@oss.sgi.com; Tue, 18 Sep 2001 15:36:48 +1000 (EST) Date: Tue, 18 Sep 2001 15:36:48 +1000 (EST) From: Timothy Shimmin Message-Id: <200109180536.PAA94853@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump/librmt Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Mon Sep 17 22:36:14 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/tes/slinx-xfs-acl The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102951a cmd/xfsdump/dump/inomap.c - 1.7 cmd/xfsdump/dump/content.c - 1.12 - adds some diagnostics cmd/xfsdump/librmt/rmtopen.c - 1.7 - fix up use of RSH for uname instead of hardcoded rsh cmd/xfsdump/VERSION - 1.17 - bump version for librmt changes cmd/xfsdump/doc/CHANGES - 1.20 - document librmt changes From owner-linux-xfs@oss.sgi.com Mon Sep 17 23:16:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8I6Got22805 for linux-xfs-outgoing; Mon, 17 Sep 2001 23:16:50 -0700 Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.131]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8I6Gle22786 for ; Mon, 17 Sep 2001 23:16:47 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA07989; Tue, 18 Sep 2001 08:16:41 +0200 (CEST) Message-Id: <4.3.2.7.2.20010918081525.03ecafd0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 18 Sep 2001 08:16:26 +0200 To: Alan Eldridge , SGI XFS Dev List From: Seth Mos Subject: Re: Weird message in kernel build In-Reply-To: <20010918004152.A27704@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 00:41 18-9-2001 -0400, Alan Eldridge wrote: >Anybody know the story on this little gem: > >md5sum: WARNING: 4 of 13 computed checksums did NOT match It's from the ISDN layer. It means that 4 of the 13 drivers were not certified. >It occurs several places, including (lastly) during make modules_install. You have isdn turned on didn't you? Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Sep 17 23:27:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8I6R1w22971 for linux-xfs-outgoing; Mon, 17 Sep 2001 23:27:01 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8I6Qxe22952 for ; Mon, 17 Sep 2001 23:26:59 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f8I6Qr722905 for linux-xfs@oss.sgi.com; Tue, 18 Sep 2001 02:26:53 -0400 Date: Tue, 18 Sep 2001 02:26:52 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: Re: Weird message in kernel build Message-ID: <20010918022651.A9795@wwweasel.geeksrus.net> References: <20010918004152.A27704@wwweasel.geeksrus.net> <4.3.2.7.2.20010918081525.03ecafd0@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.20010918081525.03ecafd0@pop.xs4all.nl>; from knuffie@xs4all.nl on Tue, Sep 18, 2001 at 08:16:26AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 18, 2001 at 08:16:26AM +0200, Seth Mos wrote: >At 00:41 18-9-2001 -0400, Alan Eldridge wrote: >>Anybody know the story on this little gem: >> >>md5sum: WARNING: 4 of 13 computed checksums did NOT match > >It's from the ISDN layer. It means that 4 of the 13 drivers were not certified. > >>It occurs several places, including (lastly) during make modules_install. > >You have isdn turned on didn't you? RedHat config files, so probably yes. I didn't grep. Thanks. -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Mon Sep 17 23:53:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8I6rLn23416 for linux-xfs-outgoing; Mon, 17 Sep 2001 23:53:21 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8I6rJe23397 for ; Mon, 17 Sep 2001 23:53:19 -0700 Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id XAA07056; Mon, 17 Sep 2001 23:53:00 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id 6230C300090; Tue, 18 Sep 2001 16:44:16 +1000 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id 28B9398; Tue, 18 Sep 2001 16:44:16 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Alan Eldridge Cc: SGI XFS Dev List Subject: Re: Weird message in kernel build In-reply-to: Your message of "Tue, 18 Sep 2001 00:41:52 -0400." <20010918004152.A27704@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Sep 2001 16:44:10 +1000 Message-ID: <9971.1000795450@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 18 Sep 2001 00:41:52 -0400, Alan Eldridge wrote: >md5sum: WARNING: 4 of 13 computed checksums did NOT match Ignore, it is part of the ISDN certification. Alas it can appear even when you do not select ISDN, due to a design problem in kernel build. Fixed in kbuild 2.5. http://sourceforge.net/projects/kbuild/ From owner-linux-xfs@oss.sgi.com Tue Sep 18 04:18:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IBIgd28435 for linux-xfs-outgoing; Tue, 18 Sep 2001 04:18:42 -0700 Received: from TYO201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.214]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IBIWe28416 for ; Tue, 18 Sep 2001 04:18:32 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.197]) by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8IBIPa28187 for ; Tue, 18 Sep 2001 20:18:25 +0900 (JST) Received: from mailsv.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8IBIPZ03201 for ; Tue, 18 Sep 2001 20:18:25 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv.nec.co.jp (8.11.6/3.7W-MAILSV-NEC) with ESMTP id f8IBIKl09294 for ; Tue, 18 Sep 2001 20:18:23 +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 AAA444 for ; Tue, 18 Sep 2001 20:18:19 +0900 Received: FROM tnesgate.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Tue Sep 18 20:18:18 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by tnesgate.tnes.nec.co.jp (8.9.3/3.7W00091816) with ESMTP id UAA45432 for ; Tue, 18 Sep 2001 20:18:19 +0900 (JST) Received: from kano.bsd.tnes.nec.co.jp (kano.bsd.tnes.nec.co.jp [10.1.101.150]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f8IBIJL29133 for ; Tue, 18 Sep 2001 20:18:19 +0900 Received: (from ism@localhost) by kano.bsd.tnes.nec.co.jp (8.11.1/3.7W-01053010) id f8IBII101812; Tue, 18 Sep 2001 20:18:18 +0900 (JST) Date: Tue, 18 Sep 2001 20:18:18 +0900 (JST) Message-Id: <200109181118.f8IBII101812@kano.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: The memory mapped I/O caused the system hung From: ism@bsd.tnes.nec.co.jp (ISHIZUKA Masayuki) X-Mailer: mnews [version 1.22] 1999-12/19(Sun) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I noticed that the system hung up right after the filesystem is full by the memory mapped I/O (no terminal response and no one can enter the KDB). My environment is RedHat 7.1 + linux-2.4.10-pre10-xfs(20010918 XFS CVS Tree) + gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release). The test program attached the end of this mail could reproduce this. ex) filesystem capacity: 128MB % cd /mnt/xfs % testprog 40 /* 40 * 4MB = 160MB */ -> system hangs! [Console Messages] Unable to handle kernel paging request at virtual address cb7a868c printing eip: c012a351 *pde = 00000000 Unable to handle kernel paging request at virtual address 8109e000 printing eip: c0208990 *pde = 00000000 In case of ext2fs, this program was killed by SIGBUS. Is there anything to do for investigation? P.S. Why does disk block is allocated the reverse order by memory mapped I/O as follows? # mkfs -t xfs /dev/sda7 # mount /dev/sda7 /mnt/xfs # cd /mnt/xfs # testprog 1 # xfs_bmap hole hole: 0: [0..7]: 8312..8319 1: [8..15]: 8304..8311 2: [16..23]: 8296..8303 3: [24..31]: 8288..8295 : : 1021: [8168..8175]: 112..119 1022: [8176..8183]: 104..111 1023: [8184..8191]: 96..103 1024: [8192..4194295]: hole 1025: [4194296..4194303]: 8328..8335 % [testprog.c] --------8<--------8<--------8<--------8<--------8<--------8<-------- #include #include #include #include #include #include #define MAPSZ 4*1024*1024 int main(int argc, char *argv[]) { int fd; int count; off_t off = 0; char *cp; if (argc > 1) count = atoi(argv[1]); fd = open("hole", O_RDWR|O_CREAT|O_TRUNC, 0644); if (fd < 0) { perror("open(\"hole\")"); exit(1); } if (lseek(fd, 0x7fffffff-1, SEEK_SET) < 0) { perror("lseek"); exit(1); } if (write(fd, "a", 1) < 0) { perror("write"); exit(1); } if (lseek(fd, 0, SEEK_SET) < 0) { perror("lseek"); exit(1); } while (count--) { cp = mmap(0, MAPSZ, PROT_READ|PROT_WRITE, MAP_SHARED, fd, off); if (cp == MAP_FAILED) { perror("mmap"); exit(1); } memset(cp, '0', MAPSZ); if (msync(cp, MAPSZ, MS_SYNC) < 0) { perror("msync"); exit(1); } if (munmap(cp, MAPSZ) < 0) { perror("munmap"); exit(1); } off += MAPSZ; } } --------8<--------8<--------8<--------8<--------8<--------8<-------- -- ISHIZUKA Masayuki From owner-linux-xfs@oss.sgi.com Tue Sep 18 05:00:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IC0xb29140 for linux-xfs-outgoing; Tue, 18 Sep 2001 05:00:59 -0700 Received: from mail.cendio.se (mail.lkpg.cendio.se [193.180.23.130]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IC0te29121 for ; Tue, 18 Sep 2001 05:00:55 -0700 Received: from snoddas.lkpg.cendio.se (snoddas.lkpg.cendio.se [10.47.1.240]) by mail.cendio.se (8.9.3/8.9.3) with ESMTP id OAA14695 for ; Tue, 18 Sep 2001 14:00:53 +0200 Received: by snoddas.lkpg.cendio.se (Postfix, from userid 146) id 6BF97882473; Tue, 18 Sep 2001 14:00:53 +0200 (CEST) To: linux-xfs@oss.sgi.com Subject: Problems with XFS and Linux SMP From: Jan Smith Date: 18 Sep 2001 14:00:53 +0200 Message-ID: Lines: 21 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by mail.cendio.se id OAA14695 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8IC0ue29122 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm testing a v2.4.9 Linux kernel with your XFS-patch applied on a IBM Netfinity 5500 with two Xeon-CPU's and 2Gb RAM. The machine runs completely well in a couple of hours but does then suddenly crash totaly without any error messages at all. There seems to be something concerning race conditions between SMP locking and file locking but we are not sure. Just now are the machine running with the same kernel but in single CPU-mode and have done so for a week or more. All partitions on the machine are using XFS filesystem. Are any of you on the list knowing of any problem like this that can get our machine run more than 6-9 hours wich are the maximum uptime we have reached so far. -- -------------------------------------------------------------------------- Jan Smith Email: smith@cendio.se Cendio Systems AB WWW: www.cendio.se Teknikringen 3, Voice: +46 - (0)13 - 21 46 00 SE-583 30 LINKÖPING, SWEDEN Fax: +46 - (0)13 - 21 47 00 From owner-linux-xfs@oss.sgi.com Tue Sep 18 05:28:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ICSGo29775 for linux-xfs-outgoing; Tue, 18 Sep 2001 05:28:16 -0700 Received: from TYO201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.214]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ICSDe29756 for ; Tue, 18 Sep 2001 05:28:14 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.193]) by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8ICS7a23111 for ; Tue, 18 Sep 2001 21:28:07 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8ICS7I00650 for ; Tue, 18 Sep 2001 21:28:07 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id f8ICS6F21244 for ; Tue, 18 Sep 2001 21:28:06 +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 AAA470 for ; Tue, 18 Sep 2001 21:28:04 +0900 Received: FROM tnesgate.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Tue Sep 18 21:28:03 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by tnesgate.tnes.nec.co.jp (8.9.3/3.7W00091816) with ESMTP id VAA54849 for ; Tue, 18 Sep 2001 21:28:04 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f8ICS4L32531 for ; Tue, 18 Sep 2001 21:28:04 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id VAA23389; Tue, 18 Sep 2001 21:28:04 +0900 (JST) Message-Id: <200109181228.VAA23389@tagajo.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: QA suite 044 Date: Tue, 18 Sep 2001 21:28:04 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Just FYI. I could't find the substance of _unexpected() in cmd/xfstests/044. However, I guess it never been called until something is broken :) Cheers. Takayuki From owner-linux-xfs@oss.sgi.com Tue Sep 18 06:36:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IDadE31190 for linux-xfs-outgoing; Tue, 18 Sep 2001 06:36:39 -0700 Received: from rain.CC.Lehigh.EDU (rain.CC.Lehigh.EDU [128.180.39.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IDaZe31170 for ; Tue, 18 Sep 2001 06:36:35 -0700 Received: from Lehigh.EDU (hooch.CC.Lehigh.EDU [128.180.3.11]) by rain.CC.Lehigh.EDU (8.11.5/8.11.5) with ESMTP id f8IDZYX07390; Tue, 18 Sep 2001 09:35:39 -0400 Message-ID: <3BA74ACD.4164E048@Lehigh.EDU> Date: Tue, 18 Sep 2001 09:23:25 -0400 From: Jim Eshleman X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Jan Smith CC: linux-xfs@oss.sgi.com Subject: Re: Problems with XFS and Linux SMP References: Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by rain.CC.Lehigh.EDU id f8IDZYX07390 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8IDaae31171 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jan, Have you disabled the NMI watchdog? I had to do this on a Netfinity x370. Try booting with: nmi_watchdog=0 Jim > I'm testing a v2.4.9 Linux kernel with your XFS-patch applied on > a IBM Netfinity 5500 with two Xeon-CPU's and 2Gb RAM. > The machine runs completely well in a couple of hours but does then > suddenly crash totaly without any error messages at all. > > There seems to be something concerning race conditions between > SMP locking and file locking but we are not sure. > Just now are the machine running with the same kernel but in > single CPU-mode and have done so for a week or more. > All partitions on the machine are using XFS filesystem. > > Are any of you on the list knowing of any problem like this > that can get our machine run more than 6-9 hours wich are the > maximum uptime we have reached so far. > > -- > -------------------------------------------------------------------------- > Jan Smith Email: smith@cendio.se > Cendio Systems AB WWW: www.cendio.se > Teknikringen 3, Voice: +46 - (0)13 - 21 46 00 > SE-583 30 LINKÖPING, SWEDEN Fax: +46 - (0)13 - 21 47 00 From owner-linux-xfs@oss.sgi.com Tue Sep 18 07:15:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IEFYe31905 for linux-xfs-outgoing; Tue, 18 Sep 2001 07:15:34 -0700 Received: from hammail1.truenorth.com (h-213.61.138.102.host.de.colt.net [213.61.138.102]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IEFVe31885 for ; Tue, 18 Sep 2001 07:15:31 -0700 Received: from fcb-wilkens.com ([170.200.66.15]) by hammail1.truenorth.com (Netscape Messaging Server 4.15) with ESMTP id GJV3LN00.I5O; Tue, 18 Sep 2001 16:15:23 +0200 Message-ID: <3BA756FC.11A7ACB7@fcb-wilkens.com> Date: Tue, 18 Sep 2001 16:15:24 +0200 From: Harald Wagener Organization: FCB Wilkens X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Jim Eshleman CC: Jan Smith , linux-xfs@oss.sgi.com Subject: Re: Problems with XFS and Linux SMP References: <3BA74ACD.4164E048@Lehigh.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jim Eshleman wrote: > > Jan, > > Have you disabled the NMI watchdog? I had to do this on a Netfinity > x370. Try booting with: nmi_watchdog=0 > > Jim We have no problems with two dual PIII-800, but this is with the xfs-1.0 installation. H. -- Harald Wagener | Systemadministrator FCB/Wilkens GmbH | Tel.:+49-40-2881-1252 An der Alster 42 | Fax.:+49-40-2881-1263 20099 Hamburg | http://www.fcb-wilkens.com From owner-linux-xfs@oss.sgi.com Tue Sep 18 08:27:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IFRs000934 for linux-xfs-outgoing; Tue, 18 Sep 2001 08:27:54 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IFRqe00914 for ; Tue, 18 Sep 2001 08:27:52 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8IFRk513524 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 18 Sep 2001 08:27:46 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id RAA773442 for ; Tue, 18 Sep 2001 17:27:37 +0200 (CEST) mail_from (eric@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2889312 for ; Tue, 18 Sep 2001 10:26:26 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA88789 for ; Tue, 18 Sep 2001 10:26:25 -0500 (CDT) Received: by stout.americas.sgi.com (8.11.2/SGI-client-1.7) id f8IFQ9q01152; Tue, 18 Sep 2001 10:26:09 -0500 Message-Id: <200109181526.f8IFQ9q01152@stout.americas.sgi.com> Date: Tue, 18 Sep 2001 10:26:09 -0500 From: Eric Sandeen Subject: TAKE - Merge irix6.5f:irix:102838a Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Tue Sep 18 08:25:44 PDT 2001 Workarea: stout.americas.sgi.com:/localhome/eric/2.4.x-xfs/workarea-clean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102966a linux/fs/xfs/linux/xfs_lrw.c - 1.109 - Merge irix6.5f:irix:102838a Replace VOP_RWUNLOCK() and VOP_RWLOCK() around call to dm_send_namesp_event() in xfs_write() with xfs_rwunlock() and xfs_rwlock(). Fix for bug 831289. Also reorder xfs_rwlockf / error out condition to match irix. From owner-linux-xfs@oss.sgi.com Tue Sep 18 09:41:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IGf1l01728 for linux-xfs-outgoing; Tue, 18 Sep 2001 09:41:01 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IGewe01708 for ; Tue, 18 Sep 2001 09:40:58 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f8IGeqI30660 for linux-xfs@oss.sgi.com; Tue, 18 Sep 2001 12:40:52 -0400 Date: Tue, 18 Sep 2001 12:40:51 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: gcc-2.96-nn status Message-ID: <20010918124051.A30647@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm trying to configure my build system to make RPMS for one of our comrades-in-XFS, and I've hit a big stumbling block. RedHat's RPMS now build with gcc-2.96-74 or higher. Kgcc is probably going to go away (I can find out I think). But you can't build an athlon kernel with kgcc. What's the current status/words-of-wisdom regarding gcc-2.96-xx? Or gcc-3.x, for that matter? -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Tue Sep 18 10:04:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IH4Wm02195 for linux-xfs-outgoing; Tue, 18 Sep 2001 10:04:32 -0700 Received: from cis.ohio-state.edu (root@mail.cis.ohio-state.edu [164.107.115.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IH4Qe02175 for ; Tue, 18 Sep 2001 10:04:26 -0700 Received: from cis.ohio-state.edu (pc-786a.cis.ohio-state.edu [164.107.60.100]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id NAA03884 for ; Tue, 18 Sep 2001 13:04:20 -0400 (EDT) Message-ID: <3BA77E42.5410119A@cis.ohio-state.edu> Date: Tue, 18 Sep 2001 13:02:58 -0400 From: Arun Ramakrishnan Organization: Cluster I/O Lab,CIS Dept, The Ohio State Univ X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 CC: SGI XFS Dev List Subject: Re: gcc-2.96-nn status References: <20010918124051.A30647@wwweasel.geeksrus.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I heard that 2.96 is again a devel version of gcc which is sorta unstable.I heard posting saying that we shud downgrade to 2.95 possibly.I think with RH 7.1 ,u no longer need kgcc to compile things correctly.gcc itself works.In fact,i heard sby commenting that now kgcc seems broke in RH 7.1 and so it is safe to use only gcc in RH 7.1;while it was mandatory to use kgcc in RH 7.0!!!! I also heard that binaries produced by gcc 3.0 are going to be somewhat incompatible with the older binaries. Cheers, Arun Alan Eldridge wrote: > I'm trying to configure my build system to make RPMS for one of our > comrades-in-XFS, and I've hit a big stumbling block. > > RedHat's RPMS now build with gcc-2.96-74 or higher. Kgcc is probably going > to go away (I can find out I think). But you can't build an athlon kernel > with kgcc. > > What's the current status/words-of-wisdom regarding gcc-2.96-xx? Or gcc-3.x, > for that matter? > > -- > Alan Eldridge > from std_disclaimer import * -- Arun Ramakrishnan Graduate Research Assistant / Sys Admin Cluster I/O Lab The Ohio State University Ph : (614)-294-5523 (H) (614)-292-8458 (O) From owner-linux-xfs@oss.sgi.com Tue Sep 18 10:20:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IHK4J02523 for linux-xfs-outgoing; Tue, 18 Sep 2001 10:20:04 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IHK1e02504 for ; Tue, 18 Sep 2001 10:20:02 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f8IHJLm07886; Tue, 18 Sep 2001 13:19:21 -0400 Date: Tue, 18 Sep 2001 13:19:20 -0400 From: Alan Eldridge To: Seth Mos Cc: SGI XFS Dev List Subject: Re: gcc-2.96-nn status Message-ID: <20010918131920.A4284@wwweasel.geeksrus.net> References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010918190751.03312448@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.20010918190751.03312448@pop.xs4all.nl>; from knuffie@xs4all.nl on Tue, Sep 18, 2001 at 07:14:47PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 18, 2001 at 07:14:47PM +0200, Seth Mos wrote: >At 12:40 18-9-2001 -0400, Alan Eldridge wrote: >>I'm trying to configure my build system to make RPMS for one of our >>comrades-in-XFS, and I've hit a big stumbling block. >> >>RedHat's RPMS now build with gcc-2.96-74 or higher. Kgcc is probably going >>to go away (I can find out I think). But you can't build an athlon kernel >>with kgcc. > >I can, altough it does not have as many optimizations. So I only think that >the runtime speed would be affected. The linux kernel already knows what a >Athlon processor is and what to do with it. I think this makes a larger >difference then the compiler. > Umm, how? rpm --target athlon causes gcc to be invoked with -march=athlon, which kgcc knows nothing about so it dies. -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Tue Sep 18 10:21:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IHL2s02701 for linux-xfs-outgoing; Tue, 18 Sep 2001 10:21:02 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IHKqe02679 for ; Tue, 18 Sep 2001 10:20:54 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id TAA06996; Tue, 18 Sep 2001 19:19:13 +0200 (CEST) Message-Id: <4.3.2.7.2.20010918191512.03352ba8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 18 Sep 2001 19:18:49 +0200 To: Arun Ramakrishnan From: Seth Mos Subject: Re: gcc-2.96-nn status Cc: SGI XFS Dev List In-Reply-To: <3BA77E42.5410119A@cis.ohio-state.edu> References: <20010918124051.A30647@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 13:02 18-9-2001 -0400, Arun Ramakrishnan wrote: >Hi, > I heard that 2.96 is again a devel version of gcc which is sorta > unstable.I It was a CVS snapshot. >heard posting saying that we shud downgrade to 2.95 possibly.I think with >RH 7.1 >,u no longer need kgcc to compile things correctly.gcc itself works.In fact,i For most userland programs it seems to be fine but I have encounterd some utilities that don't like it. For kernels kgcc might be a better solution. >heard sby commenting that now kgcc seems broke in RH 7.1 and so it is safe to >use only gcc in RH 7.1;while it was mandatory to use kgcc in RH 7.0!!!! Not that I know off. > I also heard that binaries produced by gcc 3.0 are going to be somewhat >incompatible with the older binaries. No, you mean the object code. Not the binaries itself but the intermediate binary form that you have before creating the actual binary. C code -> object code -> Binary Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Sep 18 10:26:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IHQlD02890 for linux-xfs-outgoing; Tue, 18 Sep 2001 10:26:47 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IHQJe02864 for ; Tue, 18 Sep 2001 10:26:19 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAA09519 for ; Tue, 18 Sep 2001 10:25:31 -0700 (PDT) mail_from (knuffie@xs4all.nl) Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id TAA06422; Tue, 18 Sep 2001 19:15:08 +0200 (CEST) Message-Id: <4.3.2.7.2.20010918190751.03312448@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 18 Sep 2001 19:14:47 +0200 To: Alan Eldridge , SGI XFS Dev List From: Seth Mos Subject: Re: gcc-2.96-nn status In-Reply-To: <20010918124051.A30647@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 12:40 18-9-2001 -0400, Alan Eldridge wrote: >I'm trying to configure my build system to make RPMS for one of our >comrades-in-XFS, and I've hit a big stumbling block. > >RedHat's RPMS now build with gcc-2.96-74 or higher. Kgcc is probably going >to go away (I can find out I think). But you can't build an athlon kernel >with kgcc. I can, altough it does not have as many optimizations. So I only think that the runtime speed would be affected. The linux kernel already knows what a Athlon processor is and what to do with it. I think this makes a larger difference then the compiler. The IA64 folks are using 3.0.1+ which is needed because it is the only one that can generate IA64 assembler. >What's the current status/words-of-wisdom regarding gcc-2.96-xx? Or gcc-3.x, >for that matter? 2.96-85 seems relatively ok but sometimes it does funny things. So I am afraid that for generating production code we need kgcc and in the future we better start testing on 3.0+ which I have seen very little reports about. I know steve is compiling kernels with gcc-3.0 but I don't know how much testiong he has done with it. There are also a number of problems in the linux kernel itself that don't like anything above 2.95.4 (I have encounterd ISDN). Sorry, not very helpful :-) Cheers >-- >Alan Eldridge >from std_disclaimer import * -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Sep 18 10:28:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IHSBP03016 for linux-xfs-outgoing; Tue, 18 Sep 2001 10:28:11 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IHRle02973 for ; Tue, 18 Sep 2001 10:27:49 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id TAA08170; Tue, 18 Sep 2001 19:27:20 +0200 (CEST) Message-Id: <4.3.2.7.2.20010918192539.0375bbd0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 18 Sep 2001 19:27:00 +0200 To: Alan Eldridge From: Seth Mos Subject: Re: gcc-2.96-nn status Cc: SGI XFS Dev List In-Reply-To: <20010918131920.A4284@wwweasel.geeksrus.net> References: <4.3.2.7.2.20010918190751.03312448@pop.xs4all.nl> <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010918190751.03312448@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 13:19 18-9-2001 -0400, Alan Eldridge wrote: >On Tue, Sep 18, 2001 at 07:14:47PM +0200, Seth Mos wrote: > >At 12:40 18-9-2001 -0400, Alan Eldridge wrote: > >>I'm trying to configure my build system to make RPMS for one of our > >>comrades-in-XFS, and I've hit a big stumbling block. > >> > >>RedHat's RPMS now build with gcc-2.96-74 or higher. Kgcc is probably going > >>to go away (I can find out I think). But you can't build an athlon kernel > >>with kgcc. > > > >I can, altough it does not have as many optimizations. So I only think that > >the runtime speed would be affected. The linux kernel already knows what a > >Athlon processor is and what to do with it. I think this makes a larger > >difference then the compiler. > > > >Umm, how? rpm --target athlon causes gcc to be invoked with -march=athlon, >which kgcc knows nothing about so it dies. You can specify a target of i686 and have a kernel config for athlon/duron systems -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Sep 18 11:45:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IIjYS04368 for linux-xfs-outgoing; Tue, 18 Sep 2001 11:45:34 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IIjRe04349 for ; Tue, 18 Sep 2001 11:45:27 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 0F481C00B62 for ; Wed, 19 Sep 2001 02:45:24 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id A330EC00B60 for ; Wed, 19 Sep 2001 02:45:20 +0800 (PHT) Date: Wed, 19 Sep 2001 02:45:20 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Samba error during build when ACL support enabled Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, I'm trying to build the samba-2.2.1a-9 Debian packages and am having problems. I'm pretty confident it's not a problem with the build scripts of the source because when built without ACL support it goes on fine using gcc-3.0.2 (20010908). Just to make sure I rebuilt all my XFS tools especially acl and acl-dev from a current snapshot of the CVS tree. Here now follows a hopefully representative subset of the long list of errors that I get: ----- include/proto.h:284: warning: data definition has no type or storage class include/proto.h:285: parse error before '*' token include/proto.h:286: parse error before "entry" include/proto.h:287: parse error before "entry" include/proto.h:288: parse error before "entry" include/proto.h:289: parse error before "theacl" include/proto.h:290: parse error before "acl_type_t" include/proto.h:291: parse error before "acl_t" include/proto.h:293: parse error before "permset" include/proto.h:295: parse error before "posix_acl" include/proto.h:297: parse error before "the_acl" include/proto.h:298: parse error before "entry_d" include/proto.h:299: parse error before "entry_d" include/proto.h:300: parse error before "entry_d" include/proto.h:301: parse error before "sys_acl_get_file" include/proto.h:301: parse error before "acl_type_t" include/proto.h:301: warning: data definition has no type or storage class include/proto.h:302: parse error before "sys_acl_get_fd" include/proto.h:302: warning: data definition has no type or storage class include/proto.h:303: parse error before "permset" include/proto.h:304: parse error before "permset" include/proto.h:305: parse error before "permset" include/proto.h:306: parse error before "the_acl" include/proto.h:308: parse error before "sys_acl_init" include/proto.h:308: warning: data definition has no type or storage class include/proto.h:309: parse error before '*' token include/proto.h:310: parse error before "entry" include/proto.h:311: parse error before "entry" include/proto.h:312: parse error before "entry" include/proto.h:313: parse error before "theacl" include/proto.h:314: parse error before "acl_type_t" include/proto.h:315: parse error before "acl_t" include/proto.h:317: parse error before "the_acl" make[1]: *** [smbd/server.o] Error 1 make[1]: Leaving directory `/home/jijo/build/samba/samba-2.2.1a/source' make: *** [build-stamp] Error 2 ----- Note that the only differences from the "normal" build of the package is the "--with-acl-support" directive in configure. I am wondering (aside from what's wrong): if Samba is configured without ACL support, will it still respect permission settings that use ACLs? Or will it bypass these altogether? I don't need Windows NT workstations to go modifying ACLs since they mess up the execute bits anyway. But I do need them to respect ACLs as I'll be implementing ACLs to replace the current "valid users" and "write list" so that file access via NFS is identical security-wise to Samba. Thanks in advance to everyone! :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Tue Sep 18 12:10:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IJAlV04892 for linux-xfs-outgoing; Tue, 18 Sep 2001 12:10:47 -0700 Received: from relay-3v.club-internet.fr (relay-3v.club-internet.fr [194.158.96.114]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IJAde04842 for ; Tue, 18 Sep 2001 12:10:39 -0700 Received: from club-internet.fr (bas12-157.idf.club-internet.fr [213.44.252.157]) by relay-3v.club-internet.fr (Postfix) with ESMTP id 6050A17DE; Tue, 18 Sep 2001 21:10:36 +0200 (CEST) Message-ID: <3BA79FE5.27232AA@club-internet.fr> Date: Tue, 18 Sep 2001 21:26:29 +0200 From: Jean Francois Martinez X-Mailer: Mozilla 4.77 [fr] (X11; U; Linux 2.4.5-SGI_XFS_1.0.1_Indy i586) X-Accept-Language: en MIME-Version: 1.0 To: alan@geeksrus.net, linux-xfs@oss.sgi.com Cc: Seth Mos Subject: Re: gcc-2.96-nn status References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010918191512.03352ba8@pop.xs4all.nl> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos a écrit : > At 13:02 18-9-2001 -0400, Arun Ramakrishnan wrote: > >Hi, > > I heard that 2.96 is again a devel version of gcc which is sorta > > unstable.I > > It was a CVS snapshot. > It was a CVS snapshot some 18 months ago. Eighteen months of bug hunting later you can tell nothing about its stability. In fact because Gcc 2.96 was frozen over a year before gcc 3.0 and has been far more dceployed I trust it far m ore than gcc 3.0+ > > >heard posting saying that we shud downgrade to 2.95 possibly.I think with > >RH 7.1 > >,u no longer need kgcc to compile things correctly.gcc itself works.In fact,i > > For most userland programs it seems to be fine but I have encounterd some > utilities that don't like it. Gcc 2.96 requires C++ functions being declared before their use. I have found many programs who need to be fixed. > > For kernels kgcc might be a better solution. > The only gcc tested by kernel people are egcs and gcc 2.95. There is ever a danger kernel will break if compiled with a different compiler. On another hand gcc 2.96 has been used in the two most popular Linux distributions so is a good test bench. > > >heard sby commenting that now kgcc seems broke in RH 7.1 and so it is safe to > >use only gcc in RH 7.1;while it was mandatory to use kgcc in RH 7.0!!!! > > Not that I know off. AFAIK kgscc is no longer shipped with 7.1. Reason kgcc was in 7.0 was because gcc 2.96 did not compile kernel 2.2. gcc 2.96 had its bugs but in that case it was due to broken code in kernel that old more tolerant compilers accepted but should not have. kernel 2.4 has no longer this problem. > > > > I also heard that binaries produced by gcc 3.0 are going to be somewhat > >incompatible with the older binaries. > > No, you mean the object code. Not the binaries itself but the intermediate > binary form that you have before creating the actual binary. C code -> > object code -> Binary > About compiling specifically for athlon: 1) The thing who will get you real benefits are the assembler parts (ie unaffected by compiler flags). 2) On a PIII, compiling specifically for i686 gives a 15% improvement on pure C programs (my benchmark) over the worst case (compiling for plain Pentium). AMD processors tend to be more tolerant to code not specifically compiled for them since most of the time they have to cope with code optimized for Intel. Thus on kernel (mix of assembler and C) a good strategy if you want to use kgcc (aka egcs) is to go under arch/i386 and fix the file containing the compiler flags to use the -D for athlon and -march=i686. This will be a bit faster than compiling for i686. Gcc 2.96 genrates faster code than egcs but if you are wary of it the above is the best solution JFM From owner-linux-xfs@oss.sgi.com Tue Sep 18 13:24:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IKOtL06067 for linux-xfs-outgoing; Tue, 18 Sep 2001 13:24:55 -0700 Received: from orfeus.bioinfo.pl (orfeus.bioinfo.pl [212.87.21.30]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IKOpe06046 for ; Tue, 18 Sep 2001 13:24:51 -0700 Received: from a7.bioinfo.pl (theo.bioinfo.pl [192.168.1.1]) by orfeus.bioinfo.pl (Postfix) with ESMTP id ABC921FE50 for ; Tue, 18 Sep 2001 22:24:10 +0200 (CEST) Received: (from michal@localhost) by a7.bioinfo.pl (8.11.6/8.11.2) id f8IKLx404949 for linux-xfs@oss.sgi.com; Tue, 18 Sep 2001 22:21:59 +0200 Date: Tue, 18 Sep 2001 22:21:59 +0200 From: Michal Kurowski To: linux-xfs@oss.sgi.com Subject: suerblock corrupted Message-ID: <20010918222159.B4806@orfeus> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: Linux 2.4.6 on an i686 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I'm using 2.4.9 patched - from CVS. Works great but recently I managed to corrupt the superblock and I'm no longer able to mount my HD (wrong fs type, bad option.... etc.). Unfortunately there's a swap partition preceding the xfs partition on the drive and after little inspection I can see the superblock has actually been swaped... I've been rather unhappy to find out xfsdump won't do much in this case and even worse my "dd" is not able to work with huge files ( hdc2 is 40GB or something). I tried to things: 1) recompiling dd ( fileutils-4.1) - the same 2) using xfs_copy - after a while I managed to compile it all it can do is segfault... I would be grateful for any suggestions. -- Michal Kurowski From owner-linux-xfs@oss.sgi.com Tue Sep 18 13:46:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IKk4w06524 for linux-xfs-outgoing; Tue, 18 Sep 2001 13:46:04 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IKk1e06505 for ; Tue, 18 Sep 2001 13:46:01 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id NAA04282 for ; Tue, 18 Sep 2001 13:44:38 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA3001628; Tue, 18 Sep 2001 15:44:35 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA56394; Tue, 18 Sep 2001 15:44:35 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8IKk0V26493; Tue, 18 Sep 2001 15:46:00 -0500 Message-Id: <200109182046.f8IKk0V26493@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Michal Kurowski cc: linux-xfs@oss.sgi.com Subject: Re: suerblock corrupted In-Reply-To: Message from Michal Kurowski of "Tue, 18 Sep 2001 22:21:59 +0200." <20010918222159.B4806@orfeus> Date: Tue, 18 Sep 2001 15:45:59 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi, > I'm using 2.4.9 patched - from CVS. > Works great but recently I managed to corrupt the superblock and I'm > no longer able to mount my HD (wrong fs type, bad option.... etc.). > Unfortunately there's a swap partition preceding the xfs partition on > the drive and after little inspection I can see the superblock has > actually been swaped... > I've been rather unhappy to find out xfsdump won't do much in this > case and even worse my "dd" is not able to work with huge files ( hdc2 > is 40GB or something). > I tried to things: > 1) recompiling dd ( fileutils-4.1) - the same > 2) using xfs_copy - after a while I managed to compile it all it can > do is segfault... > > I would be grateful for any suggestions. Have you attempted to run xfs_repair on the filesystem? There are alternate super blocks it can attempt to replace the original with. However, if the swapper managed to get very far into the filesystem beyond the super block then you probably lost the root inode too, and at this point recovery becomes very difficult. However, repair may be able to reconnect inodes into the lost+found dir. Steve > > -- > Michal Kurowski > From owner-linux-xfs@oss.sgi.com Tue Sep 18 13:47:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IKlcB06658 for linux-xfs-outgoing; Tue, 18 Sep 2001 13:47:38 -0700 Received: from burgers (IDENT:postfix@burgers.bubbanfriends.org [216.140.122.113]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IKlZe06638 for ; Tue, 18 Sep 2001 13:47:35 -0700 Received: by burgers (Postfix, from userid 500) id 3CFEE4001BA; Tue, 18 Sep 2001 16:47:40 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by burgers (Postfix) with ESMTP id 3B9322400219; Tue, 18 Sep 2001 16:47:40 -0400 (EDT) Date: Tue, 18 Sep 2001 16:47:40 -0400 (EDT) From: Mike Burger To: Michal Kurowski Cc: Subject: Re: suerblock corrupted In-Reply-To: <20010918222159.B4806@orfeus> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I ran into a similar problem, a couple of weeks ago. I'm assuming, since you're working with hdc2, that it's not your boot or root drive? If not, perhaps xfs_repair (which was recommended to me when I was having my troubles) might do the trick? On Tue, 18 Sep 2001, Michal Kurowski wrote: > Hi, > I'm using 2.4.9 patched - from CVS. > Works great but recently I managed to corrupt the superblock and I'm > no longer able to mount my HD (wrong fs type, bad option.... etc.). > Unfortunately there's a swap partition preceding the xfs partition on > the drive and after little inspection I can see the superblock has > actually been swaped... > I've been rather unhappy to find out xfsdump won't do much in this > case and even worse my "dd" is not able to work with huge files ( hdc2 > is 40GB or something). > I tried to things: > 1) recompiling dd ( fileutils-4.1) - the same > 2) using xfs_copy - after a while I managed to compile it all it can > do is segfault... > > I would be grateful for any suggestions. > > From owner-linux-xfs@oss.sgi.com Tue Sep 18 14:06:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IL6w607109 for linux-xfs-outgoing; Tue, 18 Sep 2001 14:06:58 -0700 Received: from mail.kahkaha.net (205-158-62-39.outblaze.com [205.158.62.39]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IL6ue07090 for ; Tue, 18 Sep 2001 14:06:56 -0700 Received: (from root@localhost) by mail.kahkaha.net (8.11.6/8.11.2) id f8J05Ff02794; Wed, 19 Sep 2001 00:05:15 GMT Date: Wed, 19 Sep 2001 00:05:15 GMT Message-Id: <200109190005.f8J05Ff02794@mail.kahkaha.net> From: ebtigin@yahoo.com Subject: bootdisk To: linux-xfs@oss.sgi.com Cc: X-Originating-IP: 212.133.135.189 X-Mailer: Webmin 0.88 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--------1000857915" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ----------1000857915 Content-Type: text/plain Content-Transfer-Encoding: 7bit hi SGI; I have a problem at booting. I lost my boot disk and i try oldfashion way like booting from cd and when it prompts i write " vmlinuz root=/dev/hda1 rw " this way i can easilie boot from cd and i can reinstall lilo or i can copy my backups to another partion but this time i have trouble with XFS couse the default vmlinuz cant support XFS ( ofcourse im booting from SGI installer CD 1.0.1 for RH 7.1 and my all partitions are XFS no ant ext2 or other FS ) when i try booting from SGI installer and choose rescue menu tries to reinstall RH 7.1 is there any way to boot my box ? is there anywhere to find a rescue image supports XFS ? any way to boot from SGI installer cd ? Thank you ----------1000857915-- From owner-linux-xfs@oss.sgi.com Tue Sep 18 14:07:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IL7uD07194 for linux-xfs-outgoing; Tue, 18 Sep 2001 14:07:56 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IL7pe07175 for ; Tue, 18 Sep 2001 14:07:51 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8IL7jl22904 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 18 Sep 2001 14:07:46 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id XAA788971 for ; Tue, 18 Sep 2001 23:07:35 +0200 (CEST) mail_from (eric@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2974440 for ; Tue, 18 Sep 2001 16:06:24 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA96323 for ; Tue, 18 Sep 2001 16:06:24 -0500 (CDT) Received: by stout.americas.sgi.com (8.11.2/SGI-client-1.7) id f8IL65u07585; Tue, 18 Sep 2001 16:06:05 -0500 Message-Id: <200109182106.f8IL65u07585@stout.americas.sgi.com> Date: Tue, 18 Sep 2001 16:06:05 -0500 From: Eric Sandeen Subject: TAKE - Fix nfs refcache issues Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This should take care of the persistent extra disk usage that's seen after copying files via NFS. A few issues were causing this: 1) A temporary increase is by design, this is pre-allocation in action, coupled with a reference cache to improve NFS performance. 2) Linux is no longer calling sync on idle filesystems; this was the trigger to bump entries out of the refcache, which would then allow the pre-alloc'd space to be freed. 3) Inodes that were in the refcache, and then replaced by new inodes, weren't getting pre-alloc'd space freed. These were resolved by the following. 1) is still with us; the cache purging is still quite slow, this might be a candidate for a tuneable parameter. But, it's a feature, not a bug. :) 2) After purging some entries from the refcache, a timer is set to dirty the superblock, assuring that we'll purge more entries via sync even if the filesystem is idle. 3) Added a call to VOP_RELEASE in xfs_rwunlock to _really_ let go of the inode. Date: Tue Sep 18 13:56:42 PDT 2001 Workarea: stout.americas.sgi.com:/localhome/eric/2.4.x-xfs/workarea The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:102991a linux/fs/xfs/xfs_rw.h - 1.60 - update prototype for xfs_refcache_purge_some to include mountpoint arg linux/fs/xfs/xfs_rw.c - 1.345 - Add timer to mark sb dirty even if filesystem is idle. This ensures we'll keep purging the nfs refcache. Modify xfs_refcache_purge_some to pass in mount point, so we can get to sb linux/fs/xfs/xfs_vnodeops.c - 1.512 - Update linux inode block count after pre-alloced space is freed. Call VOP_RELEASE when releasing inodes bumped from the refcache. linux/fs/xfs/xfs_vfsops.c - 1.324 - call xfs_refcache_purge_some with mp argument From owner-linux-xfs@oss.sgi.com Tue Sep 18 14:22:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ILM7I07713 for linux-xfs-outgoing; Tue, 18 Sep 2001 14:22:07 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ILM4e07694 for ; Tue, 18 Sep 2001 14:22:04 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8ILLwl24900 for ; Tue, 18 Sep 2001 14:21:59 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA3004973; Tue, 18 Sep 2001 16:20:43 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id QAA09901; Tue, 18 Sep 2001 16:20:42 -0500 (CDT) Message-ID: <3BA7BA97.4681AFF6@sgi.com> Date: Tue, 18 Sep 2001 16:20:23 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: ebtigin@yahoo.com CC: linux-xfs@oss.sgi.com Subject: Re: bootdisk References: <200109190005.f8J05Ff02794@mail.kahkaha.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk ebtigin@yahoo.com wrote: > > hi SGI; > when i try booting from SGI installer and choose rescue menu tries to reinstall RH 7.1 It shouldn't..., type "linux rescue" at the SGI installer CD prompt, and it might start out looking like the installer (asks for language, keyboard, etc) but you will wind up with a shell prompt. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Tue Sep 18 14:45:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ILjjm08207 for linux-xfs-outgoing; Tue, 18 Sep 2001 14:45:45 -0700 Received: from chimta01.algx.net (chimta01.algx.net [216.99.233.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ILjbe08137 for ; Tue, 18 Sep 2001 14:45:37 -0700 Received: from jtsdell (66-2-81-28.customer.algx.net [66.2.81.28]) by chimmx01.algx.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GJV008E7O61UT@chimmx01.algx.net> for linux-xfs@oss.sgi.com; Tue, 18 Sep 2001 16:39:38 -0500 (CDT) Date: Tue, 18 Sep 2001 17:40:17 -0400 (EDT) From: jtrostel@snapserver.com Subject: RE: Samba error during build when ACL support enabled In-reply-to: To: Federico Sevilla III Cc: Linux XFS Mailing List Reply-to: jtrostel@snapserver.com Message-id: Organization: Snap Appliances MIME-version: 1.0 X-Mailer: XFMail 1.5.1 on Linux Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Priority: 3 (Normal) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Looks like it's not finding SMB_ACL_T. That _should_ be acl_t as defined in smb_acl.h Does chacl work on an XFS mounted file system? Where are: acl.h - should be in /usr/include/sys (not /usr/include) libacl.* - should be in /lib Does .../source/includes/includes.h have a line #ifdef HAVE_SYS_ACL_H #include #endif On 18-Sep-2001 Federico Sevilla III wrote: > Hi everyone, > > I'm trying to build the samba-2.2.1a-9 Debian packages and am having > problems. I'm pretty confident it's not a problem with the build scripts > of the source because when built without ACL support it goes on fine using > gcc-3.0.2 (20010908). > > Just to make sure I rebuilt all my XFS tools especially acl and acl-dev > from a current snapshot of the CVS tree. Here now follows a hopefully > representative subset of the long list of errors that I get: > > ----- > include/proto.h:284: warning: data definition has no type or storage class > include/proto.h:285: parse error before '*' token > include/proto.h:286: parse error before "entry" > include/proto.h:287: parse error before "entry" > include/proto.h:288: parse error before "entry" > include/proto.h:289: parse error before "theacl" > include/proto.h:290: parse error before "acl_type_t" > include/proto.h:291: parse error before "acl_t" > include/proto.h:293: parse error before "permset" > include/proto.h:295: parse error before "posix_acl" > include/proto.h:297: parse error before "the_acl" > include/proto.h:298: parse error before "entry_d" > include/proto.h:299: parse error before "entry_d" > include/proto.h:300: parse error before "entry_d" > include/proto.h:301: parse error before "sys_acl_get_file" > include/proto.h:301: parse error before "acl_type_t" > include/proto.h:301: warning: data definition has no type or storage class > include/proto.h:302: parse error before "sys_acl_get_fd" > include/proto.h:302: warning: data definition has no type or storage class > include/proto.h:303: parse error before "permset" > include/proto.h:304: parse error before "permset" > include/proto.h:305: parse error before "permset" > include/proto.h:306: parse error before "the_acl" > include/proto.h:308: parse error before "sys_acl_init" > include/proto.h:308: warning: data definition has no type or storage class > include/proto.h:309: parse error before '*' token > include/proto.h:310: parse error before "entry" > include/proto.h:311: parse error before "entry" > include/proto.h:312: parse error before "entry" > include/proto.h:313: parse error before "theacl" > include/proto.h:314: parse error before "acl_type_t" > include/proto.h:315: parse error before "acl_t" > include/proto.h:317: parse error before "the_acl" > make[1]: *** [smbd/server.o] Error 1 > make[1]: Leaving directory `/home/jijo/build/samba/samba-2.2.1a/source' > make: *** [build-stamp] Error 2 > ----- > > Note that the only differences from the "normal" build of the package is > the "--with-acl-support" directive in configure. > > I am wondering (aside from what's wrong): if Samba is configured without > ACL support, will it still respect permission settings that use ACLs? Or > will it bypass these altogether? I don't need Windows NT workstations to > go modifying ACLs since they mess up the execute bits anyway. But I do > need them to respect ACLs as I'll be implementing ACLs to replace the > current "valid users" and "write list" so that file access via NFS is > identical security-wise to Samba. > > Thanks in advance to everyone! :) > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. > GnuPG Key: -- John M. Trostel Senior Software Engineer Quantum / SnapAppliances jtrostel@snapserver.com From owner-linux-xfs@oss.sgi.com Tue Sep 18 14:46:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ILkve08334 for linux-xfs-outgoing; Tue, 18 Sep 2001 14:46:57 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ILkqe08305 for ; Tue, 18 Sep 2001 14:46:53 -0700 Received: (qmail 27378 invoked by uid 0); 18 Sep 2001 21:46:45 -0000 Received: from b223e.pppool.de (HELO gmx.de) (213.7.34.62) by mail.gmx.net (mp010-rz3) with SMTP; 18 Sep 2001 21:46:45 -0000 Message-ID: <3BA7C0C0.1AA1A470@gmx.de> Date: Tue, 18 Sep 2001 23:46:41 +0200 From: Martin Stricker Organization: http://martin-stricker.de/ http://www.surfo.net/ http://www.masterportal24.com/cgi-bin/YaBB.cgi X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: gcc-2.96-nn status References: <20010918124051.A30647@wwweasel.geeksrus.net> <3BA77E42.5410119A@cis.ohio-state.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Some clarification is needed: Arun Ramakrishnan wrote: > > I heard that 2.96 is again a devel version of gcc which is sorta > unstable. Not true. It was a CVS snapshot which was hardened and tested by Red Hat staff. If you have problems compiling your code, chances are the highest that your code is buggy, see http://www.bero.org/gcc296.html . > I heard posting saying that we shud downgrade to 2.95 possibly.I > think with RH 7.1, u no longer need kgcc to compile things > correctly.gcc itself works.In fact,i heard sby commenting that now > kgcc seems broke in RH 7.1 and so it is safe to use only gcc in RH > 7.1;while it was mandatory to use kgcc in RH 7.0!!!! In Red Hat Linux 7.0 you needed kgcc *only* to compile the kernel (thus the name) because kernel 2.2 had some bug. This bug got erased in kernel 2.4 so on any system which is no longer using kernel 2.2 you don't need (and shouldn't use) kgcc (which is called egcs-compat in RHL 7.1) any longer. Just fix your source code because it won't compile with gcc 3.x either. See the link above. > I also heard that binaries produced by gcc 3.0 are going to be > somewhat incompatible with the older binaries. Not the binaries. Binaries don't interoperate on symbol level. It's the libraries (object code) which are difficult. You cannot link to a library which was compiled with a different gcc version. So you have to compile the whole project with one compiler: kgcc, gcc 2.96-RH or gcc 3.x. Gcc 3.x should be compatible along version numers... BTW it gets even worse if you compile C++. I use gcc 2.96-RH on my RHL 7.1 only, it has worked for me (after I fixed some of my own code). I won't downgrade, and I'm still reluctant upgrading to gcc 3.x. Best regards, Martin Stricker -- Homepage: http://www.martin-stricker.de/ Registered Linux user #210635: http://counter.li.org/ From owner-linux-xfs@oss.sgi.com Tue Sep 18 14:58:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ILwmZ08691 for linux-xfs-outgoing; Tue, 18 Sep 2001 14:58:48 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ILwke08672 for ; Tue, 18 Sep 2001 14:58:46 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8ILwej20494 for ; Tue, 18 Sep 2001 14:58:40 -0700 Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id QAA47837; Tue, 18 Sep 2001 16:57:25 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.32 #1 (Debian)) id 15jSrr-0000sL-00; Tue, 18 Sep 2001 16:57:23 -0500 Date: Tue, 18 Sep 2001 16:57:23 -0500 From: Nathan Straz To: ebtigin@yahoo.com Cc: linux-xfs@oss.sgi.com Subject: Re: bootdisk Message-ID: <20010918165723.D30666@sgi.com> Mail-Followup-To: ebtigin@yahoo.com, linux-xfs@oss.sgi.com References: <200109190005.f8J05Ff02794@mail.kahkaha.net> <3BA7BA97.4681AFF6@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BA7BA97.4681AFF6@sgi.com> User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 18, 2001 at 04:20:23PM -0500, Eric Sandeen wrote: > ebtigin@yahoo.com wrote: > > when i try booting from SGI installer and choose rescue menu tries > > to reinstall RH 7.1 > > It shouldn't..., type "linux rescue" at the SGI installer CD prompt, > and it might start out looking like the installer (asks for language, > keyboard, etc) but you will wind up with a shell prompt. You should also be able to press ALT+F2 to get to the second VT and start working there. Press ALT+F1 to get back to the installer. -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Tue Sep 18 15:00:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IM0EJ08880 for linux-xfs-outgoing; Tue, 18 Sep 2001 15:00:14 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IM07e08859 for ; Tue, 18 Sep 2001 15:00:07 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f8IL8f818178; Tue, 18 Sep 2001 17:08:41 -0400 Date: Tue, 18 Sep 2001 17:08:41 -0400 From: Alan Eldridge To: Jean Francois Martinez Cc: SGI XFS Dev List Subject: Re: gcc-2.96-nn status Message-ID: <20010918170841.A17850@wwweasel.geeksrus.net> References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010918191512.03352ba8@pop.xs4all.nl> <3BA79FE5.27232AA@club-internet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BA79FE5.27232AA@club-internet.fr>; from jfm2@club-internet.fr on Tue, Sep 18, 2001 at 09:26:29PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 18, 2001 at 09:26:29PM +0200, Jean Francois Martinez wrote: >Gcc 2.96 requires C++ functions being declared before their use. I have found >many programs who need to be fixed. C++ requires functions being declared before their use. Period. Always has. All the way to the original cfront. C++ programs that have things used before their decls are broken, and should not compile on *any* C++ compiler. The issue is that the object layout and internal object management issues including vtables, etc were in flux, and gcc-2.96 uses a format that is compatible with neither 2.95 nor 3.0. This is called, in general, the C++ ABI, or Application Binary Interface. The issue is whether there are constructs in the kernel for which the optimizer generates bad code: bad in the sense of "not what was intended", as there are pieces of code in the kernel that a good optimizer will want to remove entirely, but which are necessary for correct functioning. And, I'll point out, before suggesting that is too off-topic to continue here, that since the kernel (1) doesn't contain C++ code and (2) doesn't link against anything but kernel specific modules, C++ ABI changes are a non-issue for us. *This thread is hereby declared too off-topic to live. This thread is dead. It's gone to meet it's maker. It's shuffled off the coil and gone to join the choir invisible. It's an EX-THREAD. Let it rest in peace.* >AFAIK kgscc is no longer shipped with 7.1. Reason kgcc was in 7.0 was because Kgcc, which lives in the compat-egcs-* set of rpms, is present in Rawhide as of this morning. As for RH 8.0, that's an open issue, as nothing has been announced one way or the other. But then, RedHat doesn't often announce what they're dropping. >gcc 2.96 did not compile kernel 2.2. gcc 2.96 had its bugs but in that case it >was due >to broken code in kernel that old more tolerant compilers accepted but should not >have. >kernel 2.4 has no longer this problem. See above. >About compiling specifically for athlon: > >1) The thing who will get you real benefits are the assembler parts (ie >unaffected by >compiler flags). Those are controlled by the kernel CONFIG_* defines, right? >2) On a PIII, compiling specifically for i686 gives a 15% improvement on pure C >programs >(my benchmark) over the worst case (compiling for plain Pentium). AMD >processors tend >to be more tolerant to code not specifically compiled for them since most of the >time they have >to cope with code optimized for Intel. > >Thus on kernel (mix of assembler and C) a good strategy if you want to use kgcc >(aka egcs) is >to go under arch/i386 and fix the file containing the compiler flags to use the >-D for athlon and >-march=i686. This will be a bit faster than compiling for i686. Gcc 2.96 >genrates faster code than egcs but if you are wary of it the above is the best >solution Sounds good. You've seconded a previously made suggestion, so that means at least 2 people have this working successfully. :) -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Tue Sep 18 15:14:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8IMEcq09348 for linux-xfs-outgoing; Tue, 18 Sep 2001 15:14:38 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8IMEYe09329 for ; Tue, 18 Sep 2001 15:14:34 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8IMESl31126 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 18 Sep 2001 15:14:29 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id AAA776411 for ; Wed, 19 Sep 2001 00:14:18 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA3004073; Tue, 18 Sep 2001 17:13:07 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA77920; Tue, 18 Sep 2001 17:13:07 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8IMEVT26664; Tue, 18 Sep 2001 17:14:31 -0500 Message-Id: <200109182214.f8IMEVT26664@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Martin Stricker cc: linux-xfs@oss.sgi.com Subject: Re: gcc-2.96-nn status In-Reply-To: Message from Martin Stricker of "Tue, 18 Sep 2001 23:46:41 +0200." <3BA7C0C0.1AA1A470@gmx.de> Date: Tue, 18 Sep 2001 17:14:31 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Some clarification is needed: > > Arun Ramakrishnan wrote: > > > > I heard that 2.96 is again a devel version of gcc which is sorta > > unstable. > > Not true. It was a CVS snapshot which was hardened and tested by Red Hat > staff. If you have problems compiling your code, chances are the highest > that your code is buggy, see http://www.bero.org/gcc296.html . > That refers mostly to user space things. The unfortunate issue with XFS is that it does a LOT of 64 but data manipulation, which on an ia32 means lots of messing with registers. In the few cases where I have managed to track bugs down into the actual code it has invariably been because the compiler forgot it had reused a register for something and attempted to use it for old contents rather than reloading them off the stack or out of memory. End result was usually an oops or some bizzare behavior. 95% of the XFS code base has had years of exposure in the Irix OS, and has proven very reliable there. These specific problems have only emerged on Linux, and so far the kgcc compiler (or egcs or how ever you want to refer to it) has been the most robust when it comes to generating correct code - probably because it was less aggressive about playing tricks with registers than later compilers. So, whilst I regularly do run kernels built with later compilers, there are still these occasional bugs which show up because of them and we definitely have cases where someone had corruption - rebuilt with kgcc and the corruption went away. Tracking a compiler bug from filesystem corruption on a machine on the other side of the planet is not something I care to tackle. Steve From owner-linux-xfs@oss.sgi.com Tue Sep 18 16:13:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8INDfw10393 for linux-xfs-outgoing; Tue, 18 Sep 2001 16:13:41 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8INDXe10369 for ; Tue, 18 Sep 2001 16:13:33 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id BAA08520; Wed, 19 Sep 2001 01:13:29 +0200 (CEST) Message-Id: <4.3.2.7.2.20010919010548.0335ae28@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 19 Sep 2001 01:13:11 +0200 To: Jean Francois Martinez , alan@geeksrus.net, linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: gcc-2.96-nn status In-Reply-To: <3BA79FE5.27232AA@club-internet.fr> References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010918191512.03352ba8@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8INDYe10370 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 21:26 18-9-2001 +0200, Jean Francois Martinez wrote: >Seth Mos a écrit : > > > At 13:02 18-9-2001 -0400, Arun Ramakrishnan wrote: > > >Hi, > > > I heard that 2.96 is again a devel version of gcc which is sorta > > > unstable.I > > > > It was a CVS snapshot. > > > >It was a CVS snapshot some 18 months ago. Eighteen months of bug hunting >later you can tell nothing about its stability. In fact because Gcc 2.96 was >frozen >over a year before gcc 3.0 and has been far more dceployed I trust it far m >ore than gcc 3.0+ True, but I gather 3.0+ will pop up in a lot more distributions then just redhat and mandrake. 3.0 is a official release which means it is not distribution specific. The reason that mandrake adopted is was more or less because a lot of mandrake is still redhat based. (no flame intended) The gcc people are working hard on getting 3.0 stable. Most kernel developers I met only work with official compilers. Not with wat shipped with their distro. > > >heard posting saying that we shud downgrade to 2.95 possibly.I think with > > >RH 7.1 > > >,u no longer need kgcc to compile things correctly.gcc itself works.In > fact,i > > > > For most userland programs it seems to be fine but I have encounterd some > > utilities that don't like it. > >Gcc 2.96 requires C++ functions being declared before their use. I have >found >many programs who need to be fixed. The same for gcc-3.0 > > For kernels kgcc might be a better solution. > >The only gcc tested by kernel people are egcs and gcc 2.95. There is ever a >danger kernel >will break if compiled with a different compiler. On another hand gcc >2.96 has >been used in >the two most popular Linux distributions so is a good test bench. Expect more reports of 3.0 when that turns up in a new distribution. > > >heard sby commenting that now kgcc seems broke in RH 7.1 and so it is > safe to > > >use only gcc in RH 7.1;while it was mandatory to use kgcc in RH 7.0!!!! > > > > Not that I know off. > >AFAIK kgscc is no longer shipped with 7.1. [seth@stimpy /data]$ which kgcc /usr/bin/kgcc [seth@stimpy /data]$ cat /etc/redhat-release Red Hat Linux release 7.1 (Seawolf) [seth@stimpy /data]$ rpm -ql compat-egcs|grep kgcc /usr/bin/kgcc [seth@stimpy /data]$ > Reason kgcc was in 7.0 was because >gcc 2.96 did not compile kernel 2.2. gcc 2.96 had its bugs but in that >case it >was due >to broken code in kernel that old more tolerant compilers accepted but >should not >have. >kernel 2.4 has no longer this problem. It's called compat-egcs for exactly that reason. It is a compatibility package including libs to compile packages for redhat 6.2 environments. > -march=i686. This will be a bit faster than compiling for i686. Gcc 2.96 >genrates faster code than egcs but if you are wary of it the above is the best >solution Comromises build the world -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Sep 18 16:47:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8INl0p10877 for linux-xfs-outgoing; Tue, 18 Sep 2001 16:47:00 -0700 Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8INkue10858 for ; Tue, 18 Sep 2001 16:46:56 -0700 Received: from scare ([63.231.179.33]) by lips.thebarn.com (8.12.0/8.12.0) with ESMTP id f8INkkRP000780; Tue, 18 Sep 2001 18:46:47 -0500 (CDT) Subject: Re: gcc-2.96-nn status From: Russell Cattelan To: Seth Mos Cc: Jean Francois Martinez , alan@geeksrus.net, linux-xfs@oss.sgi.com In-Reply-To: <4.3.2.7.2.20010919010548.0335ae28@pop.xs4all.nl> References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010918191512.03352ba8@pop.xs4all.nl> <4.3.2.7.2.20010919010548.0335ae28@pop.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1 X-Mailer: Evolution/0.13 (Preview Release) Date: 18 Sep 2001 18:46:47 -0500 Message-Id: <1000856809.22994.50.camel@scare> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8INkue10859 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 2001-09-18 at 18:13, Seth Mos wrote: > At 21:26 18-9-2001 +0200, Jean Francois Martinez wrote: > >Seth Mos a écrit : > > > > > At 13:02 18-9-2001 -0400, Arun Ramakrishnan wrote: > > > >Hi, > > > > I heard that 2.96 is again a devel version of gcc which is sorta > > > > unstable.I > > > > > > It was a CVS snapshot. > > > > > > >It was a CVS snapshot some 18 months ago. Eighteen months of bug hunting > >later you can tell nothing about its stability. In fact because Gcc 2.96 was > >frozen > >over a year before gcc 3.0 and has been far more dceployed I trust it far m > >ore than gcc 3.0+ > > True, but I gather 3.0+ will pop up in a lot more distributions then just > redhat and mandrake. > 3.0 is a official release which means it is not distribution specific. The > reason that mandrake adopted is was more or less because a lot of mandrake > is still redhat based. (no flame intended) Given how far ahead of Redhat Mandrake is I doubt that is true anymore. From owner-linux-xfs@oss.sgi.com Tue Sep 18 17:34:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J0YJd11606 for linux-xfs-outgoing; Tue, 18 Sep 2001 17:34:19 -0700 Received: from mail.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J0XBe11582 for ; Tue, 18 Sep 2001 17:33:11 -0700 Received: (qmail 37268 invoked from network); 19 Sep 2001 00:32:47 -0000 Received: from unknown (HELO Mario.hockeythug.net) ([64.81.17.163]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 19 Sep 2001 00:32:47 -0000 Subject: Anaconda crash on 1.0.1 install From: Jonathan Schwarz To: linux-xfs@oss.sgi.com Content-Type: multipart/mixed; boundary="=-unlbaESWI0CWGSfvr2E7" X-Mailer: Evolution/0.13.99+cvs.2001.09.09.07.08 (Preview Release) Date: 18 Sep 2001 20:32:46 -0400 Message-Id: <1000859568.22627.28.camel@Mario.hockeythug.net> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --=-unlbaESWI0CWGSfvr2E7 Content-Type: text/plain Content-Transfer-Encoding: 7bit Anaconda crashes on me whenever I try to install using the 1.0.1 install. Right after it transfers the 2nd stage image the hd, it dies. I have attached the dump (saved to floppy). The hardware is a Compaw Proliant 5000R. It has a raid 5 array on a SMART-2/P(cpqarray driver). When I installed plain RH7.1, I had a similar issue, but only once. The second time, it copied the image and continued. XFS installer has done it 3 times in a row. One problem, I think, may come from my boot floppies. The PC can't boot from a CD (even though the BIOS thinks it can) and so I made boot floppies. However, XFS 1.0.1 boot floppies don't recognize my floppy drive for my driver disk that I need for my raid array. It just freezes. I took the boot set and put on the vmlinuz and appropriate modules from 2.4.5-SGI_XFS_1.0.1BOOT. I then did the same for the driver disk. Next, I had to put xfs.o, xfs_support.o, pagebuf.o, xor.o and raid.o on a floppy and insmod them by hand. This is because the cd has the modules for the old boot kernel, and my iso won't let me rebuild it like a floppy - even mounted read-write. So I guess I have three questions - 1) Can this anaconda issue be fixed easily? 2) Can someone issue update boot disks/iso's, or help me figure out what's wrong with mine? 3) Is there something else I can change that might fix this issue otherwise? Sorry if this is so nebulous, I just don't know what's going on here now. RH 7.1 can install successfully, and I can read/write xfs filesystem with the boot kernel after loading the right modules. It doesn't matter if I do or don't format the root partition, it still crashes. Thanks for your help -- Jonathan Schwarz js@speakeasy.org -- --=-unlbaESWI0CWGSfvr2E7 Content-Type: text/plain Content-Disposition: attachment; filename=anacdump.txt Content-ID: <1000857938.22592.0.camel@Mario.hockeythug.net> Content-Transfer-Encoding: 7bit Traceback (innermost last): File "/usr/bin/anaconda", line 520, in ? intf.run(todo, test = test) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/text.py", line 1151, in run rc = apply (step[1](), args) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/text.py", line 572, in __call__ if todo.doInstall (): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1782, in doInstall if self.method.systemMounted (self.fstab, self.instPath, self.hdList.selected()): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/image.py", line 72, in systemMounted isys.lochangefd("/tmp/loop", self.loopbackFile) File "/usr/lib/anaconda/isys.py", line 76, in lochangefd _isys.lochangefd(loop, targ) SystemError: (22, 'Invalid argument') Local variables in innermost frame: file: /mnt/sysimage//rhinstall-stage2.img loop: 10 targ: 11 device: /tmp/loop ToDo object: (itodo ToDo p1 (dp2 S'resState' p3 S'' sS'progressWindow' p4 NsS'setupFilesystems' p5 I1 sS'monitorVsync' p6 S'' sS'videoCardStateNode' p7 S'' sS'serial' p8 I0 sS'ddruidReadOnly' p9 I0 sS'bootdisk' p10 I0 sS'videoRamState' p11 S'' sS'monitorOriginalName' p12 S'' sS'language' p13 (itodo Language (dp14 S'langInfoByName' p15 (dp16 S'Arabic (Yemen)' p17 (S'ar_YE' S'iso06' S'LatArCyrHeb-16' tsS'Spanish (Argentina)' p18 (S'es_AR' S'iso01' S'lat0-sun16' tsS'Italian (Italy)' p19 (S'it_IT@euro' S'iso15' S'lat0-sun16' tsS'Arabic (Lebanon)' p20 (S'ar_LB' S'iso06' S'LatArCyrHeb-16' tsS'Spanish (Guatemala)' p21 (S'es_GT' S'iso01' S'lat0-sun16' tsS'Malay (Malaysia)' p22 (S'ms_MY' S'iso01' S'lat0-sun16' tsS'Arabic (Libyan Arab Jamahiriya)' p23 (S'ar_LY' S'iso06' S'LatArCyrHeb-16' tsS'Arabic (Oman)' p24 (S'ar_OM' S'iso06' S'LatArCyrHeb-16' tsS'Arabic (Iraq)' p25 (S'ar_IQ' S'iso06' S'LatArCyrHeb-16' tsS'Arabic (Kuwait)' p26 (S'ar_KW' S'iso06' S'LatArCyrHeb-16' tsS'English (South Africa)' p27 (S'en_ZA' S'iso01' S'lat0-sun16' tsS'French (Switzerland)' p28 (S'fr_CH' S'iso01' S'lat0-sun16' tsS'Arabic (Bahrein)' p29 (S'ar_BH' S'iso06' S'LatArCyrHeb-16' tsS'Croatian' p30 (S'hr_HR' S'iso02' S'lat2-sun16' tsS'French (France)' p31 (S'fr_FR@euro' S'iso15' S'lat0-sun16' tsS'Greenlandic (Greenland)' p32 (S'kl_GL' S'iso01' S'lat0-sun16' tsS'Korean (Republic of Korea)' p33 (S'ko_KR.euckr' S'iso01' S'lat0-16' tsS'Ukrainian' p34 (S'uk_UA' S'koi8-u' S'cyr-sun16' tsS'Spanish (Mexico)' p35 (S'es_MX' S'iso01' S'lat0-sun16' tsS'Greek' p36 (S'el_GR' S'iso07' S'gr.f16' tsS'Spanish (El Salvador)' p37 (S'es_SV' S'iso01' S'lat0-sun16' tsS'Spanish (Peru)' p38 (S'es_PE' S'iso01' S'lat0-sun16' tsS'Spanish (Honduras)' p39 (S'es_HN' S'iso01' S'lat0-sun16' tsS'Spanish (Costa Rica)' p40 (S'es_CR' S'iso01' S'lat0-sun16' tsS'English (Denmark)' p41 (S'en_DK' S'iso01' S'lat0-sun16' tsS'Dutch (Netherlands)' p42 (S'nl_NL@euro' S'iso15' S'lat0-sun16' tsS'Serbian (Yugoslavia)' p43 (S'sr_YU@cyrillic' S'iso05' S'cyr-sun16' tsS'Russian (Ukraine)' p44 (S'ru_UA' S'koi8-u' S'cyr-sun16' tsS'Portuguese (Portugal)' p45 (S'pt_PT@euro' S'iso15' S'lat0-sun16' tsS'Afrikaans (South Africa)' p46 (S'af_ZA' S'iso01' S'lat0-sun16' tsS'Norwegian' p47 (S'no_NO' S'iso01' S'lat0-sun16' tsS'Arabic (Morocco)' p48 (S'ar_MA' S'iso06' S'LatArCyrHeb-16' tsS'English (Philippines)' p49 (S'en_PH' S'iso01' S'lat0-sun16' tsS'Arabic (Algeria)' p50 (S'ar_DZ' S'iso06' S'LatArCyrHeb-16' tsS'Indonesian' p51 (S'id_ID' S'iso01' S'lat0-sun16' tsS'Danish' p52 (S'da_DK' S'iso01' S'lat0-sun16' tsS'Chinese (Taiwan R.O.C.)' p53 (S'zh_TW.euctw' S'iso01' S'lat0-16' tsS'Faroese (Faroe Islands)' p54 (S'fo_FO' S'iso01' S'lat0-sun16' tsS'Galician (Spain)' p55 (S'gl_ES@euro' S'iso15' S'lat0-sun16' tsS'English (New Zealand)' p56 (S'en_NZ' S'iso01' S'lat0-sun16' tsS'Spanish (Bolivia)' p57 (S'es_BO' S'iso01' S'lat0-sun16' tsS'Cornish (Britain)' p58 (S'kw_GB' S'iso01' S'lat0-sun16' tsS'Arabic (United Arab Emirates)' p59 (S'ar_AE' S'iso06' S'LatArCyrHeb-16' tsS'German (Austria)' p60 (S'de_AT@euro' S'iso15' S'lat0-sun16' tsS'Romanian' p61 (S'ro_RO' S'iso02' S'lat2-sun16' tsS'Spanish (Paraguay)' p62 (S'es_PY' S'iso01' S'lat0-sun16' tsS'Hebrew (Israel)' p63 (S'he_IL' S'iso08' S'LatArCyrHeb-16' tsS'English (USA)' p64 (S'en_US' p65 S'iso01' p66 S'lat0-sun16' p67 tsS'Spanish (USA)' p68 (S'es_US' S'iso01' S'lat0-sun16' tsS'Portuguese (Brasil)' p69 (S'pt_BR' S'iso01' S'lat0-sun16' tsS'Spanish (Equador)' p70 (S'es_EC' S'iso01' S'lat0-sun16' tsS'Polish' p71 (S'pl_PL' S'iso02' S'lat2-sun16' tsS'Slovak' p72 (S'sk_SK' S'iso02' S'lat2-sun16' tsS'Macedonian' p73 (S'mk_MK' S'iso05' S'cyr-sun16' tsS'Spanish (Spain)' p74 (S'es_ES@euro' S'iso15' S'lat0-sun16' tsS'Spanish (Chile)' p75 (S'es_CL' S'iso01' S'lat0-sun16' tsS'Arabic (Syrian Arab Republic)' p76 (S'ar_SY' S'iso06' S'LatArCyrHeb-16' tsS'Czech' p77 (S'cs_CZ' S'iso02' S'lat2-sun16' tsS'Irish' p78 (S'ga_IE@euro' S'iso15' S'lat0-sun16' tsS'Arabic (Jordan)' p79 (S'ar_JO' S'iso06' S'LatArCyrHeb-16' tsS'Italian (Switzerland)' p80 (S'it_CH' S'iso01' S'lat0-sun16' tsS'German (Belgium)' p81 (S'de_BE@euro' S'iso15' S'lat0-sun16' tsS'Albanian' p82 (S'sq_AL' S'iso01' S'lat0-sun16' tsS'Finnish' p83 (S'fi_FI@euro' S'iso15' S'lat0-sun16' tsS'Swedish (Sweden)' p84 (S'sv_SE' S'iso01' S'lat0-sun16' tsS'English (Singapore)' p85 (S'en_SG' S'iso01' S'lat0-sun16' tsS'Dutch (Belgium)' p86 (S'nl_BE@euro' S'iso15' S'lat0-sun16' tsS'Spanish (Panama)' p87 (S'es_PA' S'iso01' S'lat0-sun16' tsS'Spanish (Venezuela)' p88 (S'es_VE' S'iso01' S'lat0-sun16' tsS'English (Great Britain)' p89 (S'en_GB' S'iso01' S'lat0-sun16' tsS'Russian' p90 (S'ru_RU.koi8r' S'koi8-u' S'cyr-sun16' tsS'Norwegian, Nynorsk (Norway)' p91 (S'nn_NO' S'iso01' S'lat0-sun16' tsS'English (Zimbabwe)' p92 (S'en_ZW' S'iso01' S'lat0-sun16' tsS'Spanish (Nicaragua)' p93 (S'es_NI' S'iso01' S'lat0-sun16' tsS'German (Luxemburg)' p94 (S'de_LU@euro' S'iso15' S'lat0-sun16' tsS'Spanish (Colombia)' p95 (S'es_CO' S'iso01' S'lat0-sun16' tsS'Basque (Spain)' p96 (S'eu_ES@euro' S'iso15' S'lat0-sun16' tsS'Arabic (Qatar)' p97 (S'ar_QA' S'iso06' S'LatArCyrHeb-16' tsS'Arabic (Egypt)' p98 (S'ar_EG' S'iso06' S'LatArCyrHeb-16' tsS'French (Belgium)' p99 (S'fr_BE@euro' S'iso15' S'lat0-sun16' tsS'English (Ireland)' p100 (S'en_IE@euro' S'iso15' S'lat0-sun16' tsS'Hungarian' p101 (S'hu_HU' S'iso02' S'lat2-sun16' tsS'Arabic (Tunisia)' p102 (S'ar_TN' S'iso06' S'LatArCyrHeb-16' tsS'French (Luxemburg)' p103 (S'fr_LU@euro' S'iso15' S'lat0-sun16' tsS'Japanese' p104 (S'ja_JP.eucJP' S'iso01' S'lat0-16' tsS'Swedish (Finland)' p105 (S'sv_FI@euro' S'iso15' S'lat0-sun16' tsS'Arabic (Saudi Arabia)' p106 (S'ar_SA' S'iso06' S'LatArCyrHeb-16' tsS'Spanish (Dominican Republic)' p107 (S'es_DO' S'iso01' S'lat0-sun16' tsS'French (Canada)' p108 (S'fr_CA' S'iso01' S'lat0-sun16' tsS'English (Canada)' p109 (S'en_CA' S'iso01' S'lat0-sun16' tsS'German (Germany)' p110 (S'de_DE@euro' S'iso15' S'lat0-sun16' tsS'Slovenian (Slovenia)' p111 (S'sl_SI' S'iso02' S'lat2-sun16' tsS'Spanish (Uruguay)' p112 (S'es_UY' S'iso01' S'lat0-sun16' tsS'German (Switzerland)' p113 (S'de_CH' S'iso01' S'lat0-sun16' tsS'English (Hong Kong)' p114 (S'en_HK' S'iso01' S'lat0-sun16' tsS'English (Australia)' p115 (S'en_AU' S'iso01' S'lat0-sun16' tsS'Catalan (Spain)' p116 (S'ca_ES@euro' S'iso15' S'lat0-sun16' tsS'Spanish (Puerto Rico)' p117 (S'es_PR' S'iso01' S'lat0-sun16' tsS'Turkish' p118 (S'tr_TR' S'iso09' S'lat5-sun16' tsS'Estonian' p119 (S'et_EE' S'iso01' S'lat0-sun16' tsS'Arabic (Sudan)' p120 (S'ar_SD' S'iso06' S'LatArCyrHeb-16' tsS'Icelandic' p121 (S'is_IS' S'iso01' S'lat0-sun16' tsS'English (Botswana)' p122 (S'en_BW' S'iso01' S'lat0-sun16' tsS'Manx Gaelic (Britain)' p123 (S'gv_GB' S'iso01' S'lat0-sun16' tssS'allSupportedLangs' p124 (lp125 g46 ag82 ag50 ag29 ag98 ag25 ag79 ag26 ag20 ag23 ag48 ag24 ag97 ag106 ag120 ag76 ag102 ag59 ag17 ag96 ag116 ag53 ag58 ag30 ag77 ag52 ag86 ag42 ag115 ag122 ag109 ag41 ag89 ag114 ag100 ag56 ag49 ag85 ag27 ag64 ag92 ag119 ag54 ag83 ag99 ag108 ag31 ag103 ag28 ag55 ag60 ag81 ag110 ag94 ag113 ag36 ag32 ag63 ag101 ag121 ag51 ag78 ag19 ag80 ag104 ag33 ag73 ag22 ag123 ag47 ag91 ag71 ag69 ag45 ag61 ag90 ag44 ag43 ag72 ag111 ag18 ag57 ag75 ag95 ag40 ag107 ag37 ag70 ag21 ag39 ag35 ag93 ag87 ag62 ag38 ag117 ag74 ag68 ag112 ag88 ag105 ag84 ag118 ag34 asS'info' p126 (dp127 S'SYSFONT' p128 g67 sS'SUPPORTED' p129 S'en_US:en' p130 sS'SYSFONTACM' p131 g66 sS'LANG' p132 g65 ssS'supported' p133 (lp134 g64 asS'default' p135 g64 sbsS'instClass' p136 (icustom InstallClass (dp137 S'rootPasswordCrypted' p138 I0 sS'raidList' p139 (lsS'nameserver' p140 S'' sS'x' NsS'rootPassword' p141 NsS'makeBootdisk' p142 I0 sS'installType' p143 NsS'postScript' p144 NsS'earlySwapOn' p145 I0 sS'networkDevice' p146 NsS'fstab' p147 (lsS'clearText' p148 NsS'lilo' p149 (S'mbr' p150 I1 S'' tsg13 NsS'name' p151 S'' sS'postInChroot' p152 I0 sS'pixmap' p153 S'' sS'partitions' p154 (lp155 (S'/boot' p156 (I48 I-1 I0 t(S'' I-1 I0 t(I0 S'xfs' p157 I0 tNta(S'/' (I700 I-1 I1 t(S'' I-1 I0 t(I0 g157 I0 tNta(S'swap' p158 (I496 I992 I1 t(S'' I-1 I0 t(I0 NI0 tNtasS'clearType' p159 S'wkst' p160 sS'gateway' p161 S'' sS'mouse' p162 NsS'packages' p163 NsS'timezone' p164 NsS'zeroMbr' p165 I0 sS'keyboard' p166 NsS'groups' p167 NsS'bootProto' p168 NsS'netmask' p169 S'' sS'langdefault' p170 NsS'skipSteps' p171 (dsS'auth' p172 (I1 I1 I0 S'' I0 S'' I0 I0 S'' S'' I0 S'' S'' S'' I0 S'' S'' tsS'hostname' p173 NsS'langsupported' p174 NsS'showgroups' p175 NsS'ip' p176 S'' sS'firewall' p177 (I-1 I1 (lp178 S'' I0 I0 I0 I0 I0 I0 tsS'defaultRunlevel' p179 NsS'desktop' p180 S'' sS'clearPartText' p181 S'Automatic partitioning will erase any preexisting Linux installations on your system.' p182 sS'clearParts' p183 I2 sbsS'bdstate' p184 S'' sS'extraModules' p185 (lp186 (S'/tmp/modules/tlan' S'net' S'tlan' ta(S'/tmp/modules/cpqarray' p187 S'scsi' p188 S'cpqarray' p189 tasS'skipLilo' p190 I0 sS'rootpassword' p191 NsS'fdDevice' p192 S'fd0' p193 sS'installSystem' p194 I1 sS'comps' p195 NsS'verifiedState' p196 (lp197 ((icomps Package p198 (dp199 S'size' p200 I548864 sS'chains' p201 (lp202 (lp203 (icomps Component p204 (dp205 S'includes' p206 (lsg151 S'Everything' p207 sS'hidden' p208 I0 sg135 I0 sS'pkgs' p209 (lp210 g198 a(icomps Package p211 (dp212 g200 I327680 sg201 (lp213 (lp214 (icomps Component p215 (dp216 g206 (lp217 (icomps Component p218 (dp219 g206 (lsg151 S'Printer Support' p220 sg208 I0 sg135 I1 sg209 (lp221 (icomps Package p222 (dp223 g200 I5685248 sg201 (lp224 (lp225 g218 aa(lp226 g204 aasS'selected' p227 I1 sS'h' --=-unlbaESWI0CWGSfvr2E7-- From owner-linux-xfs@oss.sgi.com Tue Sep 18 18:16:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J1G1q12417 for linux-xfs-outgoing; Tue, 18 Sep 2001 18:16:01 -0700 Received: from zion.rivenstone.net (dhcp065-024-121-117.columbus.rr.com [65.24.121.117]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J1Fwe12398 for ; Tue, 18 Sep 2001 18:15:58 -0700 Received: from there (gibraltar.rivenstone.net [192.168.1.1]) by zion.rivenstone.net (Postfix) with SMTP id B33524B542; Tue, 18 Sep 2001 16:24:01 -0400 (EDT) Content-Type: text/plain; charset="iso-8859-1" From: Joseph Fannin To: Seth Mos , Alan Eldridge Subject: Re: gcc-2.96-nn status Date: Tue, 18 Sep 2001 21:15:55 -0400 X-Mailer: KMail [version 1.3.1] Cc: SGI XFS Dev List References: <4.3.2.7.2.20010918190751.03312448@pop.xs4all.nl> <4.3.2.7.2.20010918192539.0375bbd0@pop.xs4all.nl> In-Reply-To: <4.3.2.7.2.20010918192539.0375bbd0@pop.xs4all.nl> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20010918202402.B33524B542@zion.rivenstone.net> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tuesday 18 September 2001 13:27, Seth Mos wrote: > At 13:19 18-9-2001 -0400, Alan Eldridge wrote: > >On Tue, Sep 18, 2001 at 07:14:47PM +0200, Seth Mos wrote: > > >At 12:40 18-9-2001 -0400, Alan Eldridge wrote: > > >I can, altough it does not have as many optimizations. So I only think > > > that the runtime speed would be affected. The linux kernel already > > > knows what a Athlon processor is and what to do with it. I think this > > > makes a larger difference then the compiler. > > > >Umm, how? rpm --target athlon causes gcc to be invoked with -march=athlon, > >which kgcc knows nothing about so it dies. > > You can specify a target of i686 and have a kernel config for athlon/duron > systems kgcc / egcs doesn't have k6 optimizations either. :-( Yet the kbuild scripts somehow know this and use -march=i586 when -march=k6 is not available. I'm sure the same test could be created for the athlon, and would be accepted into the kernel, but no one has bothered to do it. -- Joseph Fannin jhf@rivenstone.net "Bull in pure form is rare; there is usually some contamination by data." -- William Graves Perry Jr. From owner-linux-xfs@oss.sgi.com Tue Sep 18 18:25:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J1PGY12715 for linux-xfs-outgoing; Tue, 18 Sep 2001 18:25:16 -0700 Received: from zion.rivenstone.net (dhcp065-024-121-117.columbus.rr.com [65.24.121.117]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J1PDe12696 for ; Tue, 18 Sep 2001 18:25:13 -0700 Received: from there (gibraltar.rivenstone.net [192.168.1.1]) by zion.rivenstone.net (Postfix) with SMTP id 422E24B542 for ; Tue, 18 Sep 2001 16:33:18 -0400 (EDT) Content-Type: text/plain; charset="iso-8859-1" From: Joseph Fannin To: linux-xfs@oss.sgi.com Subject: 2.4.10-pre12 / gcc3 Date: Tue, 18 Sep 2001 21:25:12 -0400 X-Mailer: KMail [version 1.3.1] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20010918203318.422E24B542@zion.rivenstone.net> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Are the (wonderful) linux-xfs developers waiting a bit to merge CVS up to -pre11 / pre12 because of the large-scale VM changes, or has the work necessary for that merge just not been completed yet (perhaps because those same changes make it difficult)? I'll admit it; I'm eager to try the new VM stuff but I have an XFS / on my 'devel' box. On a second note, are the xfs developers prepared to look at kernel oopsen, etc. from kernels built with gcc3? RedHat 7.2 *cough*fairfax*cough* will almost certainly include it, though it won't be the default compiler. I may send one tonight, though it'll probably be a build failure rather than a bug. -- Joseph Fannin jhf@rivenstone.net "Bull in pure form is rare; there is usually some contamination by data." -- William Graves Perry Jr. From owner-linux-xfs@oss.sgi.com Tue Sep 18 18:46:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J1kFX13196 for linux-xfs-outgoing; Tue, 18 Sep 2001 18:46:15 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J1kDe13176 for ; Tue, 18 Sep 2001 18:46:13 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8J1k6l18859 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 18 Sep 2001 18:46:06 -0700 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id DAA802280 for ; Wed, 19 Sep 2001 03:45:56 +0200 (CEST) mail_from (kaos@melbourne.sgi.com) Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by nodin.corp.sgi.com (8.11.4/8.11.2/nodin-1.0) with ESMTP id f8J1ixs145050; Tue, 18 Sep 2001 18:44:59 -0700 (PDT) Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id B76E9300095; Wed, 19 Sep 2001 11:43:25 +1000 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id DEC86AB; Wed, 19 Sep 2001 11:43:25 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Joseph Fannin Cc: Seth Mos , Alan Eldridge , SGI XFS Dev List Subject: Re: gcc-2.96-nn status In-reply-to: Your message of "Tue, 18 Sep 2001 21:15:55 -0400." <20010918202402.B33524B542@zion.rivenstone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Sep 2001 11:43:20 +1000 Message-ID: <18091.1000863800@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 18 Sep 2001 21:15:55 -0400, Joseph Fannin wrote: > kgcc / egcs doesn't have k6 optimizations either. :-( Yet the kbuild >scripts somehow know this and use -march=i586 when -march=k6 is not >available. I'm sure the same test could be created for the athlon, and would >be accepted into the kernel, but no one has bothered to do it. 2.4.9 arch/i386/Makefile already does this ifdef CONFIG_MK6 CFLAGS += $(shell if $(CC) -march=k6 -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then echo "-march=k6"; else echo "-march=i586"; fi) endif ifdef CONFIG_MK7 CFLAGS += $(shell if $(CC) -march=athlon -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then echo "-march=athlon"; else echo "-march=i686 -mal ign-functions=4"; fi) endif From owner-linux-xfs@oss.sgi.com Tue Sep 18 19:24:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J2OHH13919 for linux-xfs-outgoing; Tue, 18 Sep 2001 19:24:17 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J2OEe13900 for ; Tue, 18 Sep 2001 19:24:15 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA09499 for ; Tue, 18 Sep 2001 19:22:52 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id MAA16359; Wed, 19 Sep 2001 12:23:03 +1000 Date: Wed, 19 Sep 2001 12:23:03 +1000 From: Keith Owens Message-Id: <200109190223.MAA16359@sherman.melbourne.sgi.com> Subject: TAKE - Support preemtible kernel Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Add include sched.h to support preemtible kernel. With this patch, XFS is reported to be preemtible ready. Date: Tue Sep 18 19:19:52 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103029a linux/fs/xfs_support/mutex.h - 1.2 linux/fs/xfs_support/atomic.h - 1.2 From owner-linux-xfs@oss.sgi.com Tue Sep 18 22:07:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J57HX17432 for linux-xfs-outgoing; Tue, 18 Sep 2001 22:07:17 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J57Ce17410 for ; Tue, 18 Sep 2001 22:07:12 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id WAA07088 for ; Tue, 18 Sep 2001 22:07:15 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id PAA95957 for linux-xfs@oss.sgi.com; Wed, 19 Sep 2001 15:05:54 +1000 (EST) Date: Wed, 19 Sep 2001 15:05:54 +1000 (EST) From: Nathan Scott Message-Id: <200109190505.PAA95957@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsprogs Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Tue Sep 18 16:49:43 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103021a cmd/xfstests/044 - 1.2 - define an _unexpected routine to handle unexpected command failure. Date: Tue Sep 18 21:52:16 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103034a cmd/xfstests/common.quota - 1.10 - ensure bulkstat ioctl directed to the filesystem, rather than the device on which it sits. problem is really in quota-tools, but we can workaround it till they're fixed. Date: Tue Sep 18 22:03:59 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103038a cmd/xfsprogs/include/builddefs.in - 1.17 cmd/xfsprogs/mkfs/Makefile - 1.8 cmd/xfsprogs/debian/Makefile - 1.5 cmd/xfsprogs/doc/CHANGES - 1.37 cmd/xfsprogs/configure.in - 1.12 cmd/xfsprogs/debian/changelog - 1.28 cmd/xfsprogs/VERSION - 1.29 cmd/xfsprogs/libdisk/lvm_user.h - 1.2 cmd/xfsprogs/libdisk/drivers.c - 1.4 cmd/xfsprogs/libdisk/lvm.h - 1.3 cmd/xfsprogs/libdisk/lvm.c - 1.3 cmd/xfsprogs/libdisk/liblvm.h - 1.4 cmd/xfsprogs/libdisk/Makefile - 1.2 - incorporate Martin's changes to rework the LVM support in mkfs. From owner-linux-xfs@oss.sgi.com Tue Sep 18 22:33:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J5XJM17802 for linux-xfs-outgoing; Tue, 18 Sep 2001 22:33:19 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J5XGe17783 for ; Tue, 18 Sep 2001 22:33:16 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f8J5XAj08461 for ; Tue, 18 Sep 2001 22:33:10 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id QAA29052; Wed, 19 Sep 2001 16:31:54 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id QAA77655; Wed, 19 Sep 2001 16:31:53 +1100 (AEDT) Date: Wed, 19 Sep 2001 16:31:52 +1100 From: Nathan Scott To: Rupa Schomaker Cc: linux-xfs@oss.sgi.com Subject: Re: OOPS: 2.4.5 + 1.0.1 patches Message-ID: <20010919163152.G348836@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 rupa-list+linux-xfs@rupa.com on Mon, Sep 17, 2001 at 04:09:15PM -0700 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Sep 17, 2001 at 04:09:15PM -0700, Rupa Schomaker wrote: > While using apt to update pidentd, I got the following error: > > Unpacking replacement pidentd ... > E: Sub-process /usr/bin/dpkg received a segmentation fault. which Debian version is this? (and in particular, which gcc) -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 18 23:21:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J6LhL18693 for linux-xfs-outgoing; Tue, 18 Sep 2001 23:21:43 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J6Lce18674 for ; Tue, 18 Sep 2001 23:21:38 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id XAA05946 for ; Tue, 18 Sep 2001 23:21:29 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id RAA29293; Wed, 19 Sep 2001 17:20:19 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id RAA04448; Wed, 19 Sep 2001 17:20:18 +1100 (AEDT) Date: Wed, 19 Sep 2001 17:20:17 +1100 From: Nathan Scott To: Takayuki Sasaki Cc: linux-xfs@oss.sgi.com Subject: Re: XFS + quota-3.01-pre9 + LVM ( QA suite 050 ) Message-ID: <20010919172017.A435188@wobbly.melbourne.sgi.com> References: <200109171210.VAA18856@tagajo.bsd.tnes.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109171210.VAA18856@tagajo.bsd.tnes.nec.co.jp>; from sasaki@bsd.tnes.nec.co.jp on Mon, Sep 17, 2001 at 09:10:32PM +0900 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Sep 17, 2001 at 09:10:32PM +0900, Takayuki Sasaki wrote: > Hi there, > > I try to run QA suite 050, and noticed that the following kernel > message is displayed on console: > > lvm -- lvm_blk_ioctl: unknown command 0xc0105865 > > I checked 050 and found that it was caused by "quot /dev/vg0/foo". > quot calls ioctl(XFS_IOC_FSBULKSTAT). > > However, if I try same thing on another box, it is OK. > The difference of these boxes are the revision of quota-tools. > > One is the latest quota-tools quota-3.01-pre9 and the another is > quota-3.01-pre?. ( sorry, I cannot find out exactry revision ...) > > To get the mount point of the filesystem, the old quot calls > getmntent() in mounttable() and it works ( ie. it returns > "/mnt/foo"). > > The new ( 3.01-pre9 ) quot calls get_next_mount() which is in > quotasys.c, but it not seems to work ( ie. it returns > "/dev/vg0/foo"). > > Has anyone met the same problem before? > Nope, but you are right - looks like this got broken by a change to the common routine you've called out. I'll take it up with the quota-tools folk. thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 18 23:28:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J6SkI18885 for linux-xfs-outgoing; Tue, 18 Sep 2001 23:28:46 -0700 Received: from relay-4v.club-internet.fr (relay-4v.club-internet.fr [194.158.96.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J6SZe18865 for ; Tue, 18 Sep 2001 23:28:36 -0700 Received: from club-internet.fr (bas14-140.idf.club-internet.fr [213.44.254.140]) by relay-4v.club-internet.fr (Postfix) with ESMTP id DB537168C; Wed, 19 Sep 2001 08:28:33 +0200 (CEST) Message-ID: <3BA83ECB.D022D19D@club-internet.fr> Date: Wed, 19 Sep 2001 08:44:27 +0200 From: jfm2@club-internet.fr X-Mailer: Mozilla 4.76 [fr] (X11; U; Linux 2.4.5-SGI_XFS_1.0.1_Indy i586) X-Accept-Language: en MIME-Version: 1.0 To: Seth Mos Cc: alan@geeksrus.net, linux-xfs@oss.sgi.com Subject: Re: gcc-2.96-nn status References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010918191512.03352ba8@pop.xs4all.nl> <4.3.2.7.2.20010919010548.0335ae28@pop.xs4all.nl> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos a écrit : > > At 21:26 18-9-2001 +0200, Jean Francois Martinez wrote: > >Seth Mos a écrit : > > > > > At 13:02 18-9-2001 -0400, Arun Ramakrishnan wrote: > > > >Hi, > > > > I heard that 2.96 is again a devel version of gcc which is sorta > > > > unstable.I > > > > > > It was a CVS snapshot. > > > > > > >It was a CVS snapshot some 18 months ago. Eighteen months of bug hunting > >later you can tell nothing about its stability. In fact because Gcc 2.96 was > >frozen > >over a year before gcc 3.0 and has been far more dceployed I trust it far m > >ore than gcc 3.0+ > > True, but I gather 3.0+ will pop up in a lot more distributions then just > redhat and mandrake. > 3.0 is a official release which means it is not distribution specific. The > reason that mandrake adopted is was more or less because a lot of mandrake > is still redhat based. (no flame intended) > I don't care which one is official what I care is which one crashes o and which one miscompiles less often For now gcc 3.0 is unproven and at least gcc 3.0 (don't know about gcc 3.0.1) has some horrific bugs far worse than those gcc 2.96 had in september 2000. Also RedHat and Mandrake have far more users than all the remaining distributions combined. Both RedHat ad Mandrake are poised to ship gcc 3 but gcc 2.96 will be the default compiler. Mandrake is no longer a clone of RedHat. Factors were gcc 2.96 superior C++ respective to gcc 2.95, faster executables (benchmarked) and perhaps support of Itanium. > The gcc people are working hard on getting 3.0 stable. Most kernel > developers I met only work with official compilers. Not with wat shipped > with their distro. > Kernel developers only accepted gcc 2.95 much later than it becvame official. First official label does not confer magically bug free status and second because kernel is very specific and requires specific testing of the compiler. > > > >heard posting saying that we shud downgrade to 2.95 possibly.I think with > > > >RH 7.1 > > > >,u no longer need kgcc to compile things correctly.gcc itself works.In > > fact,i > > > > > > For most userland programs it seems to be fine but I have encounterd some > > > utilities that don't like it. > > > >Gcc 2.96 requires C++ functions being declared before their use. I have > >found > >many programs who need to be fixed. > > The same for gcc-3.0 > > > > For kernels kgcc might be a better solution. > > > >The only gcc tested by kernel people are egcs and gcc 2.95. There is ever a > >danger kernel > >will break if compiled with a different compiler. On another hand gcc > >2.96 has > >been used in > >the two most popular Linux distributions so is a good test bench. > > Expect more reports of 3.0 when that turns up in a new distribution. > > > > >heard sby commenting that now kgcc seems broke in RH 7.1 and so it is > > safe to > > > >use only gcc in RH 7.1;while it was mandatory to use kgcc in RH 7.0!!!! > > > > > > Not that I know off. > > > >AFAIK kgscc is no longer shipped with 7.1. > > [seth@stimpy /data]$ which kgcc > /usr/bin/kgcc > [seth@stimpy /data]$ cat /etc/redhat-release > Red Hat Linux release 7.1 (Seawolf) > [seth@stimpy /data]$ rpm -ql compat-egcs|grep kgcc > /usr/bin/kgcc > [seth@stimpy /data]$ > > > Reason kgcc was in 7.0 was because > >gcc 2.96 did not compile kernel 2.2. gcc 2.96 had its bugs but in that > >case it > >was due > >to broken code in kernel that old more tolerant compilers accepted but > >should not > >have. > >kernel 2.4 has no longer this problem. > > It's called compat-egcs for exactly that reason. It is a compatibility > package including libs to compile packages for redhat 6.2 environments. > > > -march=i686. This will be a bit faster than compiling for i686. Gcc > 2.96 > >genrates faster code than egcs but if you are wary of it the above is the best > >solution > > Comromises build the world > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. -- Jean Francois Martinez The Independence project: because Linux should be for everyone http://independence.seul.org From owner-linux-xfs@oss.sgi.com Wed Sep 19 00:36:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J7aom20169 for linux-xfs-outgoing; Wed, 19 Sep 2001 00:36:50 -0700 Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J7aie20140 for ; Wed, 19 Sep 2001 00:36:45 -0700 Received: from bt02e0.god.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id f8J7aZZ14890 for ; Wed, 19 Sep 2001 09:36:35 +0200 (MET DST) Received: from god.bel.alcatel.be (bt02e1.god.bel.alcatel.be [138.203.145.14]) by bt02e0.god.bel.alcatel.be (8.9.3+Sun/8.9.3/1.1) with ESMTP id JAA09230 for ; Wed, 19 Sep 2001 09:35:44 +0200 (MET DST) Message-ID: <3BA84A54.B780F99D@god.bel.alcatel.be> Date: Wed, 19 Sep 2001 09:33:40 +0200 From: kris buggenhout X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: Re: gcc-2.96-nn status References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010918191512.03352ba8@pop.xs4all.nl> <4.3.2.7.2.20010919010548.0335ae28@pop.xs4all.nl> <3BA83ECB.D022D19D@club-internet.fr> Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by relay1.alcatel.be id f8J7aZZ14890 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8J7aje20141 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk jfm2@club-internet.fr wrote: > > Seth Mos a écrit : > > > > At 21:26 18-9-2001 +0200, Jean Francois Martinez wrote: > > >Seth Mos a écrit : > > > > > > > At 13:02 18-9-2001 -0400, Arun Ramakrishnan wrote: > > > > >Hi, > > > > > I heard that 2.96 is again a devel version of gcc which is sorta > > > > > unstable.I > > > > > > > > It was a CVS snapshot. > > > > > > > > > >It was a CVS snapshot some 18 months ago. Eighteen months of bug hunting > > >later you can tell nothing about its stability. In fact because Gcc 2.96 was > > >frozen > > >over a year before gcc 3.0 and has been far more dceployed I trust it far m > > >ore than gcc 3.0+ > > > > True, but I gather 3.0+ will pop up in a lot more distributions then just > > redhat and mandrake. > > 3.0 is a official release which means it is not distribution specific. The > > reason that mandrake adopted is was more or less because a lot of mandrake > > is still redhat based. (no flame intended) > > > > I don't care which one is official what I care is which one crashes o > and which one miscompiles less often > For now gcc 3.0 is unproven and at least gcc 3.0 (don't know about gcc > 3.0.1) > has some horrific bugs far worse than those gcc 2.96 had in september > 2000. > > Also RedHat and Mandrake have far more users than all the remaining > distributions > combined. Both RedHat ad Mandrake are poised to ship gcc 3 but gcc 2.96 > will be > the default compiler. > > Mandrake is no longer a clone of RedHat. Factors were gcc 2.96 superior > C++ > respective to gcc 2.95, faster executables (benchmarked) and perhaps > support of > Itanium. Funny, I have been using gcc 3+ for months for building kernels, xfs whatever... and havent got any problems yet. one system is running semi-production with 1TByte of storage attached to it.(a 2 CPU 4Gig machine) runnin an xfs kernel (mid august CVS) for 4 weeks built with gcc3 no problems yet... although we tested the system thoroughly on hardware failures. pulling power in the midst of a performance test ... etc. and had no barfs till date... only 1 problem but there I found a workaround ... increasing size of xfs fs that had been grown already, unmounting and xfs_repairing, mounting and extending ... worked From owner-linux-xfs@oss.sgi.com Wed Sep 19 01:31:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J8VgF21229 for linux-xfs-outgoing; Wed, 19 Sep 2001 01:31:42 -0700 Received: from pipe.aspec.ru (nobody@relay1.aspec.ru [217.14.198.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J8Vbe21210 for ; Wed, 19 Sep 2001 01:31:39 -0700 Received: from p100.p100.belkam.com ([192.168.22.254]) by pipe.aspec.ru (8.11.1/8.11.1) with ESMTP id f8J8VUv11747 for ; Wed, 19 Sep 2001 13:31:30 +0500 (SAMST) Received: from belkam.com ([192.168.22.111]) by p100.p100.belkam.com (8.9.3/8.9.3) with ESMTP id NAA29991 for ; Wed, 19 Sep 2001 13:31:30 +0500 Message-ID: <3BA8D65A.1010202@belkam.com> Date: Wed, 19 Sep 2001 13:31:06 -0400 From: Dmitry Melekhov User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010808 X-Accept-Language: ru, en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: quota Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello! I can't understand where xfs quota is stored. After remounting partition all quotas disappeared. From owner-linux-xfs@oss.sgi.com Wed Sep 19 01:49:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8J8n7121635 for linux-xfs-outgoing; Wed, 19 Sep 2001 01:49:07 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8J8n4e21616 for ; Wed, 19 Sep 2001 01:49:04 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id BAA21261 for ; Wed, 19 Sep 2001 01:49:06 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA00075; Wed, 19 Sep 2001 19:47:45 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA26286; Wed, 19 Sep 2001 18:47:44 +1000 (AEDT) Date: Wed, 19 Sep 2001 18:47:44 +1000 From: Nathan Scott To: Dmitry Melekhov Cc: linux-xfs@oss.sgi.com Subject: Re: quota Message-ID: <20010919184744.A435350@wobbly.melbourne.sgi.com> References: <3BA8D65A.1010202@belkam.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BA8D65A.1010202@belkam.com>; from dm@belkam.com on Wed, Sep 19, 2001 at 01:31:06PM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Sep 19, 2001 at 01:31:06PM -0400, Dmitry Melekhov wrote: > Hello! hi there, > I can't understand where xfs quota is stored. XFS stores quota information in two "hidden" inodes which hang off the primary superblock. They are not visible via "ls" (no directory entries for these two), as is common in other quota implementations (eg. the Linux VFS, as used by ext2 and other Linux filesystems). The information in the README.quota file in xfsprogs may help you get a better feel for these concepts. > After remounting partition all quotas disappeared. You must mount with the appropriate quota flags (always) to preserve quota information. If you don't, the quota checked flag will be cleared during mount, and no accounting will be performed for the duration of that mount. On the next mount with quota, you'll be forced to do a fresh quotacheck (which is done during mount for XFS, not via the quotacheck(8) tool) in order to reenable quota. Hope this helps. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Wed Sep 19 04:01:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JB1Ro23703 for linux-xfs-outgoing; Wed, 19 Sep 2001 04:01:27 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JB1Ne23683 for ; Wed, 19 Sep 2001 04:01:24 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id NAA05222; Wed, 19 Sep 2001 13:00:04 +0200 (CEST) Message-Id: <4.3.2.7.2.20010919125752.03ef32a8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 19 Sep 2001 12:59:43 +0200 To: Dmitry Melekhov , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: quota In-Reply-To: <3BA8D65A.1010202@belkam.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 13:31 19-9-2001 -0400, Dmitry Melekhov wrote: >Hello! > >I can't understand where xfs quota is stored. >After remounting partition all quotas disappeared. What does mount tell? and have you mounted it with the right qouta flags? Had you modified /etc/fstab so it gets remounted the right way after reboot? You give very little information so I can not really give you some real answers yet. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Sep 19 07:06:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JE6QG27990 for linux-xfs-outgoing; Wed, 19 Sep 2001 07:06:26 -0700 Received: from mail1.omnimark.com ([206.116.41.57]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JE6Le27971 for ; Wed, 19 Sep 2001 07:06:21 -0700 Received: from jupiter.hekla.exoterica.com (jupiter1.omnimark.com [192.168.1.1] (may be forged)) by mail1.omnimark.com (8.9.3/8.8.7) with ESMTP id JAA27707 for ; Wed, 19 Sep 2001 09:29:10 -0400 Received: from tux.hekla.exoterica.com (tux.hekla.exoterica.com [128.36.27.92]) by jupiter.hekla.exoterica.com (8.6.12/8.6.12) with SMTP id KAA26430 for ; Wed, 19 Sep 2001 10:07:52 -0400 Content-Type: text/plain; charset="iso-8859-1" From: "Mark G. Adams" Organization: OmniMark Technologies Corporation To: linux-xfs@oss.sgi.com Subject: Mounting an exported XFS partition on HP/UX 11.00 error Date: Wed, 19 Sep 2001 10:06:14 -0400 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01091910061409.06173@tux.hekla.exoterica.com> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Greetings. I've got a Linux box running the SGI-modified RedHat 7.1. Kernel is 2.4.3-SGI_XFS_1.0.1smp. I'm exporting one of the xfs partitions via NFS, and trying to mount it on an HP/UX 11.00 machine. The HP machine is able to mount nfs-exported ext2 partitions from another identical Linux box w/o a problem. However, when I try to mount a nfs-exported xfs partition, it is inaccessible after mounting. No error is returned while mounting, and I don't see an error in the Linux box's log. --------- # mount -F nfs -o hard,intr,rw tux:/u/rd/mga /mnt # ls mnt mnt unreadable # df df: open of tux:/u/rd/mga failed /home (/dev/vg00/lvol5 ): 36336 blocks 4840 i-nodes /opt (/dev/vg00/lvol6 ): 251108 blocks 33466 i-nodes /tmp (/dev/vg00/lvol4 ): 96272 blocks 12819 i-nodes /u (/dev/vg01/lvol1 ): 4007190 blocks 534166 i-nodes /usr (/dev/vg00/lvol7 ): 130354 blocks 17297 i-nodes /var (/dev/vg00/lvol8 ): 412596 blocks 54813 i-nodes /stand (/dev/vg00/lvol1 ): 99986 blocks 13404 i-nodes / (/dev/vg00/lvol3 ): 175136 blocks 23344 i-nodes --------- I am able to mount and access the partition if I specify vers=2 as one of the mount options. However, then I see the following behaviour: when any user tries to log into the HP machine, the login hangs for almost 1 minute. If I do a 'ps -elf' while somebody's logging in, I see that /usr/bin/quota's running for that user, and presumably that's what's hanging. Anybody have any ideas/suggestions? Thanks. //Mark -- Mark G. Adams Research & Development OmniMark Technologies Ottawa, Ontario, Canada mgadams@omnimark.com From owner-linux-xfs@oss.sgi.com Wed Sep 19 07:32:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JEWVx28564 for linux-xfs-outgoing; Wed, 19 Sep 2001 07:32:31 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JEWRe28545 for ; Wed, 19 Sep 2001 07:32:27 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8JEWHl03828 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Wed, 19 Sep 2001 07:32:17 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA792498 for ; Wed, 19 Sep 2001 16:32:07 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA3008039; Wed, 19 Sep 2001 09:30:59 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA85362; Wed, 19 Sep 2001 09:30:58 -0500 (CDT) Message-ID: <3BA8AC08.2AFA991D@sgi.com> Date: Wed, 19 Sep 2001 09:30:32 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Schwarz CC: linux-xfs@oss.sgi.com Subject: Re: Anaconda crash on 1.0.1 install References: <1000859568.22627.28.camel@Mario.hockeythug.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jonathan Schwarz wrote: > Anaconda crashes on me whenever I try to install using the 1.0.1 > install. Right after it transfers the 2nd stage image the hd, it dies. > One problem, I think, may come from my boot floppies. The PC can't boot > from a CD (even though the BIOS thinks it can) and so I made boot > floppies. However, XFS 1.0.1 boot floppies don't recognize my floppy > drive for my driver disk that I need for my raid array. It just freezes. > I took the boot set and put on the vmlinuz and appropriate modules from > 2.4.5-SGI_XFS_1.0.1BOOT. Hm, you're in uncharted waters here... for starters, the 2nd stage image contains modules that will probably try to load. That won't work if you are running a different kernel when you boot the installer. Also, 2.4.5 is a "pure" Linus kernel + XFS, with none of Red Hat's additions, this may cause unknown problems. > I then did the same for the driver disk. Where'd this driver disk come from? If it has modules that work with RH 7.1, those won't load under the 2.4.5 kernel. Let's back up and see what the errors are when you try the original XFS installer boot floppy? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Sep 19 07:46:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JEkZn28956 for linux-xfs-outgoing; Wed, 19 Sep 2001 07:46:35 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JEkHe28933 for ; Wed, 19 Sep 2001 07:46:17 -0700 Received: from ceejay (c729227-a.aurora1.co.home.com [24.10.134.178]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id HAA15738 for ; Wed, 19 Sep 2001 07:46:11 -0700 (PDT) mail_from (info@xenoform.net) Message-ID: <000b01c14114$d3a96550$0100a8c0@ceejay> From: "XenoFORM team." To: linux-xfs@oss.sgi.com Subject: XenoFORM Date: Wed, 19 Sep 2001 17:10:24 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01C1412D.F8F20970" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0008_01C1412D.F8F20970 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Greetings ! We have noticed your presence and would like to offer our services to = you. My name is Oleg, and I`m the lead artist of the XenoForm workgroup. = We are a recently founded team of professionals formed of designers, = artists, web-designers, and programmers. Presently, XenoForm employs = seven people.=20 At XenoForm, we are 3D artists, HTML/XML web programmers, musicians and = sound engineers, and experts in video composition and computer = animation. Everyone on the XenoForm team is an artist and expert in his = own field, with talents that cross over to other areas. Each XenoForm = member has over 5 years' experience in his respective field. Everyone = here has general familiarity with the industry standard professional = program suites and applications used to create modern multimedia. You = can see many examples of our work at http://xenoform.devil.ru.=20 XenoForm is based in the former Soviet Union, where highly skilled work = has a value estimated far below contracts of similar quality performed = elsewhere Europe or the USA. This means that XenoForm is uniquely poised = to assist the creation of your multimedia with the maximum return on = your investment in our services. We maintain close communications with = our project liasons to keep you involved in the stages of progress, = ensuring mutual understanding of the tasks we provide. Our experts are = ready to work night and day to satisfy all possible requirements to the = work assigned to us. Work on your project will be not cease until every = aspect of our product meets your satisfaction. When the construction of your project is completed, we don't consider = our job to be over. If you ever need an addition, correction, or = alteration, XenoForm will gladly improve on our previous projects as our = clients require. We offer highly professional and qualified work in the following areas:=20 Traditional design * Graphic design, visual concept, composition=20 * Custom graphics creation and image processing * High-end printable media creation (presentation materials, production = packaging, labels etc.)=20 Web-design and programming=20 * Custom graphics, image processing, and optimized images for Internet = use * HTML and XML page layout, including creation of style, patterns, and = systems to quickly update customer projects * Java and JavaScript programming for special effects and web page = interfacing * Macromedia FLASH - both high-grade sites on Flash and custom-made = elements (flash intro, interfaces, animation, soundtracks, effects)=20 * Programming on a server - oriented languages like PHP, PERL, ASP, = DHTML scripting and mechanisms for interactive pages, service of = databases and search systems * Creation of databases for SQL-based applications and integration with = user pages, including filling of databases and creation of interactive = information processing systems 3D graphics=20 * Professional model creation to any degree of complexity (for use in = many 3D-packages or CAD systems) * Modeling complex static or animated 3D-scenes and characters * Interior modeling (such as rooms and buildings) * Creation of high-grade 3D video clips for cinema, TV, and multimedia * Creation of low-poly models optimized for computer games on any of = existing platforms and 3D internet oriented browser plug-ins, for = example VRML and Shockwave 3D Video and audio * Professional nonlinear video composition (we can combine live video = and computer animations of any type!) * Musical composition and sound effects * Professional audio-composition and processing. Creation custom-made = musical tracks for broadcast video and radio, flash-presentations etc. Average monthly productivity=20 With our present resources and team members, XenoForm can make up to = five web sites of average complexity in a single month. This workload = does not restrict other projects, we can also create 3D models, = animation, and video clips in the same time frame. The audio studio is = independent from these two business lines and is capable of producing up = to 30 soundtracks per month for other clients.=20 Contact us=20 You can contact via e-mail: info@xenoform.net Visit our site: http://xenoform.devil.ru=20 Resently completed projects:=20 http://www.ipkonfig.com http://www.gamingin3d.com Sincerely Yours,=20 Oleg, Lead artist of XenoForm team. ------=_NextPart_000_0008_01C1412D.F8F20970 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
Greetings=20 !

We have noticed your presence and = would like=20 to offer our services to you. My name is Oleg, and I`m the lead artist = of the=20 XenoForm workgroup. We are a recently founded team of professionals = formed of=20 designers, artists, web-designers, and programmers. = Presently,=20 XenoForm employs seven people.

At XenoForm, we are 3D artists, = HTML/XML=20 web programmers, musicians and sound engineers, and experts in video = composition=20 and computer animation. Everyone on the XenoForm team is an artist and = expert in=20 his own field, with talents that cross over to other areas. Each = XenoForm member=20 has over 5 years' experience in his respective field. = Everyone=20 here has general familiarity with the industry standard professional = program=20 suites and applications used to create modern multimedia. You can see = many=20 examples of our work at http://xenoform.devil.ru.=20

XenoForm is based in the former Soviet Union, where = highly=20 skilled work has a value estimated far below = contracts=20 of similar quality performed elsewhere Europe or the USA. This means = that=20 XenoForm is uniquely poised to assist the creation of your multimedia = with the=20 maximum return on your investment in our services. We maintain close=20 communications with our project liasons to keep you involved in the = stages of=20 progress, ensuring mutual understanding of the tasks we  provide. = Our=20 experts are ready to work night and day to satisfy all possible = requirements to=20 the work assigned to us. Work on your project will be not cease until = every=20 aspect of our product meets your satisfaction.

When the = construction of=20 your project is completed, we don't consider our job to be over. If you = ever=20 need an addition, correction, or alteration, XenoForm will gladly = improve on our=20 previous projects as our clients=20 require.
We offer highly = professional and=20 qualified work in the following areas:

Traditional=20 design

* Graphic design, visual concept, composition =
*=20 Custom graphics creation and image processing
* High-end printable = media=20 creation (presentation materials, production packaging, labels etc.)=20

Web-design and programming

* Custom = graphics,=20 image processing, and optimized images for Internet use
* HTML and = XML page=20 layout, including creation of style, patterns, and systems to quickly = update=20 customer projects
* Java and JavaScript programming for special = effects and=20 web page interfacing
* Macromedia FLASH - both high-grade sites on = Flash and=20 custom-made elements (flash intro, interfaces, animation, soundtracks, = effects)=20
* Programming on a server - oriented languages like PHP, PERL, ASP, = DHTML=20 scripting and mechanisms for interactive pages, service of databases and = search=20 systems
* Creation of databases for SQL-based applications and = integration=20 with user pages, including filling of databases and creation of = interactive=20 information processing systems

3D graphics =

*=20 Professional model creation to any degree of complexity (for use in many = 3D-packages or CAD systems)
* Modeling complex static or animated = 3D-scenes=20 and characters
* Interior modeling (such as rooms and buildings)
* = Creation of high-grade 3D video clips for cinema, TV, and = multimedia
*=20 Creation of low-poly models optimized for computer games on any of = existing=20 platforms and 3D internet oriented browser plug-ins, for example VRML = and=20 Shockwave 3D

Video and audio

* = Professional=20 nonlinear video composition (we can combine live video and computer = animations=20 of any type!)
* Musical composition and sound effects
* = Professional=20 audio-composition and processing. Creation custom-made musical tracks = for=20 broadcast video and radio, flash-presentations = etc.

Average=20 monthly productivity

With our present resources and = team=20 members, XenoForm can make up to five web sites of average complexity in = a=20 single month. This workload does not restrict other projects, we can = also create=20 3D models, animation, and video clips in the same time frame. The audio = studio=20 is independent from these two business lines and is capable of producing = up to=20 30 soundtracks per month for other clients.

Contact us=20

You can contact via e-mail: info@xenoform.net
Visit our = site: http://xenoform.devil.ru =
 
Resently completed projects: =
http://www.ipkonfig.com
=
http://www.gamingin3d.com
 
Sincerely Yours, =
Oleg,=20 Lead artist of XenoForm team.
 
------=_NextPart_000_0008_01C1412D.F8F20970-- From owner-linux-xfs@oss.sgi.com Wed Sep 19 07:58:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JEwIv29296 for linux-xfs-outgoing; Wed, 19 Sep 2001 07:58:18 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JEw9e29275 for ; Wed, 19 Sep 2001 07:58:09 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8JEw4l06680 for ; Wed, 19 Sep 2001 07:58:04 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2923858; Wed, 19 Sep 2001 09:56:48 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA88343; Wed, 19 Sep 2001 09:56:48 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id JAA25590; Wed, 19 Sep 2001 09:56:47 -0500 (CDT) Message-Id: <200109191456.JAA25590@fsgi158.americas.sgi.com> Subject: Re: Mounting an exported XFS partition on HP/UX 11.00 error To: mgadams@omnimark.com (Mark G. Adams) Date: Wed, 19 Sep 2001 09:56:46 -0500 (CDT) Cc: linux-xfs@oss.sgi.com In-Reply-To: <01091910061409.06173@tux.hekla.exoterica.com> from "Mark G. Adams" at Sep 19, 2001 10:06:14 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Greetings. > > I've got a Linux box running the SGI-modified RedHat 7.1. Kernel is > 2.4.3-SGI_XFS_1.0.1smp. I'm exporting one of the xfs partitions via NFS, and > trying to mount it on an HP/UX 11.00 machine. > > The HP machine is able to mount nfs-exported ext2 partitions from another > identical Linux box w/o a problem. However, when I try to mount a > nfs-exported xfs partition, it is inaccessible after mounting. No error is > returned while mounting, and I don't see an error in the Linux box's log. > --------- > # mount -F nfs -o hard,intr,rw tux:/u/rd/mga /mnt > # ls mnt > mnt unreadable > # df > df: open of tux:/u/rd/mga failed > /home (/dev/vg00/lvol5 ): 36336 blocks 4840 i-nodes > /opt (/dev/vg00/lvol6 ): 251108 blocks 33466 i-nodes > /tmp (/dev/vg00/lvol4 ): 96272 blocks 12819 i-nodes > /u (/dev/vg01/lvol1 ): 4007190 blocks 534166 i-nodes > /usr (/dev/vg00/lvol7 ): 130354 blocks 17297 i-nodes > /var (/dev/vg00/lvol8 ): 412596 blocks 54813 i-nodes > /stand (/dev/vg00/lvol1 ): 99986 blocks 13404 i-nodes > / (/dev/vg00/lvol3 ): 175136 blocks 23344 i-nodes > --------- > > I am able to mount and access the partition if I specify vers=2 as one of the > mount options. However, then I see the following behaviour: when any user > tries to log into the HP machine, the login hangs for almost 1 minute. If I > do a 'ps -elf' while somebody's logging in, I see that /usr/bin/quota's > running for that user, and presumably that's what's hanging. > > Anybody have any ideas/suggestions? > Anything interesting from tcpdump when you do the df? For example: tcpdump -s 300 ip host and Tad From owner-linux-xfs@oss.sgi.com Wed Sep 19 08:11:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JFBYX29796 for linux-xfs-outgoing; Wed, 19 Sep 2001 08:11:34 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JFBUe29774 for ; Wed, 19 Sep 2001 08:11:30 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8JFBOj25511 for ; Wed, 19 Sep 2001 08:11:24 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA3011396; Wed, 19 Sep 2001 10:10:08 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA99004; Wed, 19 Sep 2001 10:10:08 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8JFBPJ22325; Wed, 19 Sep 2001 10:11:25 -0500 Message-Id: <200109191511.f8JFBPJ22325@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Joseph Fannin cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.10-pre12 / gcc3 In-Reply-To: Message from Joseph Fannin of "Tue, 18 Sep 2001 21:25:12 EDT." <20010918203318.422E24B542@zion.rivenstone.net> Date: Wed, 19 Sep 2001 10:11:24 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Are the (wonderful) linux-xfs developers waiting a bit to merge CVS up to > > -pre11 / pre12 because of the large-scale VM changes, or has the work > necessary for that merge just not been completed yet (perhaps because those > same changes make it difficult)? I'll admit it; I'm eager to try the new VM > stuff but I have an XFS / on my 'devel' box. I wish Linus would admit that he is working on 2.5 - this is not exactly a minor change to be making right now. I managed to get a pre11 kernel up yesterday, and it was VERY easy to get processes killed by the oom handler. pre12 merge is underway right now. I suspect it will take a while to get this one sorted out - since major surgery in the VM does have an affect on XFS. > > On a second note, are the xfs developers prepared to look at kernel > oopsen, etc. from kernels built with gcc3? RedHat 7.2 *cough*fairfax*cough* > will almost certainly include it, though it won't be the default compiler. I > > may send one tonight, though it'll probably be a build failure rather than a > bug. Well, it all depends on how good the oops report is - and almost certainly we would need more details - such as a disassembly of the complete function which the oops happened in, oh and possibly you machine too ;-) Steve > > -- > Joseph Fannin > jhf@rivenstone.net > > "Bull in pure form is rare; there is usually some contamination by data." > -- William Graves Perry Jr. From owner-linux-xfs@oss.sgi.com Wed Sep 19 08:46:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JFk6u30447 for linux-xfs-outgoing; Wed, 19 Sep 2001 08:46:06 -0700 Received: from vortex.xnote.com ([65.105.237.130]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JFk3e30428 for ; Wed, 19 Sep 2001 08:46:04 -0700 Received: from xnote.com (slccheck01.firsthealth.com [209.180.88.28]) by vortex.xnote.com (8.11.0/8.8.7) with ESMTP id f8JErmn08220 for ; Wed, 19 Sep 2001 08:53:48 -0600 Message-ID: <3BA8BD94.4050908@xnote.com> Date: Wed, 19 Sep 2001 09:45:24 -0600 From: Vernon McPherron User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.3) Gecko/20010801 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: .config for 1.0.1 PR3 installer Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've loaded RH 7.1 (sgi 1.0.1 PR3) and have since used the cvs kernel. The problem I have is when I installed the kernel source rpm, I couldn't find the config. There are a few "settings" in the 2.4.3 (1.0.1 PR3) kernel that I'd like to compile in the cvs kernel. (i.e. power management, etc.) when I searched for the config that was used to compile that kernel I couldn't find it. I looked in the /usr/src/linux for the .config. Nothing. Should this have been in the rpm? -- -=/Vernon McPherron/=- From owner-linux-xfs@oss.sgi.com Wed Sep 19 09:01:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JG1J530798 for linux-xfs-outgoing; Wed, 19 Sep 2001 09:01:19 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JG1Fe30776 for ; Wed, 19 Sep 2001 09:01:15 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id JAA23308 for ; Wed, 19 Sep 2001 09:01:18 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA3009839; Wed, 19 Sep 2001 10:59:58 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA45411; Wed, 19 Sep 2001 10:59:58 -0500 (CDT) Message-ID: <3BA8C0E1.DC11873F@sgi.com> Date: Wed, 19 Sep 2001 10:59:29 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Vernon McPherron CC: linux-xfs@oss.sgi.com Subject: Re: .config for 1.0.1 PR3 installer References: <3BA8BD94.4050908@xnote.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Vernon McPherron wrote: > when I searched for the config that was used to compile that kernel I > couldn't find it. I looked in the /usr/src/linux for the .config. Nothing. Is it in /usr/src/linux/configs? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Sep 19 09:03:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JG3Dc30941 for linux-xfs-outgoing; Wed, 19 Sep 2001 09:03:13 -0700 Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JG3Ae30919 for ; Wed, 19 Sep 2001 09:03:10 -0700 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.11.6/8.11.6) with ESMTP id f8JG2r511258; Wed, 19 Sep 2001 12:03:01 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Wed, 19 Sep 2001 12:02:53 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: To: Vernon McPherron cc: Subject: Re: .config for 1.0.1 PR3 installer In-Reply-To: <3BA8BD94.4050908@xnote.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 19 Sep 2001 at 9:45am, Vernon McPherron wrote > I've loaded RH 7.1 (sgi 1.0.1 PR3) and have since used the cvs kernel. > > The problem I have is when I installed the kernel source rpm, I couldn't > find the config. There are a few "settings" in the 2.4.3 (1.0.1 PR3) > kernel that I'd like to compile in the cvs kernel. (i.e. power > management, etc.) > > when I searched for the config that was used to compile that kernel I > couldn't find it. I looked in the /usr/src/linux for the .config. Nothing. > > Should this have been in the rpm? [jlb@philip jlb]$ cd /usr/src/linux-2.4/configs/ [jlb@philip configs]$ ls kernel-2.4.5-i386-BOOT.config kernel-2.4.5-i586.config kernel-2.4.5-i386-smp.config kernel-2.4.5-i686-enterprise.config kernel-2.4.5-i386.config kernel-2.4.5-i686-smp.config kernel-2.4.5-i586-smp.config kernel-2.4.5-i686.config -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From owner-linux-xfs@oss.sgi.com Wed Sep 19 09:12:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JGCim31243 for linux-xfs-outgoing; Wed, 19 Sep 2001 09:12:44 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JGCee31224 for ; Wed, 19 Sep 2001 09:12:41 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15jjxn-0006YD-00; Wed, 19 Sep 2001 12:12:39 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f8JGCcw03356; Wed, 19 Sep 2001 12:12:38 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Vernon McPherron Cc: linux-xfs@oss.sgi.com Subject: Re: .config for 1.0.1 PR3 installer References: <3BA8BD94.4050908@xnote.com> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 19 Sep 2001 12:12:38 -0400 In-Reply-To: <3BA8BD94.4050908@xnote.com> Message-ID: Lines: 20 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Vernon" == Vernon McPherron writes: Vernon> I've loaded RH 7.1 (sgi 1.0.1 PR3) and have since used the cvs Vernon> kernel. The problem I have is when I installed the kernel Vernon> source rpm, I couldn't find the config. There are a few Vernon> "settings" in the 2.4.3 (1.0.1 PR3) kernel that I'd like to Vernon> compile in the cvs kernel. (i.e. power management, etc.) Vernon> when I searched for the config that was used to compile that Vernon> kernel I couldn't find it. I looked in the /usr/src/linux for Vernon> the .config. Nothing. You can find the .config here: ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/kernel_rpms/RHlinux-2.4.3/kernel-2.4.3-SGI_XFS_1.0.1.src.rpm -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Wed Sep 19 09:30:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JGUVn31626 for linux-xfs-outgoing; Wed, 19 Sep 2001 09:30:31 -0700 Received: from mail.fdrinnovation.com (mail.fdrinnovation.com [207.140.179.15]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JGUSe31607 for ; Wed, 19 Sep 2001 09:30:28 -0700 Received: from bobnt.fdrinnovation.com ([192.168.150.40]) by mail.fdrinnovation.com (Netscape Messaging Server 4.15) with ESMTP id GJX4HG00.210; Wed, 19 Sep 2001 12:29:40 -0400 Message-Id: <5.1.0.14.2.20010919121845.00a8cec0@mail.fdrinnovation.com> X-Sender: bperper@mail.fdrinnovation.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 19 Sep 2001 12:29:50 -0400 To: linux-xfs@oss.sgi.com From: "Bob Perper" Subject: XFS & the RedHat Installer Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, My name is Bob Perper and I'm a developer of the backup product UPSTREAM. When I used the "XFS for Red Hat Linux 7.1 Installer" to upgrade my RedHat 7.0 system to 7.1, it all worked well. However, when I tried: mkfs -t xfs /dev/hdb1 It reported the error: mkfs.xfs: No such file or directory. There's also no fsck.xfs in /sbin. However, the xfs daemon is running. I've been somewhat afraid to try to install any RPM's since it seems to be partially installed now. Where should I go from here? Thanks, Bob Perper bperper@fdrinnovation.com (973) 890-7300 From owner-linux-xfs@oss.sgi.com Wed Sep 19 09:40:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JGeKI31896 for linux-xfs-outgoing; Wed, 19 Sep 2001 09:40:20 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JGeHe31877 for ; Wed, 19 Sep 2001 09:40:17 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8JGeBl18452 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Wed, 19 Sep 2001 09:40:11 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id SAA844075 for ; Wed, 19 Sep 2001 18:40:02 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA3013909; Wed, 19 Sep 2001 11:38:53 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA65611; Wed, 19 Sep 2001 11:38:52 -0500 (CDT) Message-ID: <3BA8CA02.1072389@sgi.com> Date: Wed, 19 Sep 2001 11:38:26 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Bob Perper CC: linux-xfs@oss.sgi.com Subject: Re: XFS & the RedHat Installer References: <5.1.0.14.2.20010919121845.00a8cec0@mail.fdrinnovation.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Bob Perper wrote: > > Hi, > My name is Bob Perper and I'm a developer of the backup product > UPSTREAM. When I used the "XFS for Red Hat Linux 7.1 Installer" to upgrade > my RedHat 7.0 system to 7.1, it all worked well. However, when I tried: > mkfs -t xfs /dev/hdb1 > It reported the error: > mkfs.xfs: No such file or directory. > There's also no fsck.xfs in /sbin. > However, the xfs daemon is running. That's the X Font Server, it won't help. :) > I've been somewhat afraid to try to install any RPM's since it seems to > be partially installed now. Where should I go from here? Check to make sure you have any of the XFS userspace RPMs installed - try rpm -q xfsprogs If it's not installed, install it. It's possible that since you didn't have it in RH 7.0, the installer didn't "upgrade" it, and you'll have to install it by hand. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Sep 19 09:46:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JGk0p32161 for linux-xfs-outgoing; Wed, 19 Sep 2001 09:46:00 -0700 Received: from ms1.adiis.net (IDENT:root@ms1.adiis.net [207.177.36.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JGjue32142 for ; Wed, 19 Sep 2001 09:45:56 -0700 Received: (from root@localhost) by ms1.adiis.net (8.11.2/8.11.2) id f8JGjtf23886; Wed, 19 Sep 2001 11:45:55 -0500 Received: from dialupoffice.adiis.net (IDENT:rbutler@dialupoffice.adiis.net [207.177.36.9]) by ms1.adiis.net (8.11.2/8.11.2) with ESMTP id f8JGjrJ23719; Wed, 19 Sep 2001 11:45:53 -0500 Subject: Re: XFS & the RedHat Installer From: Ryan Butler To: Bob Perper Cc: linux-xfs@oss.sgi.com In-Reply-To: <5.1.0.14.2.20010919121845.00a8cec0@mail.fdrinnovation.com> References: <5.1.0.14.2.20010919121845.00a8cec0@mail.fdrinnovation.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Evolution-Format: text/plain X-Mailer: Evolution/0.13.99+cvs.2001.09.19.07.08 (Preview Release) Date: 19 Sep 2001 11:45:52 -0500 Message-Id: <1000917953.8060.1.camel@dialupoffice.adiis.net> Mime-Version: 1.0 X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello Bob, If you upgraded from RedHat 7.0 without XFS to RedHat 7.1 with XFS using the upgrade path, it probably did not install the RPMS for the xfs utilities since they wouldn't have been installed originally to be upgraded. In addition, the xfs daemon has nothing to do witht he XFS filesystem, the daemon is the X font server daemon. The best thing to do would to installt he xfs RPMS off the SGI CD or download them from oss.sgi.com and install them. Ryan Butler ADI Internet Solutions rbutler@adiis.net On Wed, 2001-09-19 at 11:29, Bob Perper wrote: > Hi, > My name is Bob Perper and I'm a developer of the backup product > UPSTREAM. When I used the "XFS for Red Hat Linux 7.1 Installer" to upgrade > my RedHat 7.0 system to 7.1, it all worked well. However, when I tried: > mkfs -t xfs /dev/hdb1 > It reported the error: > mkfs.xfs: No such file or directory. > There's also no fsck.xfs in /sbin. > However, the xfs daemon is running. > I've been somewhat afraid to try to install any RPM's since it seems to > be partially installed now. Where should I go from here? > Thanks, > > Bob Perper > bperper@fdrinnovation.com > (973) 890-7300 From owner-linux-xfs@oss.sgi.com Wed Sep 19 10:47:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JHlMt00634 for linux-xfs-outgoing; Wed, 19 Sep 2001 10:47:22 -0700 Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JHlHe00615 for ; Wed, 19 Sep 2001 10:47:17 -0700 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.11.6/8.11.6) with ESMTP id f8JGfLh11566; Wed, 19 Sep 2001 12:41:28 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Wed, 19 Sep 2001 12:41:21 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: To: Bob Perper cc: Subject: Re: XFS & the RedHat Installer In-Reply-To: <5.1.0.14.2.20010919121845.00a8cec0@mail.fdrinnovation.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 19 Sep 2001 at 12:29pm, Bob Perper wrote > Hi, > My name is Bob Perper and I'm a developer of the backup product > UPSTREAM. When I used the "XFS for Red Hat Linux 7.1 Installer" to upgrade > my RedHat 7.0 system to 7.1, it all worked well. However, when I tried: > mkfs -t xfs /dev/hdb1 > It reported the error: > mkfs.xfs: No such file or directory. Do you have the xfsprogs RPM installed? > There's also no fsck.xfs in /sbin. Same RPM, although keep in mind that the function of fsck.xfs (as the rather droll man page points out) is to "do nothing, successfully". > However, the xfs daemon is running. That's Something Completely Different -- the X font server. > I've been somewhat afraid to try to install any RPM's since it seems to > be partially installed now. Where should I go from here? I've never used the installer, but it looks like it missed some stuff. First, make sure that you are running an XFS kernel ('uname -a'). Then make sure that you have the userland stuff installed -- at least xfsprogs and xfsprogs-devel. Then have another go at it. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From owner-linux-xfs@oss.sgi.com Wed Sep 19 10:50:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JHoki00805 for linux-xfs-outgoing; Wed, 19 Sep 2001 10:50:46 -0700 Received: from mail1.omnimark.com ([206.116.41.57]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JHode00783 for ; Wed, 19 Sep 2001 10:50:39 -0700 Received: from jupiter.hekla.exoterica.com (jupiter1.omnimark.com [192.168.1.1] (may be forged)) by mail1.omnimark.com (8.9.3/8.8.7) with ESMTP id NAA28803; Wed, 19 Sep 2001 13:13:28 -0400 Received: from tux.hekla.exoterica.com (tux.hekla.exoterica.com [128.36.27.92]) by jupiter.hekla.exoterica.com (8.6.12/8.6.12) with SMTP id NAA00162; Wed, 19 Sep 2001 13:52:11 -0400 Content-Type: text/plain; charset="iso-8859-1" From: "Mark G. Adams" Organization: OmniMark Technologies Corporation To: Tad Dolphay Subject: Re: Mounting an exported XFS partition on HP/UX 11.00 error Date: Wed, 19 Sep 2001 13:50:32 -0400 X-Mailer: KMail [version 1.2] Cc: linux-xfs@oss.sgi.com References: <200109191456.JAA25590@fsgi158.americas.sgi.com> In-Reply-To: <200109191456.JAA25590@fsgi158.americas.sgi.com> MIME-Version: 1.0 Message-Id: <0109191350320E.06173@tux.hekla.exoterica.com> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wednesday 19 September 2001 10:56 am, Tad Dolphay wrote: > Anything interesting from tcpdump when you do the df? > > For example: > tcpdump -s 300 ip host and Hi, Tad. Ok, made some progress. The 1st problem (error with 'df' or 'cd') has nothing to do with xfs, and only has to do with the wierd way HP/UX deals with nfs permissions. I managed to reproduce that problem on an ext2 partition, and was due to the exported directory having no permissions for other users (770). As it turns out, 'df' worked fine as the user with permissions for the exported dir; just not any other users, including root. Yet another way that HP/UX has to be different from everybody else. The 2nd problem (quota checking hanging) stuck around, and I found the following problem in the tcp trace when doing a 'df' (tux is the Linux box, Osiris is the HP/UX 11.00 box): 13:33:52.241467 eth0 < osiris.hekla.exoterica.com.49273 > tux.hekla.exoterica.com.sunrpc: S 643514180:643514180(0) win 32768 13:33:52.241467 eth0 > tux.hekla.exoterica.com.sunrpc > osiris.hekla.exoterica.com.49273: S 3702664261:3702664261(0) ack 643514181 win 5840 (DF) 13:33:52.241467 eth0 < osiris.hekla.exoterica.com.49273 > tux.hekla.exoterica.com.sunrpc: F 1:1(0) ack 1 win 32768 13:33:52.241467 eth0 > tux.hekla.exoterica.com.sunrpc > osiris.hekla.exoterica.com.49273: F 1:1(0) ack 2 win 5840 (DF) 13:33:52.241467 eth0 < osiris.hekla.exoterica.com.49273 > tux.hekla.exoterica.com.sunrpc: . 2:2(0) ack 2 win 32768 13:33:52.241467 eth0 < osiris.hekla.exoterica.com.49992 > tux.hekla.exoterica.com.sunrpc: udp 56 13:33:52.241467 eth0 > tux.hekla.exoterica.com.sunrpc > osiris.hekla.exoterica.com.49992: udp 28 (DF) 13:33:52.251467 eth0 < osiris.hekla.exoterica.com.49993 > tux.hekla.exoterica.com.894: udp 92 13:33:58.241525 eth0 < osiris.hekla.exoterica.com.49993 > tux.hekla.exoterica.com.894: udp 92 13:33:58.241525 eth0 > tux.hekla.exoterica.com > osiris.hekla.exoterica.com: icmp: tux.hekla.exoterica.com udp port 894 unreachable [tos 0xc0] 13:34:10.241644 eth0 < osiris.hekla.exoterica.com.49993 > tux.hekla.exoterica.com.894: udp 92 13:34:10.241644 eth0 > tux.hekla.exoterica.com > osiris.hekla.exoterica.com: icmp: tux.hekla.exoterica.com udp port 894 unreachable [tos 0xc0] The reason was that rpc.rquotad on the Linux box was crashing upon being contacted by the HP box. I tried upgrading it to the quota-3.01pre9-0.7.1.i386.rpm errata recently released by RedHat, and the problem has gone away. Note that rpc.rquotad now outputs the following message upon logging in to the HP box: rpc.rquotad: Mountpoint (or device) /u/rd/mga not found. which I presume is harmless? (at least since I'm not actually using quotas) The version of quota which was crashing is whatever comes on the SGI-modified RedHat 7.1 install CD. So, things seem to be working now with nfs v3, although the quota crash might be a concern (especially if there's a reason that I shouldn't be using the RedHat errata package, as discussed during a previous thread). Thanks for your help. //Mark -- Mark G. Adams Research & Development OmniMark Technologies Ottawa, Ontario, Canada mgadams@omnimark.com From owner-linux-xfs@oss.sgi.com Wed Sep 19 14:12:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JLCY205395 for linux-xfs-outgoing; Wed, 19 Sep 2001 14:12:34 -0700 Received: from clubphoto.com (mail-gw.clubphoto.com [64.124.34.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JLCTe05376 for ; Wed, 19 Sep 2001 14:12:29 -0700 Received: from clubphoto.com (speedycat.clubphoto.local [192.168.168.112]) by clubphoto.com (8.9.3/8.9.3) with ESMTP id OAA21131; Wed, 19 Sep 2001 14:12:28 -0700 Message-ID: <3BA9089C.3E3C605@clubphoto.com> Date: Wed, 19 Sep 2001 14:05:32 -0700 From: "Drew 'Cheetah!' Maxwell" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com, cheetah@clubphoto.com Subject: Use of SGI-XFS-1.0.1 with RAID... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello there. I have been using the SGI XFS releases for some time now, and it has come to be that we want to include some fault tolerance for our filesystems in the form of RAID mirroring. It seems to be giving us a fair bit of problems in doing so, however. In using the CD-ROM's installer, the 'Make RAID Devices' section of the partition phase in Disk Druid was missing, so instead, I tried using KickStart: In using KickStart, the following lines were included in ks.cfg: part raid.01 --size 3000 --ondisk hda part raid.02 --size 3000 --ondisk hdc part swap --size 1000 --ondisk hda part swap --size 1000 --ondisk hdc part raid.11 --size 3000 --ondisk hda part raid.12 --size 3000 --ondisk hdc part raid.21 --size 10 --grow --ondisk hda part raid.22 --size 10 --grow --ondisk hdc raid / --level 1 --device md0 raid.01 raid.02 raid /var --level 1 --device md1 raid.11 raid.12 raid /home --level 1 --device md2 raid.21 raid.22 As per the RedHat 7.1 Manuals, this is the correct method for setting up mirrored RAID devices. However, when this is used, anaconda complains with the following error: Traceback (innermost last): File "/usr/bin/anaconda", line 520, in ? intf.run(todo, test = test) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/text.py", line 1151, in run rc = apply (step[1](), args) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/textw/partitioning_text.py", line 135, in __call__ todo.lilo.allowLiloLocationConfig(todo.fstab) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/lilo.py", line 154, in allowLiloLocationConfig bootDevice = fstab.getBootDevice() File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 267, in getBootDevice for (mntpoint, partition, fsystem, doFormat, size) in self.mountList(): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 1052, in mountList if fsType == "swap": continue NameError: fsType (I have the anaconda dump as well, if more information is required.) Any thoughts/caveats/suggestions for making the SGI XFS 1.0.1 version of RedHat Linux set up RAID mirroring from install time? Thank you. --Drew 'Cheetah!' Maxwell [cheetah@clubphoto.com] From owner-linux-xfs@oss.sgi.com Wed Sep 19 15:34:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8JMYiY06745 for linux-xfs-outgoing; Wed, 19 Sep 2001 15:34:44 -0700 Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8JMYee06726 for ; Wed, 19 Sep 2001 15:34:41 -0700 Received: (qmail 1347 invoked by uid 0); 19 Sep 2001 22:34:33 -0000 Received: from b1d02.pppool.de (HELO gmx.de) (213.7.29.2) by mail.gmx.net (mp005-rz3) with SMTP; 19 Sep 2001 22:34:33 -0000 Message-ID: <3BA91D74.B4A0157B@gmx.de> Date: Thu, 20 Sep 2001 00:34:28 +0200 From: Martin Stricker Organization: http://martin-stricker.de/ http://www.surfo.net/ http://www.masterportal24.com/cgi-bin/YaBB.cgi X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: gcc-2.96-nn status References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010918191512.03352ba8@pop.xs4all.nl> <4.3.2.7.2.20010919010548.0335ae28@pop.xs4all.nl> <3BA83ECB.D022D19D@club-internet.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk jfm2@club-internet.fr wrote: > > Both RedHat ad Mandrake are poised to ship gcc 3 but gcc 2.96 > will be the default compiler. This is due to binary compatibility between non-major releases (the ones only changing the second digit in the version number like 7.0, 7.1), at least for Red Hat (I don't use Mandrake so I don't know). Best regards, Martin Stricker -- Homepage: http://www.martin-stricker.de/ Registered Linux user #210635: http://counter.li.org/ From owner-linux-xfs@oss.sgi.com Wed Sep 19 17:09:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8K09js08564 for linux-xfs-outgoing; Wed, 19 Sep 2001 17:09:45 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8K09ee08545 for ; Wed, 19 Sep 2001 17:09:41 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 47D77C00B61 for ; Thu, 20 Sep 2001 08:09:38 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id D8170C00B60 for ; Thu, 20 Sep 2001 08:09:36 +0800 (PHT) Date: Thu, 20 Sep 2001 08:09:36 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Re: Samba error during build when ACL support enabled In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 18 Sep 2001 at 17:40, jtrostel@snapserver.com wrote: > Does chacl work on an XFS mounted file system? Yes, it works. "chacl -l *" displays the ACLs of all files (currently blank because I haven't set them). I tested setting the ACLs of a test file and it works fine. > Where are: > acl.h - should be in /usr/include/sys (not /usr/include) > libacl.* - should be in /lib acl.h is in /usr/include/sys. libacl.a and libacl.la are in /usr/lib but have symlinks pointing to them in /lib, too. libacl.so and company are in /lib. > Does .../source/includes/includes.h have a line > > #ifdef HAVE_SYS_ACL_H > #include > #endif Yes, it does. Hmm ... I wonder what could be wrong. :( Perhaps I can wait for the major ACL code merging work to be in working order before trying again. --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Wed Sep 19 21:13:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8K4Dae12348 for linux-xfs-outgoing; Wed, 19 Sep 2001 21:13:36 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8K4DVe12328 for ; Wed, 19 Sep 2001 21:13:32 -0700 Received: from johnson.mail.mindspring.net (johnson.mail.mindspring.net [207.69.200.177]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id VAA00661 for ; Wed, 19 Sep 2001 21:13:23 -0700 (PDT) mail_from (jtrostel@mindspring.com) Received: from [209.86.24.88] (user-38lc62o.dialup.mindspring.com [209.86.24.88]) by johnson.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id AAA27184; Thu, 20 Sep 2001 00:03:53 -0400 (EDT) From: John M Trostel Message-ID: <2.1-3965581-253-B-OEWW@mail.mindspring.com> To: Federico Sevilla III , Linux XFS Mailing List Date: Wed, 19 Sep 2001 23:42:23 -0500 Subject: Re: Samba error during build when ACL support enabled X-Mailer: Eudora 2.1 for PalmOS Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk My copies here work fine. I don't think you need to wait for any "major ACL code merging work". The stuff SAMBA needs for day to day operations is there and functional. I don't have my laptop here now, but something you mentioned did get my interest. You say that chacl shows no ACLs (as you haven't set any yet.) Try this: 1. Set "reasonable" normal & default ACLs on the directory representing the share. u::rwx,g::rwx,o::rwx,m::rwx/u::rwx,g::r-x,o::r-x,m::rwx comes to mind :-> 2. create a new file in the share Federico Sevilla III wrote: > Hmm ... I wonder what could be wrong. :( > > Perhaps I can wait for the major ACL code merging work to be in working > order before trying again. > > --> Jijo -- Visor Mail from ... John M Trostel jtrostel@snapserver.com Linux OS Engineer Quantum / Snap Appliances From owner-linux-xfs@oss.sgi.com Wed Sep 19 22:45:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8K5jW713587 for linux-xfs-outgoing; Wed, 19 Sep 2001 22:45:32 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8K5jOe13567 for ; Wed, 19 Sep 2001 22:45:24 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id HAA29022; Thu, 20 Sep 2001 07:45:21 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id HAA28370; Thu, 20 Sep 2001 07:45:20 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 3AEA157306; Thu, 20 Sep 2001 07:44:46 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 7CF9B25835; Thu, 20 Sep 2001 07:44:42 +0200 (CEST) Message-ID: <3BA9824A.7ECF6FA3@ch.sauter-bc.com> Date: Thu, 20 Sep 2001 07:44:42 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: "Drew 'Cheetah!' Maxwell" Cc: linux-xfs@oss.sgi.com Subject: Re: Use of SGI-XFS-1.0.1 with RAID... References: <3BA9089C.3E3C605@clubphoto.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Drew 'Cheetah!' Maxwell" schrieb: > > Hello there. > > I have been using the SGI XFS releases for some time now, and it has > come to be that we want to include some fault tolerance for our > filesystems in the form of RAID mirroring. It seems to be giving us a > fair bit of problems in doing so, however. I don't know whats going on in your case but setting up Software RAID at install time has always worked for me with the RH-7.1-XFS-1.0(+.1) installer. Maybe you have to check you CD's? Did you try to you fdisk and setup some partitions with type fd and then using the installer to just create the RAID? -Simon > In using the CD-ROM's installer, the 'Make RAID Devices' section of the > partition phase in Disk Druid was missing, so instead, I tried using > KickStart: > > In using KickStart, the following lines were included in ks.cfg: > > part raid.01 --size 3000 --ondisk hda > part raid.02 --size 3000 --ondisk hdc > part swap --size 1000 --ondisk hda > part swap --size 1000 --ondisk hdc > part raid.11 --size 3000 --ondisk hda > part raid.12 --size 3000 --ondisk hdc > part raid.21 --size 10 --grow --ondisk hda > part raid.22 --size 10 --grow --ondisk hdc > raid / --level 1 --device md0 raid.01 raid.02 > raid /var --level 1 --device md1 raid.11 raid.12 > raid /home --level 1 --device md2 raid.21 raid.22 > > As per the RedHat 7.1 Manuals, this is the correct method for setting up > mirrored RAID devices. However, when this is used, anaconda complains > with the following error: > > Traceback (innermost last): > File "/usr/bin/anaconda", line 520, in ? > intf.run(todo, test = test) > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/text.py", line 1151, in > run > rc = apply (step[1](), args) > File > "/var/tmp/anaconda-7.1//usr/lib/anaconda/textw/partitioning_text.py", > line 135, in __call__ > todo.lilo.allowLiloLocationConfig(todo.fstab) > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/lilo.py", line 154, in > allowLiloLocationConfig > bootDevice = fstab.getBootDevice() > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 267, in > getBootDevice > for (mntpoint, partition, fsystem, doFormat, size) in > self.mountList(): > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 1052, in > mountList > if fsType == "swap": continue > NameError: fsType > > (I have the anaconda dump as well, if more information is required.) > > Any thoughts/caveats/suggestions for making the SGI XFS 1.0.1 version of > RedHat Linux > set up RAID mirroring from install time? > > Thank you. > > --Drew 'Cheetah!' Maxwell [cheetah@clubphoto.com] From owner-linux-xfs@oss.sgi.com Thu Sep 20 00:16:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8K7GDk15066 for linux-xfs-outgoing; Thu, 20 Sep 2001 00:16:13 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8K7G9e15047 for ; Thu, 20 Sep 2001 00:16:09 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 4BFFBC00B61 for ; Thu, 20 Sep 2001 15:16:05 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id F4193C00B60 for ; Thu, 20 Sep 2001 15:16:02 +0800 (PHT) Date: Thu, 20 Sep 2001 15:16:02 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Re: Samba error during build when ACL support enabled In-Reply-To: <2.1-3965581-253-B-OEWW@mail.mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 19 Sep 2001 at 23:42, John M Trostel wrote: > My copies here work fine. I don't think you need to wait for any > "major ACL code merging work". The stuff SAMBA needs for day to day > operations is there and functional. It's actually not the working that's a problem. Packages I built against I think the XFS tree circa kernel 2.4.8 still wrk, but I can't build any new packages because of the previously mentioned errors. :( --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Thu Sep 20 01:07:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8K87Oi15881 for linux-xfs-outgoing; Thu, 20 Sep 2001 01:07:24 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8K87Ke15862 for ; Thu, 20 Sep 2001 01:07:20 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id BAA08122 for ; Thu, 20 Sep 2001 01:07:21 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA08760; Thu, 20 Sep 2001 19:06:01 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id TAA41044; Thu, 20 Sep 2001 19:06:00 +1100 (AEDT) Date: Thu, 20 Sep 2001 19:05:59 +1100 From: Nathan Scott To: Federico Sevilla III Cc: Linux XFS Mailing List Subject: Re: Samba error during build when ACL support enabled Message-ID: <20010920190559.C416300@wobbly.melbourne.sgi.com> References: <2.1-3965581-253-B-OEWW@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jijo@leathercollection.ph on Thu, Sep 20, 2001 at 03:16:02PM +0800 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Thu, Sep 20, 2001 at 03:16:02PM +0800, Federico Sevilla III wrote: > On Wed, 19 Sep 2001 at 23:42, John M Trostel wrote: > > My copies here work fine. I don't think you need to wait for any > > "major ACL code merging work". The stuff SAMBA needs for day to day > > operations is there and functional. > > It's actually not the working that's a problem. Packages I built against I > think the XFS tree circa kernel 2.4.8 still wrk, but I can't build any new > packages because of the previously mentioned errors. :( > I had a quick look - the problem seems to be this little gem from the file "samba-2.2.1a/debian/config.cache": ... # POSIX ACL support not present in Linux 2.2; not allowed in the # Debian packages, even if present on the build machine. ac_cv_header_sys_acl_h=${ac_cv_header_sys_acl_h=no} ... this has the effect of forcing the configure script to not find sys/acl.h, which has the follow-on effect of not defining HAVE_SYS_ACL_H in the generated source/include/config.h header, which then has the nasty effect of skipping over the sys/acl.h include in the rest of the sources, which ultimately causes the compile errors you see. If you change the above debian/config.cache line to instead be: ac_cv_header_sys_acl_h=${ac_cv_header_sys_acl_h=yes} you should be right - it Works For Me (tm) anyway. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 20 01:14:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8K8E7c16153 for linux-xfs-outgoing; Thu, 20 Sep 2001 01:14:07 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8K8E3e16132 for ; Thu, 20 Sep 2001 01:14:03 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id CC0B1C00B61 for ; Thu, 20 Sep 2001 16:14:00 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id EB318C00B60 for ; Thu, 20 Sep 2001 16:13:57 +0800 (PHT) Date: Thu, 20 Sep 2001 16:13:57 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Re: Samba error during build when ACL support enabled In-Reply-To: <20010920190559.C416300@wobbly.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 20 Sep 2001 at 19:05, Nathan Scott wrote: > I had a quick look - the problem seems to be this little gem from the > file "samba-2.2.1a/debian/config.cache": Aha! Another file to check regularly. ;> > ... > # POSIX ACL support not present in Linux 2.2; not allowed in the > # Debian packages, even if present on the build machine. > > ac_cv_header_sys_acl_h=${ac_cv_header_sys_acl_h=no} Thank you very much. Done that and it Works For Me (tm) too. At least it _builds_. And it wasn't an XFS issue after all. My apologies for something that I should've asked in the Samba list instead. Thanks again, Nathan. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Thu Sep 20 02:15:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8K9FMQ17506 for linux-xfs-outgoing; Thu, 20 Sep 2001 02:15:22 -0700 Received: from smtp-server.nlr.nl (spider.nlr.nl [137.17.80.200]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8K9FIe17482 for ; Thu, 20 Sep 2001 02:15:18 -0700 Received: from nlr.nl (doorbel-2.nlr.nl [137.17.128.65]) by smtp-server.nlr.nl (8.11.6/8.11.6/NLR 24/01/2001) with ESMTP id f8K9F7X1090234; Thu, 20 Sep 2001 11:15:07 +0200 (CDT) Disclaimer: "The National Aerospace Laboratory NLR DOES NOT ACCEPT ANY FINANCIAL COMMITMENT derived from this message." Message-ID: <3BA9A62D.84376F17@nlr.nl> Date: Thu, 20 Sep 2001 10:17:50 +0200 From: Paul Arendsen Organization: National Aerospace Laboratory X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4-64GB-SMP i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS in kernel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Guys What is keep you from including XFS in the kernel itself. Reiserfs is included and ext3 is on its way. I use SuSE at home and RedHat-with-XFS at the office and I would like to use XFS and SuSE. Since including stuff in the kernel is essential for long term (I do not want the hassle echa time I update my distribution) Paul -- ------------------------------------------------------------------ From: Paul Arendsen Address: National Aerospace Lab. E-Mail - arends@nlr.nl Voorsterweg 31 8316 PR Marknesse Phone (+31)527 - 248675 (The Netherlands) telefax (+31)527 - 248210 ------------------------------------------------------------------ From owner-linux-xfs@oss.sgi.com Thu Sep 20 02:21:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8K9LVH17845 for linux-xfs-outgoing; Thu, 20 Sep 2001 02:21:31 -0700 Received: from uk-exch.magma-da.com ([195.224.245.42]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8K9LSe17825 for ; Thu, 20 Sep 2001 02:21:28 -0700 Message-ID: <414DB4427DE6D411846200B0D078E84B169DD1@uk-exch.magma-da.com> From: "Saunders, Andrew (Magma-da/Reading-UK)" To: "'linux-xfs@oss.sgi.com'" Cc: "Saunders, Andrew (Magma-da/Reading-UK)" , "Ronny Adsetts (E-mail)" Subject: Bad write page, under 2.4.9 kernel Date: Thu, 20 Sep 2001 10:14:14 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi there, I have recently installed XFS on a 2.4.9 kernel using the XFS patch patch-2.4.9-xfs-2001-08-26.bz2 . If I create a fairly large file using: thor:/users/andrews# dd if=/dev/zero of=big_file bs=1M count=4096 and then issue a few thor:/users/andrews# ls -ltr in the directory where the file is being written I get the following messages logged by the kernel. Sep 20 10:00:14 thor kernel: Bad write on page 0xc1822a30 Sep 20 10:00:27 thor kernel: Bad write on page 0xc113d8f0 Sep 20 10:00:27 thor kernel: Bad write on page 0xc16d16d0 Sep 20 10:00:28 thor kernel: Bad write on page 0xc109500c Sep 20 10:00:28 thor kernel: Bad write on page 0xc12b2834 Sep 20 10:00:30 thor kernel: Bad write on page 0xc11d5944 Anyone got an ideas what could be causing this? The machine I am running on is a dual Pentium III 1Ghz, with 512Mb and has a Mylex DAC960 configured for RAID5? I put the put the same kernel on my home computer and that seems fine. Could this be an SMP issue? Many Thanks Andrew From owner-linux-xfs@oss.sgi.com Thu Sep 20 05:49:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KCngO22048 for linux-xfs-outgoing; Thu, 20 Sep 2001 05:49:42 -0700 Received: from rain.CC.Lehigh.EDU (rain.CC.Lehigh.EDU [128.180.39.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KCnWe22029 for ; Thu, 20 Sep 2001 05:49:32 -0700 Received: from Lehigh.EDU (hooch.CC.Lehigh.EDU [128.180.3.11]) by rain.CC.Lehigh.EDU (8.11.5/8.11.5) with ESMTP id f8KCmgT04501; Thu, 20 Sep 2001 08:48:47 -0400 Message-ID: <3BA9E2BF.F1392BCD@Lehigh.EDU> Date: Thu, 20 Sep 2001 08:36:15 -0400 From: Jim Eshleman X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: "Saunders, Andrew (Magma-da/Reading-UK)" CC: "'linux-xfs@oss.sgi.com'" , "Ronny Adsetts (E-mail)" Subject: Re: Bad write page, under 2.4.9 kernel References: <414DB4427DE6D411846200B0D078E84B169DD1@uk-exch.magma-da.com> Content-Type: multipart/mixed; boundary="------------A5CC3E3436BC8930A0E5310D" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------A5CC3E3436BC8930A0E5310D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I also am seeing the "Bad write on page" errors. Attached is syslog info from two incidents. The first was after three weeks uptime, the second was after one week uptime. The system is a heavily-loaded mail server, IBM Netfinity x370 8-way PIII Xeon, 8.5GB RAM (HIGHMEM enabled) running 2.4.9 + patch-2.4.9-xfs-2001-08-17 compiled with egcs-2.91.66. The XFS filesystems are on top of LVM, on top of hardware RAID1E. After the errors the system becomes unresponsive. I suspected a 2.4 VM bug but searching LKML archives turns up no hits, so maybe it is XFS related. I also saw the error after six hours running 2.4.9 + linux-2.4.9-xfs-2001-08-26.patch. Jim --------------A5CC3E3436BC8930A0E5310D Content-Type: text/plain; charset=us-ascii; name="bug.1" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="bug.1" Sep 11 17:05:41 xxxx kernel: Bad write on page 0xc13169a8 Sep 11 17:05:49 xxxx kernel: Warning: buffer 0xeaa97c60 with weird blockno (0) Sep 11 17:05:49 xxxx kernel: kernel BUG at ll_rw_blk.c:1011! Sep 11 17:05:49 xxxx kernel: invalid operand: 0000 Sep 11 17:05:49 xxxx kernel: CPU: 1 Sep 11 17:05:49 xxxx kernel: EIP: 0010:[ll_rw_block+141/540] Sep 11 17:05:49 xxxx kernel: EIP: 0010:[] Sep 11 17:05:49 xxxx kernel: EFLAGS: 00010286 Sep 11 17:05:49 xxxx kernel: eax: 00000020 ebx: 00003a04 ecx: 00000001 edx: 00000001 Sep 11 17:05:49 xxxx kernel: esi: 00000000 edi: 00000200 ebp: d3fc9d44 esp: d3fc9cec Sep 11 17:05:49 xxxx kernel: ds: 0018 es: 0018 ss: 0018 Sep 11 17:05:49 xxxx kernel: Process procmail (pid: 6664, stackpage=d3fc9000) Sep 11 17:05:49 xxxx kernel: Stack: c022d850 c022db02 000003f3 dae17bf8 eaa97c60 d3fc9d60 00000000 eaa97c60 Sep 11 17:05:49 xxxx kernel: 4e4d4c4b 5251504f 56555453 5a595857 00001000 c0137764 00000001 00000001 Sep 11 17:05:49 xxxx kernel: d3fc9d44 dae17be0 e336a24c e336a234 00000001 d3fc9d60 eaa97c60 37633630 Sep 11 17:05:49 xxxx kernel: Call Trace: [fsync_inode_buffers+176/396] [scrup+107/260] [reschedule_idle+575/588] [lf+47/92] [printk+417/432] Sep 11 17:05:49 xxxx kernel: Call Trace: [] [] [] [] [] Sep 11 17:05:49 xxxx kernel: [__refile_buffer+100/108] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-525546/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-524566/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-522417/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-522112/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-121076/96] Sep 11 17:05:49 xxxx kernel: [] [] [] [] [] [] Sep 11 17:05:49 xxxx kernel: [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-135678/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-221589/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-96284/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-63804/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-529609/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-8064/96] Sep 11 17:05:49 xxxx kernel: [] [] [] [] [] [] Sep 11 17:05:49 xxxx kernel: [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-82175/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-115171/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-8064/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-83263/96] [sys_fsync+92/140] [system_call+51/56] Sep 11 17:05:49 xxxx kernel: [] [] [] [] [] [] Sep 11 17:05:49 xxxx kernel: Sep 11 17:05:49 xxxx kernel: Code: 0f 0b 83 c4 0c 83 c5 04 46 3b 74 24 30 7c b0 8b 4c 24 2c f6 Sep 11 17:06:18 xxxx kernel: kernel BUG at ll_rw_blk.c:692! Sep 11 17:06:18 xxxx kernel: invalid operand: 0000 Sep 11 17:06:18 xxxx kernel: CPU: 1 Sep 11 17:06:18 xxxx kernel: EIP: 0010:[__make_request+180/1968] Sep 11 17:06:18 xxxx kernel: EIP: 0010:[] Sep 11 17:06:18 xxxx kernel: EFLAGS: 00010282 Sep 11 17:06:18 xxxx kernel: eax: 0000001f ebx: eaa97c60 ecx: 00000002 edx: 00000004 Sep 11 17:06:18 xxxx kernel: esi: 00002000 edi: 00004000 ebp: ca13b218 esp: ca19be80 Sep 11 17:06:18 xxxx kernel: ds: 0018 es: 0018 ss: 0018 Sep 11 17:06:18 xxxx kernel: Process kupdated (pid: 14, stackpage=ca19b000) Sep 11 17:06:18 xxxx kernel: Stack: c022d850 c022db02 000002b4 00000008 eaa97c60 031d9000 00000000 ca115a80 Sep 11 17:06:18 xxxx kernel: 00000001 00000008 ca14b370 ca14b200 f7137000 00000000 00004000 ca13b248 Sep 11 17:06:18 xxxx kernel: ca116620 0841b240 002007d0 00000000 00000000 002007d0 00000202 c017f2c0 Sep 11 17:06:18 xxxx kernel: Call Trace: [generic_make_request+176/272] [submit_bh+88/116] [write_locked_buffers+30/40] [write_some_buffers+202/308] [sync_old_buffers+112/168] Sep 11 17:06:18 xxxx kernel: Call Trace: [] [] [] [] [] Sep 11 17:06:18 xxxx kernel: [kupdate+309/316] [stext+0/100] [kernel_thread+26/48] [kernel_thread+35/48] Sep 11 17:06:18 xxxx kernel: [] [] [] [] Sep 11 17:06:18 xxxx kernel: Sep 11 17:06:18 xxxx kernel: Code: 0f 0b 83 c4 0c 8d b4 26 00 00 00 00 8b 74 24 5c 56 8b 7c 24 --------------A5CC3E3436BC8930A0E5310D Content-Type: text/plain; charset=us-ascii; name="bug.2" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="bug.2" Sep 18 18:04:24 xxxx kernel: Bad write on page 0xc1fcfff0 Sep 18 18:04:24 xxxx kernel: Warning: buffer 0xf2404720 with weird blockno (0) Sep 18 18:04:24 xxxx kernel: Warning: buffer 0xf2404720 with weird blockno (0) Sep 18 18:04:24 xxxx kernel: kernel BUG at ll_rw_blk.c:1011! Sep 18 18:04:24 xxxx kernel: invalid operand: 0000 Sep 18 18:04:24 xxxx kernel: CPU: 3 Sep 18 18:04:24 xxxx kernel: EIP: 0010:[ll_rw_block+141/540] Sep 18 18:04:24 xxxx kernel: EIP: 0010:[] Sep 18 18:04:24 xxxx kernel: EFLAGS: 00010286 Sep 18 18:04:24 xxxx kernel: eax: 00000020 ebx: 00003a04 ecx: 00000001 edx: 00000001 Sep 18 18:04:24 xxxx kernel: esi: 00000000 edi: 00000200 ebp: d6bf3d44 esp: d6bf3cec Sep 18 18:04:24 xxxx kernel: ds: 0018 es: 0018 ss: 0018 Sep 18 18:04:24 xxxx kernel: Process procmail (pid: 12614, stackpage=d6bf3000) Sep 18 18:04:24 xxxx kernel: Stack: c022d850 c022db02 000003f3 f4f5bbd8 f2404720 d6bf3d60 00000000 f2404720 Sep 18 18:04:24 xxxx kernel: 4e4d4c4b 5251504f 56555453 5a595857 00001000 c0137764 00000001 00000001 Sep 18 18:04:24 xxxx kernel: d6bf3d44 f4f5bbc0 ec8ac614 ec8ac5fc 00000001 d6bf3d60 f2404720 34373230 Sep 18 18:04:24 xxxx kernel: Call Trace: [fsync_inode_buffers+176/396] [scrup+107/260] [lf+47/92] [vt_console_print+728/752] [printk+417/432] Sep 18 18:04:24 xxxx kernel: Call Trace: [] [] [] [] [] Sep 18 18:04:24 xxxx kernel: [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-525593/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-517888/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-525561/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-524566/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-522417/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-522112/96] Sep 18 18:04:24 xxxx kernel: [] [] [] [] [] [] Sep 18 18:04:24 xxxx kernel: [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-121076/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-135678/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-221589/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-96284/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-63804/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-529609/96] Sep 18 18:04:24 xxxx kernel: [] [] [] [] [] [] Sep 18 18:04:24 xxxx kernel: [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-8064/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-82175/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-115171/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-8064/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9-xfs/kernel/drivers/net/3+-83263/96] [sys_fsync+92/140] Sep 18 18:04:24 xxxx kernel: [] [] [] [] [] [] Sep 18 18:04:24 xxxx kernel: [system_call+51/56] Sep 18 18:04:24 xxxx kernel: [] Sep 18 18:04:24 xxxx kernel: Sep 18 18:04:24 xxxx kernel: Code: 0f 0b 83 c4 0c 83 c5 04 46 3b 74 24 30 7c b0 8b 4c 24 2c f6 Sep 18 18:04:29 xxxx kernel: kernel BUG at ll_rw_blk.c:692! Sep 18 18:04:29 xxxx kernel: invalid operand: 0000 Sep 18 18:04:29 xxxx kernel: CPU: 6 Sep 18 18:04:29 xxxx kernel: EIP: 0010:[__make_request+180/1968] Sep 18 18:04:29 xxxx kernel: EIP: 0010:[] Sep 18 18:04:29 xxxx kernel: EFLAGS: 00010282 Sep 18 18:04:29 xxxx kernel: eax: 0000001f ebx: f2404720 ecx: 00000002 edx: 00000010 Sep 18 18:04:29 xxxx kernel: esi: 00002000 edi: 00004000 ebp: ca11ae18 esp: ca19be80 Sep 18 18:04:29 xxxx kernel: ds: 0018 es: 0018 ss: 0018 Sep 18 18:04:29 xxxx kernel: Process kupdated (pid: 14, stackpage=ca19b000) Sep 18 18:04:29 xxxx kernel: Stack: c022d850 c022db02 000002b4 00000008 f2404720 031d9000 00000000 ca1196c0 Sep 18 18:04:29 xxxx kernel: 00000001 00000008 f7144970 f7144800 f70a0000 00000000 00004000 ca11ae48 Sep 18 18:04:29 xxxx kernel: ca1189e0 0841ae40 002007d0 00000000 00000000 002007d0 00000202 c017f2c0 Sep 18 18:04:29 xxxx kernel: Call Trace: [generic_make_request+176/272] [submit_bh+88/116] [write_locked_buffers+30/40] [write_some_buffers+290/308] [sync_old_buffers+112/168] Sep 18 18:04:29 xxxx kernel: Call Trace: [] [] [] [] [] Sep 18 18:04:29 xxxx kernel: [kupdate+309/316] [stext+0/100] [kernel_thread+26/48] [kernel_thread+35/48] Sep 18 18:04:29 xxxx kernel: [] [] [] [] Sep 18 18:04:29 xxxx kernel: Sep 18 18:04:29 xxxx kernel: Code: 0f 0b 83 c4 0c 8d b4 26 00 00 00 00 8b 74 24 5c 56 8b 7c 24 --------------A5CC3E3436BC8930A0E5310D-- From owner-linux-xfs@oss.sgi.com Thu Sep 20 06:44:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KDirD23061 for linux-xfs-outgoing; Thu, 20 Sep 2001 06:44:53 -0700 Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KDioe23042 for ; Thu, 20 Sep 2001 06:44:50 -0700 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.11.6/8.11.6) with ESMTP id f8KDilm15250; Thu, 20 Sep 2001 09:44:47 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Thu, 20 Sep 2001 09:44:47 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: To: Paul Arendsen cc: Subject: Re: XFS in kernel In-Reply-To: <3BA9A62D.84376F17@nlr.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 20 Sep 2001 at 10:17am, Paul Arendsen wrote > What is keep you from including XFS in the kernel itself. > Reiserfs is included and ext3 is on its way. > http://oss.sgi.com/projects/xfs/faq.html#linuskernel -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From owner-linux-xfs@oss.sgi.com Thu Sep 20 07:45:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KEjP324694 for linux-xfs-outgoing; Thu, 20 Sep 2001 07:45:25 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KEjKe24675 for ; Thu, 20 Sep 2001 07:45:20 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id HAA01736 for ; Thu, 20 Sep 2001 07:43:59 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2981822; Thu, 20 Sep 2001 09:44:00 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA59062; Thu, 20 Sep 2001 09:44:00 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8KEj7i14848; Thu, 20 Sep 2001 09:45:07 -0500 Message-Id: <200109201445.f8KEj7i14848@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Paul Arendsen cc: linux-xfs@oss.sgi.com Subject: Re: XFS in kernel In-Reply-To: Message from Paul Arendsen of "Thu, 20 Sep 2001 10:17:50 +0200." <3BA9A62D.84376F17@nlr.nl> Date: Thu, 20 Sep 2001 09:45:07 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi Guys > > What is keep you from including XFS in the kernel itself. > Reiserfs is included and ext3 is on its way. It is not a what it is a who, called Linus. Hans Reiser mounted a major campaign over several months to get into the kernel, and it took a while after that to get the bugs out. There are mumblings about ext3, but it does make quite a lot of mainline kernel changes I am told, so I would not be so sure - except for the fact that Redhat appears to be going to make it their default filesystem. As for us, there have been efforts, which met with zero response from Linus to get XFS into the kernel. Various folks then told us - wait for 2.5 and then backport from there. In the meantime I have about 3 million other things to do at the moment which are not even to do with Linux, and do not have the time to continually bombard Linus with patches. One other reason XFS is harder to get in is that we have some code in the middle of the VM system to deal with delayed allocate pages, and if you follow Linux kernel development you will realize that the VM has been rewritten several times over the last few months, it is not the most stable thing in the world. Item 3 million and one on my list right now is getting the latest VM rewrite and XFS to talk to each other (no it is not bottom of the list, but you try doing major surgery on two operating systems at once and staying sane). At the moment an effort is under way to merge the XFS acl interface with the ext2 acl interface so we can get a system call - Linus will not accept more than one interface in this area. Once this is done then our intrusions into the mainline kernel will be smaller and we can try again. This will also make it easier for distributions to include XFS - we appear to be in the latest Mandrake release by the way. Steve > > I use SuSE at home and RedHat-with-XFS at the office and > I would like to use XFS and SuSE. Since including stuff > in the kernel is essential for long term (I do not want > the hassle echa time I update my distribution) > > Paul > > -- > > ------------------------------------------------------------------ > > From: Paul Arendsen > > Address: National Aerospace Lab. E-Mail - arends@nlr.nl > Voorsterweg 31 > 8316 PR Marknesse Phone (+31)527 - 248675 > (The Netherlands) telefax (+31)527 - 248210 > > ------------------------------------------------------------------ From owner-linux-xfs@oss.sgi.com Thu Sep 20 07:58:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KEwib25090 for linux-xfs-outgoing; Thu, 20 Sep 2001 07:58:44 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KEwge25071 for ; Thu, 20 Sep 2001 07:58:42 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8KEwal17828 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Thu, 20 Sep 2001 07:58:36 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA904302 for ; Thu, 20 Sep 2001 16:58:33 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA3022315; Thu, 20 Sep 2001 09:57:17 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA04998; Thu, 20 Sep 2001 09:57:14 -0500 (CDT) Message-ID: <3BAA0391.CF9BE02C@sgi.com> Date: Thu, 20 Sep 2001 09:56:17 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: "Drew 'Cheetah!' Maxwell" CC: linux-xfs@oss.sgi.com Subject: Re: Use of SGI-XFS-1.0.1 with RAID... References: <3BA9089C.3E3C605@clubphoto.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Drew 'Cheetah!' Maxwell" wrote: > mountList > if fsType == "swap": continue > NameError: fsType Please use the update disks to fix this bug. There have also been reports that kickstart+raid has some problems; if you run into this, you may need to install by hand. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Sep 20 08:19:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KFJUE25744 for linux-xfs-outgoing; Thu, 20 Sep 2001 08:19:30 -0700 Received: from mail.microdiscovery.de (postfix@gap.microdiscovery.de [195.143.236.170]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KFJQe25725 for ; Thu, 20 Sep 2001 08:19:27 -0700 Message-ID: <3BAA08FB.3080204@microdiscovery.de> Date: Thu, 20 Sep 2001 17:19:23 +0200 From: Bartosch Pixa Organization: MicroDiscovery User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010918 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: question: xfs + lvm + kernel 2.4.9 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, i'm trying to get a kernel 2.4.9 working with XFS and LVM 1.0.1-rc2, i got some errors after aplying the XFS patch (linux-2.4.9-xfs-2001-08-26.patch) to a already LVM patched kernel, the errors were only in the LVM parts of the kernel, so my question is now if it's sane to ignore these errors or if there are issues with XFS and LVM. thx in advance Bartosch Pixa -- Bartosch Pixa, bartosch.pixa@microdiscovery.de MicroDiscovery GmbH Immanuelkirchstr. 12, D-10405 Berlin, Germany Tel.: +49-(0)30-44350900, Fax: +49-(0)30-443509010 From owner-linux-xfs@oss.sgi.com Thu Sep 20 08:54:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KFsYi26656 for linux-xfs-outgoing; Thu, 20 Sep 2001 08:54:34 -0700 Received: from ntserv1.vytalnet.com (vytalnet.com [209.121.88.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KFsLe26629 for ; Thu, 20 Sep 2001 08:54:22 -0700 Received: from pcminy ([209.121.88.254]) by ntserv1.vytalnet.com (Post.Office MTA v3.5.3 release 223 ID# 0-54530U100L2S100V35) with SMTP id com for ; Thu, 20 Sep 2001 11:54:10 -0400 Message-ID: <02af01c141ec$db39cc50$4201a8c0@vytalnet.com> From: Min.Yuan@VytalNet.com (Min Yuan) To: Subject: readdir() problem when using -D_FILE_OFFSET_BITS=64 in gcc Date: Thu, 20 Sep 2001 11:56:42 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_02AC_01C141CB.507F6FA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_02AC_01C141CB.507F6FA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Redhat7.1 supports large file(>2GB), but you have to add = -D_FILE_OFFSET_BITS=3D64 to gcc =20 The following is a very simple program: #include #include #include int main() { DIR *dr; struct dirent *dent; dr =3D opendir("/var/run"); while ((dent =3D readdir(dr)) !=3D NULL) { printf("inode:%d and d_name:%s\n", dent->d_ino, dent->d_name); } return 0; } if it is compiled without -D_FILE_OFFSET_BITS=3D64, readdir() works = fine. ./a.out inode:293788 and d_name:. inode:97921 and d_name:.. inode:881483 and d_name:netreport inode:294131 and d_name:utmp inode:392276 and d_name:news inode:115000 and d_name:named inode:115290 and d_name:sudo inode:1355948 and d_name:mysqld inode:115698 and d_name:pvm3 inode:296305 and d_name:runlevel.dir inode:296306 and d_name:syslogd.pid inode:296307 and d_name:klogd.pid inode:296308 and d_name:apmd.pid inode:296309 and d_name:atd.pid inode:296310 and d_name:sshd.pid inode:296311 and d_name:xinetd.pid inode:296312 and d_name:sendmail.pid inode:296314 and d_name:crond.pid inode:296313 and d_name:gpm.pid inode:296315 and d_name:xfs.pid inode:296316 and d_name:gdm.pid But if it is compiled with -D_FILE_OFFSET_BITS=3D64, then readdir() has = problem in getting file name. ./a.out inode:293788 and d_name:(null) inode:97921 and d_name:(null) inode:881483 and d_name:(null) inode:294131 and d_name:(null) inode:392276 and d_name:(null) inode:115000 and d_name:(null) inode:115290 and d_name:(null) inode:1355948 and d_name:(null) inode:115698 and d_name:(null) inode:296305 and d_name:(null) inode:296306 and d_name:(null) inode:296307 and d_name:(null) inode:296308 and d_name:(null) inode:296309 and d_name:(null) inode:296310 and d_name:(null) inode:296311 and d_name:(null) inode:296312 and d_name:(null) inode:296314 and d_name:(null) inode:296313 and d_name:(null) inode:296315 and d_name:(null) inode:296316 and d_name:(null) WHY? Is there any way to solve it? Min Yuan=20 ------=_NextPart_000_02AC_01C141CB.507F6FA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Redhat7.1 supports large file(>2GB), = but you=20 have to add -D_FILE_OFFSET_BITS=3D64 to gcc
 
The following is a very simple=20 program:
 
#include = <sys/types.h>
#include=20 <stdio.h>
#include <dirent.h>
 
int main() {
DIR *dr;
struct = dirent=20 *dent;
dr =3D opendir("/var/run");
while ((dent =3D readdir(dr)) = !=3D NULL)=20 {
 printf("inode:%d and d_name:%s\n", dent->d_ino,=20 dent->d_name);
}
return 0;
}
 
if it is compiled without=20 -D_FILE_OFFSET_BITS=3D64, readdir() works fine.
./a.out
inode:293788 and = d_name:.
inode:97921 and=20 d_name:..
inode:881483 and d_name:netreport
inode:294131 and=20 d_name:utmp
inode:392276 and d_name:news
inode:115000 and=20 d_name:named
inode:115290 and d_name:sudo
inode:1355948 and=20 d_name:mysqld
inode:115698 and d_name:pvm3
inode:296305 and=20 d_name:runlevel.dir
inode:296306 and = d_name:syslogd.pid
inode:296307 and=20 d_name:klogd.pid
inode:296308 and d_name:apmd.pid
inode:296309 and = d_name:atd.pid
inode:296310 and d_name:sshd.pid
inode:296311 and=20 d_name:xinetd.pid
inode:296312 and = d_name:sendmail.pid
inode:296314 and=20 d_name:crond.pid
inode:296313 and d_name:gpm.pid
inode:296315 and=20 d_name:xfs.pid
inode:296316 and d_name:gdm.pid
 
But if it is compiled = with=20 -D_FILE_OFFSET_BITS=3D64, then readdir() has problem in getting file=20 name.
./a.out
inode:293788 and = d_name:(null)
inode:97921 and=20 d_name:(null)
inode:881483 and d_name:(null)
inode:294131 and=20 d_name:(null)
inode:392276 and d_name:(null)
inode:115000 and=20 d_name:(null)
inode:115290 and d_name:(null)
inode:1355948 and=20 d_name:(null)
inode:115698 and d_name:(null)
inode:296305 and=20 d_name:(null)
inode:296306 and d_name:(null)
inode:296307 and=20 d_name:(null)
inode:296308 and d_name:(null)
inode:296309 and=20 d_name:(null)
inode:296310 and d_name:(null)
inode:296311 and=20 d_name:(null)
inode:296312 and d_name:(null)
inode:296314 and=20 d_name:(null)
inode:296313 and d_name:(null)
inode:296315 and=20 d_name:(null)
inode:296316 and d_name:(null)
 
WHY? Is there any way to solve = it?

 
Min Yuan =
------=_NextPart_000_02AC_01C141CB.507F6FA0-- From owner-linux-xfs@oss.sgi.com Thu Sep 20 09:18:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KGIKJ27316 for linux-xfs-outgoing; Thu, 20 Sep 2001 09:18:20 -0700 Received: from legba.tvnet.hu (legba.tvnet.hu [195.38.96.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KGIHe27297 for ; Thu, 20 Sep 2001 09:18:17 -0700 Received: from dumballah.tvnet.hu (zeus.city.tvnet.hu [195.38.100.182]) by legba.tvnet.hu (8.9.3+Sun/8.9.3) with ESMTP id SAA06644 for ; Thu, 20 Sep 2001 18:18:14 +0200 (MEST) Message-ID: <3BAA1687.8040905@dumballah.tvnet.hu> Date: Thu, 20 Sep 2001 18:17:11 +0200 From: Sipos Ferenc User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010917 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: offtopic: supermount patch Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi! Does someone know of the supermount patch for 2.4.10-pre10-xfs kernels? I've found only for 2.4.0, and thing has changed a bit since then. Any information, when will it be in the mainstream kernel or in the sgi cvs xfs kernel?Thx for your help. Paco From owner-linux-xfs@oss.sgi.com Thu Sep 20 09:22:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KGM3U27488 for linux-xfs-outgoing; Thu, 20 Sep 2001 09:22:03 -0700 Received: from ntserv1.vytalnet.com (com.vytalnet.com [209.121.88.10] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KGLoe27469 for ; Thu, 20 Sep 2001 09:21:50 -0700 Received: from pcminy ([209.121.88.254]) by ntserv1.vytalnet.com (Post.Office MTA v3.5.3 release 223 ID# 0-54530U100L2S100V35) with SMTP id com for ; Thu, 20 Sep 2001 12:21:42 -0400 Message-ID: <02c601c141f0$b3f07000$4201a8c0@vytalnet.com> From: Min.Yuan@VytalNet.com (Min Yuan) To: Subject: readdir() problem when using -D_FILE_OFFSET_BITS=64 in gcc Date: Thu, 20 Sep 2001 12:24:15 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_02C3_01C141CF.29BE2F10" X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_02C3_01C141CF.29BE2F10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Redhat7.1 supports large file(>2GB), but you have to add = -D_FILE_OFFSET_BITS=3D64 to gcc =20 The following is a very simple program: #include #include #include int main() { DIR *dr; struct dirent *dent; dr =3D opendir("/var/run"); while ((dent =3D readdir(dr)) !=3D NULL) { printf("inode:%d and d_name:%s\n", dent->d_ino, dent->d_name); } return 0; } if it is compiled without -D_FILE_OFFSET_BITS=3D64, readdir() works = fine. ./a.out inode:293788 and d_name:. inode:97921 and d_name:.. inode:881483 and d_name:netreport inode:294131 and d_name:utmp inode:392276 and d_name:news inode:115000 and d_name:named inode:115290 and d_name:sudo inode:1355948 and d_name:mysqld inode:115698 and d_name:pvm3 inode:296305 and d_name:runlevel.dir inode:296306 and d_name:syslogd.pid inode:296307 and d_name:klogd.pid inode:296308 and d_name:apmd.pid inode:296309 and d_name:atd.pid inode:296310 and d_name:sshd.pid inode:296311 and d_name:xinetd.pid inode:296312 and d_name:sendmail.pid inode:296314 and d_name:crond.pid inode:296313 and d_name:gpm.pid inode:296315 and d_name:xfs.pid inode:296316 and d_name:gdm.pid But if it is compiled with -D_FILE_OFFSET_BITS=3D64, then readdir() has = problem in getting file name. ./a.out inode:293788 and d_name:(null) inode:97921 and d_name:(null) inode:881483 and d_name:(null) inode:294131 and d_name:(null) inode:392276 and d_name:(null) inode:115000 and d_name:(null) inode:115290 and d_name:(null) inode:1355948 and d_name:(null) inode:115698 and d_name:(null) inode:296305 and d_name:(null) inode:296306 and d_name:(null) inode:296307 and d_name:(null) inode:296308 and d_name:(null) inode:296309 and d_name:(null) inode:296310 and d_name:(null) inode:296311 and d_name:(null) inode:296312 and d_name:(null) inode:296314 and d_name:(null) inode:296313 and d_name:(null) inode:296315 and d_name:(null) inode:296316 and d_name:(null) WHY? Is there any way to solve it? =20 Min Yuan=20 ------=_NextPart_000_02C3_01C141CF.29BE2F10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Redhat7.1 supports large file(>2GB), = but you=20 have to add -D_FILE_OFFSET_BITS=3D64 to gcc
 
The following is a very simple=20 program:
 
#include = <sys/types.h>
#include=20 <stdio.h>
#include <dirent.h>
 
int main() {
DIR *dr;
struct = dirent=20 *dent;
dr =3D opendir("/var/run");
while ((dent =3D readdir(dr)) = !=3D NULL)=20 {
 printf("inode:%d and d_name:%s\n", dent->d_ino,=20 dent->d_name);
}
return 0;
}
 
if it is compiled without=20 -D_FILE_OFFSET_BITS=3D64, readdir() works fine.
./a.out
inode:293788 and = d_name:.
inode:97921 and=20 d_name:..
inode:881483 and d_name:netreport
inode:294131 and=20 d_name:utmp
inode:392276 and d_name:news
inode:115000 and=20 d_name:named
inode:115290 and d_name:sudo
inode:1355948 and=20 d_name:mysqld
inode:115698 and d_name:pvm3
inode:296305 and=20 d_name:runlevel.dir
inode:296306 and = d_name:syslogd.pid
inode:296307 and=20 d_name:klogd.pid
inode:296308 and d_name:apmd.pid
inode:296309 and = d_name:atd.pid
inode:296310 and d_name:sshd.pid
inode:296311 and=20 d_name:xinetd.pid
inode:296312 and = d_name:sendmail.pid
inode:296314 and=20 d_name:crond.pid
inode:296313 and d_name:gpm.pid
inode:296315 and=20 d_name:xfs.pid
inode:296316 and d_name:gdm.pid
 
But if it is compiled = with=20 -D_FILE_OFFSET_BITS=3D64, then readdir() has problem in getting file=20 name.
./a.out
inode:293788 and = d_name:(null)
inode:97921 and=20 d_name:(null)
inode:881483 and d_name:(null)
inode:294131 and=20 d_name:(null)
inode:392276 and d_name:(null)
inode:115000 and=20 d_name:(null)
inode:115290 and d_name:(null)
inode:1355948 and=20 d_name:(null)
inode:115698 and d_name:(null)
inode:296305 and=20 d_name:(null)
inode:296306 and d_name:(null)
inode:296307 and=20 d_name:(null)
inode:296308 and d_name:(null)
inode:296309 and=20 d_name:(null)
inode:296310 and d_name:(null)
inode:296311 and=20 d_name:(null)
inode:296312 and d_name:(null)
inode:296314 and=20 d_name:(null)
inode:296313 and d_name:(null)
inode:296315 and=20 d_name:(null)
inode:296316 and d_name:(null)
 
WHY? Is there any way to solve = it?

 
Min Yuan=20
------=_NextPart_000_02C3_01C141CF.29BE2F10-- From owner-linux-xfs@oss.sgi.com Thu Sep 20 09:34:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KGY6M27804 for linux-xfs-outgoing; Thu, 20 Sep 2001 09:34:06 -0700 Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KGY3e27785 for ; Thu, 20 Sep 2001 09:34:03 -0700 Received: from scare ([63.231.179.33]) by lips.thebarn.com (8.12.0/8.12.0) with ESMTP id f8KGY8RP017915; Thu, 20 Sep 2001 11:34:09 -0500 (CDT) Subject: Re: offtopic: supermount patch From: Russell Cattelan To: Sipos Ferenc Cc: linux-xfs@oss.sgi.com In-Reply-To: <3BAA1687.8040905@dumballah.tvnet.hu> References: <3BAA1687.8040905@dumballah.tvnet.hu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 20 Sep 2001 11:33:57 -0500 Message-Id: <1001003638.12784.15.camel@scare> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 2001-09-20 at 11:17, Sipos Ferenc wrote: > Hi! > > Does someone know of the supermount patch for 2.4.10-pre10-xfs kernels? > I've found only for 2.4.0, and thing has changed a bit since then. Any > information, when will it be in the mainstream kernel or in the sgi cvs > xfs kernel?Thx for your help. > > Paco The latest mandrake kernel has a new rewritten supermount... try starting there. -Russell From owner-linux-xfs@oss.sgi.com Thu Sep 20 09:45:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KGjKn28115 for linux-xfs-outgoing; Thu, 20 Sep 2001 09:45:20 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KGjHe28096 for ; Thu, 20 Sep 2001 09:45:17 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8KGjBj28028 for ; Thu, 20 Sep 2001 09:45:12 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA3011185; Thu, 20 Sep 2001 11:43:55 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA16515; Thu, 20 Sep 2001 11:43:54 -0500 (CDT) Message-ID: <3BAA1C91.31E8B65D@sgi.com> Date: Thu, 20 Sep 2001 11:42:57 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: "Saunders, Andrew (Magma-da/Reading-UK)" CC: "'linux-xfs@oss.sgi.com'" , "Ronny Adsetts (E-mail)" Subject: Re: Bad write page, under 2.4.9 kernel References: <414DB4427DE6D411846200B0D078E84B169DD1@uk-exch.magma-da.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Saunders, Andrew (Magma-da/Reading-UK)" wrote: > Sep 20 10:00:14 thor kernel: Bad write on page 0xc1822a30 The short, but perhaps unsatisfying answer is that you can probably just ignore this error. The code in pagebuf_write_full_page that generates it is identical to the code in buffer.c:block_write_full_page - except block_write_full_page doesn't print an error. This looks like it's just a case of XFS being too noisy. I'll look at it a bit more, but in the end we'll probably just remove the warning message. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Sep 20 10:02:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KH2Xd28500 for linux-xfs-outgoing; Thu, 20 Sep 2001 10:02:33 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KH2Te28477 for ; Thu, 20 Sep 2001 10:02:30 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15k7DY-0001Qp-00; Thu, 20 Sep 2001 13:02:28 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f8KH2PW04946; Thu, 20 Sep 2001 13:02:25 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Bartosch Pixa Cc: linux-xfs@oss.sgi.com Subject: Re: question: xfs + lvm + kernel 2.4.9 References: <3BAA08FB.3080204@microdiscovery.de> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 20 Sep 2001 13:02:25 -0400 In-Reply-To: <3BAA08FB.3080204@microdiscovery.de> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Bartosch" == Bartosch Pixa writes: Bartosch> i'm trying to get a kernel 2.4.9 working with XFS and LVM Bartosch> 1.0.1-rc2, i got some errors after aplying the XFS patch Bartosch> (linux-2.4.9-xfs-2001-08-26.patch) to a already LVM patched Bartosch> kernel, the errors were only in the LVM parts of the kernel, Bartosch> so my question is now if it's sane to ignore these errors or Bartosch> if there are issues with XFS and LVM. 1.0.1-rc3 should be out next week. I would recommend you hold off until then. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Thu Sep 20 11:03:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KI3jF29853 for linux-xfs-outgoing; Thu, 20 Sep 2001 11:03:45 -0700 Received: from aquila.nns.ch (aquila.nns.ch [62.32.16.77]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KI3ee29834 for ; Thu, 20 Sep 2001 11:03:40 -0700 Received: by aquila.nns.ch (Postfix, from userid 1000) id 50601C03362; Thu, 20 Sep 2001 20:03:39 +0200 (CEST) Date: Thu, 20 Sep 2001 20:03:39 +0200 From: Jade Nicoletti To: linux-xfs@oss.sgi.com Subject: kernel update? Message-ID: <20010920200339.A12574@aquila.nns.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.20i Organization: Nicoletti Net Services X-URL: http://nns.ch/ Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi I'm running linux 2.4.7-pre6-xfs on a production server. It's a debian potato installation with some self compiled packages from sid to get all the kernel dependences fulfilled. I used gcc 2.95.2 to compile the kernel (and all other stuff). Everything works fine and I'd like to thank you for your work. The system is now up for over two monthes and I have never had any problems. XFS is a great filesystem :) Now, I have to add more RAM to the server. And as I have to reboot the machine for that, I thought I probably should update the kernel too. What do you guys recommend? 1) No kernel update 2) Go with patches/linux-2.4.9-xfs-2001-08-26.patch.bz2 3) Wait for linux-2.4.10 and the corresponding patch For the last option I would have to build the kernel on an other system because 2.4.10 needs at least gcc 2.95.3 and I don't want do update the compiler (or any other important system packages apart from the kernel) on the production server. Thank you. -Jade. -- =============================================================================== Jade Nicoletti Nicoletti Net Services Tel. 01 240 4774 Geschäftsleitung Postfach 2519 Fax 01 240 4775 System-Administration 8021 Zürich ============================================[ Weitere Infos: http://nns.ch/ ]== From owner-linux-xfs@oss.sgi.com Thu Sep 20 11:16:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KIGds30204 for linux-xfs-outgoing; Thu, 20 Sep 2001 11:16:39 -0700 Received: from Milos.fw.matav.hu (firewall-user@matav-3.matav.hu [145.236.252.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KIGYe30181 for ; Thu, 20 Sep 2001 11:16:34 -0700 Received: by matav-1.matav.hu with smtp; Thu, 20 Sep 2001 20:16:32 +0200 Received: from helka (helka [127.0.0.1]) by helka.tii.matav.hu (Postfix) with ESMTP id 59CFD2D; Thu, 20 Sep 2001 20:12:51 +0200 (CEST) Date: Thu, 20 Sep 2001 20:12:48 +0200 (CEST) From: Narancs v1 X-X-Sender: To: Cc: Subject: XFS to main kernel source Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! First of all, I want to thank you the great job you do to Linux! Linux is a great OS/kernel and XFS is my favorite FS since I tried it. Problems: When will be the XFS patch integrated to main tree? I'm really fed up with trying to get linux-2.4.9 + acXX or preXX + xfs together. I'm using XFS from notebooks to DB servers and it's really hard to compile a good and fresh kernel. Now I currently have some machines like 2.4.10-pre-xfs and so on. I want to have some features from -ac tree and/or the latest pre kernels, but patching fails, I have to do things by hand with the .rej files, and I can make mistakes so I have a kernel in the notebook which handles the ps/2 mouse in X very bad (the cursor jumps on big use I/O or CPU, maybe sy with the interrupts is wrong.) I know it takes time and resources, but if once XFS is in the main tree as Reiser is in (maybe other folks wants ext3 to get in too) - this problem will be eleminated, and I could use ie. the usb/SCSI module hp scanner with xfs and dvd playback too. thanks ------------------------- Narancs v1 IT Security Administrator "Security of information is an illusion. What is in one's mind gets into the collective consciousness (akasha), so that can be read with meditation ;-) You don't have to hack. Just 'remember'! You're the one." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjuqMaMACgkQGp+ylEhMCIU1ywCfT1PRsEKeULNyptmQqMawsY9Q d3AAnAzHagKVkiX1JPjfebuIUicC+Mr/ =kvPu -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Thu Sep 20 11:20:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KIKKZ30418 for linux-xfs-outgoing; Thu, 20 Sep 2001 11:20:20 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KIKFe30398 for ; Thu, 20 Sep 2001 11:20:16 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id LAA25314 for ; Thu, 20 Sep 2001 11:20:18 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA3015069; Thu, 20 Sep 2001 13:18:53 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA49387; Thu, 20 Sep 2001 13:18:52 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8KIJw715359; Thu, 20 Sep 2001 13:19:58 -0500 Message-Id: <200109201819.f8KIJw715359@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jade Nicoletti cc: linux-xfs@oss.sgi.com Subject: Re: kernel update? In-Reply-To: Message from Jade Nicoletti of "Thu, 20 Sep 2001 20:03:39 +0200." <20010920200339.A12574@aquila.nns.ch> Content-Transfer-Encoding: 8bit Date: Thu, 20 Sep 2001 13:19:58 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi > > I'm running linux 2.4.7-pre6-xfs on a production server. It's a debian potato > installation with some self compiled packages from sid to get all the kernel > dependences fulfilled. I used gcc 2.95.2 to compile the kernel (and all other > stuff). > > Everything works fine and I'd like to thank you for your work. The system is > now up for over two monthes and I have never had any problems. XFS is a great > filesystem :) > > Now, I have to add more RAM to the server. And as I have to reboot the machin > e > for that, I thought I probably should update the kernel too. > > What do you guys recommend? > > 1) No kernel update > 2) Go with patches/linux-2.4.9-xfs-2001-08-26.patch.bz2 > 3) Wait for linux-2.4.10 and the corresponding patch I would hold off on 2.4.10 - there have been some major kernel changes which will affect XFS, it may take a while to shake out the bugs. The 2.4.9 version appears to be running OK. I would see if you get any other feedback from the list about this, you should also ask yourself if you should change a working combination. If you have had no problems with the kernel you have been running and do not need to update for some specific bug fix then the least risky option is to stay with this version, you should certainly keep it available as a fallback option. > > For the last option I would have to build the kernel on an other system > because 2.4.10 needs at least gcc 2.95.3 and I don't want do update the > compiler (or any other important system packages apart from the kernel) on > the production server. > I have managed to build the latest pre kernel using kgcc which is egcs-2.91.66 so this may no longer be true. > Thank you. > > -Jade. > Steve From owner-linux-xfs@oss.sgi.com Thu Sep 20 11:24:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KIOCa30617 for linux-xfs-outgoing; Thu, 20 Sep 2001 11:24:12 -0700 Received: from codon.com (www.stampercentral.com [64.78.130.125]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KIO9e30598 for ; Thu, 20 Sep 2001 11:24:09 -0700 Received: (qmail 17628 invoked by uid 516); 20 Sep 2001 18:42:09 -0000 Received: from nw@codon.com by helix with qmail-scanner-0.96 (. Clean. Processed in 0.042334 secs); 20 Sep 2001 18:42:09 -0000 Received: from weasel.local.iboats.com (HELO weasel) (64.78.130.80) by codon.com with SMTP; 20 Sep 2001 18:42:09 -0000 Message-ID: <003601c14200$77893b00$50824e40@iboats.com> From: "Steve Wolfe" To: References: Subject: Re: XFS to main kernel source Date: Thu, 20 Sep 2001 12:17:10 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > When will be the XFS patch integrated to main tree? (snip) >> I'm really fed up with trying to get linux-2.4.9 + acXX or preXX + xfs >> together. (snip) >>> I would hold off on 2.4.10 - there have been some major kernel changes >>> which will affect XFS, it may take a while to shake out the bugs. The 2.4.9 >>> version appears to be running OK. I would see if you get any other feedback I'd just like to add, for the record, that while I really do love XFS, because of things like the above statement from Steve Lord, I really can't use it on my production machines until it is tied into the regular kernel tree. I imagine that you're already doing everything that you can to get it integrated, I'm not griping, just giving (hopefully) constructive feedback. steve From owner-linux-xfs@oss.sgi.com Thu Sep 20 11:31:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KIVYS30860 for linux-xfs-outgoing; Thu, 20 Sep 2001 11:31:34 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KIVUe30841 for ; Thu, 20 Sep 2001 11:31:30 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA04383 for ; Thu, 20 Sep 2001 11:30:10 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA3019097; Thu, 20 Sep 2001 13:30:13 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA19171; Thu, 20 Sep 2001 13:30:13 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8KIVIk18442; Thu, 20 Sep 2001 13:31:18 -0500 Message-Id: <200109201831.f8KIVIk18442@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Steve Wolfe" cc: linux-xfs@oss.sgi.com Subject: Re: XFS to main kernel source In-Reply-To: Message from "Steve Wolfe" of "Thu, 20 Sep 2001 12:17:10 MDT." <003601c14200$77893b00$50824e40@iboats.com> Date: Thu, 20 Sep 2001 13:31:18 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > When will be the XFS patch integrated to main tree? > > (snip) > > >> I'm really fed up with trying to get linux-2.4.9 + acXX or preXX + xfs > >> together. > > (snip) > > >>> I would hold off on 2.4.10 - there have been some major kernel changes > >>> which will affect XFS, it may take a while to shake out the bugs. The > 2.4.9 > >>> version appears to be running OK. I would see if you get any other > feedback > > I'd just like to add, for the record, that while I really do love XFS, > because of things like the above statement from Steve Lord, I really can't > use it on my production machines until it is tied into the regular kernel > tree. I imagine that you're already doing everything that you can to get > it integrated, I'm not griping, just giving (hopefully) constructive > feedback. Well, since the changes are being made to the Linux VM, not to XFS, if I was in your situation I would ask myself if I should be running recent 2.4 kernels in production with any filesystem. I am not convinced that being in the mainline kernel is much of a help right now. Oh, and we are not the ones who need this form of feedback ;-) Steve From owner-linux-xfs@oss.sgi.com Thu Sep 20 11:31:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KIVx930985 for linux-xfs-outgoing; Thu, 20 Sep 2001 11:31:59 -0700 Received: from antares.cedar.buffalo.edu (antares.cedar.Buffalo.EDU [128.205.33.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KIVte30958 for ; Thu, 20 Sep 2001 11:31:55 -0700 Received: (qmail 10350 invoked from network); 20 Sep 2001 18:31:54 -0000 Received: from cepheus.cedar.buffalo.edu (128.205.33.197) by antares.cedar.buffalo.edu with SMTP; 20 Sep 2001 18:31:54 -0000 Received: (from ajay@localhost) by cepheus.cedar.buffalo.edu (8.9.3/8.9.3) id OAA21716 for linux-xfs@oss.sgi.com; Thu, 20 Sep 2001 14:31:54 -0400 (EDT) Date: Thu, 20 Sep 2001 14:31:54 -0400 From: Ajay Shekhawat To: linux-xfs@oss.sgi.com Subject: Kickstart woes Message-ID: <20010920143153.A21689@cepheus.cedar.buffalo.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Center for Document Analysis and Recognition X-OfficePhone: +1 (716)-645-6164 ext. 101 X-Fax-Number: +1 (716)-645-6176 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm trying to do a kickstart installation using the "bootnet" image from the XFS 1.0.1 distribution (RH7.1 + XFS). My ks.cfg file looks like this: zerombr yes clearpart --all part / --size 2048 --fs xfs part /boot --size 32 --fs xfs part /tmp --size 1024 --fs xfs part /var --size 512 --fs xfs part swap --size 512 --fs xfs part /local --size 1 --grow --fs xfs install After anaconda formats the partitions, it stops saying: Error mounting hda5 on /: No such device This most likely means the partition is not formatted Press OK Via alt-F3, I can see messages like Making XFS filesystem for hda5 Making XFS filesystem for hda1 Making XFS filesystem for hda6 Making XFS filesystem for hda7 In alt-F2 console, I can fdisk /tmp/hda without problems. Any ideas on whats going on? The disk is a Western Digital 40GB disk. Ajay From owner-linux-xfs@oss.sgi.com Thu Sep 20 11:32:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KIWb531107 for linux-xfs-outgoing; Thu, 20 Sep 2001 11:32:37 -0700 Received: from burgers (IDENT:postfix@burgers.bubbanfriends.org [216.140.122.113]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KIWXe31088 for ; Thu, 20 Sep 2001 11:32:33 -0700 Received: by burgers (Postfix, from userid 500) id 5A5EB4001C0; Thu, 20 Sep 2001 14:32:35 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by burgers (Postfix) with ESMTP id 52B4D240021C; Thu, 20 Sep 2001 14:32:35 -0400 (EDT) Date: Thu, 20 Sep 2001 14:32:35 -0400 (EDT) From: Mike Burger To: Steve Wolfe Cc: Subject: Re: XFS to main kernel source In-Reply-To: <003601c14200$77893b00$50824e40@iboats.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Can I ask which Linux distribution you're running? The reason I ask is that SGI, as you probably well know, has a full Red Hat setup, based currently on RH7.1. It installs wonderfully, and you can then download their current kernel builds...in RPM format, even. On Thu, 20 Sep 2001, Steve Wolfe wrote: > > When will be the XFS patch integrated to main tree? > > (snip) > > >> I'm really fed up with trying to get linux-2.4.9 + acXX or preXX + xfs > >> together. > > (snip) > > >>> I would hold off on 2.4.10 - there have been some major kernel changes > >>> which will affect XFS, it may take a while to shake out the bugs. The > 2.4.9 > >>> version appears to be running OK. I would see if you get any other > feedback > > I'd just like to add, for the record, that while I really do love XFS, > because of things like the above statement from Steve Lord, I really can't > use it on my production machines until it is tied into the regular kernel > tree. I imagine that you're already doing everything that you can to get > it integrated, I'm not griping, just giving (hopefully) constructive > feedback. > > steve > > > From owner-linux-xfs@oss.sgi.com Thu Sep 20 11:46:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KIkwv31575 for linux-xfs-outgoing; Thu, 20 Sep 2001 11:46:58 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KIkse31507 for ; Thu, 20 Sep 2001 11:46:54 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA11812; Thu, 20 Sep 2001 20:46:47 +0200 (CEST) Message-Id: <4.3.2.7.2.20010920204025.03328198@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 20 Sep 2001 20:46:13 +0200 To: Jade Nicoletti , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: kernel update? In-Reply-To: <20010920200339.A12574@aquila.nns.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 20:03 20-9-2001 +0200, Jade Nicoletti wrote: >Hi > >I'm running linux 2.4.7-pre6-xfs on a production server. It's a debian potato >installation with some self compiled packages from sid to get all the kernel >dependences fulfilled. I used gcc 2.95.2 to compile the kernel (and all other >stuff). > >Everything works fine and I'd like to thank you for your work. The system is >now up for over two monthes and I have never had any problems. XFS is a great >filesystem :) > >Now, I have to add more RAM to the server. And as I have to reboot the machine >for that, I thought I probably should update the kernel too. > >What do you guys recommend? > >1) No kernel update It it works for you don't break it. If you add ram and it starts crashing you have a good reason to start looking at the ram. Touch 1 piece at a time. >2) Go with patches/linux-2.4.9-xfs-2001-08-26.patch.bz2 This has some of the min/max issues but seems to do fine for most people. >3) Wait for linux-2.4.10 and the corresponding patch The VM is reworked as Steve said in another email and this might take a while to stabalize since XFS interacts with the VM. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Sep 20 11:47:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KIlFl31665 for linux-xfs-outgoing; Thu, 20 Sep 2001 11:47:15 -0700 Received: from imapserverb.fnal.gov (imapserverb.fnal.gov [131.225.9.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KIlBe31646 for ; Thu, 20 Sep 2001 11:47:11 -0700 Received: from imapserverb.fnal.gov ([131.225.9.17]) by imapserverb.fnal.gov (Netscape Messaging Server 4.15) with SMTP id GJZ5IN00.1OC for ; Thu, 20 Sep 2001 13:47:11 -0500 Received: from fnal.gov ([131.225.7.82]) by imapserverb.fnal.gov (NAVIEG 2.1 bld 63) with SMTP id M2001092013471030981 for ; Thu, 20 Sep 2001 13:47:10 -0500 Message-ID: <3BAA39AF.C6E42BDB@fnal.gov> Date: Thu, 20 Sep 2001 13:47:11 -0500 From: yocum@fnal.gov X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 CC: "'linux-xfs@oss.sgi.com'" Subject: Re: Bad write page, under 2.4.9 kernel References: <414DB4427DE6D411846200B0D078E84B169DD1@uk-exch.magma-da.com> <3BAA1C91.31E8B65D@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > > "Saunders, Andrew (Magma-da/Reading-UK)" wrote: > > > Sep 20 10:00:14 thor kernel: Bad write on page 0xc1822a30 > > The short, but perhaps unsatisfying answer is that you can probably just > ignore this error. The code in pagebuf_write_full_page that generates > it is identical to the code in buffer.c:block_write_full_page - except > block_write_full_page doesn't print an error. This looks like it's just > a case of XFS being too noisy. > > I'll look at it a bit more, but in the end we'll probably just remove > the warning message. I'll be interested in the final answer to this too, since I'm seeing it as well after moving to the 2.4.9 kernel in an effort to get away from these error messages: Sep 20 13:29:41 sdssdp8 kernel: __alloc_pages: 0-order allocation failed. Sep 20 13:33:06 sdssdp8 last message repeated 364 times But, that didn't work. At least kswapd isn't chewing up 20-40% of my CPU with 2.4.9 like it was with 2.4.8. I guess I'll have to hope that the VM gets fixed in 2.4.10.... *sigh* Dan -- Dan Yocum Sloan Digital Sky Survey, Fermilab 630.840.6509 yocum@fnal.gov, http://www.sdss.org SDSS. Mapping the Universe. From owner-linux-xfs@oss.sgi.com Thu Sep 20 11:54:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KIsHB31954 for linux-xfs-outgoing; Thu, 20 Sep 2001 11:54:17 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KIsCe31932 for ; Thu, 20 Sep 2001 11:54:12 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA05847; Thu, 20 Sep 2001 20:54:05 +0200 (CEST) Message-Id: <4.3.2.7.2.20010920204746.033e08f0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 20 Sep 2001 20:53:29 +0200 To: "Steve Wolfe" , From: Seth Mos Subject: Re: XFS to main kernel source In-Reply-To: <003601c14200$77893b00$50824e40@iboats.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 12:17 20-9-2001 -0600, Steve Wolfe wrote: > > When will be the XFS patch integrated to main tree? > > (snip) FAQ > >> I'm really fed up with trying to get linux-2.4.9 + acXX or preXX + xfs > >> together. > >(snip) Worrysome combination. > >>> I would hold off on 2.4.10 - there have been some major kernel changes > >>> which will affect XFS, it may take a while to shake out the bugs. The >2.4.9 > >>> version appears to be running OK. I would see if you get any other >feedback > > I'd just like to add, for the record, that while I really do love XFS, >because of things like the above statement from Steve Lord, I really can't >use it on my production machines until it is tied into the regular kernel It might be a bit extreme since you might need to patch your kernel to make some hardware work. Intergrating XFS in the mainstream kernel won't make the patching process any easier. XFS interacts with the VM and will thus always require work. 2.5 would make it easier since it looks like it will be a lot friendlier for intergrating XFS into it. In the mean time I am happily running XFS on my production servers with good results and have had no (knock on wood) XFS related problems in the past half year. >tree. I imagine that you're already doing everything that you can to get >it integrated, I'm not griping, just giving (hopefully) constructive >feedback. They are working it. It needs time. Rome was not built in a day. We are stil working on the little shack in the back :-) Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Sep 20 12:05:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KJ56H32259 for linux-xfs-outgoing; Thu, 20 Sep 2001 12:05:06 -0700 Received: from codon.com (zombiewarrior.com [64.78.130.125]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KJ53e32239 for ; Thu, 20 Sep 2001 12:05:03 -0700 Received: (qmail 18648 invoked by uid 516); 20 Sep 2001 19:23:04 -0000 Received: from nw@codon.com by helix with qmail-scanner-0.96 (. Clean. Processed in 0.051998 secs); 20 Sep 2001 19:23:04 -0000 Received: from weasel.local.iboats.com (HELO weasel) (64.78.130.80) by codon.com with SMTP; 20 Sep 2001 19:23:04 -0000 Message-ID: <001701c14206$314ab0a0$50824e40@iboats.com> From: "Steve Wolfe" To: References: <4.3.2.7.2.20010920204746.033e08f0@pop.xs4all.nl> Subject: Re: XFS to main kernel source Date: Thu, 20 Sep 2001 12:58:08 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Intergrating XFS in the mainstream kernel won't make the patching process > any easier. XFS interacts with the VM and will thus always require work. But supposedly, things get tested before released in an official kernel version. > In the mean time I am happily running XFS on my production servers with > good results and have had no (knock on wood) XFS related problems in the > past half year. While I haven't had problems with the functionality, but I've run into a number of problems in the patching/compiling area. If I want to use the pre-patched kernel source available for download, that's always easy, but trying to patch other versions isn't always a walk in the park, and I prefer having greater freedom to choose the kernel version that I want. It's a real pain in the read when you need a certain kernel version for one device, another kernel version to make your file system work, another kernel version for something else.... > They are working it. It needs time. Rome was not built in a day. We are > stil working on the little shack in the back :-) I know. Like I said, I'm not complaining or griping. You guys are doing amazing things, and I'm extremely appreciative. I hope that my comments were constructive. : ) steve From owner-linux-xfs@oss.sgi.com Thu Sep 20 12:13:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KJDhb32514 for linux-xfs-outgoing; Thu, 20 Sep 2001 12:13:43 -0700 Received: from burgers (IDENT:postfix@burgers.bubbanfriends.org [216.140.122.113]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KJDde32495 for ; Thu, 20 Sep 2001 12:13:39 -0700 Received: by burgers (Postfix, from userid 500) id 2B5B64001C0; Thu, 20 Sep 2001 15:13:44 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by burgers (Postfix) with ESMTP id 29E0C240021C; Thu, 20 Sep 2001 15:13:44 -0400 (EDT) Date: Thu, 20 Sep 2001 15:13:44 -0400 (EDT) From: Mike Burger To: Steve Lord Cc: Steve Wolfe , Subject: Re: XFS to main kernel source In-Reply-To: <200109201831.f8KIVIk18442@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Luckily, he also copied it to the kernel mailing list. On Thu, 20 Sep 2001, Steve Lord wrote: > > > When will be the XFS patch integrated to main tree? > > > > (snip) > > > > >> I'm really fed up with trying to get linux-2.4.9 + acXX or preXX + xfs > > >> together. > > > > (snip) > > > > >>> I would hold off on 2.4.10 - there have been some major kernel changes > > >>> which will affect XFS, it may take a while to shake out the bugs. The > > 2.4.9 > > >>> version appears to be running OK. I would see if you get any other > > feedback > > > > I'd just like to add, for the record, that while I really do love XFS, > > because of things like the above statement from Steve Lord, I really can't > > use it on my production machines until it is tied into the regular kernel > > tree. I imagine that you're already doing everything that you can to get > > it integrated, I'm not griping, just giving (hopefully) constructive > > feedback. > > Well, since the changes are being made to the Linux VM, not to XFS, > if I was in your situation I would ask myself if I should be running recent > 2.4 kernels in production with any filesystem. I am not convinced that being > in the mainline kernel is much of a help right now. > > Oh, and we are not the ones who need this form of feedback ;-) > > Steve > > > From owner-linux-xfs@oss.sgi.com Thu Sep 20 12:53:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KJr5a00905 for linux-xfs-outgoing; Thu, 20 Sep 2001 12:53:05 -0700 Received: from chef.cc.absoval.com (cpe-66-1-218-101.fl.sprintbbd.net [66.1.218.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KJr0e00886 for ; Thu, 20 Sep 2001 12:53:00 -0700 Received: from ieee.org (IDENT:bs@thebs.cc.absoval.com [192.168.100.89]) by chef.cc.absoval.com (8.9.3/8.9.3) with ESMTP id PAA13729; Thu, 20 Sep 2001 15:52:36 -0400 Message-ID: <3BAA4900.1A1E0987@ieee.org> Date: Thu, 20 Sep 2001 15:52:32 -0400 From: Bryan-TheBS-Smith Organization: SmithConcepts/AbsoluteValueSystems X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Wolfe CC: linux-xfs@oss.sgi.com Subject: Re: XFS to main kernel source References: <003601c14200$77893b00$50824e40@iboats.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Wolfe wrote: > I'd just like to add, for the record, that while I really do love XFS, > because of things like the above statement from Steve Lord, I really > can't use it on my production machines until it is tied into the regular > kernel tree. If you stick with select, well-tested kernels, you shouldn't have any issues. I've learned *NOT* to use the latest kernel from experience dating back to 2.0. I'd rather "hold back" and use RedHat/SGI release kernels on most of my systems. I also feel that XFS is more stable than Ext2/Ext3 on kernel 2.4, because of all the testing SGI does before putting a version number on it. Understand I was a big time adopter of Ext3 under 2.2. While this may no longer be true as of newer kernels (2.4.6+???), it definately was as of 2.4.3 when XFS 1.0.1 was released -- at least in my file server trials for NFS/SMB. The fact that it's got POSIX ACL support, including Samba 2.2 integration, as well as official Quota support tells me its better supported and tested than some other JFS'. Even IBM's JFS, unless I am mistake, seems to be lacking in a lot of basic support, like for NFS and quotas. And I still see people having ReiserFS issues with non-Linux NFS clients (anyone not having any issues?). I know most people don't care about such things, but I do for my needs. -- TheBS Over two dozen systems with XFS 1.0.1, no data loss -- Bryan "TheBS" Smith mailto:b.j.smith@ieee.org chat:thebs413 Engineer AbsoluteValue Systems, Inc. http://www.linux-wlan.org President SmithConcepts, Inc. http://www.SmithConcepts.com From owner-linux-xfs@oss.sgi.com Thu Sep 20 13:03:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KK3ha01252 for linux-xfs-outgoing; Thu, 20 Sep 2001 13:03:43 -0700 Received: from the-village.bc.nu (lightning.swansea.linux.org.uk [194.168.151.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KK3ee01233 for ; Thu, 20 Sep 2001 13:03:41 -0700 Received: from alan by the-village.bc.nu with local (Exim 3.22 #1) id 15kA2A-00060O-00; Thu, 20 Sep 2001 21:02:54 +0100 Subject: Re: XFS to main kernel source To: narancs@narancs.tii.matav.hu (Narancs v1) Date: Thu, 20 Sep 2001 21:02:54 +0100 (BST) Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org In-Reply-To: from "Narancs v1" at Sep 20, 2001 08:12:48 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > When will be the XFS patch integrated to main tree? > I'm really fed up with trying to get linux-2.4.9 + acXX or preXX + xfs > together. I can only speak for -ac but right now I have no plan to tackle the merge except as an "its in 2.5, its ok in 2.5 backport" task From owner-linux-xfs@oss.sgi.com Thu Sep 20 13:08:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KK8ku01466 for linux-xfs-outgoing; Thu, 20 Sep 2001 13:08:46 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KK8he01439 for ; Thu, 20 Sep 2001 13:08:43 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id ; Thu, 20 Sep 2001 15:07:49 -0500 Message-ID: <85063BBE668FD411944400D0B744267A8885A7@AUSMAIL> From: "Gonyou, Austin" To: "'Alan Cox'" , narancs@narancs.tii.matav.hu Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: RE: XFS to main kernel source Date: Thu, 20 Sep 2001 15:07:48 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Won't there be a lot of changes which need to be made for it to go into 2.5 anyway though beyond just current development? Isn't 2.5 supposed to be "radically" different? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk] > Sent: Thursday, September 20, 2001 3:03 PM > To: narancs@narancs.tii.matav.hu > Cc: linux-xfs@oss.sgi.com; linux-kernel@vger.kernel.org > Subject: Re: XFS to main kernel source > > > > When will be the XFS patch integrated to main tree? > > I'm really fed up with trying to get linux-2.4.9 + acXX or > preXX + xfs > > together. > > I can only speak for -ac but right now I have no plan to > tackle the merge > except as an "its in 2.5, its ok in 2.5 backport" task > From owner-linux-xfs@oss.sgi.com Thu Sep 20 13:10:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KKATX01610 for linux-xfs-outgoing; Thu, 20 Sep 2001 13:10:29 -0700 Received: from the-village.bc.nu (lightning.swansea.linux.org.uk [194.168.151.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KKARe01591 for ; Thu, 20 Sep 2001 13:10:27 -0700 Received: from alan by the-village.bc.nu with local (Exim 3.22 #1) id 15kADf-000632-00; Thu, 20 Sep 2001 21:14:47 +0100 Subject: Re: XFS to main kernel source To: austin@coremetrics.com (Gonyou, Austin) Date: Thu, 20 Sep 2001 21:14:47 +0100 (BST) Cc: alan@lxorguk.ukuu.org.uk ('Alan Cox'), narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org In-Reply-To: <85063BBE668FD411944400D0B744267A8885A7@AUSMAIL> from "Gonyou, Austin" at Sep 20, 2001 03:07:48 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Won't there be a lot of changes which need to be made for it to go into 2.5 > anyway though beyond just current development? Isn't 2.5 supposed to be > "radically" different? Not really. 2.5 will change over time for certain but if anything the 2.5 changes will make it easier. One problem area with XFS is that it duplicates chunks of what should be generic functionality - and 2.5 needs to provide the generic paths it wants From owner-linux-xfs@oss.sgi.com Thu Sep 20 13:13:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KKDS801762 for linux-xfs-outgoing; Thu, 20 Sep 2001 13:13:28 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KKDHe01742 for ; Thu, 20 Sep 2001 13:13:17 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA04220 for ; Thu, 20 Sep 2001 13:12:58 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA3023875; Thu, 20 Sep 2001 15:11:27 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id PAA10541; Thu, 20 Sep 2001 15:11:26 -0500 (CDT) Message-ID: <3BAA4D32.17E211BA@sgi.com> Date: Thu, 20 Sep 2001 15:10:26 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Ajay Shekhawat CC: linux-xfs@oss.sgi.com Subject: Re: Kickstart woes References: <20010920143153.A21689@cepheus.cedar.buffalo.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ajay Shekhawat wrote: > After anaconda formats the partitions, it stops saying: > Error mounting hda5 on /: No such device > This most likely means the partition is not formatted > Press OK Hm, I don't think I've seen this one before - is there anything strange about your IDE setup? I could put together an update floppy with some debug messages to try to figure this one out... is there anything you can tweak in your ks.cfg, set a few more things explicitly, perhaps? I'm pretty sure people around here have done network kickstart installs without problems. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Sep 20 13:17:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KKHmm01949 for linux-xfs-outgoing; Thu, 20 Sep 2001 13:17:48 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KKHOe01922 for ; Thu, 20 Sep 2001 13:17:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA02398 for ; Thu, 20 Sep 2001 13:17:15 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA3024396; Thu, 20 Sep 2001 15:15:48 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA71944; Thu, 20 Sep 2001 15:15:48 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8KKGrL19642; Thu, 20 Sep 2001 15:16:53 -0500 Message-Id: <200109202016.f8KKGrL19642@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Alan Cox cc: austin@coremetrics.com (Gonyou, Austin), narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source In-Reply-To: Message from Alan Cox of "Thu, 20 Sep 2001 21:14:47 BST." Date: Thu, 20 Sep 2001 15:16:52 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Won't there be a lot of changes which need to be made for it to go into 2.5 > > anyway though beyond just current development? Isn't 2.5 supposed to be > > "radically" different? > > Not really. 2.5 will change over time for certain but if anything the 2.5 > changes will make it easier. One problem area with XFS is that it duplicates > chunks of what should be generic functionality - and 2.5 needs to provide > the generic paths it wants Since we have your attention - which chunks? One of the frustrations we have had is the lack of feedback from anyone who has looked at XFS. Just interested. Steve From owner-linux-xfs@oss.sgi.com Thu Sep 20 13:21:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KKLja02118 for linux-xfs-outgoing; Thu, 20 Sep 2001 13:21:45 -0700 Received: from the-village.bc.nu (lightning.swansea.linux.org.uk [194.168.151.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KKLge02099 for ; Thu, 20 Sep 2001 13:21:43 -0700 Received: from alan by the-village.bc.nu with local (Exim 3.22 #1) id 15kANe-00064a-00; Thu, 20 Sep 2001 21:25:06 +0100 Subject: Re: XFS to main kernel source To: lord@sgi.com (Steve Lord) Date: Thu, 20 Sep 2001 21:25:06 +0100 (BST) Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), austin@coremetrics.com (Gonyou Austin), narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org In-Reply-To: <200109202016.f8KKGrL19642@jen.americas.sgi.com> from "Steve Lord" at Sep 20, 2001 03:16:52 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Since we have your attention - which chunks? One of the frustrations we have > had is the lack of feedback from anyone who has looked at XFS. > > Just interested. Send me a current snapshot diff and I'll promise you some feedback. I didnt realise this was an issue Alan From owner-linux-xfs@oss.sgi.com Thu Sep 20 13:28:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KKSIs02294 for linux-xfs-outgoing; Thu, 20 Sep 2001 13:28:18 -0700 Received: from ns.caldera.de (ns.caldera.de [212.34.180.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KKSFe02275 for ; Thu, 20 Sep 2001 13:28:15 -0700 Received: (from hch@localhost) by ns.caldera.de (8.11.1/8.11.1) id f8KKQhZ07714; Thu, 20 Sep 2001 22:26:43 +0200 Date: Thu, 20 Sep 2001 22:26:43 +0200 From: Christoph Hellwig To: Steve Lord Cc: Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source Message-ID: <20010920222643.A7267@caldera.de> Mail-Followup-To: Christoph Hellwig , Steve Lord , Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org References: <200109202016.f8KKGrL19642@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: <200109202016.f8KKGrL19642@jen.americas.sgi.com>; from lord@sgi.com on Thu, Sep 20, 2001 at 03:16:52PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Sep 20, 2001 at 03:16:52PM -0500, Steve Lord wrote: > > > Won't there be a lot of changes which need to be made for it to go into 2.5 > > > anyway though beyond just current development? Isn't 2.5 supposed to be > > > "radically" different? > > > > Not really. 2.5 will change over time for certain but if anything the 2.5 > > changes will make it easier. One problem area with XFS is that it duplicates > > chunks of what should be generic functionality - and 2.5 needs to provide > > the generic paths it wants > > Since we have your attention - which chunks? One of the frustrations we have > had is the lack of feedback from anyone who has looked at XFS. o The whole vnode layer o checks already peformed by the VFS all over the place (just take a look at xfs_rename.c!) o the own quoata code o the hooks for a propritary clusterfs.. My 2 (euro-)cents, Christoph -- Of course it doesn't work. We've performed a software upgrade. From owner-linux-xfs@oss.sgi.com Thu Sep 20 13:31:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KKVoc02491 for linux-xfs-outgoing; Thu, 20 Sep 2001 13:31:50 -0700 Received: from pincoya.inf.utfsm.cl (IDENT:root@pincoya.inf.utfsm.cl [200.1.19.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KKVhe02471 for ; Thu, 20 Sep 2001 13:31:43 -0700 Received: from pincoya.inf.utfsm.cl (IDENT:vonbrand@localhost.inf.utfsm.cl [127.0.0.1]) by pincoya.inf.utfsm.cl (8.12.0/8.12.0) with ESMTP id f8KKTQZV005891; Thu, 20 Sep 2001 16:29:27 -0400 Received: from pincoya.inf.utfsm.cl (vonbrand@localhost) by pincoya.inf.utfsm.cl (8.12.0/8.12.0) with ESMTP id f8KKTN1u005873; Thu, 20 Sep 2001 16:29:24 -0400 Message-Id: <200109202029.f8KKTN1u005873@pincoya.inf.utfsm.cl> To: "Gonyou, Austin" cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source In-Reply-To: Message from "Gonyou, Austin" of "Thu, 20 Sep 2001 15:07:48 EST." <85063BBE668FD411944400D0B744267A8885A7@AUSMAIL> Date: Thu, 20 Sep 2001 16:29:23 -0400 From: Horst von Brand Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Gonyou, Austin" said: > Won't there be a lot of changes which need to be made for it to go into 2.5 > anyway though beyond just current development? Isn't 2.5 supposed to be > "radically" different? I'd better ask "What is 2.4 missing, so we can finish that up and move on to 2.5" 2.5 will have its own way of finding out what new, shiny, exciting features to acquire... -- Dr. Horst H. von Brand Usuario #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513 From owner-linux-xfs@oss.sgi.com Thu Sep 20 13:41:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KKfC102780 for linux-xfs-outgoing; Thu, 20 Sep 2001 13:41:12 -0700 Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KKf4e02760 for ; Thu, 20 Sep 2001 13:41:08 -0700 Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id QAA24768; Thu, 20 Sep 2001 16:40:53 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id QAA05648; Thu, 20 Sep 2001 16:40:52 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Thu, 20 Sep 2001 16:40:51 -0400 (EDT) From: Alexander Viro To: Steve Lord cc: Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source In-Reply-To: <200109202016.f8KKGrL19642@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 20 Sep 2001, Steve Lord wrote: > > > Won't there be a lot of changes which need to be made for it to go into 2.5 > > > anyway though beyond just current development? Isn't 2.5 supposed to be > > > "radically" different? > > > > Not really. 2.5 will change over time for certain but if anything the 2.5 > > changes will make it easier. One problem area with XFS is that it duplicates > > chunks of what should be generic functionality - and 2.5 needs to provide > > the generic paths it wants > > Since we have your attention - which chunks? One of the frustrations we have > had is the lack of feedback from anyone who has looked at XFS. Locking. There is a _lot_ of duplication between fs/namei.c and fs/xfs/* - you definitely don't need most of the stuff you do with locks there. I understand that some of that stuff may be needed for CXFS, and I would really like to see the description of locking requirements of that animal. Parts that are needed only on IRIX since IRIX VFS is braindead should go. Parts that can be moved to generic code should be moved (with sane set of methods provided by filesystems a-la CXFS). The rest will become much simpler. From owner-linux-xfs@oss.sgi.com Thu Sep 20 13:45:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KKjeu03005 for linux-xfs-outgoing; Thu, 20 Sep 2001 13:45:40 -0700 Received: from the-village.bc.nu (lightning.swansea.linux.org.uk [194.168.151.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KKjce02986 for ; Thu, 20 Sep 2001 13:45:38 -0700 Received: from alan by the-village.bc.nu with local (Exim 3.22 #1) id 15kAlk-00068F-00; Thu, 20 Sep 2001 21:50:00 +0100 Subject: Re: XFS to main kernel source To: vonbrand@inf.utfsm.cl (Horst von Brand) Date: Thu, 20 Sep 2001 21:50:00 +0100 (BST) Cc: austin@coremetrics.com (Gonyou Austin), linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org In-Reply-To: <200109202029.f8KKTN1u005873@pincoya.inf.utfsm.cl> from "Horst von Brand" at Sep 20, 2001 04:29:23 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I'd better ask "What is 2.4 missing, so we can finish that up and move on > to 2.5" 2.5 will have its own way of finding out what new, shiny, exciting > features to acquire... Linus 2.4.10pre is definitely 2.5 in disguise From owner-linux-xfs@oss.sgi.com Thu Sep 20 14:07:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KL7k003470 for linux-xfs-outgoing; Thu, 20 Sep 2001 14:07:46 -0700 Received: from antares.cedar.buffalo.edu (antares.cedar.Buffalo.EDU [128.205.33.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KL7he03450 for ; Thu, 20 Sep 2001 14:07:43 -0700 Received: (qmail 12303 invoked from network); 20 Sep 2001 21:07:42 -0000 Received: from cepheus.cedar.buffalo.edu (128.205.33.197) by antares.cedar.buffalo.edu with SMTP; 20 Sep 2001 21:07:42 -0000 Received: (from ajay@localhost) by cepheus.cedar.buffalo.edu (8.9.3/8.9.3) id RAA23638; Thu, 20 Sep 2001 17:07:41 -0400 (EDT) Date: Thu, 20 Sep 2001 17:07:41 -0400 From: Ajay Shekhawat To: Eric Sandeen Cc: linux-xfs@oss.sgi.com Subject: Re: Kickstart woes Message-ID: <20010920170741.A23625@cepheus.cedar.buffalo.edu> References: <20010920143153.A21689@cepheus.cedar.buffalo.edu> <3BAA4D32.17E211BA@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: <3BAA4D32.17E211BA@sgi.com>; from sandeen@sgi.com on Thu, Sep 20, 2001 at 03:10:26PM -0500 Organization: Center for Document Analysis and Recognition X-OfficePhone: +1 (716)-645-6164 ext. 101 X-Fax-Number: +1 (716)-645-6176 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Sep 20, 2001 at 03:10:26PM -0500, Eric Sandeen wrote: > > After anaconda formats the partitions, it stops saying: > > Error mounting hda5 on /: No such device > > This most likely means the partition is not formatted > > Press OK > > Hm, I don't think I've seen this one before - is there anything strange > about your IDE setup? I could put together an update floppy with some > debug messages to try to figure this one out... is there anything you > can tweak in your ks.cfg, set a few more things explicitly, perhaps? > I'm pretty sure people around here have done network kickstart installs > without problems. > > -Eric Update: I used the exact same ks.cfg file, replaced "--fs xfs" with "--fs ext2", and it installed fine. What could be going wrong? Ajay From owner-linux-xfs@oss.sgi.com Thu Sep 20 14:32:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KLW4N04020 for linux-xfs-outgoing; Thu, 20 Sep 2001 14:32:04 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KLVxe04001 for ; Thu, 20 Sep 2001 14:31:59 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8KLVql26837 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Thu, 20 Sep 2001 14:31:52 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id XAA912171 for ; Thu, 20 Sep 2001 23:31:50 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA3017896; Thu, 20 Sep 2001 16:30:33 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA39167; Thu, 20 Sep 2001 16:30:33 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8KLVbB19795; Thu, 20 Sep 2001 16:31:37 -0500 Message-Id: <200109202131.f8KLVbB19795@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: hch@sgi.com, Steve Lord , Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source In-Reply-To: Message from Christoph Hellwig of "Thu, 20 Sep 2001 22:26:43 +0200." <20010920222643.A7267@caldera.de> Date: Thu, 20 Sep 2001 16:31:37 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Thu, Sep 20, 2001 at 03:16:52PM -0500, Steve Lord wrote: > > Since we have your attention - which chunks? One of the frustrations we hav > e > > had is the lack of feedback from anyone who has looked at XFS. > > o The whole vnode layer Two answers here - economics and code stability. This is a filesystem which has been worked on by people being payed to do so by a corporation, therefore there is a budget (long since blown). It was simpler and hence cheaper to wrap XFS in a conversion layer than to rework the code down into the bowels of the filesystem. Then the stability part of it, we started with a working filesystem, from an engineering standpoint it made more sense to keep as much of the existing code base intact as possible - the less surgery performed the better in terms of keeping things running, and making it easy to take enhancements and fixes made in the Irix base into the Linux code (we don't do it the other way around). > o checks already peformed by the VFS all over the place > (just take a look at xfs_rename.c!) I think I will answer this one more slowly and in response to Al Viro's email. But that economics/stability thing comes into it again. > o the own quoata code XFS quotas are transactional, when space is added to a file the quota is adjusted in the same transaction. It is fairly hard to do this without your own quota code. > o the hooks for a propritary clusterfs.. Well we have to make money on something you know.... and in reality there are not a lot of them in the filesystem. Thanks Steve > > My 2 (euro-)cents, > > Christoph > > -- > Of course it doesn't work. We've performed a software upgrade. From owner-linux-xfs@oss.sgi.com Thu Sep 20 16:46:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8KNkrG06595 for linux-xfs-outgoing; Thu, 20 Sep 2001 16:46:53 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8KNkne06576 for ; Thu, 20 Sep 2001 16:46:49 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id QAA07435 for ; Thu, 20 Sep 2001 16:46:48 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id JAA13743; Fri, 21 Sep 2001 09:45:25 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA88039; Fri, 21 Sep 2001 10:45:23 +1100 (AEDT) Date: Fri, 21 Sep 2001 10:45:23 +1100 From: Nathan Scott To: Min Yuan Cc: linux-xfs@oss.sgi.com Subject: Re: readdir() problem when using -D_FILE_OFFSET_BITS=64 in gcc Message-ID: <20010921104522.G416300@wobbly.melbourne.sgi.com> References: <02c601c141f0$b3f07000$4201a8c0@vytalnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <02c601c141f0$b3f07000$4201a8c0@vytalnet.com>; from Min.Yuan@VytalNet.com on Thu, Sep 20, 2001 at 12:24:15PM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Thu, Sep 20, 2001 at 12:24:15PM -0400, Min Yuan wrote: > Redhat7.1 supports large file(>2GB), but you have to add -D_FILE_OFFSET_BITS=64 to gcc > > The following is a very simple program: > > #include > #include > #include > > int main() { > DIR *dr; > struct dirent *dent; > dr = opendir("/var/run"); > while ((dent = readdir(dr)) != NULL) { > printf("inode:%d and d_name:%s\n", dent->d_ino, dent->d_name); > } > return 0; > } Your program has a bug in it. ;) When compiled with -D_FILE_OFFSET_BITS=64 you need to change the line: printf("inode:%d and d_name:%s\n", dent->d_ino, dent->d_name); ^^ to: printf("inode:%lld and d_name:%s\n", dent->d_ino, dent->d_name); ^^^^ and then you should find it works as expected. If you want the same source to work correctly either with or without the compile option, you need to use the second printf but cast "dent->d_ino" to "(long long)dent->d_ino". To be even more correct, you should be using unsigned long long (%llu) because __ino64_t maps to __u_quad_t which is unsigned. Hope this helps. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 20 18:11:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L1B2L07941 for linux-xfs-outgoing; Thu, 20 Sep 2001 18:11:02 -0700 Received: from mail.ramhb.co.nz (root@mail1.ramhb.co.nz [202.27.218.7]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L1Aue07922 for ; Thu, 20 Sep 2001 18:10:56 -0700 Received: from joelm(border.ramhb.co.nz[202.27.218.10]) (1515 bytes) by mail.ramhb.co.nz via smail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Fri, 21 Sep 2001 13:10:54 +1200 (NZST) (Smail-3.2.0.101 1997-Dec-17 #5 built 1998-Feb-20) From: "Joel Macklow" To: linux-xfs@oss.sgi.com Date: Fri, 21 Sep 2001 13:13:22 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: /var disappears ! Reply-to: joelm@ramhb.co.nz Message-ID: <3BAB3CF2.12827.6C1B9A26@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi We are running an AMD Athlon 1Ghz server with 512Mb RAM and 2 x 40GB 7200rpm IBM Deskstar drives. The inital installation is RedHat 7.1 and using the SGI-RedHat 7.1 XFS 1.0 ISO from the download site. The kernel has since been upgraded to 2.4.3-XFS and XFS to 1.0.1. The problem we are encountering is that periodically the /var partition (dev/hdb1) can no longer be written to. The mount point disappears! An 'ls -la' at root level shows /var is not there, however a 'df -m' shows the volume as present and its capacities. We are now considering moving the /var partition into the / in order to try and solve the problem. Can you shed any light on what is going on? We can supply SSH details for an engineer if so desired. I appreciate your time and hope that by fixing this, we can continue to recommend and implement XFS on other production systems. Regards Joel **************************** Joel Macklow Solutions Engineer Ramhb Internet Services **************************** From owner-linux-xfs@oss.sgi.com Thu Sep 20 18:29:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L1TvT08304 for linux-xfs-outgoing; Thu, 20 Sep 2001 18:29:57 -0700 Received: from mail.ramhb.co.nz (root@mail1.ramhb.co.nz [202.27.218.7]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L1Tre08279 for ; Thu, 20 Sep 2001 18:29:54 -0700 Received: from joelm(border.ramhb.co.nz[202.27.218.10]) (853 bytes) by mail.ramhb.co.nz via smail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Fri, 21 Sep 2001 13:29:52 +1200 (NZST) (Smail-3.2.0.101 1997-Dec-17 #5 built 1998-Feb-20) From: "Joel Macklow" To: linux-xfs@oss.sgi.com Date: Fri, 21 Sep 2001 13:32:20 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: more info re /var disappears Reply-to: joelm@ramhb.co.nz Message-ID: <3BAB4164.28223.6C2CF573@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Have just had this happen. /var is still listed in / cd /var is ok ls shows nothing listed cd to /var/log is ok ls shows nothing df still shows volume, mount point and Mb used ok. Any ideas gratefully received Regards Joel **************************** Joel Macklow Solutions Engineer Ramhb Internet Services **************************** From owner-linux-xfs@oss.sgi.com Thu Sep 20 18:41:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L1f7s08593 for linux-xfs-outgoing; Thu, 20 Sep 2001 18:41:07 -0700 Received: from mail09.voicenet.com (mail09.voicenet.com [207.103.0.35]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L1f4e08574 for ; Thu, 20 Sep 2001 18:41:04 -0700 Received: (qmail 408 invoked from network); 21 Sep 2001 01:41:03 -0000 Received: from dialup1820-pri.dialup18x.voicenet.com (207.103.118.20) by mail09.voicenet.com with SMTP; 21 Sep 2001 01:41:03 -0000 Subject: Re: more info re /var disappears From: Herbert Rutledge To: joelm@ramhb.co.nz Cc: linux-xfs@oss.sgi.com In-Reply-To: <3BAB4164.28223.6C2CF573@localhost> References: <3BAB4164.28223.6C2CF573@localhost> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Evolution-Format: text/plain X-Mailer: Evolution/0.13.99+cvs.2001.09.20.15.42 (Preview Release) Date: 20 Sep 2001 21:45:57 -0400 Message-Id: <1001036759.2161.4.camel@desktop> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 2001-09-21 at 16:32, Joel Macklow wrote: > cd /var is ok > ls shows nothing listed > cd to /var/log is ok > ls shows nothing > df still shows volume, mount point and Mb used ok. > > Any ideas gratefully received I had this happen once. I still have no idea what caused it, but xfs_repair fixed it. From owner-linux-xfs@oss.sgi.com Thu Sep 20 19:03:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L23Aw09062 for linux-xfs-outgoing; Thu, 20 Sep 2001 19:03:10 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L237e09036 for ; Thu, 20 Sep 2001 19:03:07 -0700 Received: from idcomm.com (IDENT:xtbL492AqVl3Bxgf6YzLo0yCoRb/18id@x2-pip65.idcomm.com [209.60.72.76]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f8L2Edi21113 for ; Thu, 20 Sep 2001 20:14:39 -0600 Message-ID: <3BAAA06E.162CD1EC@idcomm.com> Date: Thu, 20 Sep 2001 20:05:34 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: more info re /var disappears References: <3BAB4164.28223.6C2CF573@localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Joel Macklow wrote: > > Have just had this happen. > > /var is still listed in / > cd /var is ok > ls shows nothing listed > cd to /var/log is ok > ls shows nothing > df still shows volume, mount point and Mb used ok. > > Any ideas gratefully received > > Regards > > Joel > > **************************** > Joel Macklow > Solutions Engineer > Ramhb Internet Services > **************************** You might try display via non-ls means, such as echo (echo *) or find (find . -name "*" -xdev -print). See if ls is at fault. With the earlier readdir() thread, I would wonder if maybe the app is failing with similar 64 bit flaws from a printf type statement. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Thu Sep 20 20:14:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L3E0E10060 for linux-xfs-outgoing; Thu, 20 Sep 2001 20:14:00 -0700 Received: from webber.adilger.int (h24-64-71-161.cg.shawcable.net [24.64.71.161]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L3Due10039 for ; Thu, 20 Sep 2001 20:13:56 -0700 Received: from webber.adilger.int (adilger@localhost [127.0.0.1]) by localhost (8.12.0.Beta10/8.12.0.Beta10/Debian 8.12.0.Beta10) with ESMTP id f8L3CO1D021954; Thu, 20 Sep 2001 21:12:24 -0600 Received: (from adilger@localhost) by webber.adilger.int (8.12.0.Beta10/8.12.0.Beta10/Debian 8.12.0.Beta10) id f8L3CL2b021952; Thu, 20 Sep 2001 21:12:21 -0600 From: Andreas Dilger Date: Thu, 20 Sep 2001 21:12:21 -0600 To: Steve Lord Cc: hch@sgi.com, Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source Message-ID: <20010920211221.G14526@turbolinux.com> Mail-Followup-To: Steve Lord , hch@sgi.com, Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org References: <20010920222643.A7267@caldera.de> <200109202131.f8KLVbB19795@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200109202131.f8KLVbB19795@jen.americas.sgi.com> User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sep 20, 2001 16:31 -0500, Steve Lord wrote: > XFS quotas are transactional, when space is added to a file the quota is > adjusted in the same transaction. It is fairly hard to do this without your > own quota code. Actually not. The quotas in ext3 are transactional as well. It's just that the "ext3" journal layer allows nested transactions, so it is possible to start a write transaction, call into the journal code which calls back into the ext3 write code to start a nested transaction on the journal file (i.e. it is in the same transaction as the initial write), and then the initial write completes. Cheers, Andreas -- Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry?" http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert From owner-linux-xfs@oss.sgi.com Thu Sep 20 20:25:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L3Piv10483 for linux-xfs-outgoing; Thu, 20 Sep 2001 20:25:44 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L3Pfe10463 for ; Thu, 20 Sep 2001 20:25:41 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id UAA00312 for ; Thu, 20 Sep 2001 20:24:21 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id WAA3025619; Thu, 20 Sep 2001 22:24:18 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id WAA75933; Thu, 20 Sep 2001 22:24:18 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8L3PKi20270; Thu, 20 Sep 2001 22:25:20 -0500 Message-Id: <200109210325.f8L3PKi20270@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Steve Lord , hch@ns.caldera.de, Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source In-Reply-To: Message from Andreas Dilger of "Thu, 20 Sep 2001 21:12:21 MDT." <20010920211221.G14526@turbolinux.com> Date: Thu, 20 Sep 2001 22:25:20 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Sep 20, 2001 16:31 -0500, Steve Lord wrote: > > XFS quotas are transactional, when space is added to a file the quota is > > adjusted in the same transaction. It is fairly hard to do this without your > > own quota code. > > Actually not. The quotas in ext3 are transactional as well. It's just > that the "ext3" journal layer allows nested transactions, so it is possible > to start a write transaction, call into the journal code which calls back > into the ext3 write code to start a nested transaction on the journal file > (i.e. it is in the same transaction as the initial write), and then the > initial write completes. OK, good point, but doing a major rewrite of XFS to use a different transaction mechanism is not really on the cards, plus we have on disk compatibility with the Irix version to consider. Steve From owner-linux-xfs@oss.sgi.com Thu Sep 20 21:43:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L4hjS11764 for linux-xfs-outgoing; Thu, 20 Sep 2001 21:43:45 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L4hae11743 for ; Thu, 20 Sep 2001 21:43:36 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id VAA00595 for ; Thu, 20 Sep 2001 21:43:38 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id OAA15260; Fri, 21 Sep 2001 14:42:02 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id PAA69673; Fri, 21 Sep 2001 15:42:00 +1100 (AEDT) Date: Fri, 21 Sep 2001 15:42:00 +1100 From: Nathan Scott To: Steve Lord Cc: hch@ns.caldera.de, Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source Message-ID: <20010921154159.H416300@wobbly.melbourne.sgi.com> References: <200109210325.f8L3PKi20270@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: <200109210325.f8L3PKi20270@jen.americas.sgi.com>; from lord@sgi.com on Thu, Sep 20, 2001 at 10:25:20PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Thu, Sep 20, 2001 at 10:25:20PM -0500, Steve Lord wrote: > > On Sep 20, 2001 16:31 -0500, Steve Lord wrote: > > > XFS quotas are transactional, when space is added to a file the quota is > > > adjusted in the same transaction. It is fairly hard to do this without your > > > own quota code. > > > > Actually not. The quotas in ext3 are transactional as well. It's just > > that the "ext3" journal layer allows nested transactions, so it is possible > > to start a write transaction, call into the journal code which calls back > > into the ext3 write code to start a nested transaction on the journal file > > (i.e. it is in the same transaction as the initial write), and then the > > initial write completes. > > OK, good point, but doing a major rewrite of XFS to use a different > transaction mechanism is not really on the cards, plus we have on disk > compatibility with the Irix version to consider. > XFS also uses quite a different _model_ of quota, and it is tightly integrated into XFS (by its very nature). There are a number of issues that it attempts to address, and in particular it works around the inherent problems of the traditional quotacheck/mount/quotaon/quotaoff model (ie. the BSD quota model which the Linux VFS also uses, and which was used in IRIX for the EFS filesystem). Its simply different, there are advantages and disadvantages of each way, but XFS is particularly aimed at scalability, and the desire to never have to run quotacheck(8) on large filesystems was one of the issues which the original design aimed to address. So XFS quota should be a non-issue. I have had discussions with Jan Kara and Alan in the past about how to most cleanly integrate it with their (new) VFS quota, and they seem happy with the design we collectively came up with (its slightly different to the one in both the XFS patch and Alan's patch at the moment). cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 20 23:00:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L60Fd13172 for linux-xfs-outgoing; Thu, 20 Sep 2001 23:00:15 -0700 Received: from ns.caldera.de (ns.caldera.de [212.34.180.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L60Be13152 for ; Thu, 20 Sep 2001 23:00:11 -0700 Received: (from hch@localhost) by ns.caldera.de (8.11.1/8.11.1) id f8L5wsV18304; Fri, 21 Sep 2001 07:58:54 +0200 Date: Fri, 21 Sep 2001 07:58:54 +0200 From: Christoph Hellwig To: Steve Lord Cc: Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source Message-ID: <20010921075854.A11617@caldera.de> Mail-Followup-To: Christoph Hellwig , Steve Lord , Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org References: <200109202131.f8KLVbB19795@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: <200109202131.f8KLVbB19795@jen.americas.sgi.com>; from lord@sgi.com on Thu, Sep 20, 2001 at 04:31:37PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Sep 20, 2001 at 04:31:37PM -0500, Steve Lord wrote: > > o The whole vnode layer > > Two answers here - economics and code stability. This is a filesystem > which has been worked on by people being payed to do so by a corporation, > therefore there is a budget (long since blown). It was simpler and hence > cheaper to wrap XFS in a conversion layer than to rework the code down > into the bowels of the filesystem. Then the stability part of it, we > started with a working filesystem, from an engineering standpoint it > made more sense to keep as much of the existing code base intact as > possible - the less surgery performed the better in terms of keeping > things running, and making it easy to take enhancements and fixes made > in the Irix base into the Linux code (we don't do it the other way around). I completly understand SGI's reson to do this - but yet I don't want to see such code in the mainline for obvios reasons.. > > o the hooks for a propritary clusterfs.. > > Well we have to make money on something you know.... and in reality > there are not a lot of them in the filesystem. Again I understand SGI's reasoning - but such hooks are usually not considered to be a good thing line. Christoph -- Of course it doesn't work. We've performed a software upgrade. From owner-linux-xfs@oss.sgi.com Thu Sep 20 23:13:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L6DbG13505 for linux-xfs-outgoing; Thu, 20 Sep 2001 23:13:37 -0700 Received: from sio.vamo.orbitel.bg (dns.vamo.orbitel.bg [195.24.63.30]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L6DUe13485 for ; Thu, 20 Sep 2001 23:13:32 -0700 Received: from vamo.orbitel.bg (ivandi@localhost [127.0.0.1]) by sio.vamo.orbitel.bg (8.10.2/8.10.2) with ESMTP id f8L6DPd13061 for ; Fri, 21 Sep 2001 09:13:25 +0300 Message-ID: <3BAADA85.FD679D05@vamo.orbitel.bg> Date: Fri, 21 Sep 2001 09:13:25 +0300 From: Ivan Ivanov X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.19 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: "crash tests" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I have made some "crash tests" of ext2,ext3, ReiserFS and XFS. The situation with XFS looks strange. I 'll show two cases: 1. Power fail during coping large file - large enough to have time to turn off power :) size is not important. On other filesystems part of the file is in place after recover - but NOT on XFS - name is there but the size is 0. 2. Overwriting file - it is easy to reproduce: open a non empty text file with mcedit(this editor places all file in memory and complete overwrites on save), type some text, press F2 to save, press enter to confirm and in the same time, just after enter press reset. After reboot the file size is zero and the contents is lost - old contents too. This hapens only on XFS partition. On other filesystems old contents of the file is preserved. I think that it is not normal for a filesystem. Many programs load their config files in memory and complete rewrite them on save. Cheers Ivan From owner-linux-xfs@oss.sgi.com Fri Sep 21 00:41:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L7fhi15162 for linux-xfs-outgoing; Fri, 21 Sep 2001 00:41:43 -0700 Received: from vitelus.com (vitelus.com [64.81.243.207]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L7fee15142 for ; Fri, 21 Sep 2001 00:41:40 -0700 Received: from aaronl by vitelus.com with local (Exim 3.32 #1 (Debian)) id 15kKwA-0001cP-00; Fri, 21 Sep 2001 00:41:26 -0700 Date: Fri, 21 Sep 2001 00:41:26 -0700 From: Aaron Lehmann To: Joel Macklow Cc: linux-xfs@oss.sgi.com Subject: Re: more info re /var disappears Message-ID: <20010921004126.B6092@vitelus.com> References: <3BAB4164.28223.6C2CF573@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BAB4164.28223.6C2CF573@localhost> User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Sep 21, 2001 at 01:32:20PM -0700, Joel Macklow wrote: > Have just had this happen. > > /var is still listed in / > cd /var is ok > ls shows nothing listed I had the same problem with my /home. The distinctive symptom was messages about in-memory corruption in dmesg. I ran xfs_repair and it appears to be fixed. From owner-linux-xfs@oss.sgi.com Fri Sep 21 01:44:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8L8iGG16435 for linux-xfs-outgoing; Fri, 21 Sep 2001 01:44:16 -0700 Received: from Milos.fw.matav.hu (firewall-user@matav-3.matav.hu [145.236.252.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8L8iBe16416 for ; Fri, 21 Sep 2001 01:44:11 -0700 Received: by matav-1.matav.hu with smtp; Fri, 21 Sep 2001 10:44:09 +0200 Received: from helka (helka [127.0.0.1]) by helka.tii.matav.hu (Postfix) with ESMTP id E980A2D; Fri, 21 Sep 2001 10:40:21 +0200 (CEST) Date: Fri, 21 Sep 2001 10:40:16 +0200 (CEST) From: Narancs v1 X-X-Sender: To: Christoph Hellwig Cc: Steve Lord , Alan Cox , "Gonyou, Austin" , , Subject: Re: XFS to main kernel source In-Reply-To: <20010921075854.A11617@caldera.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oh guys I did not think that this is so "technically impossible". It's good for me to be informed what phylosofical differences you have between SGI and Linux programming style. If the merge will not happen in around a half year - I think SGI/XFS "will lose market share". And Ext3 is gonna get more of the pie as that is (maybe) possible to patch in the kernel. I really hope, that there will be a nice technical solution to this issue and there will be no political decisions over technical. Thanks - ------------------------- Narancs v1 IT Security Administrator "Security of information is an illusion. What is in one's mind gets into the collective consciousness (akasha), so that can be read with meditation ;-) You don't have to hack. Just 'remember'! You're the one." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjuq/PUACgkQGp+ylEhMCIV0tQCeLKOrR4z1QZLWugIiA8hDZM7t TQQAn0fD6QhhtuvNYUZB/si5CQa/XtaE =k0Lx -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Fri Sep 21 03:02:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LA2Z918006 for linux-xfs-outgoing; Fri, 21 Sep 2001 03:02:35 -0700 Received: from executor.fornax.net ([202.174.32.114]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LA2We17987 for ; Fri, 21 Sep 2001 03:02:32 -0700 Received: (qmail 30063 invoked from network); 21 Sep 2001 10:02:31 -0000 Received: from adl-office.airnet.com.au (HELO fornax.net) (203.34.190.136) by 202.174.32.114 with SMTP; 21 Sep 2001 10:02:31 -0000 Message-ID: <3BAB1035.7040203@fornax.net> Date: Fri, 21 Sep 2001 19:32:29 +0930 From: saveme User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Bad superblock, no secondary Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk *sigh* I've pretty much resigned myself to lost data, but I thought I may as well ask (nay, beg!) the list for help. Whe xfs_repair reports that the superblock is no good, and the secondary can't be found, that's pretty much it, isn't it? No way to get data back from here? (No, no backup. That's what a RAID controller is for. But I'm learning that a RAID controller is not that much use when it dies, taking your XFS partition with it.... :-( TIA, Andrew Hill. From owner-linux-xfs@oss.sgi.com Fri Sep 21 03:11:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LABbn18234 for linux-xfs-outgoing; Fri, 21 Sep 2001 03:11:37 -0700 Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LABXe18214 for ; Fri, 21 Sep 2001 03:11:34 -0700 Received: from bt02e0.god.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id f8LABN105365 for ; Fri, 21 Sep 2001 12:11:23 +0200 (MET DST) Received: from god.bel.alcatel.be (bt02e1.god.bel.alcatel.be [138.203.145.14]) by bt02e0.god.bel.alcatel.be (8.9.3+Sun/8.9.3/1.1) with ESMTP id MAA22229 for ; Fri, 21 Sep 2001 12:10:31 +0200 (MET DST) Message-ID: <3BAB119A.29888F3D@god.bel.alcatel.be> Date: Fri, 21 Sep 2001 12:08:26 +0200 From: kris buggenhout X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: Re: XFS to main kernel source References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Narancs v1 wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Oh guys I did not think that this is so "technically impossible". > It's good for me to be informed what phylosofical differences you have > between SGI and Linux programming style. > > If the merge will not happen in around a half year - I think SGI/XFS "will > lose market share". And Ext3 is gonna get more of the pie as that is > (maybe) possible to patch in the kernel. > I dont think ext3 will be the contender as the design of ext3 is only a patched up ext2, with a lot of limitations to it... I would be more concerned if Reiserfs should get its act together or IBM invests more time into Enterprise storage manager ( on top of jfs) For the enterprose world I see Vxfs as a threat ... in unison with volume manager.If Veritas pulls that off in a reasonable time frame... a lot of company's will opt for Vxfs and volume manager, because it can be used on almost all of their platforms : wincrap2k, Solaris, Irix, Linux, HPUX, AIX,... etc... having a unified fs architecture across platforms is a bonus ... knowledge of platform is not as important anymore regarding storage ( which is a large part of systems management).... From owner-linux-xfs@oss.sgi.com Fri Sep 21 03:17:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LAHOp18446 for linux-xfs-outgoing; Fri, 21 Sep 2001 03:17:24 -0700 Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LAGwe18422 for ; Fri, 21 Sep 2001 03:17:21 -0700 Received: from bt02e0.god.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id f8LAGI006463; Fri, 21 Sep 2001 12:16:22 +0200 (MET DST) Received: from god.bel.alcatel.be (bt02e1.god.bel.alcatel.be [138.203.145.14]) by bt02e0.god.bel.alcatel.be (8.9.3+Sun/8.9.3/1.1) with ESMTP id MAA22415; Fri, 21 Sep 2001 12:15:27 +0200 (MET DST) Message-ID: <3BAB12C1.7FA57C8A@god.bel.alcatel.be> Date: Fri, 21 Sep 2001 12:13:21 +0200 From: kris buggenhout X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" CC: saveme Subject: Re: Bad superblock, no secondary References: <3BAB1035.7040203@fornax.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk saveme wrote: > > *sigh* I've pretty much resigned myself to lost data, but I thought I > may as well ask (nay, beg!) the list for help. > > Whe xfs_repair reports that the superblock is no good, and the secondary > can't be found, that's pretty much it, isn't it? No way to get data back > from here? hmm dont think ya gonne rescue something from that ... If its very important data ... ya could do something stupid like : creating a new fs on another disk, using dd dump info from the other disk on the new disk... carefully offsetting, not to overwrite the superblock, and try xfs_repair on it .... but that wont work I guess > > (No, no backup. That's what a RAID controller is for. But I'm learning > that a RAID controller is not that much use when it dies, taking your > XFS partition with it.... :-( > IMHO a RAID controller is not a safeguard that eliminates the need for backup... Learning the hard way can be expensive ... ;) From owner-linux-xfs@oss.sgi.com Fri Sep 21 03:24:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LAOLf18618 for linux-xfs-outgoing; Fri, 21 Sep 2001 03:24:21 -0700 Received: from executor.fornax.net ([202.174.32.114]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LAOIe18599 for ; Fri, 21 Sep 2001 03:24:18 -0700 Received: (qmail 30196 invoked from network); 21 Sep 2001 10:24:17 -0000 Received: from adl-office.airnet.com.au (HELO fornax.net) (203.34.190.136) by 202.174.32.114 with SMTP; 21 Sep 2001 10:24:17 -0000 Message-ID: <3BAB1550.8080106@fornax.net> Date: Fri, 21 Sep 2001 19:54:16 +0930 From: saveme User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913 X-Accept-Language: en-us MIME-Version: 1.0 To: kris buggenhout CC: "linux-xfs@oss.sgi.com" Subject: Re: Bad superblock, no secondary References: <3BAB1035.7040203@fornax.net> <3BAB12C1.7FA57C8A@god.bel.alcatel.be> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk kris buggenhout wrote: > IMHO a RAID controller is not a safeguard that eliminates the need for > backup... Yeah, so I have found. > Learning the hard way can be expensive ... ;) Well, work can pay for the bandwidth, and most of the really important code is actually backed up - it's just all the MP3s and personal code that you collect over the years - it's not impossible to live without it, but I doubt I will feel quite right using my computer for some time.... :-( Thanks anyhoo! Cheers, Andrew Hill. From owner-linux-xfs@oss.sgi.com Fri Sep 21 04:09:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LB9Df19565 for linux-xfs-outgoing; Fri, 21 Sep 2001 04:09:13 -0700 Received: from bbaer.muenster.de (bbaer.muenster.de [195.202.32.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LB97e19546 for ; Fri, 21 Sep 2001 04:09:07 -0700 Received: from server.nick.de (mueasb-wan041.citykom.de [195.202.39.41]) by bbaer.muenster.de (8.9.3/8.9.3) with ESMTP id NAA22143 for ; Fri, 21 Sep 2001 13:08:51 +0200 X-Authentication-Warning: bbaer.muenster.de: Host mueasb-wan041.citykom.de [195.202.39.41] claimed to be server.nick.de Received: from there (linux.nick.de [192.168.1.1]) by server.nick.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with SMTP id LAA21684 for ; Fri, 21 Sep 2001 11:47:00 +0200 Message-Id: <200109210947.LAA21684@server.nick.de> Content-Type: text/plain; charset="iso-8859-1" From: Nick (Gunnar) Bluth To: Subject: Re: question concerning upgrades Date: Fri, 21 Sep 2001 13:07:41 +0200 X-Mailer: KMail [version 1.3.1] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Sonntag, 16. September 2001 23:17 schrieb Martin K. Petersen: > FWIW, I've already taken a few initial stabs at it. The new Red Hat > installer has better support for handling multiple filesystems, so it > is easier to deal with than 7.1 was. > > We usually have an installer out within a few days of a RH release. > Whether it will happen this time depends on a lot of things. But > we're trying... I'm holding the final release in my very hands at this moment. Maybe I could help? Nick -- Nick (Gunnar) Bluth Muenster/Germany bluth@muenster.de RHCE/RHCX +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ In 1984 mainstream users were choosing VMS over UNIX. Ten years later they are choosing Windows over UNIX. What part of that message aren't you getting? - Tom Payne From owner-linux-xfs@oss.sgi.com Fri Sep 21 05:18:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LCIuo20995 for linux-xfs-outgoing; Fri, 21 Sep 2001 05:18:56 -0700 Received: from chef.cc.absoval.com (cpe-66-1-218-101.fl.sprintbbd.net [66.1.218.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LCIoe20975 for ; Fri, 21 Sep 2001 05:18:51 -0700 Received: from ieee.org (IDENT:bs@thebs.cc.absoval.com [192.168.100.89]) by chef.cc.absoval.com (8.9.3/8.9.3) with ESMTP id IAA16117; Fri, 21 Sep 2001 08:18:35 -0400 Message-ID: <3BAB3018.CFE4290C@ieee.org> Date: Fri, 21 Sep 2001 08:18:32 -0400 From: Bryan-TheBS-Smith Organization: SmithConcepts/AbsoluteValueSystems X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: en MIME-Version: 1.0 To: kris buggenhout CC: "linux-xfs@oss.sgi.com" Subject: Re: XFS to main kernel source References: <3BAB119A.29888F3D@god.bel.alcatel.be> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk kris buggenhout wrote: > I dont think ext3 will be the contender as the design of ext3 is > only a patched up ext2, with a lot of limitations to it... Being that Ext3 is based on Ext2, a very trusted filesystem in many circles, I'd reverse that statement "I don't think ext3 will be the contender." Even Hans Reiser has changed his opinion on Ext3, because he finally realized that people are using it for those very reasons. > I would be more concerned if Reiserfs should get its act together or Although ReiserFS is a very novel and advanced filesystem, and is probably the future of filesystem design, it's breaking of traditional UNIX layout and structures is just too much of an issue to those of us who run UNIX networks. I need reliable NFS and I need quota support. Plus I don't trust its recovery mechanisms, as its focus seems to be on features. > IBM invests more time into Enterprise storage manager ( on top > of jfs) JFS seems to be lacking as much compatibility as ReiserFS. Something tells me that this is because it was a port from OS/2 rather than AIX's version??? I haven't used or tested JFS so I'm making these statements blind. Feel free to rebuke me on this, I just looked at its feature list, what was missing and dismissed it from any consideration. > For the enterprose world I see Vxfs as a threat ... in unison with > volume manager.If Veritas pulls that off in a reasonable time > frame... a lot of company's will opt for Vxfs and volume manager, > because it can be used on almost all of their platforms : wincrap2k, > Solaris, Irix, Linux, HPUX, AIX,... etc... I take it it is not OSS? ;-PPP It must be OSS or at least of commodity cost to gain widespread acceptance, regardless of superiority. > having a unified fs architecture across platforms is a bonus ... > knowledge of platform is not as important anymore regarding storage ( > which is a large part of systems management).... True, oh so true. Of course gaining access to Windows internals isn't exactly something an OSS project can do. -- TheBS -- Bryan "TheBS" Smith mailto:b.j.smith@ieee.org chat:thebs413 Engineer AbsoluteValue Systems, Inc. http://www.linux-wlan.org President SmithConcepts, Inc. http://www.SmithConcepts.com From owner-linux-xfs@oss.sgi.com Fri Sep 21 06:20:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LDKgq22302 for linux-xfs-outgoing; Fri, 21 Sep 2001 06:20:42 -0700 Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LDKZe22283 for ; Fri, 21 Sep 2001 06:20:35 -0700 Received: from bt02e0.god.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id f8LDKLL26211; Fri, 21 Sep 2001 15:20:21 +0200 (MET DST) Received: from god.bel.alcatel.be (bt02e1.god.bel.alcatel.be [138.203.145.14]) by bt02e0.god.bel.alcatel.be (8.9.3+Sun/8.9.3/1.1) with ESMTP id PAA29912; Fri, 21 Sep 2001 15:19:29 +0200 (MET DST) Message-ID: <3BAB3DE5.2C94E1C2@god.bel.alcatel.be> Date: Fri, 21 Sep 2001 15:17:25 +0200 From: kris buggenhout X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Bryan-TheBS-Smith , "linux-xfs@oss.sgi.com" Subject: Re: XFS to main kernel source References: <3BAB119A.29888F3D@god.bel.alcatel.be> <3BAB3018.CFE4290C@ieee.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Bryan-TheBS-Smith wrote: > > kris buggenhout wrote: > > I dont think ext3 will be the contender as the design of ext3 is > > only a patched up ext2, with a lot of limitations to it... > > Being that Ext3 is based on Ext2, a very trusted filesystem in many > circles, I'd reverse that statement "I don't think ext3 will be the > contender." Even Hans Reiser has changed his opinion on Ext3, > because he finally realized that people are using it for those very > reasons. > ok for casual usage and not too big a fs, but when it tends to grow ext3 has a lot of problems. > > I would be more concerned if Reiserfs should get its act together or > > Although ReiserFS is a very novel and advanced filesystem, and is > probably the future of filesystem design, it's breaking of > traditional UNIX layout and structures is just too much of an issue > to those of us who run UNIX networks. I need reliable NFS and I > need quota support. Plus I don't trust its recovery mechanisms, as > its focus seems to be on features. > > > IBM invests more time into Enterprise storage manager ( on top > > of jfs) > > JFS seems to be lacking as much compatibility as ReiserFS. > Something tells me that this is because it was a port from OS/2 > rather than AIX's version??? I haven't used or tested JFS so I'm > making these statements blind. Feel free to rebuke me on this, I > just looked at its feature list, what was missing and dismissed it > from any consideration. I am not talking of the jfs they have out, Enterprise storage manager is built on lvm and jfs from AIX.. this has not yet been released into OSS, but will be. > > > For the enterprose world I see Vxfs as a threat ... in unison with > > volume manager.If Veritas pulls that off in a reasonable time > > frame... a lot of company's will opt for Vxfs and volume manager, > > because it can be used on almost all of their platforms : wincrap2k, > > Solaris, Irix, Linux, HPUX, AIX,... etc... > > I take it it is not OSS? ;-PPP It must be OSS or at least of > commodity cost to gain widespread acceptance, regardless of > superiority. If You have tens or hundreds of servers already with volume manager and Vxfs, the ability to have low cost servers on low cost hardware have the same ... this will let it have momentum in the corporate world. > > > having a unified fs architecture across platforms is a bonus ... > > knowledge of platform is not as important anymore regarding storage ( > > which is a large part of systems management).... > > True, oh so true. Of course gaining access to Windows internals > isn't exactly something an OSS project can do. > Samba ? wine ... bochs ... ? IMHO it wont be easy, but it's certainly not undo-able... This is why I am so involved in using XFS .... From owner-linux-xfs@oss.sgi.com Fri Sep 21 06:31:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LDVAD22584 for linux-xfs-outgoing; Fri, 21 Sep 2001 06:31:10 -0700 Received: from rain.CC.Lehigh.EDU (rain.CC.Lehigh.EDU [128.180.39.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LDV3e22559 for ; Fri, 21 Sep 2001 06:31:03 -0700 Received: from Lehigh.EDU (hooch.CC.Lehigh.EDU [128.180.3.11]) by rain.CC.Lehigh.EDU (8.11.5/8.11.5) with ESMTP id f8LDUFT10128; Fri, 21 Sep 2001 09:30:20 -0400 Message-ID: <3BAB3DF2.CDD1658C@Lehigh.EDU> Date: Fri, 21 Sep 2001 09:17:38 -0400 From: Jim Eshleman X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Eric Sandeen CC: "'linux-xfs@oss.sgi.com'" Subject: Re: Bad write page, under 2.4.9 kernel References: <414DB4427DE6D411846200B0D078E84B169DD1@uk-exch.magma-da.com> <3BAA1C91.31E8B65D@sgi.com> Content-Type: multipart/mixed; boundary="------------097549D802D313456EF1BAD2" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------097549D802D313456EF1BAD2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Eric Sandeen wrote: > > "Saunders, Andrew (Magma-da/Reading-UK)" wrote: > > > Sep 20 10:00:14 thor kernel: Bad write on page 0xc1822a30 > > The short, but perhaps unsatisfying answer is that you can probably just > ignore this error. The code in pagebuf_write_full_page that generates > it is identical to the code in buffer.c:block_write_full_page - except > block_write_full_page doesn't print an error. This looks like it's just > a case of XFS being too noisy. > > I'll look at it a bit more, but in the end we'll probably just remove > the warning message. Eric, In my case the "Bad write on page" always preceeds "Warning: buffer ... with weird blockno" and then a pair of "kernel BUG at ll_rw_blk.c" errors. Attached is the syslog output from the most recent, 2.4.9 + linux-2.4.9-xfs-2001-08-26.patch. Any ideas if this is XFS, 2.4 VM bug, something else? Jim --------------097549D802D313456EF1BAD2 Content-Type: text/plain; charset=us-ascii; name="bug.3" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="bug.3" Sep 19 04:30:17 xxxx kernel: Bad write on page 0xc1e102f8 Sep 19 04:30:17 xxxx kernel: Warning: buffer 0xca61f660 with weird blockno (0) Sep 19 04:30:17 xxxx kernel: Warning: buffer 0xca61f660 with weird blockno (0) Sep 19 04:30:17 xxxx kernel: kernel BUG at ll_rw_blk.c:1011! Sep 19 04:30:17 xxxx kernel: invalid operand: 0000 Sep 19 04:30:17 xxxx kernel: CPU: 0 Sep 19 04:30:17 xxxx kernel: EIP: 0010:[ll_rw_block+141/540] Sep 19 04:30:17 xxxx kernel: EIP: 0010:[] Sep 19 04:30:17 xxxx kernel: EFLAGS: 00010286 Sep 19 04:30:17 xxxx kernel: eax: 00000020 ebx: 00003a04 ecx: 00000001 edx: 00000001 Sep 19 04:30:17 xxxx kernel: esi: 00000000 edi: 00000200 ebp: e7b25d44 esp: e7b25cec Sep 19 04:30:17 xxxx kernel: ds: 0018 es: 0018 ss: 0018 Sep 19 04:30:17 xxxx kernel: Process procmail (pid: 6746, stackpage=e7b25000) Sep 19 04:30:17 xxxx kernel: Stack: c022d871 c022db42 000003f3 d08e4858 ca61f660 e7b25d60 00000000 ca61f660 Sep 19 04:30:17 xxxx kernel: 4e4d4c4b 5251504f 56555453 5a595857 00001000 c0137774 00000001 00000001 Sep 19 04:30:17 xxxx kernel: e7b25d44 d08e4840 e5db8808 e5db87f0 00000001 e7b25d60 ca61f660 66363630 Sep 19 04:30:17 xxxx kernel: Call Trace: [fsync_inode_buffers+176/396] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-158521/96] [vsnprintf+1146/1228] [hide_cursor+128/136] [vt_console_print+728/752] Sep 19 04:30:17 xxxx kernel: Call Trace: [] [] [] [] [] Sep 19 04:30:17 xxxx kernel: [printk+417/432] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-525609/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-517888/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-525577/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-524582/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-522433/96] Sep 19 04:30:17 xxxx kernel: [] [] [] [] [] [] Sep 19 04:30:17 xxxx kernel: [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-522128/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-121364/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-135614/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-221573/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-96572/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-65164/96] Sep 19 04:30:17 xxxx kernel: [] [] [] [] [] [] Sep 19 04:30:17 xxxx kernel: [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-529609/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-9472/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-83599/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-115459/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-9472/96] [3c59x:__insmod_3c59x_O/lib/modules/2.4.9a-xfs/kernel/drivers/net/+-84687/96] Sep 19 04:30:17 xxxx kernel: [] [] [] [] [] [] Sep 19 04:30:17 xxxx kernel: [sys_fsync+92/140] [system_call+51/56] Sep 19 04:30:17 xxxx kernel: [] [] Sep 19 04:30:17 xxxx kernel: Sep 19 04:30:17 xxxx kernel: Code: 0f 0b 83 c4 0c 83 c5 04 46 3b 74 24 30 7c b0 8b 4c 24 2c f6 Sep 19 04:30:34 xxxx kernel: kernel BUG at ll_rw_blk.c:692! Sep 19 04:30:34 xxxx kernel: invalid operand: 0000 Sep 19 04:30:34 xxxx kernel: CPU: 4 Sep 19 04:30:34 xxxx kernel: EIP: 0010:[__make_request+180/1968] Sep 19 04:30:34 xxxx kernel: EIP: 0010:[] Sep 19 04:30:34 xxxx kernel: EFLAGS: 00010286 Sep 19 04:30:34 xxxx kernel: eax: 0000001f ebx: ca61f660 ecx: 00000002 edx: 00000020 Sep 19 04:30:34 xxxx kernel: esi: 00002000 edi: 00004000 ebp: ca11f818 esp: ca19de8c Sep 19 04:30:34 xxxx kernel: ds: 0018 es: 0018 ss: 0018 Sep 19 04:30:34 xxxx kernel: Process bdflush (pid: 13, stackpage=ca19d000) Sep 19 04:30:34 xxxx kernel: Stack: c022d871 c022db42 000002b4 00000008 ca61f660 031d9000 00000000 ca113920 Sep 19 04:30:34 xxxx kernel: 00000001 00000008 f709ad70 f709ac00 f7058000 00000000 00004000 ca11f848 Sep 19 04:30:34 xxxx kernel: ca11f840 0841f840 002007d0 00000000 00000000 002007d0 00000202 c017f280 Sep 19 04:30:34 xxxx kernel: Call Trace: [generic_make_request+176/272] [submit_bh+88/116] [write_locked_buffers+30/40] [write_some_buffers+202/308] [bdflush+146/216] Sep 19 04:30:34 xxxx kernel: Call Trace: [] [] [] [] [] Sep 19 04:30:34 xxxx kernel: [stext+0/100] [kernel_thread+35/48] Sep 19 04:30:34 xxxx kernel: [] [] Sep 19 04:30:34 xxxx kernel: Sep 19 04:30:34 xxxx kernel: Code: 0f 0b 83 c4 0c 8d b4 26 00 00 00 00 8b 74 24 5c 56 8b 7c 24 --------------097549D802D313456EF1BAD2-- From owner-linux-xfs@oss.sgi.com Fri Sep 21 06:36:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LDa3l22782 for linux-xfs-outgoing; Fri, 21 Sep 2001 06:36:03 -0700 Received: from chef.cc.absoval.com (cpe-66-1-218-101.fl.sprintbbd.net [66.1.218.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LDZxe22763 for ; Fri, 21 Sep 2001 06:35:59 -0700 Received: from ieee.org (IDENT:bs@thebs.cc.absoval.com [192.168.100.89]) by chef.cc.absoval.com (8.9.3/8.9.3) with ESMTP id JAA16385; Fri, 21 Sep 2001 09:35:46 -0400 Message-ID: <3BAB422F.D0C0BCF6@ieee.org> Date: Fri, 21 Sep 2001 09:35:43 -0400 From: Bryan-TheBS-Smith Organization: SmithConcepts/AbsoluteValueSystems X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: en MIME-Version: 1.0 To: kris buggenhout CC: "linux-xfs@oss.sgi.com" Subject: Re: XFS to main kernel source References: <3BAB119A.29888F3D@god.bel.alcatel.be> <3BAB3018.CFE4290C@ieee.org> <3BAB3DE5.2C94E1C2@god.bel.alcatel.be> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk kris buggenhout wrote: > ok for casual usage and not too big a fs, but when it tends to grow > ext3 has a lot of problems. I've had a 100GB Ext3 volume for almost 15 months no. 0 issues. Now that's running on kernel 2.2.16 using full data journaling, something that has changed with 2.4 -- where the VM system has changed to the point where full data journaling is not implemented as the simple "double buffer" it was on 2.2 -- but it's still nice to be able to drop down to an Ext2 fsck if you ever get into trouble. > I am not talking of the jfs they have out, Enterprise storage manager is > built on lvm and jfs from AIX.. this has not yet been released into OSS, > but will be. Well that's good news. I'm curious as to why IBM didn't do this in the first place. Is it non-IBM licensed code that they must replace before they do? > If You have tens or hundreds of servers already with volume manager and > Vxfs, the ability to have low cost servers on low cost hardware have the > same ... this will let it have momentum in the corporate world. I don't disagree with you there. > Samba ? wine ... bochs ... ? IMHO it wont be easy, but it's certainly > not undo-able... As someone who was involved with FreeDOS, it is a very, very frustrating and slow development process to reverse engineer, bug for bug. > This is why I am so involved in using XFS .... Me too. I trust XFS more than Ext2/Ext3 on kernel 2.4. -- TheBS -- Bryan "TheBS" Smith mailto:b.j.smith@ieee.org chat:thebs413 Engineer AbsoluteValue Systems, Inc. http://www.linux-wlan.org President SmithConcepts, Inc. http://www.SmithConcepts.com From owner-linux-xfs@oss.sgi.com Fri Sep 21 06:42:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LDgEO23018 for linux-xfs-outgoing; Fri, 21 Sep 2001 06:42:14 -0700 Received: from ns.caldera.de (ns.caldera.de [212.34.180.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LDgAe22998 for ; Fri, 21 Sep 2001 06:42:11 -0700 Received: (from hch@localhost) by ns.caldera.de (8.11.1/8.11.1) id f8LDdw118340; Fri, 21 Sep 2001 15:39:58 +0200 Date: Fri, 21 Sep 2001 15:39:58 +0200 From: Christoph Hellwig To: Bryan-TheBS-Smith Cc: kris buggenhout , "linux-xfs@oss.sgi.com" Subject: Re: XFS to main kernel source Message-ID: <20010921153958.A17527@caldera.de> References: <3BAB119A.29888F3D@god.bel.alcatel.be> <3BAB3018.CFE4290C@ieee.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BAB3018.CFE4290C@ieee.org>; from b.j.smith@ieee.org on Fri, Sep 21, 2001 at 08:18:32AM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Sep 21, 2001 at 08:18:32AM -0400, Bryan-TheBS-Smith wrote: > JFS seems to be lacking as much compatibility as ReiserFS. > Something tells me that this is because it was a port from OS/2 > rather than AIX's version??? I haven't used or tested JFS so I'm > making these statements blind. Feel free to rebuke me on this, I > just looked at its feature list, what was missing and dismissed it > from any consideration. JFS/Linux is based on JFS for OS/2. JFS2 for AIX5 is based on JFS for OS/2 as well. > I take it it is not OSS? ;-PPP It must be OSS or at least of > commodity cost to gain widespread acceptance, regardless of > superiority. There is a free VxFS driver in the Linux kernel driver (written by me), currently is is read-only, but that will change in the long-term. But's that's probably not the implementation he was refering to. Christoph -- Of course it doesn't work. We've performed a software upgrade. From owner-linux-xfs@oss.sgi.com Fri Sep 21 06:44:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LDirK23181 for linux-xfs-outgoing; Fri, 21 Sep 2001 06:44:53 -0700 Received: from ns.caldera.de (ns.caldera.de [212.34.180.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LDioe23162 for ; Fri, 21 Sep 2001 06:44:51 -0700 Received: (from hch@localhost) by ns.caldera.de (8.11.1/8.11.1) id f8LDibK18677; Fri, 21 Sep 2001 15:44:37 +0200 Date: Fri, 21 Sep 2001 15:44:37 +0200 From: Christoph Hellwig To: kris buggenhout Cc: Bryan-TheBS-Smith , "linux-xfs@oss.sgi.com" Subject: Re: XFS to main kernel source Message-ID: <20010921154437.B17527@caldera.de> References: <3BAB119A.29888F3D@god.bel.alcatel.be> <3BAB3018.CFE4290C@ieee.org> <3BAB3DE5.2C94E1C2@god.bel.alcatel.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BAB3DE5.2C94E1C2@god.bel.alcatel.be>; from buggenkr@god.bel.alcatel.be on Fri, Sep 21, 2001 at 03:17:25PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Sep 21, 2001 at 03:17:25PM +0200, kris buggenhout wrote: > I am not talking of the jfs they have out, Enterprise storage manager is > built on lvm and jfs from AIX.. this has not yet been released into OSS, > but will be. You're talking crap. JFS1 for AIX is so deep integrated into the AIX VM architecture that porting doesn't make sense at all. In AIX5 it is replaced by JFS2 that has the same JFS for OS/2 root as JFS for Linux. Christoph P.S. this is _really_ getting offtopic From owner-linux-xfs@oss.sgi.com Fri Sep 21 07:15:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LEFGa23889 for linux-xfs-outgoing; Fri, 21 Sep 2001 07:15:16 -0700 Received: from bbaer.muenster.de (bbaer.muenster.de [195.202.32.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LEFDe23870 for ; Fri, 21 Sep 2001 07:15:13 -0700 Received: from server.nick.de (mueasa-wan145.citykom.de [195.202.34.145]) by bbaer.muenster.de (8.9.3/8.9.3) with ESMTP id QAA04680 for ; Fri, 21 Sep 2001 16:15:11 +0200 X-Authentication-Warning: bbaer.muenster.de: Host mueasa-wan145.citykom.de [195.202.34.145] claimed to be server.nick.de Received: from there (linux.nick.de [192.168.1.1]) by server.nick.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with SMTP id MAA22042 for ; Fri, 21 Sep 2001 12:25:31 +0200 Message-Id: <200109211025.MAA22042@server.nick.de> Content-Type: text/plain; charset="iso-8859-1" From: Nick (Gunnar) Bluth To: linux-xfs@oss.sgi.com Subject: Re: gcc-2.96-nn status Date: Fri, 21 Sep 2001 13:46:13 +0200 X-Mailer: KMail [version 1.3.1] References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010919010548.0335ae28@pop.xs4all.nl> <1000856809.22994.50.camel@scare> In-Reply-To: <1000856809.22994.50.camel@scare> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Mittwoch, 19. September 2001 01:46 schrieb Russell Cattelan: > > True, but I gather 3.0+ will pop up in a lot more distributions then just > > redhat and mandrake. > > 3.0 is a official release which means it is not distribution specific. > > The reason that mandrake adopted is was more or less because a lot of > > mandrake is still redhat based. (no flame intended) > > Given how far ahead of Redhat Mandrake is I doubt that is true anymore. Well, about 50% of it is maintained by Bero (Red Hat Germany).... BTW: 7.2 Final has gcc3 with it (but optional) Nick -- Nick (Gunnar) Bluth Muenster/Germany bluth@muenster.de RHCE/RHCX +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ In 1984 mainstream users were choosing VMS over UNIX. Ten years later they are choosing Windows over UNIX. What part of that message aren't you getting? - Tom Payne From owner-linux-xfs@oss.sgi.com Fri Sep 21 07:19:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LEJhs24112 for linux-xfs-outgoing; Fri, 21 Sep 2001 07:19:43 -0700 Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LEJbe24093 for ; Fri, 21 Sep 2001 07:19:39 -0700 Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226]) by math.psu.edu (8.9.3/8.9.3) with ESMTP id KAA00434; Fri, 21 Sep 2001 10:19:34 -0400 (EDT) Received: from localhost (viro@localhost) by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id KAA08314; Fri, 21 Sep 2001 10:19:33 -0400 (EDT) X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs Date: Fri, 21 Sep 2001 10:19:33 -0400 (EDT) From: Alexander Viro To: Steve Lord cc: hch@sgi.com, Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source In-Reply-To: <200109202131.f8KLVbB19795@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 20 Sep 2001, Steve Lord wrote: > Two answers here - economics and code stability. This is a filesystem > which has been worked on by people being payed to do so by a corporation, > therefore there is a budget (long since blown). It was simpler and hence > cheaper to wrap XFS in a conversion layer than to rework the code down > into the bowels of the filesystem. Then the stability part of it, we > started with a working filesystem, from an engineering standpoint it > made more sense to keep as much of the existing code base intact as > possible - the less surgery performed the better in terms of keeping > things running, and making it easy to take enhancements and fixes made > in the Irix base into the Linux code (we don't do it the other way around). True, but there's a cost of maintaining the source and reducing the size of said source by order of magnitude will help to reduce _that_. The argument would make sense if you were treating everything under your compatibility layer as a black box, but I sincerely hope that it's not the case. > > o checks already peformed by the VFS all over the place > > (just take a look at xfs_rename.c!) > > I think I will answer this one more slowly and in response to Al Viro's > email. But that economics/stability thing comes into it again. Looking forward to that... Just documenting the exclusion requirements of CXFS would help. Big way. As it is, you are bordering on the "adding undocumented API for proprietory module" and while I've got no problems with the last part (I don't suffer from stallmanellosis), I really don't like the first one. Nobody's asking to give up the guts of CXFS, but having its exclusion requirements documented is a different story. From owner-linux-xfs@oss.sgi.com Fri Sep 21 07:46:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LEkKQ24724 for linux-xfs-outgoing; Fri, 21 Sep 2001 07:46:20 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LEkGe24705 for ; Fri, 21 Sep 2001 07:46:16 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8LEk9l25535 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Fri, 21 Sep 2001 07:46:09 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA950325 for ; Fri, 21 Sep 2001 16:46:11 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA3023098; Fri, 21 Sep 2001 09:44:50 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA93435; Fri, 21 Sep 2001 09:44:50 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8LEjlW24891; Fri, 21 Sep 2001 09:45:47 -0500 Message-Id: <200109211445.f8LEjlW24891@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Alexander Viro cc: Steve Lord , hch@ns.caldera.de, Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source In-Reply-To: Message from Alexander Viro of "Fri, 21 Sep 2001 10:19:33 EDT." Date: Fri, 21 Sep 2001 09:45:47 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > > On Thu, 20 Sep 2001, Steve Lord wrote: > > > Two answers here - economics and code stability. This is a filesystem > > which has been worked on by people being payed to do so by a corporation, > > therefore there is a budget (long since blown). It was simpler and hence > > cheaper to wrap XFS in a conversion layer than to rework the code down > > into the bowels of the filesystem. Then the stability part of it, we > > started with a working filesystem, from an engineering standpoint it > > made more sense to keep as much of the existing code base intact as > > possible - the less surgery performed the better in terms of keeping > > things running, and making it easy to take enhancements and fixes made > > in the Irix base into the Linux code (we don't do it the other way around). > > True, but there's a cost of maintaining the source and reducing the > size of said source by order of magnitude will help to reduce _that_. Well there is not an order of magnitude in it, and it then leaves SGI in the situation of having two even more divergent versions of XFS than we have now. I do realise there are two conflicting goals in all of this. > > The argument would make sense if you were treating everything under > your compatibility layer as a black box, but I sincerely hope that > it's not the case. Well, not everything, but the vast majority of the xfs code has not had to change at all, we have a different buffer cache interface, and the read/write path is different, and the inode creation/teardown interface needed surgery to work with linux inodes, oh and endian conversion. But apart from that ...... > > > > o checks already peformed by the VFS all over the place > > > (just take a look at xfs_rename.c!) > > > > I think I will answer this one more slowly and in response to Al Viro's > > email. But that economics/stability thing comes into it again. > > Looking forward to that... Just documenting the exclusion requirements > of CXFS would help. Big way. As it is, you are bordering on the "adding > undocumented API for proprietory module" and while I've got no problems > with the last part (I don't suffer from stallmanellosis), I really don't > like the first one. Nobody's asking to give up the guts of CXFS, but > having its exclusion requirements documented is a different story. Working on the locking first, the tricky part is how locks interact with the transaction mechanism. Steve From owner-linux-xfs@oss.sgi.com Fri Sep 21 07:59:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LExNl25086 for linux-xfs-outgoing; Fri, 21 Sep 2001 07:59:23 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LExLe25067 for ; Fri, 21 Sep 2001 07:59:21 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8LExGl26904 for ; Fri, 21 Sep 2001 07:59:16 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2957662; Fri, 21 Sep 2001 09:58:00 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA20012; Fri, 21 Sep 2001 09:57:59 -0500 (CDT) Message-ID: <3BAB5535.1BD8EE59@sgi.com> Date: Fri, 21 Sep 2001 09:56:53 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Jim Eshleman CC: "'linux-xfs@oss.sgi.com'" Subject: Re: Bad write page, under 2.4.9 kernel References: <414DB4427DE6D411846200B0D078E84B169DD1@uk-exch.magma-da.com> <3BAA1C91.31E8B65D@sgi.com> <3BAB3DF2.CDD1658C@Lehigh.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jim Eshleman wrote: > In my case the "Bad write on page" always preceeds "Warning: buffer > ... with weird blockno" and then a pair of "kernel BUG at ll_rw_blk.c" > errors. Attached is the syslog output from the most recent, 2.4.9 + > linux-2.4.9-xfs-2001-08-26.patch. Any ideas if this is XFS, 2.4 VM bug, > something else? Hm.... ok I have a 2.4.9 system up and running now, what do you do to hit this error? Is it easy to reproduce? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Sep 21 08:05:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LF56725384 for linux-xfs-outgoing; Fri, 21 Sep 2001 08:05:06 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LF54e25365 for ; Fri, 21 Sep 2001 08:05:04 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8LF4wj08720 for ; Fri, 21 Sep 2001 08:04:58 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA3030976; Fri, 21 Sep 2001 10:03:43 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA04906; Fri, 21 Sep 2001 10:03:42 -0500 (CDT) Message-ID: <3BAB568C.AE3A0C35@sgi.com> Date: Fri, 21 Sep 2001 10:02:36 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: joelm@ramhb.co.nz CC: linux-xfs@oss.sgi.com Subject: Re: /var disappears ! References: <3BAB3CF2.12827.6C1B9A26@localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Joel Macklow wrote: > We can supply SSH details for an engineer if so > desired. Hi Joel - That might be helpful, problem is finding time to do it... we're getting spread thin around here. :) Any chance you could hook up a serial console to the box? That would make debugging easier. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Sep 21 08:09:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LF9BO25621 for linux-xfs-outgoing; Fri, 21 Sep 2001 08:09:11 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LF99e25602 for ; Fri, 21 Sep 2001 08:09:09 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8LF93j08924 for ; Fri, 21 Sep 2001 08:09:03 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA3031366; Fri, 21 Sep 2001 10:07:48 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA56165; Fri, 21 Sep 2001 10:07:47 -0500 (CDT) Message-ID: <3BAB5780.3CD71F41@sgi.com> Date: Fri, 21 Sep 2001 10:06:40 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Ivan Ivanov CC: linux-xfs@oss.sgi.com Subject: Re: "crash tests" References: <3BAADA85.FD679D05@vamo.orbitel.bg> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ivan Ivanov wrote: > I have made some "crash tests" of ext2,ext3, ReiserFS and XFS. The > situation with XFS looks strange. I 'll show two cases: Hi Ivan - The short answer is at http://oss.sgi.com/projects/xfs/faq.html#nulls However, the fact that you don't see this behavior on other filesystems warrants some investigation... something I'd like to do when priorites allow... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Sep 21 08:22:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LFMJV25937 for linux-xfs-outgoing; Fri, 21 Sep 2001 08:22:19 -0700 Received: from rain.CC.Lehigh.EDU (rain.CC.Lehigh.EDU [128.180.39.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LFMGe25918 for ; Fri, 21 Sep 2001 08:22:16 -0700 Received: from Lehigh.EDU (hooch.CC.Lehigh.EDU [128.180.3.11]) by rain.CC.Lehigh.EDU (8.11.5/8.11.5) with ESMTP id f8LFL5T06039; Fri, 21 Sep 2001 11:21:11 -0400 Message-ID: <3BAB57EB.59A2E22B@Lehigh.EDU> Date: Fri, 21 Sep 2001 11:08:27 -0400 From: Jim Eshleman X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Eric Sandeen CC: "'linux-xfs@oss.sgi.com'" Subject: Re: Bad write page, under 2.4.9 kernel References: <414DB4427DE6D411846200B0D078E84B169DD1@uk-exch.magma-da.com> <3BAA1C91.31E8B65D@sgi.com> <3BAB3DF2.CDD1658C@Lehigh.EDU> <3BAB5535.1BD8EE59@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > > Jim Eshleman wrote: > > > In my case the "Bad write on page" always preceeds "Warning: buffer > > ... with weird blockno" and then a pair of "kernel BUG at ll_rw_blk.c" > > errors. Attached is the syslog output from the most recent, 2.4.9 + > > linux-2.4.9-xfs-2001-08-26.patch. Any ideas if this is XFS, 2.4 VM bug, > > something else? > > Hm.... ok I have a 2.4.9 system up and running now, what do you do to > hit this error? Is it easy to reproduce? Okay, get about 5,000 users or so to hit it with POP/IMAP connections and use it as their incoming/outgoing SMTP server :-) No, sorry, it's not easy to reproduce. I've not been able to pinpoint anything that triggers the error. It has happened once early in the AM during automated backup, and twice in the evening (5-7PM) when the load is moderate. It has not happened during working hours yet, when load is highest. From my previous e-mail in this thread: > I also am seeing the "Bad write on page" errors. Attached is syslog > info from two incidents. The first was after three weeks uptime, the > second was after one week uptime. The system is a heavily-loaded mail > server, IBM Netfinity x370 8-way PIII Xeon, 8.5GB RAM (HIGHMEM enabled) > running 2.4.9 + patch-2.4.9-xfs-2001-08-17 compiled with egcs-2.91.66. > The XFS filesystems are on top of LVM, on top of hardware RAID1E. After > the errors the system becomes unresponsive. I suspected a 2.4 VM bug > but searching LKML archives turns up no hits, so maybe it is XFS > related. I also saw the error after six hours running 2.4.9 + > linux-2.4.9-xfs-2001-08-26.patch. Jim From owner-linux-xfs@oss.sgi.com Fri Sep 21 08:52:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LFqWQ26523 for linux-xfs-outgoing; Fri, 21 Sep 2001 08:52:32 -0700 Received: from mail.teatime.com.tw (mail.teatime.com.tw [210.241.226.252]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LFqSe26498 for ; Fri, 21 Sep 2001 08:52:28 -0700 Received: from localhost ([127.0.0.1] helo=mail.teatime.com.tw ident=root) by mail.teatime.com.tw with smtp (Exim 3.32 #1 (Debian)) id 15kSbF-0004E7-00 for ; Fri, 21 Sep 2001 23:52:21 +0800 Received: from p176.inside ([192.168.0.176]) by mail.teatime.com.tw (TeaTime Mail Server 0.6.4) with SMTP id spool/smahDCv2a for ; Fri, 21 Sep 01 23:51:39 +0800 Date: Fri, 21 Sep 2001 23:53:17 +0800 From: Tommy Wu To: linux-xfs@oss.sgi.com Subject: kernel error for xfs_force_shutdown ? Reply-To: tommy@teatime.com.tw Organization: TeaTime Development Message-Id: <20010921233921.60E2.NEWSLETTER@teatime.com.tw> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.00.07 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi! I got the some message like in my log. Sep 18 15:13:35 hisdb kernel: xfs_force_shutdown(sd(8,17),0x8) called from line 4072 of file xfs_bmap.c. Return address = 0xc0188c64 Sep 18 15:13:35 hisdb kernel: Corruption of in-memory data detected. Shutting down filesystem: sd(8,17) Sep 18 15:13:35 hisdb kernel: Please umount the filesystem, and rectify the problem(s) Sep 21 20:09:21 hisdb kernel: xfs_force_shutdown(sd(8,17),0x8) called from line 4072 of file xfs_bmap.c. Return address = 0xc0188c64 Sep 21 20:09:21 hisdb kernel: Corruption of in-memory data detected. Shutting down filesystem: sd(8,17) Sep 21 20:09:21 hisdb kernel: Please umount the filesystem, and rectify the problem(s) Is there something wrong ? This machine running over 1 month. This message display in this week.... My hardward: PIII 1Gx2, 1G ram, SCSI U160 x 2 channel, 1 x 9.1G scsi hdd, 1 hardward RAID (6xxG) Software: Debain GNU/Linux woody, kernel 2.4.9 with XFS patch, oracle 9.0.1, heartbeat -- Tommy Wu mailto:tommy@teatime.com.tw http://www.teatime.com.tw/~tommy ICQ: 22766091 Mobile Phone: +886 936 909490 TeaTime BBS +886 2 31515964 24Hrs V.Everything From owner-linux-xfs@oss.sgi.com Fri Sep 21 08:54:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LFsYT26704 for linux-xfs-outgoing; Fri, 21 Sep 2001 08:54:34 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LFsWe26682 for ; Fri, 21 Sep 2001 08:54:32 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA13076 for ; Fri, 21 Sep 2001 08:54:34 -0700 (PDT) mail_from (eric@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA3031615 for ; Fri, 21 Sep 2001 10:53:15 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA51974 for ; Fri, 21 Sep 2001 10:53:15 -0500 (CDT) Received: by stout.americas.sgi.com (8.11.2/SGI-client-1.7) id f8LFq8700436; Fri, 21 Sep 2001 10:52:08 -0500 Message-Id: <200109211552.f8LFq8700436@stout.americas.sgi.com> Date: Fri, 21 Sep 2001 10:52:08 -0500 From: Eric Sandeen Subject: TAKE - Merge irix6.5f:irix:102826a Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Fri Sep 21 08:52:43 PDT 2001 Workarea: stout.americas.sgi.com:/localhome/eric/2.4.x-xfs/workarea-clean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103218a linux/fs/xfs/xfs_dmapi.c - 1.38 - Merge irix6.5f:irix:102826a Add do/while loop around the dm_send_data_event() call in xfs_dm_send_data_event() to verify that the event has not been reset in the event mask while obtaining the xfs locks. Remove the behavior lock/unlock which was unnecessary. The behavior cannot be unlocked while sending the the DMAPI event without opening the possibility that the vnode will be exported. Fix for bug 831666. From owner-linux-xfs@oss.sgi.com Fri Sep 21 09:19:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LGJxv27278 for linux-xfs-outgoing; Fri, 21 Sep 2001 09:19:59 -0700 Received: from mail.microdiscovery.de (postfix@gap.microdiscovery.de [195.143.236.170]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LGJse27259 for ; Fri, 21 Sep 2001 09:19:54 -0700 Subject: Re: question: xfs + lvm + kernel 2.4.9 From: Bartosch Pixa To: "Martin K. Petersen" Cc: linux-xfs@oss.sgi.com In-Reply-To: References: <3BAA08FB.3080204@microdiscovery.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 21 Sep 2001 18:19:40 +0200 Message-Id: <1001089180.19204.4.camel@bad> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 2001-09-20 at 19:02, Martin K. Petersen wrote: > >>>>> "Bartosch" == Bartosch Pixa writes: > > Bartosch> i'm trying to get a kernel 2.4.9 working with XFS and LVM > Bartosch> 1.0.1-rc2, i got some errors after aplying the XFS patch > Bartosch> (linux-2.4.9-xfs-2001-08-26.patch) to a already LVM patched > Bartosch> kernel, the errors were only in the LVM parts of the kernel, > Bartosch> so my question is now if it's sane to ignore these errors or > Bartosch> if there are issues with XFS and LVM. > > 1.0.1-rc3 should be out next week. I would recommend you hold off > until then. thx for the info, i sure will, but still there is the question if there are any problems with lvm and xfs (the rejecter files during the patch for example) thx for the help -- Bartosch Pixa, bartosch.pixa@microdiscovery.de MicroDiscovery GmbH Immanuelkirchstr. 12, D-10405 Berlin, Germany Tel.: +49-(0)30-44350900, Fax: +49-(0)30-443509010 From owner-linux-xfs@oss.sgi.com Fri Sep 21 10:01:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LH1ta28017 for linux-xfs-outgoing; Fri, 21 Sep 2001 10:01:55 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LH1Ye27996 for ; Fri, 21 Sep 2001 10:01:34 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8LH1Sl06850 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Fri, 21 Sep 2001 10:01:28 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id TAA966994 for ; Fri, 21 Sep 2001 19:01:29 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA3035681 for ; Fri, 21 Sep 2001 12:00:09 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA46695 for ; Fri, 21 Sep 2001 12:00:09 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id f8LH16o06696; Fri, 21 Sep 2001 12:01:06 -0500 Message-Id: <200109211701.f8LH16o06696@jen.americas.sgi.com> Date: Fri, 21 Sep 2001 12:01:06 -0500 Subject: TAKE - merge up to 2.4.10-pre12 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk OK, took a little time to study the VM changes and find a buffer leak in XFS. Everything appears to be working now, stands up to heavy stress, passes regression tests. And yes I know pre13 is out already. Date: Fri Sep 21 09:28:50 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge1 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103220a linux/scripts/mkversion - 1.1 linux/scripts/mkspec - 1.1 linux/drivers/ide/ataraid.h - 1.1 linux/drivers/net/pcmcia/xircom_cb.c - 1.1 linux/drivers/ide/pdcraid.h - 1.1 linux/drivers/ide/pdcraid.c - 1.1 linux/drivers/ide/hptraid.h - 1.1 linux/drivers/ide/hptraid.c - 1.1 linux/drivers/ide/ataraid.c - 1.1 linux/lib/rbtree.c - 1.1 linux/include/linux/nmi.h - 1.1 linux/include/linux/rbtree.h - 1.1 linux/arch/i386/kernel/nmi.c - 1.1 linux/lib/bust_spinlocks.c - 1.1 linux/net/netsyms.c - 1.37 linux/net/ipv6/ip6_output.c - 1.12 linux/net/ipv4/tcp.c - 1.31 linux/net/core/dev.c - 1.42 linux/mm/vmscan.c - 1.74 linux/mm/vmalloc.c - 1.32 linux/mm/swapfile.c - 1.37 linux/mm/swap_state.c - 1.29 linux/mm/swap.c - 1.12 linux/mm/slab.c - 1.27 linux/mm/page_io.c - 1.16 linux/mm/page_alloc.c - 1.53 linux/mm/mremap.c - 1.23 linux/mm/mprotect.c - 1.16 linux/mm/mmap_avl.c - 1.3 linux/mm/mmap.c - 1.40 linux/mm/mlock.c - 1.15 linux/mm/memory.c - 1.60 linux/mm/filemap.c - 1.86 linux/lib/Makefile - 1.8 linux/kernel/sysctl.c - 1.41 linux/kernel/sys.c - 1.25 linux/kernel/signal.c - 1.19 linux/kernel/sched.c - 1.40 linux/kernel/printk.c - 1.13 linux/kernel/panic.c - 1.14 linux/kernel/ksyms.c - 1.109 linux/kernel/fork.c - 1.37 linux/kernel/Makefile - 1.25 linux/include/linux/timer.h - 1.10 linux/include/linux/sysrq.h - 1.5 linux/include/linux/sysctl.h - 1.37 linux/include/linux/swapctl.h - 1.3 linux/include/linux/swap.h - 1.39 linux/include/linux/slab.h - 1.17 linux/include/linux/sched.h - 1.44 linux/include/linux/pci.h - 1.48 linux/include/linux/pagemap.h - 1.29 linux/include/linux/mm.h - 1.64 linux/include/linux/major.h - 1.28 linux/include/linux/loop.h - 1.5 linux/include/linux/list.h - 1.8 linux/include/linux/kernel.h - 1.26 linux/include/linux/kbd_kern.h - 1.7 linux/include/linux/fs.h - 1.119 linux/include/linux/ext2_fs_i.h - 1.4 linux/include/linux/elf.h - 1.14 linux/include/linux/console.h - 1.7 linux/include/linux/blkdev.h - 1.38 linux/include/asm-sparc64/processor.h - 1.18 linux/include/asm-sparc64/fcntl.h - 1.11 linux/include/asm-sparc/processor.h - 1.14 linux/include/asm-sparc/fcntl.h - 1.11 linux/include/asm-ppc/processor.h - 1.28 linux/include/asm-mips/processor.h - 1.17 linux/include/asm-m68k/processor.h - 1.12 linux/include/asm-i386/processor.h - 1.28 linux/include/asm-i386/page.h - 1.19 linux/include/asm-i386/irq.h - 1.4 linux/include/asm-i386/fcntl.h - 1.8 linux/include/asm-arm/processor.h - 1.18 linux/include/asm-alpha/processor.h - 1.13 linux/include/asm-alpha/fcntl.h - 1.10 linux/fs/super.c - 1.55 linux/fs/proc/kmsg.c - 1.7 linux/fs/open.c - 1.31 linux/fs/namei.c - 1.38 linux/fs/inode.c - 1.52 linux/fs/file_table.c - 1.16 linux/fs/fcntl.c - 1.16 linux/fs/ext2/inode.c - 1.29 linux/fs/ext2/fsync.c - 1.11 linux/fs/ext2/dir.c - 1.17 linux/fs/exec.c - 1.47 linux/fs/devices.c - 1.15 linux/fs/dcache.c - 1.28 linux/fs/buffer.c - 1.82 linux/fs/block_dev.c - 1.25 linux/drivers/video/fbcon.c - 1.22 linux/drivers/sound/sb_card.c - 1.27 linux/drivers/scsi/mesh.c - 1.10 linux/drivers/scsi/megaraid.c - 1.27 linux/drivers/sbus/char/sunkbd.c - 1.17 linux/drivers/pci/quirks.c - 1.24 linux/drivers/pci/pci.c - 1.43 linux/drivers/net/eepro100.c - 1.32 linux/drivers/net/bmac.c - 1.15 linux/drivers/net/Makefile - 1.46 linux/drivers/net/Config.in - 1.46 linux/drivers/net/3c59x.c - 1.29 linux/drivers/macintosh/mac_keyb.c - 1.15 linux/drivers/macintosh/adb.c - 1.12 linux/drivers/char/vt.c - 1.21 linux/drivers/char/vc_screen.c - 1.11 linux/drivers/char/tty_ioctl.c - 1.5 linux/drivers/char/sysrq.c - 1.16 linux/drivers/char/serial.c - 1.48 linux/drivers/char/random.c - 1.18 linux/drivers/char/pc_keyb.c - 1.25 linux/drivers/char/keyboard.c - 1.21 linux/drivers/char/console.c - 1.24 linux/drivers/block/rd.c - 1.34 linux/drivers/block/loop.c - 1.36 linux/drivers/block/ll_rw_blk.c - 1.75 linux/arch/sparc64/kernel/ptrace.c - 1.12 linux/arch/sparc64/kernel/init_task.c - 1.5 linux/arch/sparc/lib/debuglocks.c - 1.6 linux/arch/sparc/kernel/ptrace.c - 1.12 linux/arch/sparc/kernel/init_task.c - 1.4 linux/arch/ppc/kernel/ptrace.c - 1.11 linux/arch/ppc/kernel/process.c - 1.31 linux/arch/ppc/kernel/ppc_ksyms.c - 1.35 linux/arch/ppc/amiga/config.c - 1.12 linux/arch/ppc/Makefile - 1.21 linux/arch/mips/kernel/ptrace.c - 1.13 linux/arch/mips/kernel/init_task.c - 1.5 linux/arch/m68k/kernel/ptrace.c - 1.10 linux/arch/m68k/kernel/process.c - 1.12 linux/arch/i386/mm/fault.c - 1.19 linux/arch/i386/mm/extable.c - 1.5 linux/arch/i386/lib/usercopy.c - 1.6 linux/arch/i386/kernel/traps.c - 1.39 linux/arch/i386/kernel/time.c - 1.17 linux/arch/i386/kernel/smp.c - 1.34 linux/arch/i386/kernel/setup.c - 1.54 linux/arch/i386/kernel/ptrace.c - 1.17 linux/arch/i386/kernel/process.c - 1.34 linux/arch/i386/kernel/irq.c - 1.36 linux/arch/i386/kernel/io_apic.c - 1.29 linux/arch/i386/kernel/init_task.c - 1.6 linux/arch/i386/kernel/i386_ksyms.c - 1.41 linux/arch/i386/kernel/apm.c - 1.33 linux/arch/i386/kernel/Makefile - 1.22 linux/arch/i386/defconfig - 1.71 linux/arch/i386/config.in - 1.60 linux/arch/arm/kernel/ptrace.c - 1.14 linux/arch/arm/kernel/init_task.c - 1.6 linux/arch/alpha/mm/fault.c - 1.14 linux/arch/alpha/kernel/traps.c - 1.15 linux/arch/alpha/kernel/ptrace.c - 1.12 linux/arch/alpha/kernel/process.c - 1.18 linux/arch/alpha/kernel/irq.c - 1.20 linux/Makefile - 1.124 linux/Documentation/sysrq.txt - 1.11 linux/Documentation/Configure.help - 1.99 linux/Documentation/Changes - 1.41 linux/drivers/block/cpqarray.c - 1.29 linux/kernel/ptrace.c - 1.15 linux/drivers/char/raw.c - 1.18 linux/include/asm-i386/apic.h - 1.13 linux/include/linux/irq.h - 1.9 linux/include/asm-i386/hw_irq.h - 1.20 linux/arch/i386/kernel/i8259.c - 1.23 linux/arch/sh/kernel/ptrace.c - 1.11 linux/arch/sh/kernel/init_task.c - 1.2 linux/include/asm-sh/processor.h - 1.15 linux/include/asm-i386/kmap_types.h - 1.5 linux/drivers/pcmcia/i82365.c - 1.20 linux/drivers/net/pcmcia/Makefile - 1.18 linux/drivers/net/pcmcia/Config.in - 1.24 linux/arch/i386/kernel/smpboot.c - 1.22 linux/Documentation/nmi_watchdog.txt - 1.4 linux/mm/highmem.c - 1.26 linux/mm/bootmem.c - 1.16 linux/include/linux/highmem.h - 1.14 linux/fs/proc/proc_misc.c - 1.21 linux/include/asm-i386/pgalloc.h - 1.11 linux/mm/numa.c - 1.9 linux/include/linux/mmzone.h - 1.17 linux/include/linux/cache.h - 1.2 linux/drivers/net/aironet4500_proc.c - 1.8 linux/drivers/net/aironet4500_core.c - 1.15 linux/drivers/net/aironet4500_card.c - 1.13 linux/drivers/char/agp/agpgart_be.c - 1.24 linux/drivers/char/agp/agp.h - 1.16 linux/drivers/usb/scanner.c - 1.23 linux/arch/i386/kernel/apic.c - 1.19 linux/arch/i386/kernel/mpparse.c - 1.12 linux/include/asm-i386/mpspec.h - 1.5 linux/include/asm-i386/io_apic.h - 1.4 linux/drivers/usb/usb-uhci.c - 1.28 linux/drivers/usb/scanner.h - 1.15 linux/drivers/atm/iphase.c - 1.11 linux/arch/ia64/kernel/init_task.c - 1.2 linux/arch/ia64/kernel/ptrace.c - 1.12 linux/drivers/scsi/qla1280.h - 1.2 linux/drivers/net/gmac.c - 1.10 linux/drivers/net/gmac.h - 1.5 linux/include/asm-ia64/processor.h - 1.13 linux/drivers/video/sun3fb.c - 1.6 linux/include/linux/lvm.h - 1.10 linux/include/asm-mips64/processor.h - 1.10 linux/arch/mips64/mm/fault.c - 1.9 linux/arch/mips64/kernel/init_task.c - 1.2 linux/arch/mips64/kernel/ptrace.c - 1.8 linux/arch/alpha/kernel/irq_alpha.c - 1.7 linux/drivers/usb/wacom.c - 1.14 linux/drivers/ide/ide.c - 1.30 linux/drivers/ide/Makefile - 1.11 linux/drivers/ide/Config.in - 1.14 linux/Documentation/DocBook/Makefile - 1.18 linux/arch/s390/kernel/init_task.c - 1.2 linux/include/asm-s390/processor.h - 1.7 linux/arch/s390/kernel/ptrace.c - 1.6 linux/arch/i386/kernel/msr.c - 1.11 linux/fs/xfs/xfs_qm.c - 1.70 linux/kdb/modules/kdbm_vm.c - 1.12 linux/include/linux/kdb.h - 1.17 linux/kdb/kdbmain.c - 1.20 linux/kdb/kdb_io.c - 1.8 linux/arch/i386/kdb/kdba_io.c - 1.13 linux/kdb/modules/kdbm_pg.c - 1.39 linux/fs/pagebuf/page_buf.c - 1.99 linux/fs/pagebuf/page_buf_io.c - 1.98 linux/drivers/usb/storage/scsiglue.c - 1.15 linux/include/asm-sparc/kmap_types.h - 1.4 linux/drivers/input/keybdev.c - 1.6 linux/drivers/md/lvm.c - 1.20 linux/drivers/block/cciss.c - 1.16 linux/drivers/macintosh/adbhid.c - 1.3 linux/drivers/md/md.c - 1.24 linux/include/asm-ppc/kmap_types.h - 1.6 linux/mm/oom_kill.c - 1.6 linux/include/asm-parisc/processor.h - 1.4 linux/arch/i386/kernel/dmi_scan.c - 1.7 linux/arch/parisc/kernel/ptrace.c - 1.4 linux/arch/parisc/kernel/pdc_cons.c - 1.2 linux/drivers/sound/ymfpci.c - 1.10 linux/arch/parisc/kernel/init_task.c - 1.2 linux/mm/shmem.c - 1.13 linux/fs/reiserfs/inode.c - 1.12 linux/fs/reiserfs/file.c - 1.4 linux/include/asm-s390x/processor.h - 1.3 linux/arch/s390x/kernel/ptrace.c - 1.5 linux/arch/s390x/kernel/init_task.c - 1.2 linux/arch/cris/kernel/process.c - 1.7 linux/arch/cris/kernel/ptrace.c - 1.6 linux/include/asm-cris/processor.h - 1.5 linux/drivers/scsi/aic7xxx_old/aic7xxx_proc.c - 1.3 linux/drivers/scsi/aic7xxx_old.c - 1.7 linux/drivers/block/paride/bpck6.c - 1.2 linux/include/linux/compiler.h - 1.3 linux/drivers/net/irda/irda-usb.c - 1.7 linux/drivers/net/wireless/hermes.c - 1.4 linux/drivers/net/wireless/hermes.h - 1.4 linux/drivers/net/wireless/orinoco.c - 1.4 linux/drivers/net/wireless/orinoco.h - 1.4 linux/drivers/net/wireless/orinoco_cs.c - 1.6 linux/drivers/mtd/nand/Config.in - 1.4 linux/drivers/mtd/maps/Config.in - 1.2 linux/drivers/net/wireless/airo.c - 1.7 linux/drivers/char/sonypi.h - 1.2 linux/drivers/char/sonypi.c - 1.2 linux/drivers/ieee1394/nodemgr.c - 1.5 linux/Documentation/sound/btaudio - 1.2 linux/drivers/sound/btaudio.c - 1.3 linux/drivers/usb/CDCEther.c - 1.2 linux/include/linux/prefetch.h - 1.2 linux/drivers/net/ns83820.c - 1.2 From owner-linux-xfs@oss.sgi.com Fri Sep 21 10:31:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LHV1V28577 for linux-xfs-outgoing; Fri, 21 Sep 2001 10:31:01 -0700 Received: from web20204.mail.yahoo.com (web20204.mail.yahoo.com [216.136.226.59]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LHUwe28557 for ; Fri, 21 Sep 2001 10:30:58 -0700 Message-ID: <20010921173058.77098.qmail@web20204.mail.yahoo.com> Received: from [65.170.102.27] by web20204.mail.yahoo.com via HTTP; Fri, 21 Sep 2001 10:30:58 PDT Date: Fri, 21 Sep 2001 10:30:58 -0700 (PDT) From: Lee Go-Tze Subject: Re: XFS to main kernel source To: kris buggenhout , "linux-xfs@oss.sgi.com" In-Reply-To: <3BAB119A.29888F3D@god.bel.alcatel.be> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --- kris buggenhout wrote: > For the enterprose world I see Vxfs as a threat ... in unison with > volume manager.If Veritas pulls that off in a reasonable time > frame... a > lot of company's will opt for Vxfs and volume manager, because it > can be > used on almost all of their platforms : wincrap2k, Solaris, Irix, > Linux, > HPUX, AIX,... etc... But I doubt VxFS and VxVM will be GPL'ed or open source. Veritas hasn't made any move in that direction. GoTze __________________________________________________ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/ From owner-linux-xfs@oss.sgi.com Fri Sep 21 11:01:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LI1SQ29262 for linux-xfs-outgoing; Fri, 21 Sep 2001 11:01:28 -0700 Received: from gateway1.brets.elevating.com (adsl-216-63-236-137.dsl.tulsok.swbell.net [216.63.236.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LI1Me29243 for ; Fri, 21 Sep 2001 11:01:22 -0700 Received: from elevating.com (bretdell.brets.elevating.com [192.168.0.128]) by gateway1.brets.elevating.com (8.9.3/8.8.7) with ESMTP id NAA30140; Fri, 21 Sep 2001 13:01:21 -0500 Message-ID: <3BAB8071.BB917283@elevating.com> Date: Fri, 21 Sep 2001 13:01:21 -0500 From: Bret Hughes X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, ja MIME-Version: 1.0 To: linux-xfs Subject: mksf problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am unable to create a filesystem on a raid 5 volume on a compaq 3000. I finally(with the help of this list ) got XFS installed and running after hosing the MBR now I need to add an additional partition to this box with some of the left over space. I used fdisk /dev/ida/c0d0 to create a new 10GB partition and it appears to have worked: [root@compaq3 /sbin]# fdisk -l /dev/ida/c0d0 Disk /dev/ida/c0d0: 255 heads, 32 sectors, 8711 cylinders Units = cylinders of 8160 * 512 bytes Device Boot Start End Blocks Id System /dev/ida/c0d0p1 * 10 22 53040 83 Linux /dev/ida/c0d0p2 23 8711 35451120 5 Extended /dev/ida/c0d0p3 1 9 36704 12 Compaq diagnostics /dev/ida/c0d0p5 23 73 208064 82 Linux swap /dev/ida/c0d0p6 74 136 257024 83 Linux /dev/ida/c0d0p7 137 199 257024 83 Linux /dev/ida/c0d0p8 200 262 257024 83 Linux /dev/ida/c0d0p9 263 764 2048144 83 Linux /dev/ida/c0d0p10 765 2019 5120384 83 Linux /dev/ida/c0d0p11 2020 4529 10240784 83 Linux Partition table entries are not in disk order c0d0p11 is the new partition. when I try to create the filesytem I get this: [root@compaq3 /sbin]# mkfs -t xfs /dev/ida/c0d0p11 mkfs.xfs: cannot open /dev/ida/c0d0p11: No such device or address the device file is there: [root@compaq3 /sbin]# ls -l /dev/ida/c0d0* brw-rw---- 1 root disk 72, 0 Mar 23 22:37 /dev/ida/c0d0 brw-rw---- 1 root disk 72, 1 Mar 23 22:37 /dev/ida/c0d0p1 brw-rw---- 1 root disk 72, 10 Mar 23 22:37 /dev/ida/c0d0p10 brw-rw---- 1 root disk 72, 11 Mar 23 22:37 /dev/ida/c0d0p11 brw-rw---- 1 root disk 72, 12 Mar 23 22:37 /dev/ida/c0d0p12 brw-rw---- 1 root disk 72, 13 Mar 23 22:37 /dev/ida/c0d0p13 brw-rw---- 1 root disk 72, 14 Mar 23 22:37 /dev/ida/c0d0p14 brw-rw---- 1 root disk 72, 15 Mar 23 22:37 /dev/ida/c0d0p15 brw-rw---- 1 root disk 72, 2 Mar 23 22:37 /dev/ida/c0d0p2 brw-rw---- 1 root disk 72, 3 Mar 23 22:37 /dev/ida/c0d0p3 brw-rw---- 1 root disk 72, 4 Mar 23 22:37 /dev/ida/c0d0p4 brw-rw---- 1 root disk 72, 5 Mar 23 22:37 /dev/ida/c0d0p5 brw-rw---- 1 root disk 72, 6 Mar 23 22:37 /dev/ida/c0d0p6 brw-rw---- 1 root disk 72, 7 Mar 23 22:37 /dev/ida/c0d0p7 brw-rw---- 1 root disk 72, 8 Mar 23 22:37 /dev/ida/c0d0p8 brw-rw---- 1 root disk 72, 9 Mar 23 22:37 /dev/ida/c0d0p9 Any ideas about what am I doing wrong? I have a terrible cold and am under the influence of couch medicine so I may be missing something simple. Bret From owner-linux-xfs@oss.sgi.com Fri Sep 21 11:04:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LI4Mr29445 for linux-xfs-outgoing; Fri, 21 Sep 2001 11:04:22 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LI47e29422 for ; Fri, 21 Sep 2001 11:04:07 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8LI3xj05682 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Fri, 21 Sep 2001 11:04:00 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id UAA947521 for ; Fri, 21 Sep 2001 20:04:00 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA3036288; Fri, 21 Sep 2001 13:02:40 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA68875; Fri, 21 Sep 2001 13:02:35 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8LI3Vf32124; Fri, 21 Sep 2001 13:03:31 -0500 Message-Id: <200109211803.f8LI3Vf32124@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Alexander Viro cc: Steve Lord , Alan Cox , "Gonyou, Austin" , narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS to main kernel source In-Reply-To: Message from Alexander Viro of "Thu, 20 Sep 2001 16:40:51 EDT." Date: Fri, 21 Sep 2001 13:03:30 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I started writing this, and then got dragged in various other directions, so I am sending this out as a starting point - I will also be offline until Monday, we have to go to a wedding... so I am not ignoring responses, just probably not reading email. Steve > > > On Thu, 20 Sep 2001, Steve Lord wrote: > > > > > Since we have your attention - which chunks? One of the frustrations we hav > e > > had is the lack of feedback from anyone who has looked at XFS. > > Locking. There is a _lot_ of duplication between fs/namei.c and fs/xfs/* - > you definitely don't need most of the stuff you do with locks there. Looks like its time for the xfs locking tutorial.... I am going to walk through this in terms of the internal locks within XFS and how they interact. The XFS inode has two main locks, these are both multi reader, single writer sleep locks which have some semantics beyond those provided by the Linux i_sema lock. There is one other lock which could probably be removed on linux - it relates to readahead state, but we are not using the readahead code within XFS so.... the final lock is the flush lock which is used to synchronize flush activity on the inode (only one flush at once for an inode). These multireader locks have a couple of other things we can do with them - trylock and demote being the two we use right now I think. We have the ilock and the iolock. The ilock is used to protect the core of the inode, and the iolock is used to protect file data, the iolock is above the ilock in the locking hierarchy, but is obtained much less of the time. The ilock is closely tied in with the transaction system. In general the sequence of events when performing a transaction which modifies an inode in xfs is as follows: 1. obtain the ilock, do access & resource checks, fail the request if there are problems. 2. drop the ilock (we cannot hold the lock whilst doing the next step) 3. allocate a transaction and reserve the transaction space. The reason this cannot be performed with the lock is that reserving space in the log can require flushing metadata out to disk (to allow old log contents to be overwritten). In order to flush the metadata out to disk we need to ensure it is stable - which means we need a lock. So should an inode be at the tail of the log and we need to start another transaction on it, if we held the lock across the transaction reserve we have a deadlock. 4. relock the inode - reperform the checks, drop locks, cancel transaction and return error if things changed. 5. start metadata modifications - all objects are locked as required and remain locked until the transaction is committed. 6. commit transaction. This copies contents of the modified objects into an in core log buffer, the individual items are 'pinned' into memory - which prevents a disk write, and unlocked - which means new operations can access them. 7. write log buffer to disk, this is triggered by it being full, a sync transaction or filesystem sync activity (write_super). On completion of this we move the log items into something called the active item list and unpin them. 8. metadata flush, triggered by background flushing, or by step 3 above taking items from the active item list. The flush gets the ilock on inodes and the flush lock. The inode lock is held until the inode contents are updated in an inode buffer, the flush lock is held until the buffer write completes. 9. Metadate write completes - items are removed from the active item list and the tail of the log is moved if required. Threads waiting for log space (in step 3) are woken up. So, there are lots of places in xfs which use the ilock for synchronization between the top half - threads in system calls, and the bottom half - the flushing of metadata to disk. Attempting to replace the ilock in the xfs inode with the i_sema from the linux inode is not really a straightfoward task. This is really a little different from the rename checks performed by xfs. I suspect we can remove these, but really we cannot just blindly go replacing the ilock in the xfs inode with the i_sema and expect anything reasonable to happen. > > I understand that some of that stuff may be needed for CXFS, and I would > really like to see the description of locking requirements of that animal. Well, the main question here would be should cxfs have to go up to the top of the vfs layer in linux, or can it go straight into xfs. Moving some of the current locking out of xfs would mean the former. > > Parts that are needed only on IRIX since IRIX VFS is braindead should go. > Parts that can be moved to generic code should be moved (with sane set of > methods provided by filesystems a-la CXFS). The rest will become much simpler > . Brain dead is your term, I would go more for having a different design philosopy, but yes there is still code in xfs which is not needed under the linux vfs. I am not yet sure what could be regarded as generic, and I am not convinced making xfs simpler is as simple as you paint it as being. Steve From owner-linux-xfs@oss.sgi.com Fri Sep 21 11:35:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LIZeA30507 for linux-xfs-outgoing; Fri, 21 Sep 2001 11:35:40 -0700 Received: from rover (rover.mkp.net [209.217.122.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LIZae30488 for ; Fri, 21 Sep 2001 11:35:36 -0700 Received: from localhost.localdomain ([127.0.0.1] helo=jcb.mkp.net) by rover with esmtp (Exim 3.33 #1) id 15kV9C-0004FK-00; Fri, 21 Sep 2001 14:35:34 -0400 Received: (from mkp@localhost) by jcb.mkp.net (8.11.2/8.9.3) id f8LIZXc06275; Fri, 21 Sep 2001 14:35:33 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Bartosch Pixa Cc: linux-xfs@oss.sgi.com Subject: Re: question: xfs + lvm + kernel 2.4.9 References: <3BAA08FB.3080204@microdiscovery.de> <1001089180.19204.4.camel@bad> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 21 Sep 2001 14:35:33 -0400 In-Reply-To: <1001089180.19204.4.camel@bad> Message-ID: Lines: 18 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Bartosch" == Bartosch Pixa writes: >> 1.0.1-rc3 should be out next week. I would recommend you hold off >> until then. Bartosch> thx for the info, i sure will, but still there is the Bartosch> question if there are any problems with lvm and xfs (the Bartosch> rejecter files during the patch for example) Hard to tell when I haven't seen the errors. But apart from the snapshotting issues that are on my list of things to fix, no. I don't know of any problems. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Sep 21 12:31:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LJVjx31734 for linux-xfs-outgoing; Fri, 21 Sep 2001 12:31:45 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LJVYe31711 for ; Fri, 21 Sep 2001 12:31:34 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA04024 for ; Fri, 21 Sep 2001 12:30:13 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA3033355 for ; Fri, 21 Sep 2001 14:30:15 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA08511 for ; Fri, 21 Sep 2001 14:30:14 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id f8LJVAu32464; Fri, 21 Sep 2001 14:31:10 -0500 Message-Id: <200109211931.f8LJVAu32464@jen.americas.sgi.com> Date: Fri, 21 Sep 2001 14:31:10 -0500 Subject: TAKE - merge up to 2.4.10-pre13 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Here is the next one. Date: Fri Sep 21 12:28:42 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103243a linux/include/asm-sh/tlb.h - 1.1 linux/include/asm-s390x/tlb.h - 1.1 linux/include/asm-sparc/tlb.h - 1.1 linux/include/asm-s390/tlb.h - 1.1 linux/include/asm-m68k/tlb.h - 1.1 linux/include/asm-ia64/tlb.h - 1.1 linux/include/asm-i386/tlb.h - 1.1 linux/include/asm-sparc64/tlb.h - 1.1 linux/include/asm-generic/tlb.h - 1.1 linux/include/asm-arm/tlb.h - 1.1 linux/include/asm-alpha/tlb.h - 1.1 linux/net/unix/af_unix.c - 1.36 linux/net/sunrpc/xdr.c - 1.5 linux/net/sunrpc/sunrpc_syms.c - 1.10 linux/net/ipv6/route.c - 1.20 linux/net/ipv6/raw.c - 1.21 linux/net/ipv6/ipv6_sockglue.c - 1.13 linux/net/ipv6/ip6_output.c - 1.13 linux/net/ipv6/icmp.c - 1.16 linux/net/ipv4/tcp_timer.c - 1.21 linux/net/ipv4/tcp_output.c - 1.22 linux/net/ipv4/tcp_input.c - 1.29 linux/net/ipv4/tcp.c - 1.32 linux/net/ipv4/route.c - 1.26 linux/net/ipv4/ipmr.c - 1.19 linux/net/ipv4/ipip.c - 1.18 linux/net/ipv4/ip_sockglue.c - 1.16 linux/net/core/dev.c - 1.43 linux/mm/vmscan.c - 1.75 linux/mm/swapfile.c - 1.38 linux/mm/swap_state.c - 1.30 linux/mm/page_io.c - 1.17 linux/mm/page_alloc.c - 1.54 linux/mm/mremap.c - 1.24 linux/mm/mmap.c - 1.41 linux/mm/memory.c - 1.61 linux/mm/filemap.c - 1.87 linux/init/main.c - 1.58 linux/include/linux/sunrpc/xdr.h - 1.6 linux/include/linux/mm.h - 1.65 linux/include/linux/lockd/xdr.h - 1.5 linux/include/asm-sparc64/timex.h - 1.3 linux/include/asm-sparc64/processor.h - 1.19 linux/include/asm-sparc64/pgtable.h - 1.24 linux/include/asm-sparc64/fcntl.h - 1.12 linux/include/asm-sparc/processor.h - 1.15 linux/include/asm-sparc/fcntl.h - 1.12 linux/fs/proc/array.c - 1.31 linux/fs/nfsd/vfs.c - 1.37 linux/fs/nfsd/nfssvc.c - 1.15 linux/fs/nfsd/nfsfh.c - 1.31 linux/fs/nfsd/nfs3xdr.c - 1.20 linux/fs/nfsd/nfs3proc.c - 1.10 linux/fs/lockd/xdr.c - 1.10 linux/fs/devices.c - 1.16 linux/fs/buffer.c - 1.83 linux/fs/block_dev.c - 1.26 linux/drivers/video/tcxfb.c - 1.8 linux/drivers/video/leofb.c - 1.8 linux/drivers/video/creatorfb.c - 1.11 linux/drivers/video/cgthreefb.c - 1.9 linux/drivers/video/cgsixfb.c - 1.10 linux/drivers/video/cgfourteenfb.c - 1.11 linux/drivers/video/bwtwofb.c - 1.10 linux/drivers/usb/hub.c - 1.38 linux/drivers/net/yellowfin.c - 1.25 linux/drivers/net/Makefile - 1.47 linux/drivers/net/Config.in - 1.47 linux/drivers/fc4/soc.c - 1.9 linux/drivers/block/rd.c - 1.35 linux/drivers/block/ll_rw_blk.c - 1.76 linux/arch/sparc64/solaris/timod.c - 1.15 linux/arch/sparc64/solaris/misc.c - 1.20 linux/arch/sparc64/solaris/fs.c - 1.14 linux/arch/sparc64/mm/ultra.S - 1.18 linux/arch/sparc64/mm/init.c - 1.32 linux/arch/sparc64/lib/blockops.S - 1.13 linux/arch/sparc64/kernel/traps.c - 1.14 linux/arch/sparc64/kernel/trampoline.S - 1.8 linux/arch/sparc64/kernel/time.c - 1.15 linux/arch/sparc64/kernel/smp.c - 1.28 linux/arch/sparc64/kernel/setup.c - 1.20 linux/arch/sparc64/kernel/process.c - 1.21 linux/arch/sparc64/kernel/ioctl32.c - 1.43 linux/arch/sparc64/kernel/init_task.c - 1.6 linux/arch/sparc64/kernel/head.S - 1.11 linux/arch/sparc64/kernel/etrap.S - 1.6 linux/arch/sparc64/kernel/dtlb_base.S - 1.9 linux/arch/sparc64/kernel/dtlb_backend.S - 1.8 linux/arch/sparc64/defconfig - 1.49 linux/arch/sparc64/config.in - 1.44 linux/arch/sparc/mm/srmmu.c - 1.26 linux/arch/sparc/mm/init.c - 1.26 linux/arch/sparc/lib/debuglocks.c - 1.7 linux/arch/sparc/kernel/setup.c - 1.19 linux/arch/m68k/mm/init.c - 1.13 linux/arch/i386/mm/init.c - 1.30 linux/arch/alpha/mm/init.c - 1.19 linux/Makefile - 1.125 linux/Documentation/Configure.help - 1.100 linux/arch/sh/mm/init.c - 1.16 linux/drivers/net/starfire.c - 1.20 linux/drivers/net/ncr885e.h - 1.3 linux/drivers/net/ncr885e.c - 1.12 linux/drivers/net/ncr885_debug.h - 1.2 linux/arch/ia64/mm/init.c - 1.11 linux/fs/lockd/xdr4.c - 1.6 linux/drivers/net/tulip/tulip_core.c - 1.29 linux/net/ipv4/netfilter/ipfwadm_core.c - 1.8 linux/arch/s390/mm/init.c - 1.7 linux/net/ipv4/tcp_minisocks.c - 1.9 linux/drivers/md/md.c - 1.25 linux/mm/shmem.c - 1.14 linux/arch/s390x/mm/init.c - 1.3 linux/drivers/net/sungem.c - 1.8 linux/include/linux/sonypi.h - 1.2 linux/drivers/net/dl2k.h - 1.3 linux/Documentation/networking/dl2k.txt - 1.3 linux/drivers/net/dl2k.c - 1.4 linux/drivers/sound/btaudio.c - 1.4 linux/drivers/net/ns83820.c - 1.3 linux/include/linux/eeprom.h - 1.2 linux/arch/i386/kernel/nmi.c - 1.2 From owner-linux-xfs@oss.sgi.com Fri Sep 21 12:42:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LJgex32014 for linux-xfs-outgoing; Fri, 21 Sep 2001 12:42:40 -0700 Received: from zion.rivenstone.net (dhcp065-024-121-117.columbus.rr.com [65.24.121.117]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LJgae31981 for ; Fri, 21 Sep 2001 12:42:36 -0700 Received: from there (gibraltar.rivenstone.net [192.168.1.1]) by zion.rivenstone.net (Postfix) with SMTP id B7D0F4B570 for ; Fri, 21 Sep 2001 10:50:15 -0400 (EDT) Content-Type: text/plain; charset="iso-8859-1" From: Joseph Fannin To: linux-xfs@oss.sgi.com Subject: Re: TAKE - merge up to 2.4.10-pre13 Date: Fri, 21 Sep 2001 15:42:33 -0400 X-Mailer: KMail [version 1.3.1] References: <200109211931.f8LJVAu32464@jen.americas.sgi.com> In-Reply-To: <200109211931.f8LJVAu32464@jen.americas.sgi.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20010921145015.B7D0F4B570@zion.rivenstone.net> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Friday 21 September 2001 15:31, you wrote: > Here is the next one. > > Date: Fri Sep 21 12:28:42 PDT 2001 > Workarea: jen.americas.sgi.com:/src/lord/xfs-merge Does it work? You have a point about the VM stuff being changed in a stable kernel... but I think I'd have to say Linus is working on 2.3, not 2.5. ;-) -- Joseph Fannin jhf@rivenstone.net "Bull in pure form is rare; there is usually some contamination by data." -- William Graves Perry Jr. From owner-linux-xfs@oss.sgi.com Fri Sep 21 12:49:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LJn1E32201 for linux-xfs-outgoing; Fri, 21 Sep 2001 12:49:01 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LJmxe32182 for ; Fri, 21 Sep 2001 12:48:59 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8LJmrj14164 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Fri, 21 Sep 2001 12:48:53 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA964519 for ; Fri, 21 Sep 2001 21:48:55 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA3032169; Fri, 21 Sep 2001 14:47:32 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA43558; Fri, 21 Sep 2001 14:47:32 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8LJmSw32526; Fri, 21 Sep 2001 14:48:28 -0500 Message-Id: <200109211948.f8LJmSw32526@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Joseph Fannin cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - merge up to 2.4.10-pre13 In-Reply-To: Message from Joseph Fannin of "Fri, 21 Sep 2001 15:42:33 EDT." <20010921145015.B7D0F4B570@zion.rivenstone.net> Date: Fri, 21 Sep 2001 14:48:27 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Friday 21 September 2001 15:31, you wrote: > > Here is the next one. > > > > Date: Fri Sep 21 12:28:42 PDT 2001 > > Workarea: jen.americas.sgi.com:/src/lord/xfs-merge > > Does it work? It seems to. I actually made the xfs footprint in the main kernel smaller in the pre12 kernel, so the new VM was a little easier to deal with from that point of view. Steve From owner-linux-xfs@oss.sgi.com Fri Sep 21 12:56:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LJujW32482 for linux-xfs-outgoing; Fri, 21 Sep 2001 12:56:45 -0700 Received: from server3.thinmail.com (IDENT:root@server3.thinmail.com [64.39.29.150]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LJuhe32463 for ; Fri, 21 Sep 2001 12:56:43 -0700 Received: (from root@localhost) by server3.thinmail.com (8.9.3/8.9.3) id PAA28084 for linux-xfs@oss.sgi.com; Fri, 21 Sep 2001 15:02:40 -0500 Received: from daedalus.cs.brandeis.edu (IDENT:root@daedalus.cs.brandeis.edu [129.64.3.179]) by server3.thinmail.com (8.9.3/8.9.3) with ESMTP id PAA28051 for ; Fri, 21 Sep 2001 15:02:36 -0500 Received: (from aaronm@localhost) by daedalus.cs.brandeis.edu (8.9.3/8.9.3) id PAA25956 for linux-xfs@oss.sgi.com.ml.to; Fri, 21 Sep 2001 15:56:28 -0400 Date: Fri, 21 Sep 2001 15:56:28 -0400 Subject: Stable Version? Message-ID: <20010921155628.A25935@daedalus.cs.brandeis.edu> User-Agent: Mutt/1.2.5i X-Thinmail: Processed by Thinmail build 0044, Revision: 1.137 , id 28059 X-Thinmail-Loop: fa750-827cfd80d6215eec To: linux-xfs@oss.sgi.com From: Aaron Macks Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've got a workgroup server serving 20GB off of XFS via NFS. Currently it's running the 2,4,5 kernel from the 1.0.1 release. I've noticed that the cvs tree is up past 2.4.9, but do these provide any benifit to the XFS/NFS system, or are they just keeping up with the main tree? Aaron -- _______________________________________________________ Aaron Macks(aaronm@cs.brandeis.edu) My sheep has seven gall bladders, that makes me the King of the Universe! From owner-linux-xfs@oss.sgi.com Fri Sep 21 13:04:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LK4d832744 for linux-xfs-outgoing; Fri, 21 Sep 2001 13:04:39 -0700 Received: from wiley.ceo.com (66-2-81-28.customer.algx.net [66.2.81.28]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LK4ae32724 for ; Fri, 21 Sep 2001 13:04:36 -0700 Received: from mindspring.com (IDENT:danny@localhost [127.0.0.1]) by wiley.ceo.com (8.11.6/8.11.6) with ESMTP id f8LKQgA06247; Fri, 21 Sep 2001 16:26:44 -0400 Message-ID: <3BABA282.F9F855F@mindspring.com> Date: Fri, 21 Sep 2001 16:26:42 -0400 From: Danny Cox Reply-To: DCox@SnapServer.com Organization: Snap X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.10-pre12-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Linux Kernel Mailing List , Linux-XFS Subject: 2.4.10-pre12 Missing EXPORT_SYMBOL? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk All, I updated my kernel to 2.4.10-pre12, and upon 'make modules_install', depmod reported a missing symbol: tty_register_ldisc, from ppp_async. I added a 'EXPORT_SYMBOL(tty_register_ldisc)' just after the tty_register_ldisc definition in drivers/char/tty_io.c, and all was well. Just FYI. -- "Men occasionally stumble over the truth, but most of them pick themselves up and hurry off as if nothing had happened." -- Winston Churchill Danny From owner-linux-xfs@oss.sgi.com Fri Sep 21 13:13:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LKDhH00556 for linux-xfs-outgoing; Fri, 21 Sep 2001 13:13:43 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LKDee00535 for ; Fri, 21 Sep 2001 13:13:40 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8LKDZj16026 for ; Fri, 21 Sep 2001 13:13:35 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA3032929; Fri, 21 Sep 2001 15:12:19 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id PAA83540; Fri, 21 Sep 2001 15:12:19 -0500 (CDT) Message-ID: <3BAB9EDE.29E2D09@sgi.com> Date: Fri, 21 Sep 2001 15:11:10 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Aaron Macks CC: linux-xfs@oss.sgi.com Subject: Re: Stable Version? References: <20010921155628.A25935@daedalus.cs.brandeis.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Aaron Macks wrote: > > I've > noticed that the cvs tree is up past 2.4.9, but do these provide any > benifit to the XFS/NFS system, or are they just keeping up with the > main tree? Some of both. If you're having specific issues with the underlying 2.4.5 kernel that are fixed in the later kernels, that might be a reason to upgrade. If you're having specific issues with XFS, post them here and we can let you know whether they have been addressed in later kernels. But if things are working well, don't try to fix it. :) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Sep 21 16:29:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8LNThu03931 for linux-xfs-outgoing; Fri, 21 Sep 2001 16:29:43 -0700 Received: from mtiwmhc21.worldnet.att.net (mtiwmhc21.worldnet.att.net [204.127.131.46]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8LNTee03912 for ; Fri, 21 Sep 2001 16:29:40 -0700 Received: from lnuxlab.ath.cx ([12.77.149.66]) by mtiwmhc21.worldnet.att.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010921232934.CGZG1680.mtiwmhc21.worldnet.att.net@lnuxlab.ath.cx> for ; Fri, 21 Sep 2001 23:29:34 +0000 Received: by lnuxlab.ath.cx (Postfix, from userid 1000) id 5F9741F33; Fri, 21 Sep 2001 19:29:32 -0400 (EDT) Date: Fri, 21 Sep 2001 19:29:32 -0400 From: khromy To: linux-xfs@oss.sgi.com Subject: 2.4.10-pre13-xfs Unresolved symbols in pagebuf.o Message-ID: <20010921192932.A26436@lnuxlab.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Latest cvs checkout as of: Fri Sep 21 19:29:04 EDT 2001 make modules_install fails with: depmod: *** Unresolved symbols in /lib/modules/2.4.10-pre13-xfs/kernel/fs/pagebuf/pagebuf.o depmod: discard_bh_page -- L1: khromy ;khromy at lnuxlab.ath.cx From owner-linux-xfs@oss.sgi.com Fri Sep 21 17:38:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8M0cL105030 for linux-xfs-outgoing; Fri, 21 Sep 2001 17:38:21 -0700 Received: from gateway1.brets.elevating.com (adsl-216-63-236-137.dsl.tulsok.swbell.net [216.63.236.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8M0cIe05010 for ; Fri, 21 Sep 2001 17:38:19 -0700 Received: from elevating.com (bretdell.brets.elevating.com [192.168.0.128]) by gateway1.brets.elevating.com (8.9.3/8.8.7) with ESMTP id TAA31567; Fri, 21 Sep 2001 19:38:17 -0500 Message-ID: <3BABDD79.DF2571E8@elevating.com> Date: Fri, 21 Sep 2001 19:38:17 -0500 From: Bret Hughes X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, ja MIME-Version: 1.0 To: linux-xfs Subject: Re: mksf problems References: <3BAB8071.BB917283@elevating.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Bret Hughes wrote: > > I am unable to create a filesystem on a raid 5 volume on a compaq 3000. > > I finally(with the help of this list ) got XFS installed and running > after hosing the MBR now I need to add an additional partition to this > box with some of the left over space. I used fdisk /dev/ida/c0d0 to > create a new 10GB partition and it appears to have worked: > > Any ideas about what am I doing wrong? I have a terrible cold and am > under the influence of couch medicine so I may be missing something > simple. > > Bret Still not sure what the deal was but a reboot fixed it. Bret From owner-linux-xfs@oss.sgi.com Fri Sep 21 18:20:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8M1K8t05794 for linux-xfs-outgoing; Fri, 21 Sep 2001 18:20:08 -0700 Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8M1K0e05774 for ; Fri, 21 Sep 2001 18:20:01 -0700 Received: from walt400.localhost (user-2inia8t.dialup.mindspring.com [165.121.41.29]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA14989; Fri, 21 Sep 2001 21:19:58 -0400 (EDT) Received: from mindspring.com (localhost.localdomain [127.0.0.1]) by walt400.localhost (Postfix) with ESMTP id 12C87970E; Fri, 21 Sep 2001 18:21:41 -0700 (PDT) Message-ID: <3BABE7A4.2090703@mindspring.com> Date: Fri, 21 Sep 2001 18:21:40 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4+) Gecko/20010920 X-Accept-Language: en-us MIME-Version: 1.0 To: Bret Hughes Cc: linux-xfs Subject: Re: mksf problems References: <3BAB8071.BB917283@elevating.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sorry, not sure what is going on here either. Just wanted to mention that I could relate to your current condition. I too have had bad "couch" medicine which rendered me mostly disabled :) Although, with the *right* kind of couch medicine, I've felt much better during and afterwards :-) I know, pretty bad stuff. -Walt Bret Hughes wrote: > I am unable to create a filesystem on a raid 5 volume on a compaq 3000. > > I finally(with the help of this list ) got XFS installed and running > after hosing the MBR now I need to add an additional partition to this > box with some of the left over space. I used fdisk /dev/ida/c0d0 to > create a new 10GB partition and it appears to have worked: > > [root@compaq3 /sbin]# fdisk -l /dev/ida/c0d0 > > Disk /dev/ida/c0d0: 255 heads, 32 sectors, 8711 cylinders > Units = cylinders of 8160 * 512 bytes > > Device Boot Start End Blocks Id System > /dev/ida/c0d0p1 * 10 22 53040 83 Linux > /dev/ida/c0d0p2 23 8711 35451120 5 Extended > /dev/ida/c0d0p3 1 9 36704 12 Compaq > diagnostics > /dev/ida/c0d0p5 23 73 208064 82 Linux swap > /dev/ida/c0d0p6 74 136 257024 83 Linux > /dev/ida/c0d0p7 137 199 257024 83 Linux > /dev/ida/c0d0p8 200 262 257024 83 Linux > /dev/ida/c0d0p9 263 764 2048144 83 Linux > /dev/ida/c0d0p10 765 2019 5120384 83 Linux > /dev/ida/c0d0p11 2020 4529 10240784 83 Linux > > Partition table entries are not in disk order > > > c0d0p11 is the new partition. > > when I try to create the filesytem I get this: > > [root@compaq3 /sbin]# mkfs -t xfs /dev/ida/c0d0p11 > mkfs.xfs: cannot open /dev/ida/c0d0p11: No such device or address > > the device file is there: > > [root@compaq3 /sbin]# ls -l /dev/ida/c0d0* > brw-rw---- 1 root disk 72, 0 Mar 23 22:37 /dev/ida/c0d0 > brw-rw---- 1 root disk 72, 1 Mar 23 22:37 /dev/ida/c0d0p1 > brw-rw---- 1 root disk 72, 10 Mar 23 22:37 /dev/ida/c0d0p10 > brw-rw---- 1 root disk 72, 11 Mar 23 22:37 /dev/ida/c0d0p11 > brw-rw---- 1 root disk 72, 12 Mar 23 22:37 /dev/ida/c0d0p12 > brw-rw---- 1 root disk 72, 13 Mar 23 22:37 /dev/ida/c0d0p13 > brw-rw---- 1 root disk 72, 14 Mar 23 22:37 /dev/ida/c0d0p14 > brw-rw---- 1 root disk 72, 15 Mar 23 22:37 /dev/ida/c0d0p15 > brw-rw---- 1 root disk 72, 2 Mar 23 22:37 /dev/ida/c0d0p2 > brw-rw---- 1 root disk 72, 3 Mar 23 22:37 /dev/ida/c0d0p3 > brw-rw---- 1 root disk 72, 4 Mar 23 22:37 /dev/ida/c0d0p4 > brw-rw---- 1 root disk 72, 5 Mar 23 22:37 /dev/ida/c0d0p5 > brw-rw---- 1 root disk 72, 6 Mar 23 22:37 /dev/ida/c0d0p6 > brw-rw---- 1 root disk 72, 7 Mar 23 22:37 /dev/ida/c0d0p7 > brw-rw---- 1 root disk 72, 8 Mar 23 22:37 /dev/ida/c0d0p8 > brw-rw---- 1 root disk 72, 9 Mar 23 22:37 /dev/ida/c0d0p9 > > > > > Any ideas about what am I doing wrong? I have a terrible cold and am > under the influence of couch medicine so I may be missing something > simple. > > > Bret > > From owner-linux-xfs@oss.sgi.com Fri Sep 21 18:23:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8M1Nxn05957 for linux-xfs-outgoing; Fri, 21 Sep 2001 18:23:59 -0700 Received: from maul.jdc.home (Nm@c999639-a.carneg1.pa.home.com [24.180.243.111]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8M1Nte05938 for ; Fri, 21 Sep 2001 18:23:55 -0700 Received: from warblade.jdc.home (warblade.jdc.home [10.1.1.2]) by maul.jdc.home (8.12.0.Beta19/8.12.0.Beta19/Debian 8.12.0.Beta19) with ESMTP id f8M1ODej012582; Fri, 21 Sep 2001 20:24:13 -0500 Subject: Re: mksf problems From: Jim Crilly To: Bret Hughes Cc: linux-xfs In-Reply-To: <3BABDD79.DF2571E8@elevating.com> References: <3BAB8071.BB917283@elevating.com> <3BABDD79.DF2571E8@elevating.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 21 Sep 2001 21:22:04 -0400 Message-Id: <1001121724.595.13.camel@warblade> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 2001-09-21 at 20:38, Bret Hughes wrote: > Bret Hughes wrote: > > > > I am unable to create a filesystem on a raid 5 volume on a compaq 3000. > > > > I finally(with the help of this list ) got XFS installed and running > > after hosing the MBR now I need to add an additional partition to this > > box with some of the left over space. I used fdisk /dev/ida/c0d0 to > > create a new 10GB partition and it appears to have worked: > > > > > > Any ideas about what am I doing wrong? I have a terrible cold and am > > under the influence of couch medicine so I may be missing something > > simple. > > > > Bret > > Still not sure what the deal was but a reboot fixed it. If you created the partition after the box was booted and any part of the disk was in use (mounted, swapon'd, etc) you have to reboot for the new partition table to be usable. > > Bret -- Help protect your rights on-line. Join the Electronic Frontiers Foundation today: http://www.eff.org/join ----------------------------------------------------------------------- Security: Antonyms: See Microsoft ----------------------------------------------------------------------- "We are coming after you. God may have mercy on you, but we won't," declared Sen. John McCain, R-Arizona. From owner-linux-xfs@oss.sgi.com Fri Sep 21 19:22:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8M2MaO07405 for linux-xfs-outgoing; Fri, 21 Sep 2001 19:22:36 -0700 Received: from gateway1.brets.elevating.com (adsl-216-63-236-137.dsl.tulsok.swbell.net [216.63.236.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8M2MWe07382 for ; Fri, 21 Sep 2001 19:22:33 -0700 Received: from elevating.com (brethome.hughes.elevating.com [10.0.0.53]) by gateway1.brets.elevating.com (8.9.3/8.8.7) with ESMTP id VAA31849; Fri, 21 Sep 2001 21:22:25 -0500 Message-ID: <3BABF5E1.92F341CA@elevating.com> Date: Fri, 21 Sep 2001 21:22:25 -0500 From: Bret Hughes X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, ja MIME-Version: 1.0 To: Jim Crilly CC: linux-xfs Subject: Re: mksf problems References: <3BAB8071.BB917283@elevating.com> <3BABDD79.DF2571E8@elevating.com> <1001121724.595.13.camel@warblade> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jim Crilly wrote: > > On Fri, 2001-09-21 at 20:38, Bret Hughes wrote: > > Bret Hughes wrote: > > > > > > I am unable to create a filesystem on a raid 5 volume on a compaq 3000. > > > > > > I finally(with the help of this list ) got XFS installed and running > > > after hosing the MBR now I need to add an additional partition to this > > > box with some of the left over space. I used fdisk /dev/ida/c0d0 to > > > create a new 10GB partition and it appears to have worked: > > > > > > > > > > Any ideas about what am I doing wrong? I have a terrible cold and am > > > under the influence of couch medicine so I may be missing something > > > simple. > > > > > > Bret > > > > Still not sure what the deal was but a reboot fixed it. > > If you created the partition after the box was booted and any part of > the disk was in use (mounted, swapon'd, etc) you have to reboot for the > new partition table to be usable. > Well, that is indeed the case. Thanks. I do not recall this happening in the past is this an XFS thing? I'll admit to not doing too much partioning but I think I would remember having to reboot in the past. I have even less experience with the Smart-2 raid controllers but certainly more than when I started this upgrade. Now if I can just get the amanda server stuff working with the rpms I will be grinning. Bret From owner-linux-xfs@oss.sgi.com Fri Sep 21 21:50:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8M4owh09776 for linux-xfs-outgoing; Fri, 21 Sep 2001 21:50:58 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8M4ose09757 for ; Fri, 21 Sep 2001 21:50:55 -0700 Received: (qmail 26963 invoked from network); 22 Sep 2001 04:50:48 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 22 Sep 2001 04:50:48 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id BF5BE300090; Sat, 22 Sep 2001 14:49:42 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 39E97B8; Sat, 22 Sep 2001 14:49:42 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Bret Hughes Cc: linux-xfs Subject: Re: mksf problems In-reply-to: Your message of "Fri, 21 Sep 2001 21:22:25 EST." <3BABF5E1.92F341CA@elevating.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Sep 2001 14:49:36 +1000 Message-ID: <18294.1001134176@ocs3.intra.ocs.com.au> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 21 Sep 2001 21:22:25 -0500, Bret Hughes wrote: >Well, that is indeed the case. Thanks. I do not recall this happening >in the past is this an XFS thing? I'll admit to not doing too much >partioning but I think I would remember having to reboot in the past. It is a general kernel problem. Sometimes the new partition table is picked up immediately, sometimes it is not. The 2.5 merge of the page and buffer cache should remove the disk block aliasing problem and, as a side effect, fix the partitioning glitch. From owner-linux-xfs@oss.sgi.com Sat Sep 22 16:34:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8MNY1w20313 for linux-xfs-outgoing; Sat, 22 Sep 2001 16:34:01 -0700 Received: from vitelus.com (vitelus.com [64.81.243.207]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8MNXve20294 for ; Sat, 22 Sep 2001 16:33:58 -0700 Received: from aaronl by vitelus.com with local (Exim 3.32 #1 (Debian)) id 15kwHK-0000l9-00 for ; Sat, 22 Sep 2001 16:33:46 -0700 Date: Sat, 22 Sep 2001 16:33:46 -0700 From: Aaron Lehmann To: linux-xfs@oss.sgi.com Subject: CVS broken, it seems Message-ID: <20010922163346.A2770@vitelus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk make[2]: Entering directory `/usr/src/linux-2.4-xfs/linux/mm' make[2]: *** No rule to make target `mmap_avl.c', needed by `mmap.o'. Stop. Did someone forget to add this file to the CVS repository? From owner-linux-xfs@oss.sgi.com Sat Sep 22 20:02:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8N32Bq23197 for linux-xfs-outgoing; Sat, 22 Sep 2001 20:02:11 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8N327e23176 for ; Sat, 22 Sep 2001 20:02:07 -0700 Received: (qmail 5450 invoked from network); 23 Sep 2001 03:02:04 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 23 Sep 2001 03:02:04 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 71D91300095; Sun, 23 Sep 2001 13:00:57 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 04CD1B8; Sun, 23 Sep 2001 13:00:56 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Aaron Lehmann Cc: linux-xfs@oss.sgi.com Subject: Re: CVS broken, it seems In-reply-to: Your message of "Sat, 22 Sep 2001 16:33:46 MST." <20010922163346.A2770@vitelus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Sep 2001 13:00:51 +1000 Message-ID: <5978.1001214051@ocs3.intra.ocs.com.au> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 22 Sep 2001 16:33:46 -0700, Aaron Lehmann wrote: >make[2]: Entering directory `/usr/src/linux-2.4-xfs/linux/mm' >make[2]: *** No rule to make target `mmap_avl.c', needed by `mmap.o'. Stop. > >Did someone forget to add this file to the CVS repository? That file was deleted by Linus in 2.4.10-pre11 and is no longer in linux/mm/Makefile. It has been removed from the internal tree, if it is still referenced in CVS then there is an error in CVS or at your end. Try rm -rf linux/mm and refresh from CVS, see if mm/Makefile still refers to mmap_avl.o. From owner-linux-xfs@oss.sgi.com Sat Sep 22 20:08:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8N38u023388 for linux-xfs-outgoing; Sat, 22 Sep 2001 20:08:56 -0700 Received: from vitelus.com (vitelus.com [64.81.243.207]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8N38re23369 for ; Sat, 22 Sep 2001 20:08:53 -0700 Received: from aaronl by vitelus.com with local (Exim 3.32 #1 (Debian)) id 15kzdS-0001B2-00; Sat, 22 Sep 2001 20:08:50 -0700 Date: Sat, 22 Sep 2001 20:08:50 -0700 From: Aaron Lehmann To: Keith Owens Cc: linux-xfs@oss.sgi.com Subject: Re: CVS broken, it seems Message-ID: <20010922200850.A4518@vitelus.com> References: <20010922163346.A2770@vitelus.com> <5978.1001214051@ocs3.intra.ocs.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5978.1001214051@ocs3.intra.ocs.com.au> User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Sep 23, 2001 at 01:00:51PM +1000, Keith Owens wrote: > On Sat, 22 Sep 2001 16:33:46 -0700, > Aaron Lehmann wrote: > >make[2]: Entering directory `/usr/src/linux-2.4-xfs/linux/mm' > >make[2]: *** No rule to make target `mmap_avl.c', needed by `mmap.o'. Stop. > > > >Did someone forget to add this file to the CVS repository? > > That file was deleted by Linus in 2.4.10-pre11 and is no longer in > linux/mm/Makefile. It has been removed from the internal tree, if it > is still referenced in CVS then there is an error in CVS or at your > end. Try rm -rf linux/mm and refresh from CVS, see if mm/Makefile > still refers to mmap_avl.o. Odd, that fixed it. I don't know why it would since cvs updating mm showed it as up to date (and no M's). From owner-linux-xfs@oss.sgi.com Sun Sep 23 02:54:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8N9sUv29294 for linux-xfs-outgoing; Sun, 23 Sep 2001 02:54:30 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8N9sQe29274 for ; Sun, 23 Sep 2001 02:54:26 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 9FE23C00B61 for ; Sun, 23 Sep 2001 17:54:23 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 36C08C00B60 for ; Sun, 23 Sep 2001 17:54:20 +0800 (PHT) Date: Sun, 23 Sep 2001 17:54:20 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Interesting Filesystem Benchmarks Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, Stumbled upon this very interesting filesystem benchmark. It's nothing radical, but reaffirms a lot of what we already "know". What's more, they have very pleasant stuff to report about XFS, and overall recommend our preferred filesystem. I hope this will serve as a pat on the back to our devoted developers. Thanks a lot guys! :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Sun Sep 23 06:39:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8NDdCL05302 for linux-xfs-outgoing; Sun, 23 Sep 2001 06:39:12 -0700 Received: from supai.oit.umass.edu (supai.oit.umass.edu [128.119.175.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8NDd9e05283 for ; Sun, 23 Sep 2001 06:39:09 -0700 Received: from CONVERSION-DAEMON by supai.oit.umass.edu (PMDF V5.2-32 #38130) id <0GK400701B678A@supai.oit.umass.edu> for linux-xfs@oss.sgi.com; Sun, 23 Sep 2001 09:37:19 -0400 (EDT) Received: from killgoretrout (fild-426.res.umass.edu [128.119.145.170]) by supai.oit.umass.edu (PMDF V5.2-32 #38130) with SMTP id <0GK4004GMB67PA@supai.oit.umass.edu> for linux-xfs@oss.sgi.com; Sun, 23 Sep 2001 09:37:19 -0400 (EDT) Date: Sun, 23 Sep 2001 09:36:26 -0400 From: Bryce Riner Subject: Re: CVS broken, it seems To: linux-xfs@oss.sgi.com Message-id: <002d01c14434$bec22ff0$aa917780@killgoretrout> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 X-Mailer: Microsoft Outlook Express 6.00.2479.0006 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <20010922163346.A2770@vitelus.com> <5978.1001214051@ocs3.intra.ocs.com.au> <20010922200850.A4518@vitelus.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Sun, Sep 23, 2001 at 01:00:51PM +1000, Keith Owens wrote: > > On Sat, 22 Sep 2001 16:33:46 -0700, > > Aaron Lehmann wrote: > > >make[2]: Entering directory `/usr/src/linux-2.4-xfs/linux/mm' > > >make[2]: *** No rule to make target `mmap_avl.c', needed by `mmap.o'. Stop. > > > > > >Did someone forget to add this file to the CVS repository? > > > > That file was deleted by Linus in 2.4.10-pre11 and is no longer in > > linux/mm/Makefile. It has been removed from the internal tree, if it > > is still referenced in CVS then there is an error in CVS or at your > > end. Try rm -rf linux/mm and refresh from CVS, see if mm/Makefile > > still refers to mmap_avl.o. > > Odd, that fixed it. I don't know why it would since cvs updating mm > showed it as up to date (and no M's). > That sounds like a dependency problem, did you do a 'make dep' before compiling? From owner-linux-xfs@oss.sgi.com Sun Sep 23 12:46:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8NJkS709714 for linux-xfs-outgoing; Sun, 23 Sep 2001 12:46:28 -0700 Received: from giants.mandrakesoft.com (office.mandrakesoft.com [195.68.114.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8NJkOe09694 for ; Sun, 23 Sep 2001 12:46:24 -0700 Received: by giants.mandrakesoft.com (Postfix, from userid 500) id 0ACD5C0AE; Sun, 23 Sep 2001 21:46:12 +0200 (CEST) To: Nick (Gunnar) Bluth Cc: linux-xfs@oss.sgi.com Subject: Re: gcc-2.96-nn status References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010919010548.0335ae28@pop.xs4all.nl> <1000856809.22994.50.camel@scare> <200109211025.MAA22042@server.nick.de> From: Chmouel Boudjnah Date: 23 Sep 2001 21:46:12 +0200 In-Reply-To: <200109211025.MAA22042@server.nick.de> (Nick's message of "Fri, 21 Sep 2001 13:46:13 +0200") Message-ID: Lines: 8 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.0.104 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nick (Gunnar) Bluth writes: > > Given how far ahead of Redhat Mandrake is I doubt that is true anymore. > Well, about 50% of it is maintained by Bero (Red Hat Germany).... pardon ? bero leave the company like 2 years ago.... > BTW: 7.2 Final has gcc3 with it (but optional) From owner-linux-xfs@oss.sgi.com Sun Sep 23 15:19:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8NMJOb12827 for linux-xfs-outgoing; Sun, 23 Sep 2001 15:19:24 -0700 Received: from femail36.sdc1.sfba.home.com (femail36.sdc1.sfba.home.com [24.254.60.26]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8NMJLe12806 for ; Sun, 23 Sep 2001 15:19:21 -0700 Received: from cr598116-a.wlfdle1.on.wave.home.com ([24.112.74.120]) by femail36.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010923221916.MNAK13666.femail36.sdc1.sfba.home.com@cr598116-a.wlfdle1.on.wave.home.com> for ; Sun, 23 Sep 2001 15:19:16 -0700 From: Gerald Henriksen To: linux-xfs@oss.sgi.com Subject: Re: gcc-2.96-nn status Date: Sun, 23 Sep 2001 18:19:16 -0400 Message-ID: References: <20010918124051.A30647@wwweasel.geeksrus.net> <4.3.2.7.2.20010919010548.0335ae28@pop.xs4all.nl> <1000856809.22994.50.camel@scare> <200109211025.MAA22042@server.nick.de> In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8NMJLe12807 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 23 Sep 2001 21:46:12 +0200, you wrote: >Nick (Gunnar) Bluth writes: > >> > Given how far ahead of Redhat Mandrake is I doubt that is true anymore. >> Well, about 50% of it is maintained by Bero (Red Hat Germany).... > >pardon ? bero leave the company like 2 years ago.... Maybe somebody should tell Bero then given that I have archived a message he posted to one of the Red Hat mailing lists on August 9th of this year which was sent from his redhat.de account. From owner-linux-xfs@oss.sgi.com Sun Sep 23 15:42:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8NMgFM13614 for linux-xfs-outgoing; Sun, 23 Sep 2001 15:42:15 -0700 Received: from UberGeek.coremetrics.com ([209.184.141.163]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8NMgCe13593 for ; Sun, 23 Sep 2001 15:42:12 -0700 Received: (from austin@localhost) by UberGeek.coremetrics.com (8.11.6/8.11.6) id f8NMbUD08241; Sun, 23 Sep 2001 17:37:30 -0500 X-Authentication-Warning: UberGeek.coremetrics.com: austin set sender to austin@coremetrics.com using -f Subject: 2.4.10 patch? From: Austin Gonyou To: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.14.99+cvs.2001.09.22.08.08 (Preview Release) Date: 23 Sep 2001 17:37:30 -0500 Message-Id: <1001284650.8217.1.camel@UberGeek> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Is there a 2.4.10 final patch available yet? Also, when that patch is available, will it have the preemption patch in there as well? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Sun Sep 23 15:58:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8NMw1P14203 for linux-xfs-outgoing; Sun, 23 Sep 2001 15:58:01 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8NMvve14183 for ; Sun, 23 Sep 2001 15:57:57 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id AAA01396; Mon, 24 Sep 2001 00:57:47 +0200 (CEST) Message-Id: <4.3.2.7.2.20010924005502.02d4b418@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 24 Sep 2001 00:57:05 +0200 To: Austin Gonyou , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: 2.4.10 patch? In-Reply-To: <1001284650.8217.1.camel@UberGeek> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:37 23-9-2001 -0500, Austin Gonyou wrote: >Is there a 2.4.10 final patch available yet? Also, when that patch is >available, will it have the preemption patch in there as well? It will only be based on a vanilla linus kernel. It does come with kdb though byt that is for development reasons. Give the folks a couple of days time to work it out. You don't want to download a patch that does not work. The extra time is used for testing and making sure it is sane. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Sep 23 16:22:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8NNMCe15080 for linux-xfs-outgoing; Sun, 23 Sep 2001 16:22:12 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8NNLpe15049 for ; Sun, 23 Sep 2001 16:21:56 -0700 Received: (qmail 13951 invoked from network); 23 Sep 2001 23:21:13 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 23 Sep 2001 23:21:13 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 5DA9E303030; Mon, 24 Sep 2001 09:21:03 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 18137B8; Mon, 24 Sep 2001 09:21:03 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Austin Gonyou Cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.10 patch? In-reply-to: Your message of "23 Sep 2001 17:37:30 EST." <1001284650.8217.1.camel@UberGeek> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Sep 2001 09:20:57 +1000 Message-ID: <2363.1001287257@ocs3.intra.ocs.com.au> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 23 Sep 2001 17:37:30 -0500, Austin Gonyou wrote: >Is there a 2.4.10 final patch available yet? Also, when that patch is >available, will it have the preemption patch in there as well? The patch to XFS to coexist with the preemption patch is already in. But you have to apply the main preemption patch yourself. From owner-linux-xfs@oss.sgi.com Sun Sep 23 16:55:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8NNtoO15938 for linux-xfs-outgoing; Sun, 23 Sep 2001 16:55:50 -0700 Received: from camdb.vilcom.com (IDENT:root@[199.72.107.235]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8NNtje15916 for ; Sun, 23 Sep 2001 16:55:47 -0700 Received: from towerpc (64-40-83-60.mb.dsl.mebtel.net [64.40.83.60]) by camdb.vilcom.com (8.9.3/8.9.3) with ESMTP id UAA28418; Sun, 23 Sep 2001 20:14:06 -0400 From: "Steven Tower" To: "'Keith Owens'" , "'Austin Gonyou'" Cc: Subject: RE: 2.4.10 patch? Date: Sun, 23 Sep 2001 19:55:24 -0400 Message-ID: <000501c1448b$366ef9b0$3c532840@towerpc> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <2363.1001287257@ocs3.intra.ocs.com.au> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I realize this is off topic, can someone give me a URL where I can find the main preemption patch? Thanks. Steven >>Is there a 2.4.10 final patch available yet? Also, when that patch is >>available, will it have the preemption patch in there as well? > >The patch to XFS to coexist with the preemption patch is already in. >But you have to apply the main preemption patch yourself. From owner-linux-xfs@oss.sgi.com Sun Sep 23 17:03:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8O03pb16257 for linux-xfs-outgoing; Sun, 23 Sep 2001 17:03:51 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8O03le16238 for ; Sun, 23 Sep 2001 17:03:48 -0700 Received: (qmail 14367 invoked from network); 24 Sep 2001 00:03:45 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 24 Sep 2001 00:03:44 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 65289303030; Mon, 24 Sep 2001 10:03:34 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 0CD71B8; Mon, 24 Sep 2001 10:03:34 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: "Steven Tower" Cc: "'Austin Gonyou'" , linux-xfs@oss.sgi.com Subject: Re: 2.4.10 patch? In-reply-to: Your message of "Sun, 23 Sep 2001 19:55:24 -0400." <000501c1448b$366ef9b0$3c532840@towerpc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Sep 2001 10:03:28 +1000 Message-ID: <2994.1001289808@ocs3.intra.ocs.com.au> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 23 Sep 2001 19:55:24 -0400, "Steven Tower" wrote: >I realize this is off topic, can someone give me a URL where I can find >the main preemption patch? Thanks. http://marc.theaimsgroup.com/?l=linux-kernel&w=2&r=1&s=preemption&q=b lists the various threads. The announcement is http://marc.theaimsgroup.com/?l=linux-kernel&m=100085838604526&w=2 From owner-linux-xfs@oss.sgi.com Sun Sep 23 17:50:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8O0o9E16994 for linux-xfs-outgoing; Sun, 23 Sep 2001 17:50:09 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8O0o5e16975 for ; Sun, 23 Sep 2001 17:50:05 -0700 Received: from idcomm.com (IDENT:lUWBi0bIYGIjW7y0kdfFt2OMYZCzniJa@x2-pip70.idcomm.com [209.60.72.81]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f8O11ui25209 for ; Sun, 23 Sep 2001 19:01:56 -0600 Message-ID: <3BAE83D6.86A003D0@idcomm.com> Date: Sun, 23 Sep 2001 18:52:38 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: 2.4.10 patch? References: <2994.1001289808@ocs3.intra.ocs.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Keith Owens wrote: > > On Sun, 23 Sep 2001 19:55:24 -0400, > "Steven Tower" wrote: > >I realize this is off topic, can someone give me a URL where I can find > >the main preemption patch? Thanks. > > http://marc.theaimsgroup.com/?l=linux-kernel&w=2&r=1&s=preemption&q=b > lists the various threads. The announcement is > http://marc.theaimsgroup.com/?l=linux-kernel&m=100085838604526&w=2 I'm curious if anyone here has tried the preemption patches on XFS system, running SMP? My question is if you have any subjective comparison of how the system feels/works both with and without IO-APIC enabled? I ask since I'm forced to run noapic on an i840 chipset. noapic can have a number of subjective changes all by itself, one of which is lower responsiveness. If an XFS kernel works well on SMP machines running noapic, this might be useful for me. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Sun Sep 23 19:16:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8O2GZP18289 for linux-xfs-outgoing; Sun, 23 Sep 2001 19:16:35 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8O2GFe18268 for ; Sun, 23 Sep 2001 19:16:16 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8O2G9j14733 for ; Sun, 23 Sep 2001 19:16:10 -0700 Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id MAA31058; Mon, 24 Sep 2001 12:16:08 +1000 Date: Mon, 24 Sep 2001 12:16:08 +1000 From: Keith Owens Message-Id: <200109240216.MAA31058@sherman.melbourne.sgi.com> Subject: TAKE - Upgrade to 2.4.10 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Upgrade to 2.4.10 Date: Sun Sep 23 19:14:03 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103291a linux/drivers/acpi/kdb/README.txt - 1.1 linux/drivers/acpi/kdb/kdbm_acpi.c - 1.1 linux/drivers/acpi/debugger/Makefile - 1.1 linux/net/sunrpc/xprt.c - 1.19 linux/net/sunrpc/sched.c - 1.19 linux/net/sunrpc/pmap_clnt.c - 1.6 linux/net/sunrpc/clnt.c - 1.14 linux/net/sunrpc/auth.c - 1.10 linux/mm/vmscan.c - 1.76 linux/mm/swapfile.c - 1.39 linux/mm/swap_state.c - 1.31 linux/mm/swap.c - 1.13 linux/mm/page_alloc.c - 1.55 linux/mm/memory.c - 1.62 linux/mm/filemap.c - 1.88 linux/kernel/exec_domain.c - 1.13 linux/include/linux/swap.h - 1.40 linux/include/linux/sunrpc/xprt.h - 1.9 linux/include/linux/mm.h - 1.66 linux/include/linux/fs.h - 1.120 linux/include/linux/fcntl.h - 1.4 linux/fs/super.c - 1.56 linux/fs/nfs/file.c - 1.24 linux/fs/locks.c - 1.19 linux/fs/lockd/xdr.c - 1.11 linux/fs/lockd/clntproc.c - 1.13 linux/fs/inode.c - 1.53 linux/fs/devices.c - 1.17 linux/fs/coda/psdev.c - 1.16 linux/fs/coda/file.c - 1.15 linux/fs/block_dev.c - 1.27 linux/drivers/usb/Makefile - 1.43 linux/drivers/usb/Config.in - 1.46 linux/drivers/char/tty_io.c - 1.36 linux/drivers/char/stallion.c - 1.17 linux/drivers/char/rocket.c - 1.14 linux/drivers/char/pty.c - 1.11 linux/drivers/char/Config.in - 1.49 linux/drivers/block/rd.c - 1.36 linux/arch/i386/kernel/mtrr.c - 1.28 linux/Makefile - 1.126 linux/MAINTAINERS - 1.73 linux/Documentation/Configure.help - 1.101 linux/drivers/usb/acm.c - 1.41 linux/drivers/net/irda/toshoboe.c - 1.26 linux/drivers/char/raw.c - 1.19 linux/drivers/sound/maestro.c - 1.24 linux/include/linux/acpi.h - 1.22 linux/include/linux/agp_backend.h - 1.13 linux/drivers/char/agp/agpgart_be.c - 1.25 linux/drivers/char/agp/agp.h - 1.17 linux/drivers/usb/usb-ohci.c - 1.28 linux/Documentation/filesystems/devfs/boot-options - 1.3 linux/Documentation/filesystems/devfs/README - 1.8 linux/Documentation/filesystems/devfs/ChangeLog - 1.11 linux/include/linux/devfs_fs_kernel.h - 1.7 linux/include/linux/devfs_fs.h - 1.2 linux/fs/devfs/util.c - 1.7 linux/fs/devfs/base.c - 1.20 linux/fs/partitions/ibm.c - 1.8 linux/drivers/acpi/tables/tbxface.c - 1.6 linux/drivers/acpi/tables/tbutils.c - 1.6 linux/drivers/acpi/tables/tbinstal.c - 1.6 linux/drivers/acpi/tables/tbget.c - 1.6 linux/drivers/acpi/resources/rsxface.c - 1.6 linux/drivers/acpi/resources/rsutils.c - 1.6 linux/drivers/acpi/resources/rsmisc.c - 1.6 linux/drivers/acpi/resources/rsmemory.c - 1.6 linux/drivers/acpi/resources/rslist.c - 1.7 linux/drivers/acpi/resources/rsirq.c - 1.6 linux/drivers/acpi/resources/rsio.c - 1.6 linux/drivers/acpi/resources/rsdump.c - 1.7 linux/drivers/acpi/resources/rscreate.c - 1.7 linux/drivers/acpi/resources/rscalc.c - 1.7 linux/drivers/acpi/resources/rsaddr.c - 1.6 linux/drivers/acpi/parser/psxface.c - 1.6 linux/drivers/acpi/parser/pswalk.c - 1.6 linux/drivers/acpi/parser/psutils.c - 1.6 linux/drivers/acpi/parser/pstree.c - 1.6 linux/drivers/acpi/parser/psscope.c - 1.6 linux/drivers/acpi/parser/psparse.c - 1.7 linux/drivers/acpi/parser/psopcode.c - 1.6 linux/drivers/acpi/parser/psargs.c - 1.7 linux/drivers/acpi/os.c - 1.8 linux/drivers/acpi/namespace/nsxfobj.c - 1.9 linux/drivers/acpi/namespace/nsxfname.c - 1.6 linux/drivers/acpi/namespace/nswalk.c - 1.5 linux/drivers/acpi/namespace/nsutils.c - 1.6 linux/drivers/acpi/namespace/nssearch.c - 1.7 linux/drivers/acpi/namespace/nsobject.c - 1.6 linux/drivers/acpi/namespace/nsnames.c - 1.7 linux/drivers/acpi/namespace/nsload.c - 1.6 linux/drivers/acpi/namespace/nseval.c - 1.7 linux/drivers/acpi/namespace/nsalloc.c - 1.6 linux/drivers/acpi/namespace/nsaccess.c - 1.7 linux/drivers/acpi/include/amlcode.h - 1.6 linux/drivers/acpi/include/actypes.h - 1.8 linux/drivers/acpi/include/actables.h - 1.6 linux/drivers/acpi/include/acpixf.h - 1.7 linux/drivers/acpi/include/acpiosxf.h - 1.7 linux/drivers/acpi/include/acobject.h - 1.6 linux/drivers/acpi/include/acexcep.h - 1.6 linux/drivers/acpi/hardware/hwregs.c - 1.7 linux/drivers/acpi/hardware/hwgpe.c - 1.6 linux/drivers/acpi/hardware/hwacpi.c - 1.7 linux/drivers/acpi/events/evxfregn.c - 1.7 linux/drivers/acpi/events/evxfevnt.c - 1.6 linux/drivers/acpi/events/evxface.c - 1.6 linux/drivers/acpi/events/evsci.c - 1.7 linux/drivers/acpi/events/evrgnini.c - 1.6 linux/drivers/acpi/events/evregion.c - 1.8 linux/drivers/acpi/events/evmisc.c - 1.6 linux/drivers/acpi/events/evevent.c - 1.8 linux/drivers/acpi/driver.c - 1.11 linux/drivers/acpi/dispatcher/dswstate.c - 1.7 linux/drivers/acpi/dispatcher/dswscope.c - 1.6 linux/drivers/acpi/dispatcher/dswload.c - 1.6 linux/drivers/acpi/dispatcher/dswexec.c - 1.6 linux/drivers/acpi/dispatcher/dsutils.c - 1.6 linux/drivers/acpi/dispatcher/dsopcode.c - 1.7 linux/drivers/acpi/dispatcher/dsobject.c - 1.7 linux/drivers/acpi/dispatcher/dsmthdat.c - 1.6 linux/drivers/acpi/dispatcher/dsmethod.c - 1.6 linux/drivers/acpi/dispatcher/dsfield.c - 1.5 linux/drivers/acpi/Makefile - 1.9 linux/drivers/acpi/include/acconfig.h - 1.7 linux/drivers/acpi/include/acdebug.h - 1.6 linux/drivers/acpi/include/acdispat.h - 1.5 linux/drivers/acpi/include/acevents.h - 1.6 linux/drivers/acpi/include/acglobal.h - 1.5 linux/drivers/acpi/include/achware.h - 1.5 linux/drivers/acpi/include/acinterp.h - 1.6 linux/drivers/acpi/include/aclocal.h - 1.7 linux/drivers/acpi/include/acmacros.h - 1.6 linux/drivers/acpi/include/acnamesp.h - 1.7 linux/drivers/acpi/include/acoutput.h - 1.6 linux/drivers/acpi/include/acparser.h - 1.4 linux/drivers/acpi/include/acresrc.h - 1.4 linux/drivers/acpi/include/actbl.h - 1.5 linux/drivers/acpi/namespace/nsdump.c - 1.3 linux/drivers/acpi/parser/psfind.c - 1.4 linux/drivers/md/md.c - 1.26 linux/drivers/acpi/tables/tbconvrt.c - 1.5 linux/drivers/acpi/tables/tbxfroot.c - 1.4 linux/drivers/acpi/namespace/nsinit.c - 1.6 linux/drivers/acpi/include/actbl71.h - 1.4 linux/drivers/acpi/include/actbl2.h - 1.4 linux/drivers/acpi/include/actbl1.h - 1.3 linux/mm/shmem.c - 1.15 linux/drivers/atm/firestream.c - 1.7 linux/drivers/acpi/acpi_ksyms.c - 1.4 linux/drivers/acpi/hardware/hwsleep.c - 1.4 linux/drivers/acpi/hardware/hwtimer.c - 1.4 linux/fs/reiserfs/journal.c - 1.8 linux/drivers/acpi/ospm/ec/ecgpe.c - 1.2 linux/drivers/acpi/executer/exstore.c - 1.2 linux/drivers/acpi/ospm/ec/ec_osl.c - 1.3 linux/drivers/acpi/ospm/include/pr.h - 1.2 linux/drivers/acpi/ospm/button/bn_osl.c - 1.3 linux/drivers/acpi/utilities/utxface.c - 1.2 linux/drivers/acpi/utilities/utobject.c - 1.2 linux/drivers/acpi/utilities/utmisc.c - 1.2 linux/drivers/acpi/utilities/utinit.c - 1.2 linux/drivers/acpi/utilities/utglobal.c - 1.2 linux/drivers/acpi/utilities/uteval.c - 1.2 linux/drivers/acpi/utilities/utdelete.c - 1.2 linux/drivers/acpi/utilities/utdebug.c - 1.2 linux/drivers/acpi/utilities/utcopy.c - 1.2 linux/drivers/acpi/utilities/utalloc.c - 1.2 linux/drivers/acpi/ospm/button/bn.c - 1.2 linux/drivers/acpi/ospm/busmgr/bmutils.c - 1.2 linux/drivers/acpi/ospm/busmgr/bmsearch.c - 1.2 linux/drivers/acpi/ospm/thermal/tz.c - 1.2 linux/drivers/acpi/ospm/busmgr/bmrequest.c - 1.2 linux/drivers/acpi/ospm/busmgr/bmpower.c - 1.2 linux/drivers/acpi/ospm/busmgr/bmpm.c - 1.2 linux/drivers/acpi/ospm/busmgr/bmnotify.c - 1.2 linux/drivers/acpi/ospm/busmgr/bmdriver.c - 1.2 linux/drivers/acpi/ospm/busmgr/bm_osl.c - 1.3 linux/drivers/acpi/ospm/busmgr/bm.c - 1.2 linux/drivers/acpi/ospm/battery/bt_osl.c - 1.3 linux/drivers/acpi/ospm/battery/bt.c - 1.2 linux/drivers/acpi/include/acstruct.h - 1.2 linux/drivers/acpi/ospm/system/sm_osl.c - 1.3 linux/drivers/acpi/ospm/thermal/tz_osl.c - 1.3 linux/drivers/acpi/ospm/thermal/tzpolicy.c - 1.2 linux/drivers/acpi/ospm/system/sm.c - 1.2 linux/drivers/acpi/ospm/include/bt.h - 1.2 linux/drivers/acpi/ospm/include/bn.h - 1.2 linux/drivers/acpi/include/acutils.h - 1.2 linux/drivers/acpi/include/platform/acenv.h - 1.2 linux/drivers/acpi/ospm/include/bmpower.h - 1.2 linux/drivers/acpi/include/platform/acgcc.h - 1.3 linux/drivers/acpi/debugger/dbcmds.c - 1.2 linux/drivers/acpi/debugger/dbdisasm.c - 1.2 linux/drivers/acpi/debugger/dbdisply.c - 1.2 linux/drivers/acpi/debugger/dbexec.c - 1.2 linux/drivers/acpi/debugger/dbfileio.c - 1.2 linux/drivers/acpi/debugger/dbhistry.c - 1.2 linux/drivers/acpi/debugger/dbinput.c - 1.2 linux/drivers/acpi/debugger/dbstats.c - 1.2 linux/drivers/acpi/debugger/dbutils.c - 1.2 linux/drivers/acpi/debugger/dbxface.c - 1.2 linux/drivers/acpi/ospm/include/ec.h - 1.2 linux/drivers/acpi/ospm/processor/prpower.c - 1.2 linux/drivers/acpi/ospm/processor/prperf.c - 1.2 linux/drivers/acpi/ospm/processor/pr_osl.c - 1.3 linux/drivers/acpi/ospm/ac_adapter/ac_osl.c - 1.3 linux/drivers/acpi/ospm/processor/pr.c - 1.2 linux/drivers/acpi/ospm/ac_adapter/ac.c - 1.2 linux/drivers/acpi/executer/exxface.c - 1.2 linux/drivers/acpi/executer/exutils.c - 1.2 linux/drivers/acpi/executer/exsystem.c - 1.2 linux/drivers/acpi/executer/exstorob.c - 1.2 linux/drivers/acpi/executer/exstoren.c - 1.2 linux/drivers/acpi/ospm/include/bm.h - 1.2 linux/drivers/acpi/ospm/ec/ecmain.c - 1.2 linux/drivers/acpi/ospm/include/sm.h - 1.2 linux/drivers/acpi/ospm/include/tz.h - 1.2 linux/drivers/acpi/ospm/ec/ecspace.c - 1.2 linux/drivers/acpi/ospm/ec/ectransx.c - 1.2 linux/drivers/acpi/ospm/include/ac.h - 1.2 linux/drivers/acpi/executer/exconfig.c - 1.2 linux/drivers/acpi/executer/exconvrt.c - 1.2 linux/drivers/acpi/executer/excreate.c - 1.2 linux/drivers/acpi/executer/exdump.c - 1.2 linux/drivers/acpi/executer/exdyadic.c - 1.2 linux/drivers/acpi/executer/exfield.c - 1.2 linux/drivers/acpi/executer/exfldio.c - 1.2 linux/drivers/acpi/executer/exmisc.c - 1.2 linux/drivers/acpi/executer/exmonad.c - 1.2 linux/drivers/acpi/executer/exmutex.c - 1.2 linux/drivers/acpi/executer/exnames.c - 1.2 linux/drivers/acpi/executer/exprep.c - 1.2 linux/drivers/acpi/executer/exregion.c - 1.2 linux/drivers/acpi/executer/exresnte.c - 1.2 linux/drivers/acpi/executer/exresolv.c - 1.2 linux/drivers/acpi/executer/exresop.c - 1.2 linux/drivers/usb/CDCEther.c - 1.3 linux/drivers/usb/CDCEther.h - 1.2 linux/drivers/scsi/53c700-mem.c - 1.2 linux/drivers/ide/pdcraid.c - 1.2 linux/drivers/ide/hptraid.c - 1.2 From owner-linux-xfs@oss.sgi.com Sun Sep 23 23:15:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8O6FM822142 for linux-xfs-outgoing; Sun, 23 Sep 2001 23:15:22 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8O6FHe22121 for ; Sun, 23 Sep 2001 23:15:18 -0700 Received: (qmail 14248 invoked by uid 8); 24 Sep 2001 06:15:13 -0000 From: thomas graichen Reply-To: thomas graichen X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: lock files after crash Date: Fri, 21 Sep 2001 22:25:20 +0200 Organization: spoiled dot org Lines: 22 Distribution: local Message-ID: References: <4.3.2.7.2.20010912091115.03368618@pop.xs4all.nl> <3B9F1B27.49261933@idcomm.com> <3B9F879E.3FB8976@ch.sauter-bc.com> Reply-To: thomas graichen X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.9-xfs (i686)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter wrote: > At least you're not alone, I was having the same problem. Did you really > have a kernel crash? I don't rember what happened in my case but I > thought I was upgrading some RPM's and when I rebooted next time I just > couldn't login. IIRC I did not have a kernel crash. i observed something similar too - the reason why logging in is not really possible is the existence of some .ICEauthority-* files - simply removing them should fix the problem - so there is no magic here - the locking seems to be done pretty trivial via some kind of normal files t p.s.: i hope i got the content of the question correct - i'm trying to catch up the lists now and might have gotten something wrong - if so - please forgive me :-) -- thomas graichen ... perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. --- antoine de saint-exupery From owner-linux-xfs@oss.sgi.com Sun Sep 23 23:26:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8O6QwM22414 for linux-xfs-outgoing; Sun, 23 Sep 2001 23:26:58 -0700 Received: from mail.hs.tecmath.com (www.tecmath.de [213.69.212.80]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8O6Qpe22395 for ; Sun, 23 Sep 2001 23:26:52 -0700 Received: from tmsgi7.humanmodeling.tecmath.de ([192.168.98.14]) by mail.hs.tecmath.com with esmtp (Exim 3.16 #1) id 15lPCO-0007Eq-00; Mon, 24 Sep 2001 08:26:36 +0200 Date: Mon, 24 Sep 2001 08:26:39 +0200 From: Martin Apel X-Sender: apel@tmsgi7.humanmodeling.tecmath.de To: Bartosch Pixa cc: linux-xfs@oss.sgi.com Subject: Re: question: xfs + lvm + kernel 2.4.9 In-Reply-To: <1001089180.19204.4.camel@bad> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 21 Sep 2001, Bartosch Pixa wrote: > On Thu, 2001-09-20 at 19:02, Martin K. Petersen wrote: > > >>>>> "Bartosch" == Bartosch Pixa writes: > > > > Bartosch> i'm trying to get a kernel 2.4.9 working with XFS and LVM > > Bartosch> 1.0.1-rc2, i got some errors after aplying the XFS patch > > Bartosch> (linux-2.4.9-xfs-2001-08-26.patch) to a already LVM patched > > Bartosch> kernel, the errors were only in the LVM parts of the kernel, > > Bartosch> so my question is now if it's sane to ignore these errors or > > Bartosch> if there are issues with XFS and LVM. > > > > 1.0.1-rc3 should be out next week. I would recommend you hold off > > until then. > > thx for the info, i sure will, but still there is the question if there > are any problems with lvm and xfs (the rejecter files during the patch > for example) I am running a file server with 2.4.5 + LVM + XFS on a hardware RAID 5 array without any problems. When applying the LVM patch I had only one reject in the area of software RAID, which I didn't care about much, as we don't use that. This setup runs very stable in a production environment for roughly six weeks now. Greetings, Martin From owner-linux-xfs@oss.sgi.com Mon Sep 24 00:24:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8O7Oh323985 for linux-xfs-outgoing; Mon, 24 Sep 2001 00:24:43 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8O7Ode23964 for ; Mon, 24 Sep 2001 00:24:39 -0700 Received: from idcomm.com (IDENT:jIgHFnDIbFNirLdG+Zkp8TMc2KfmLeEU@x2-pip46.idcomm.com [209.60.72.57]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f8O7aWi25517 for ; Mon, 24 Sep 2001 01:36:32 -0600 Message-ID: <3BAEE051.33A3656E@idcomm.com> Date: Mon, 24 Sep 2001 01:27:13 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: lock files after crash References: <4.3.2.7.2.20010912091115.03368618@pop.xs4all.nl> <3B9F1B27.49261933@idcomm.com> <3B9F879E.3FB8976@ch.sauter-bc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk thomas graichen wrote: > > Simon Matter wrote: > > At least you're not alone, I was having the same problem. Did you really > > have a kernel crash? I don't rember what happened in my case but I > > thought I was upgrading some RPM's and when I rebooted next time I just > > couldn't login. IIRC I did not have a kernel crash. > > i observed something similar too - the reason why logging in is not > really possible is the existence of some .ICEauthority-* files - > simply removing them should fix the problem - so there is no magic > here - the locking seems to be done pretty trivial via some kind > of normal files > > t > > p.s.: i hope i got the content of the question correct - i'm trying > to catch up the lists now and might have gotten something > wrong - if so - please forgive me :-) > > -- > thomas graichen ... perfection is reached, not > when there is no longer anything to add, but when there is no > longer anything to take away. --- antoine de saint-exupery I've noticed that the problem isn't that the .ICEauthority-* files are still there, it is because it claims it can't lock the files. This is why I suggested a while back that whenever a filesystem recovery occurs, if flags are present in the filesystem that mark files that are already locked, they should be cleared. Apparently there is no flag preserved by the filesystem, at least not relevant to fcntl (does the kernel keep a list of locks in ram?). D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Mon Sep 24 05:22:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8OCM5Q29580 for linux-xfs-outgoing; Mon, 24 Sep 2001 05:22:05 -0700 Received: from maul.jdc.home (Nm@c999639-a.carneg1.pa.home.com [24.180.243.111]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8OCM1e29560 for ; Mon, 24 Sep 2001 05:22:01 -0700 Received: from warblade.jdc.home (warblade.jdc.home [10.1.1.2]) by maul.jdc.home (8.12.0.Beta19/8.12.0.Beta19/Debian 8.12.0.Beta19) with ESMTP id f8OCMOej019528; Mon, 24 Sep 2001 07:22:24 -0500 Subject: Re: lock files after crash From: Jim Crilly To: stimits@idcomm.com Cc: linux-xfs@oss.sgi.com In-Reply-To: <3BAEE051.33A3656E@idcomm.com> References: <4.3.2.7.2.20010912091115.03368618@pop.xs4all.nl> <3B9F1B27.49261933@idcomm.com> <3B9F879E.3FB8976@ch.sauter-bc.com> <3BAEE051.33A3656E@idcomm.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 24 Sep 2001 08:20:10 -0400 Message-Id: <1001334011.953.8.camel@warblade> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 2001-09-24 at 03:27, D. Stimits wrote: > I've noticed that the problem isn't that the .ICEauthority-* files are > still there, it is because it claims it can't lock the files. This is > why I suggested a while back that whenever a filesystem recovery occurs, > if flags are present in the filesystem that mark files that are already > locked, they should be cleared. Apparently there is no flag preserved by > the filesystem, at least not relevant to fcntl (does the kernel keep a > list of locks in ram?). > > D. Stimits, stimits@idcomm.com Most programs just use regular files, (like file.lock) to determine if a lock is held or not because the Linux kernel doesn't enforce mandatory locking by default, and you have to jump some hoops to get it enabled so it's not common. Also, the kernel associates fcntl (POSIX style) locks with the process and the inode the lock is on, but flock (BSD style) are associated with the file object in memory, neither touch the filesystem on disk. They don't work together and are totally oblivious to the other's existance. Jim -- Help protect your rights on-line. Join the Electronic Frontiers Foundation today: http://www.eff.org/join ----------------------------------------------------------------------- Security: Antonyms: See Microsoft ----------------------------------------------------------------------- "We are coming after you. God may have mercy on you, but we won't," declared Sen. John McCain, R-Arizona. From owner-linux-xfs@oss.sgi.com Mon Sep 24 07:23:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8OENuH32589 for linux-xfs-outgoing; Mon, 24 Sep 2001 07:23:56 -0700 Received: from msg.ecetra.com (dollar.ecetra.com [193.164.224.209]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8OENhe32563 for ; Mon, 24 Sep 2001 07:23:43 -0700 Received: from vie-ac.office.ecetra.com (vie-ac.office.ecetra.com [10.251.148.147] (may be forged)) by msg.ecetra.com (8.9.3/8.9.3) with ESMTP id QAA26019; Mon, 24 Sep 2001 16:22:49 +0200 Received: from localhost (localhost [127.0.0.1]) by vie-ac.office.ecetra.com (8.11.6/8.11.3) with ESMTP id f8OEMip24345; Mon, 24 Sep 2001 16:22:44 +0200 Date: Mon, 24 Sep 2001 16:22:44 +0200 (CEST) From: Adam Cioccarelli To: cc: Seth Mos , , Subject: Re: gcc-2.96-nn status In-Reply-To: <3BA83ECB.D022D19D@club-internet.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by msg.ecetra.com id QAA26019 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8OENie32564 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Just my 2 cents worth, I've been using gcc 3.0 since it came out and as far as kernel (and most other things) go I have not had any problems at all.. ------------------------------------------------------------------------------- Adam Cioccarelli (B.E Mechanical) Adam.Cioccarelli@ecetra.com Database Administrator Phone: +43 1 536 89 7725 Fax: +43 1 536 89 7719 ecetra Central European e-Finance AG Mobile:+43 664 181 4195 ------------------------------------------------------------------------------- On Wed, 19 Sep 2001 jfm2@club-internet.fr wrote: > Seth Mos a écrit : > > > > At 21:26 18-9-2001 +0200, Jean Francois Martinez wrote: > > >Seth Mos a écrit : > > > > > > > At 13:02 18-9-2001 -0400, Arun Ramakrishnan wrote: > > > > >Hi, > > > > > I heard that 2.96 is again a devel version of gcc which is sorta > > > > > unstable.I > > > > > > > > It was a CVS snapshot. > > > > > > > > > >It was a CVS snapshot some 18 months ago. Eighteen months of bug hunting > > >later you can tell nothing about its stability. In fact because Gcc 2.96 was > > >frozen > > >over a year before gcc 3.0 and has been far more dceployed I trust it far m > > >ore than gcc 3.0+ > > > > True, but I gather 3.0+ will pop up in a lot more distributions then just > > redhat and mandrake. > > 3.0 is a official release which means it is not distribution specific. The > > reason that mandrake adopted is was more or less because a lot of mandrake > > is still redhat based. (no flame intended) > > > > I don't care which one is official what I care is which one crashes o > and which one miscompiles less often > For now gcc 3.0 is unproven and at least gcc 3.0 (don't know about gcc > 3.0.1) > has some horrific bugs far worse than those gcc 2.96 had in september > 2000. > > > Also RedHat and Mandrake have far more users than all the remaining > distributions > combined. Both RedHat ad Mandrake are poised to ship gcc 3 but gcc 2.96 > will be > the default compiler. > > > Mandrake is no longer a clone of RedHat. Factors were gcc 2.96 superior > C++ > respective to gcc 2.95, faster executables (benchmarked) and perhaps > support of > Itanium. > > > > The gcc people are working hard on getting 3.0 stable. Most kernel > > developers I met only work with official compilers. Not with wat shipped > > with their distro. > > > > Kernel developers only accepted gcc 2.95 much later than it becvame > official. > First official label does not confer magically bug free status and > second because > kernel is very specific and requires specific testing of the compiler. > > > > > > >heard posting saying that we shud downgrade to 2.95 possibly.I think with > > > > >RH 7.1 > > > > >,u no longer need kgcc to compile things correctly.gcc itself works.In > > > fact,i > > > > > > > > For most userland programs it seems to be fine but I have encounterd some > > > > utilities that don't like it. > > > > > >Gcc 2.96 requires C++ functions being declared before their use. I have > > >found > > >many programs who need to be fixed. > > > > The same for gcc-3.0 > > > > > > For kernels kgcc might be a better solution. > > > > > >The only gcc tested by kernel people are egcs and gcc 2.95. There is ever a > > >danger kernel > > >will break if compiled with a different compiler. On another hand gcc > > >2.96 has > > >been used in > > >the two most popular Linux distributions so is a good test bench. > > > > Expect more reports of 3.0 when that turns up in a new distribution. > > > > > > >heard sby commenting that now kgcc seems broke in RH 7.1 and so it is > > > safe to > > > > >use only gcc in RH 7.1;while it was mandatory to use kgcc in RH 7.0!!!! > > > > > > > > Not that I know off. > > > > > >AFAIK kgscc is no longer shipped with 7.1. > > > > [seth@stimpy /data]$ which kgcc > > /usr/bin/kgcc > > [seth@stimpy /data]$ cat /etc/redhat-release > > Red Hat Linux release 7.1 (Seawolf) > > [seth@stimpy /data]$ rpm -ql compat-egcs|grep kgcc > > /usr/bin/kgcc > > [seth@stimpy /data]$ > > > > > > > > Reason kgcc was in 7.0 was because > > >gcc 2.96 did not compile kernel 2.2. gcc 2.96 had its bugs but in that > > >case it > > >was due > > >to broken code in kernel that old more tolerant compilers accepted but > > >should not > > >have. > > >kernel 2.4 has no longer this problem. > > > > It's called compat-egcs for exactly that reason. It is a compatibility > > package including libs to compile packages for redhat 6.2 environments. > > > > > -march=i686. This will be a bit faster than compiling for i686. Gcc > > 2.96 > > >genrates faster code than egcs but if you are wary of it the above is the best > > >solution > > > > Comromises build the world > > -- > > Seth > > Every program has two purposes one for which > > it was written and another for which it wasn't > > I use the last kind. > > -- > Jean Francois Martinez > > The Independence project: because Linux should be for everyone > http://independence.seul.org > From owner-linux-xfs@oss.sgi.com Mon Sep 24 08:01:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8OF1WS00968 for linux-xfs-outgoing; Mon, 24 Sep 2001 08:01:32 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8OF1Te00948 for ; Mon, 24 Sep 2001 08:01:29 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8OF1OK00789 for ; Mon, 24 Sep 2001 08:01:24 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA3050050; Mon, 24 Sep 2001 10:00:07 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA18472; Mon, 24 Sep 2001 10:00:07 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8OF0Yn20433; Mon, 24 Sep 2001 10:00:34 -0500 Message-Id: <200109241500.f8OF0Yn20433@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: khromy cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.10-pre13-xfs Unresolved symbols in pagebuf.o In-Reply-To: Message from khromy of "Fri, 21 Sep 2001 19:29:32 EDT." <20010921192932.A26436@lnuxlab.ath.cx> Date: Mon, 24 Sep 2001 10:00:34 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Latest cvs checkout as of: Fri Sep 21 19:29:04 EDT 2001 > > make modules_install fails with: > > depmod: *** Unresolved symbols in /lib/modules/2.4.10-pre13-xfs/kernel/fs/pag > ebuf/pagebuf.o > depmod: discard_bh_page > > -- > L1: khromy ;khromy at lnuxlab.ath.cx OK, this should be fixed in the cvs tree shortly. Steve From owner-linux-xfs@oss.sgi.com Mon Sep 24 08:05:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8OF54101230 for linux-xfs-outgoing; Mon, 24 Sep 2001 08:05:04 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8OF51e01209 for ; Mon, 24 Sep 2001 08:05:01 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8OF4uK00936 for ; Mon, 24 Sep 2001 08:04:56 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA3047391 for ; Mon, 24 Sep 2001 10:03:40 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA39256 for ; Mon, 24 Sep 2001 10:03:40 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id f8OF47f21243; Mon, 24 Sep 2001 10:04:07 -0500 Message-Id: <200109241504.f8OF47f21243@jen.americas.sgi.com> Date: Mon, 24 Sep 2001 10:04:07 -0500 Subject: TAKE - fix pagebuf module build Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Export missing symbol. Date: Mon Sep 24 08:03:11 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103308a linux/kernel/ksyms.c - 1.110 - export discard_bh_page for pagebuf From owner-linux-xfs@oss.sgi.com Mon Sep 24 08:53:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8OFrIf02415 for linux-xfs-outgoing; Mon, 24 Sep 2001 08:53:18 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8OFrDe02392 for ; Mon, 24 Sep 2001 08:53:15 -0700 Received: from gumby.uwyo.edu (gumby.uwyo.edu [129.72.5.18]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id IAA01604 for ; Mon, 24 Sep 2001 08:52:58 -0700 (PDT) mail_from (ringram@uwyo.edu) Received: from uwyo.edu (localhost [127.0.0.1]) by gumby.uwyo.edu (8.11.6/8.11.6) with ESMTP id f8OFmSK24324 for ; Mon, 24 Sep 2001 09:48:29 -0600 Message-ID: <3BAF55CC.B35ED24@uwyo.edu> Date: Mon, 24 Sep 2001 09:48:28 -0600 From: Russ Ingram Organization: UW Math Dept/Institute for Scientific Computation X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.10-pre10-xfs-091701 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: .deb kernel packages Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I was just wondering how many people on this list are running debian and would be interested in having .deb kernel packages. I just learned how to make kernel packages on debian and would be willing to provide them if there is enough interest. Russ -- Russel H. Ingram Unix Systems Administrator Institute for Scientific Computation University of Wyoming/Math Dept. Phone: (307)766-6546 E-Mail: ringram@uwyo.edu From owner-linux-xfs@oss.sgi.com Mon Sep 24 15:35:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8OMZoU01865 for linux-xfs-outgoing; Mon, 24 Sep 2001 15:35:50 -0700 Received: from main.braxis.co.uk (root@main.braxis.co.uk [213.77.40.29]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8OMZiD01843 for ; Mon, 24 Sep 2001 15:35:45 -0700 Received: (from kszysiu@localhost) by main.braxis.co.uk (8.11.6/8.11.6) id f8OMZsR28613 for linux-xfs@oss.sgi.com; Tue, 25 Sep 2001 00:35:54 +0200 Date: Tue, 25 Sep 2001 00:35:54 +0200 From: Krzysztof Rusocki To: linux-xfs@oss.sgi.com Subject: cvs more issues Message-ID: <20010925003554.A28390@main.braxis.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Yet again, cvsd is up and running but as far as my interpretation is correct, some lock(s) remain(s) in repository (machine crashed durring commit?) thus making impossible to update the tree cvs server: [22:12:51] waiting for cvs's lock in /cvs/linux-2.4-xfs/linux/arch/arm/mach-anakin (...) cvs server: [22:34:52] waiting for cvs's lock in /cvs/linux-2.4-xfs/linux/arch/arm/mach-anakin Cheers, Krzysztof From owner-linux-xfs@oss.sgi.com Mon Sep 24 15:30:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8OMURs01636 for linux-xfs-outgoing; Mon, 24 Sep 2001 15:30:27 -0700 Received: from wagnerlab.med.harvard.edu (wagnerlab.med.harvard.edu [134.174.146.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8OMUJD01617 for ; Mon, 24 Sep 2001 15:30:20 -0700 Received: from plato.med.harvard.edu (plato.med.harvard.edu [134.174.146.37]) by wagnerlab.med.harvard.edu (SGI-8.9.3/8.9.3) with ESMTP id SAA37456 for ; Mon, 24 Sep 2001 18:30:13 -0400 (EDT) Received: from plato.med.harvard.edu (localhost [127.0.0.1]) by plato.med.harvard.edu (SGI-8.9.3/8.9.3) with ESMTP id SAA50667; Mon, 24 Sep 2001 18:30:12 -0400 (EDT) Message-ID: <3BAFB3F4.418906C6@plato.med.harvard.edu> Date: Mon, 24 Sep 2001 18:30:12 -0400 From: Sven G Hyberts X-Mailer: Mozilla 4.76C-SGI [en] (X11; I; IRIX64 6.5 IP28) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? Content-Type: multipart/alternative; boundary="------------5B2FB6697DFF55A57F0EC552" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --------------5B2FB6697DFF55A57F0EC552 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thank you for creating XFS v.1.0.1 for RedHat 7.1 Linux! It makes me much happier not to fsck all the time!!! Anyhow, I am trying to take this a further step - provide the same diskpartition local on both SGI and Linux. The trial setup is following - a 70 Gbyte FC Seagate Cheeta, via loop one linked to an Origin200 with Qlogic's 2200 card, and via loop two linked to a PC with RedHat 7.1/2.4.3-SGI_XFS_1.0.1 kernel. The Antares P-0033 card is recognized as a Qlogic's 2100 card. The disk drive is visiable from both end, formatted from the IRIX side. Currently, I have problems with putting a xfs file system on that is seen simultaniously from both sides. Using the whole disk (i.e., starting from block 0, and using the entire disk) I am able to make usable, but independent, file systems from both sides (haven't checked crash point yet), but this is not quite what I envisioned! (I envision to make a filesystem, such that when a file is created on either one system, it is visible directly on the other opposite system....) I am thankful for advice! Sincerely, -- ________________________________________________________________________ Sven G. Hyberts, Ph.D Research Associate Harvard University, Medical School e-mail: sven_hyberts@hms.harvard.edu 240 Longwood Ave; Dept BCMP voice: (617) 432-1721, 432-3211 Boston MA 02115 - USA fax: (617) 738-0516, 432-4383 --------------5B2FB6697DFF55A57F0EC552 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  
    Thank you for creating XFS v.1.0.1 for RedHat 7.1 Linux!  It makes me much happier not to fsck all the time!!!

    Anyhow, I am trying to take this a further step - provide the same diskpartition local on both SGI and Linux.
The trial setup is following - a 70 Gbyte FC Seagate Cheeta, via loop one linked to an Origin200 with Qlogic's
2200 card, and via loop two linked to a PC with RedHat 7.1/2.4.3-SGI_XFS_1.0.1 kernel.  The Antares P-0033
card is recognized as a Qlogic's 2100 card.

    The disk drive is visiable from both end, formatted from the IRIX side.   Currently, I have problems with
putting a xfs file system on that is seen simultaniously from both sides.  Using the whole disk (i.e., starting
from block 0, and using the entire disk) I am able to make usable, but independent, file systems from both sides
(haven't checked crash point yet), but this is not quite what I envisioned!  (I envision to make a filesystem, such
that when a file  is created on either one system, it is visible directly on the other opposite system....)

    I am thankful for advice!

    Sincerely, 

-- 
________________________________________________________________________
Sven G. Hyberts, Ph.D                             Research Associate
Harvard University, Medical School  e-mail: sven_hyberts@hms.harvard.edu
240 Longwood Ave; Dept BCMP          voice: (617) 432-1721, 432-3211
Boston MA 02115 - USA                  fax: (617) 738-0516, 432-4383
  --------------5B2FB6697DFF55A57F0EC552-- From owner-linux-xfs@oss.sgi.com Mon Sep 24 17:00:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8P00Eg03771 for linux-xfs-outgoing; Mon, 24 Sep 2001 17:00:14 -0700 Received: from chmls05.mediaone.net (chmls05.mediaone.net [24.147.1.143]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8P00AD03748 for ; Mon, 24 Sep 2001 17:00:11 -0700 Received: from computer (h0010b55a3e40.ne.mediaone.net [24.128.233.51]) by chmls05.mediaone.net (8.11.1/8.11.1) with SMTP id f8P006r19574 for ; Mon, 24 Sep 2001 20:00:06 -0400 (EDT) Message-ID: <000a01c14554$bfdebea0$33e98018@ne.mediaone.net> From: "Sven & Karolyn" To: Subject: Bouncing? Date: Mon, 24 Sep 2001 19:57:58 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C14533.3565D7C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C14533.3565D7C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I had one e-mail sent to this address bounce from Germany (!) - will = this bounce too? =20 ------=_NextPart_000_0007_01C14533.3565D7C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I had one e-mail sent to this address=20 bounce from Germany (!) - will this bounce too? =20
------=_NextPart_000_0007_01C14533.3565D7C0-- From owner-linux-xfs@oss.sgi.com Mon Sep 24 17:09:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8P093v04110 for linux-xfs-outgoing; Mon, 24 Sep 2001 17:09:03 -0700 Received: from wagnerlab.med.harvard.edu (wagnerlab.med.harvard.edu [134.174.146.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8P08vD04084 for ; Mon, 24 Sep 2001 17:08:58 -0700 Received: from plato.med.harvard.edu (plato.med.harvard.edu [134.174.146.37]) by wagnerlab.med.harvard.edu (SGI-8.9.3/8.9.3) with ESMTP id UAA37264 for ; Mon, 24 Sep 2001 20:08:52 -0400 (EDT) Received: from localhost (shyberts@localhost) by plato.med.harvard.edu (SGI-8.9.3/8.9.3) with ESMTP id UAA50995 for ; Mon, 24 Sep 2001 20:08:51 -0400 (EDT) Date: Mon, 24 Sep 2001 20:08:51 -0400 From: Sven G Hyberts Reply-To: Sven Hyberts To: linux-xfs@oss.sgi.com Subject: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thank you for creating XFS v.1.0.1 for RedHat 7.1 Linux! It makes me much happier not to fsck all the time!!! Anyhow, I am trying to take this a further step - provide the same diskpartition local on both SGI and Linux. The trial setup is following - a 70 Gbyte FC Seagate Cheeta, via loop one linked to an Origin200 with Qlogic's 2200 card, and via loop two linked to a PC with RedHat 7.1/2.4.3-SGI_XFS_1.0.1 kernel. The Antares P-0033 card is recognized as a Qlogic's 2100 card. The disk drive is visible from both end, formatted from the IRIX side. Currently, I have problems with putting a xfs file system on that is seen simultaniously from both sides. Using the whole disk (i.e., starting from block 0, and using the entire disk) I am able to make usable, but independent, file systems from both sides (haven't checked crash point yet), but this is not quite what I envisioned! I envision to make a filesystem, such that when a file is created on either one system, it is visible directly on the other opposite system.... Your FAQ indicate that it is possible to bring over XFS disks from IRIX environment to the Linux environment, so, I am thankful for advice! Sincerely, -- ________________________________________________________________________ Sven G. Hyberts, Ph.D Research Associate Harvard University, Medical School e-mail: sven_hyberts@hms.harvard.edu 240 Longwood Ave; Dept BCMP voice: (617) 432-1721, 432-3211 Boston MA 02115 - USA fax: (617) 738-0516, 432-4383 From owner-linux-xfs@oss.sgi.com Mon Sep 24 20:14:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8P3EVR09174 for linux-xfs-outgoing; Mon, 24 Sep 2001 20:14:31 -0700 Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8P3ETD09151 for ; Mon, 24 Sep 2001 20:14:29 -0700 Message-Id: <200109250314.f8P3ETD09151@oss.sgi.com> Received: (qmail 34194 invoked from network); 25 Sep 2001 03:14:29 -0000 Received: from unknown (HELO there) ([216.254.50.67]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 25 Sep 2001 03:14:29 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Steven Farrier To: linux-xfs@oss.sgi.com Subject: Preemption and XFS Date: Mon, 24 Sep 2001 20:12:45 -0700 X-Mailer: KMail [version 1.3.1] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >The patch to XFS to coexist with the preemption patch is already in. >But you have to apply the main preemption patch yourself. I wanted to know what order are you supposed to install these patchs Also for patch -p1 < patch is the 1 supposed to be replaced with a 2 when installing the second patch? Steve From owner-linux-xfs@oss.sgi.com Mon Sep 24 23:54:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8P6sAY12883 for linux-xfs-outgoing; Mon, 24 Sep 2001 23:54:10 -0700 Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8P6s6D12862 for ; Mon, 24 Sep 2001 23:54:06 -0700 Received: from bt02e0.god.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id f8P6rtK24007; Tue, 25 Sep 2001 08:53:55 +0200 (MET DST) Received: from god.bel.alcatel.be (bt02e1.god.bel.alcatel.be [138.203.145.14]) by bt02e0.god.bel.alcatel.be (8.9.3+Sun/8.9.3/1.1) with ESMTP id IAA28450; Tue, 25 Sep 2001 08:53:00 +0200 (MET DST) Message-ID: <3BB0294F.66AB7201@god.bel.alcatel.be> Date: Tue, 25 Sep 2001 08:50:55 +0200 From: kris buggenhout X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" CC: Steven Farrier Subject: Re: Preemption and XFS References: <200109250314.f8P3ETD09151@oss.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steven Farrier wrote: > > >The patch to XFS to coexist with the preemption patch is already in. > >But you have to apply the main preemption patch yourself. > > I wanted to know what order are you supposed to install these patchs > normally U should patch a vanilla kernel with the preemption patch and then the xfs patch, then the xfs preemtpion patch... > Also for patch -p1 < patch is the 1 supposed to be replaced with a 2 when > installing the second patch? > not really , patch -p[n] means strip [n] levels off of the path specified in the patch file... this means U can go and sit in the dir and dont care what its called in the patch or local... :) From owner-linux-xfs@oss.sgi.com Mon Sep 24 23:55:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8P6t8i13021 for linux-xfs-outgoing; Mon, 24 Sep 2001 23:55:08 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8P6t4D13002 for ; Mon, 24 Sep 2001 23:55:04 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA03274; Tue, 25 Sep 2001 08:54:59 +0200 (CEST) Message-Id: <4.3.2.7.2.20010925085205.03f00808@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 25 Sep 2001 08:54:25 +0200 To: Steven Farrier , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Preemption and XFS In-Reply-To: <200109250314.f8P3ETD09151@oss.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 20:12 24-9-2001 -0700, Steven Farrier wrote: > >The patch to XFS to coexist with the preemption patch is already in. > >But you have to apply the main preemption patch yourself. > >I wanted to know what order are you supposed to install these patchs > >Also for patch -p1 < patch is the 1 supposed to be replaced with a 2 when >installing the second patch? No, the -p1 instructs patch to start patching in path deeper in the directory structure. A lot of times patches are for a directory that does not exist on the local side. By going into the directory you want to patch and specifying the -p1 it leaves out the first part of the path. Read the manpage. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Sep 25 00:00:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8P701113285 for linux-xfs-outgoing; Tue, 25 Sep 2001 00:00:01 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8P6xvD13244 for ; Mon, 24 Sep 2001 23:59:57 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA04909; Tue, 25 Sep 2001 08:59:31 +0200 (CEST) Message-Id: <4.3.2.7.2.20010925085830.03335520@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 25 Sep 2001 08:58:56 +0200 To: Krzysztof Rusocki , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: cvs more issues In-Reply-To: <20010925003554.A28390@main.braxis.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 00:35 25-9-2001 +0200, Krzysztof Rusocki wrote: >Yet again, > >cvsd is up and running but as far as my interpretation >is correct, some lock(s) remain(s) in repository >(machine crashed durring commit?) thus making impossible >to update the tree > >cvs server: [22:12:51] waiting for cvs's lock in >/cvs/linux-2.4-xfs/linux/arch/arm/mach-anakin >(...) >cvs server: [22:34:52] waiting for cvs's lock in >/cvs/linux-2.4-xfs/linux/arch/arm/mach-anakin Works for me although I did not try a clean checkout. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Sep 25 02:51:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8P9p5418147 for linux-xfs-outgoing; Tue, 25 Sep 2001 02:51:05 -0700 Received: from main.braxis.co.uk (root@main.braxis.co.uk [213.77.40.29]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8P9orD18102 for ; Tue, 25 Sep 2001 02:50:55 -0700 Received: (from kszysiu@localhost) by main.braxis.co.uk (8.11.6/8.11.6) id f8P9oZl10470; Tue, 25 Sep 2001 11:50:35 +0200 Date: Tue, 25 Sep 2001 11:50:35 +0200 From: Krzysztof Rusocki To: Seth Mos Cc: linux-xfs@oss.sgi.com Subject: Re: cvs more issues Message-ID: <20010925115035.A10341@main.braxis.co.uk> References: <20010925003554.A28390@main.braxis.co.uk> <4.3.2.7.2.20010925085830.03335520@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.20010925085830.03335520@pop.xs4all.nl>; from knuffie@xs4all.nl on Tue, Sep 25, 2001 at 08:58:56AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 25, 2001 at 08:58:56AM +0200, Seth Mos wrote: Hi Seth, > > Works for me although I did not try a clean checkout. Apparently I tried doing update in that "improper" time when oss crashed and slightly later when it was brought to life :/ After about one hour since then i did a fresh c-o and everything was absolutely correct. Thanks for interest. Cheers, Krzysztof > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Sep 25 08:38:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PFcpe27517 for linux-xfs-outgoing; Tue, 25 Sep 2001 08:38:51 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PFcOD27451 for ; Tue, 25 Sep 2001 08:38:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id IAA02529 for ; Tue, 25 Sep 2001 08:38:20 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA3060440; Tue, 25 Sep 2001 10:37:07 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA27447; Tue, 25 Sep 2001 10:37:06 -0500 (CDT) Message-ID: <3BB0A43B.A598329A@sgi.com> Date: Tue, 25 Sep 2001 10:35:23 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Sven Hyberts CC: linux-xfs@oss.sgi.com Subject: Re: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sven G Hyberts wrote: > > I am able to make > usable, but independent, file systems from both sides (haven't checked > crash point yet), but this is not quite what I envisioned! More information on how it fails would be helpful. For starters, have you made the filesystem on the Irix side using a 4k blocksize and version 2 directory format? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Tue Sep 25 08:38:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PFcVp27472 for linux-xfs-outgoing; Tue, 25 Sep 2001 08:38:31 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PFcQD27453 for ; Tue, 25 Sep 2001 08:38:27 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 80C6AC00B62 for ; Tue, 25 Sep 2001 23:38:23 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 078A4C00B60 for ; Tue, 25 Sep 2001 23:38:21 +0800 (PHT) Date: Tue, 25 Sep 2001 23:38:20 +0800 (PHT) From: Federico Sevilla III To: Linux XFS Mailing List Subject: Re: .deb kernel packages In-Reply-To: <3BAF55CC.B35ED24@uwyo.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 24 Sep 2001 at 09:48, Russ Ingram wrote: > I was just wondering how many people on this list are running debian > and would be interested in having .deb kernel packages. I just > learned how to make kernel packages on debian and would be willing to > provide them if there is enough interest. I'm using Debian (unstable) and have been using XFS for awhile now on production and development machines. I'm not particularly interested in getting someone else's kernel packages, but I'm sure that a lot of would-be XFS converts will appreciate XFS-enabled kernel packages available for download. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. GnuPG Key: From owner-linux-xfs@oss.sgi.com Tue Sep 25 08:57:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PFvs528176 for linux-xfs-outgoing; Tue, 25 Sep 2001 08:57:54 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PFvoD28157 for ; Tue, 25 Sep 2001 08:57:50 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 38F55C00B62 for ; Tue, 25 Sep 2001 23:57:48 +0800 (PHT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id D7035C00B60 for ; Tue, 25 Sep 2001 23:57:46 +0800 (PHT) Delivered-To: jijo@leathercollection.ph X-Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 186B5C00B62 for ; Tue, 25 Sep 2001 23:56:58 +0800 (PHT) X-Received: from wwweasel.geeksrus.net (unknown [64.67.200.82]) by gusi.leathercollection.ph (Postfix) with ESMTP id 4A591C00B60 for ; Tue, 25 Sep 2001 23:56:55 +0800 (PHT) X-Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f8PFuhS22508 for jijo@leathercollection.ph; Tue, 25 Sep 2001 11:56:43 -0400 Date: Tue, 25 Sep 2001 11:56:43 -0400 From: Alan Eldridge To: Federico Sevilla III Subject: Re: .deb kernel packages Message-ID: <20010925115643.A20726@wwweasel.geeksrus.net> References: <3BAF55CC.B35ED24@uwyo.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jijo@leathercollection.ph on Tue, Sep 25, 2001 at 11:38:20PM +0800 X-Virus-Scanned: by AMaViS perl-11 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 25, 2001 at 11:38:20PM +0800, Federico Sevilla III wrote: >I'm using Debian (unstable) and have been using XFS for awhile now on >production and development machines. I'm not particularly interested in >getting someone else's kernel packages, but I'm sure that a lot of >would-be XFS converts will appreciate XFS-enabled kernel packages >available for download. :) I make daily builds of the CVS tree, packaged into RPMS, but I don't have a server to place them on to handle the traffic. I don't wan't that hitting my home SDSL link, or it won't be a 768K link anymore. There is an excellent package called Alien that could convert the .rpm to .deb. My entire build system is available over the web as well, although it is password protected. I will rearrange the protection and then post when it is open except for the RPMS themselves. If anyone has a server that can host the rpms or debs, I can make them available on a daily basis. -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Tue Sep 25 08:58:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PFweT28250 for linux-xfs-outgoing; Tue, 25 Sep 2001 08:58:40 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PFwaD28228 for ; Tue, 25 Sep 2001 08:58:36 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id f8PFwYW22598 for linux-xfs@oss.sgi.com; Tue, 25 Sep 2001 11:58:34 -0400 Date: Tue, 25 Sep 2001 11:58:34 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: [alane@geeksrus.net: Re: .deb kernel packages] Message-ID: <20010925115834.B20726@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Sep 25, 2001 at 11:38:20PM +0800, Federico Sevilla III wrote: >I'm using Debian (unstable) and have been using XFS for awhile now on >production and development machines. I'm not particularly interested in >getting someone else's kernel packages, but I'm sure that a lot of >would-be XFS converts will appreciate XFS-enabled kernel packages >available for download. :) I make daily builds of the CVS tree, packaged into RPMS, but I don't have a server to place them on to handle the traffic. I don't wan't that hitting my home SDSL link, or it won't be a 768K link anymore. There is an excellent package called Alien that could convert the .rpm to .deb. My entire build system is available over the web as well, although it is password protected. I will rearrange the protection and then post when it is open except for the RPMS themselves. If anyone has a server that can host the rpms or debs, I can make them available on a daily basis. [alane@wwweasel alane]$ ls Projects/SGI/RPMS/current/RPMS/ acl-1.1.3-cvs.20010924.0.i386.rpm acl-devel-1.1.3-cvs.20010924.0.i386.rpm attr-1.1.3-cvs.20010924.0.i386.rpm attr-devel-1.1.3-cvs.20010924.0.i386.rpm devfsd-2.4.10-SGI_XFS_cvs.20010924.0.i386.rpm dmapi-0.2.2-cvs.20010924.0.i386.rpm dmapi-devel-0.2.2-cvs.20010924.0.i386.rpm kernel-2.4.10-SGI_XFS_cvs.20010924.0.athlon.rpm kernel-2.4.10-SGI_XFS_cvs.20010924.0.i386.rpm kernel-2.4.10-SGI_XFS_cvs.20010924.0.i686.rpm kernel-doc-2.4.10-SGI_XFS_cvs.20010924.0.i386.rpm kernel-headers-2.4.10-SGI_XFS_cvs.20010924.0.i386.rpm kernel-smp-2.4.10-SGI_XFS_cvs.20010924.0.athlon.rpm kernel-smp-2.4.10-SGI_XFS_cvs.20010924.0.i686.rpm kernel-source-2.4.10-SGI_XFS_cvs.20010924.0.i386.rpm xfsdump-1.1.4-cvs.20010924.0.i386.rpm xfsprogs-1.3.8-cvs.20010924.0.i386.rpm xfsprogs-devel-1.3.8-cvs.20010924.0.i386.rpm -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Tue Sep 25 09:59:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PGx3e29476 for linux-xfs-outgoing; Tue, 25 Sep 2001 09:59:03 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PGx0D29457 for ; Tue, 25 Sep 2001 09:59:00 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id JAA03628 for ; Tue, 25 Sep 2001 09:58:56 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2922532; Tue, 25 Sep 2001 11:57:42 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA26979; Tue, 25 Sep 2001 11:57:42 -0500 (CDT) Message-ID: <3BB0B71E.382B7F14@sgi.com> Date: Tue, 25 Sep 2001 11:55:58 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Austin Gonyou CC: linux-xfs@oss.sgi.com Subject: Re: 2.4.10 patch? References: <1001284650.8217.1.camel@UberGeek> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Austin Gonyou wrote: > > Is there a 2.4.10 final patch available yet? The patch is now available on oss.sgi.com: ftp://oss.sgi.com/projects/xfs/download/patches/ Bear in mind that this is a development snapshot, and therefore has not had extensive or rigorous testing. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Tue Sep 25 10:48:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PHmaO30454 for linux-xfs-outgoing; Tue, 25 Sep 2001 10:48:36 -0700 Received: from gumby.uwyo.edu (gumby.uwyo.edu [129.72.5.18]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PHmWD30435 for ; Tue, 25 Sep 2001 10:48:32 -0700 Received: from uwyo.edu (localhost [127.0.0.1]) by gumby.uwyo.edu (8.11.6/8.11.6) with ESMTP id f8PHrOK28203; Tue, 25 Sep 2001 11:53:25 -0600 Message-ID: <3BB0C494.B465F0BE@uwyo.edu> Date: Tue, 25 Sep 2001 11:53:24 -0600 From: Russ Ingram Reply-To: ringram@uwyo.edu Organization: UW Math Dept/Institute for Scientific Computation X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.10-pre10-xfs-091701 i686) X-Accept-Language: en MIME-Version: 1.0 To: Eric Sandeen CC: linux-xfs@oss.sgi.com Subject: Re: 2.4.10 patch? References: <1001284650.8217.1.camel@UberGeek> <3BB0B71E.382B7F14@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > > Austin Gonyou wrote: > > > > Is there a 2.4.10 final patch available yet? > > The patch is now available on oss.sgi.com: > > ftp://oss.sgi.com/projects/xfs/download/patches/ > > Bear in mind that this is a development snapshot, and therefore has not > had extensive or rigorous testing. > > -Eric > > -- > Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs > sandeen@sgi.com SGI, Inc. Is there a significant difference between the patch for 2.4.10 and the patch for 2.4.10pre13? The pre13 patch applies cleanly but I haven't actually tested the resulting kernel yet. -- Russel H. Ingram Unix Systems Administrator Institute for Scientific Computation University of Wyoming/Math Dept. Phone: (307)766-6546 E-Mail: ringram@uwyo.edu From owner-linux-xfs@oss.sgi.com Tue Sep 25 11:38:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PIc3A31638 for linux-xfs-outgoing; Tue, 25 Sep 2001 11:38:03 -0700 Received: from thor.goeci.com (thor.goeci.com [216.181.40.16]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PIbwD31619 for ; Tue, 25 Sep 2001 11:37:58 -0700 Received: by THOR with Internet Mail Service (5.5.2650.21) id ; Tue, 25 Sep 2001 14:37:52 -0400 Message-ID: From: Murthy Kambhampaty To: "'Bryan-TheBS-Smith'" , Eric Sandeen Cc: Murthy Kambhampaty , "'linux-xfs@oss.sgi.com'" Subject: RE: Installing on disks connected with 3ware adapter Date: Tue, 25 Sep 2001 14:37:48 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > -----Original Message----- > From: Bryan-TheBS-Smith [mailto:b.j.smith@ieee.org] > Sent: Monday, September 10, 2001 16:36 > To: Eric Sandeen > Cc: Murthy Kambhampaty; 'linux-xfs@oss.sgi.com' > Subject: Re: Installing on disks connected with 3ware adapter > > > Eric Sandeen wrote: > > I'm not sure how you created the drivers floppy - if it's > the same one > > you used with RH Linux 7.1, it won't work with the XFS > installer since > > we run a different (xfs-capable, 2.4.3-updated) kernel in our > > installer. You'll need to recompile the driver to be > loadable under the > > 2.4.3-BOOT kernel we use in the installer. > > I had the same issue. This is what I did: > > - Install RedHat 7.1 + XFS 1.0.1 on a regular drive > - Grab the updated firmware and drivers for the 7000 series > - Compile the driver module for the kernel, copy to > modules directory > - Create an initrd (initial root disk) for the kernel with > the 3Ware driver > - Modify and re-install LILO for the kernel+initrd > - Reboot with 3Ware card/drives connected > - Transfer over the partitions > - Boot the XFS installer into recovery mode > - Re-install LILO > > I found this to be quickest and easiest. It appears that since the XFS Installer version 1.0.1 includes the 3ware driver compiled as a module, one can simply add "alias escalade 3w-xxxx" or some such to /etc/modules.conf and skip the first 3 steps fo Bryan's excellent guide. Murthy From owner-linux-xfs@oss.sgi.com Tue Sep 25 11:44:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PIiVU31879 for linux-xfs-outgoing; Tue, 25 Sep 2001 11:44:31 -0700 Received: from thor.goeci.com (thor.goeci.com [216.181.40.16]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PIiTD31860 for ; Tue, 25 Sep 2001 11:44:29 -0700 Received: by THOR with Internet Mail Service (5.5.2650.21) id ; Tue, 25 Sep 2001 14:44:24 -0400 Message-ID: From: Murthy Kambhampaty To: "'Linux-Xfs (E-mail)" Subject: Installing to Mylex Acceleraid 352 Date: Tue, 25 Sep 2001 14:44:17 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am having a problem installing with the XFS 1.0.1. installer to a RAID5 array on a Mylex Acceleraid 352: the install goes fine, but when I reboot LILO hangs LI My system is a SuperMicro server with ServerWorks HE chipset, one SCSI HDD on channel A and Mylex card at PCI slot 4. All partitions (/,/boot,/var,/home) are formatted XFS, swap is on /dev/sda. If I install the entire system on /dev/sda, I have no problems. Thanks for the help, Murthy From owner-linux-xfs@oss.sgi.com Tue Sep 25 12:31:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PJVoC00437 for linux-xfs-outgoing; Tue, 25 Sep 2001 12:31:50 -0700 Received: from rj.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PJVmD00418 for ; Tue, 25 Sep 2001 12:31:48 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8PJVgL02090 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 25 Sep 2001 12:31:42 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA1071797 for ; Tue, 25 Sep 2001 21:31:38 +0200 (CEST) mail_from (eric@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA3063261 for ; Tue, 25 Sep 2001 14:30:24 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA76548 for ; Tue, 25 Sep 2001 14:30:24 -0500 (CDT) Received: by stout.americas.sgi.com (8.11.2/SGI-client-1.7) id f8PJSdk19141; Tue, 25 Sep 2001 14:28:39 -0500 Message-Id: <200109251928.f8PJSdk19141@stout.americas.sgi.com> Date: Tue, 25 Sep 2001 14:28:39 -0500 From: Eric Sandeen Subject: TAKE - free nfs refcache on module unload Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk If the nfs refcache was allocated & used, it never got freed on module unload. Memory leak when serving XFS via NFS, with XFS as a module. Date: Tue Sep 25 12:28:31 PDT 2001 Workarea: stout.americas.sgi.com:/localhome/eric/2.4.x-xfs/workarea-clean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103405a linux/fs/xfs/xfs_vfsops.c - 1.325 - Free nfs refcache on module unload From owner-linux-xfs@oss.sgi.com Tue Sep 25 13:32:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PKWUa02021 for linux-xfs-outgoing; Tue, 25 Sep 2001 13:32:30 -0700 Received: from tarzan.eng.uiowa.edu (tarzan.eng.uiowa.edu [128.255.22.247]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PKWRD01999 for ; Tue, 25 Sep 2001 13:32:27 -0700 Received: by tarzan.eng.uiowa.edu (Postfix, from userid 14139) id 68399241E9B; Tue, 25 Sep 2001 15:37:55 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by tarzan.eng.uiowa.edu (Postfix) with ESMTP id 661D8241E9A for ; Tue, 25 Sep 2001 15:37:55 -0400 (EDT) Date: Tue, 25 Sep 2001 15:37:55 -0400 (EDT) From: X-Sender: To: Subject: Permission Problems with XFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk We are using the 2.4.5-xfs-1.0.1 kernel running XFS on a couple 500 Gig. raids. Since the move to the 2.4.5-xfs-1.0.1 kernel our systems have been much more stable. However, we still sometimes receive odd permission mutations on some of our files in the filesystem. Lately the group write permission has been disappearing on an occational file. I couldn't find any new releases of the kernels lately so I am assuming that 2.4.5 is still the latest stable kernel. My question is, has anyone else had simular problems with this latest kernel? Thanks. ************************************************************************** Coordinated Laboratory for Computational Genomics Jesse Walters jwalters@engineering.uiowa.edu 5315SC (319) 335-5703 Iowa City, IA 52242 The gene pool could use a little chlorine. ************************************************************************** From owner-linux-xfs@oss.sgi.com Tue Sep 25 13:45:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8PKjin02327 for linux-xfs-outgoing; Tue, 25 Sep 2001 13:45:44 -0700 Received: from chimta01.algx.net (chimta01.algx.net [216.99.233.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8PKjeD02307 for ; Tue, 25 Sep 2001 13:45:40 -0700 Received: from jtsdell (66-2-81-28.customer.algx.net [66.2.81.28]) by chimmx01.algx.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GK800E93KC1XY@chimmx01.algx.net> for linux-xfs@oss.sgi.com; Tue, 25 Sep 2001 15:45:38 -0500 (CDT) Date: Tue, 25 Sep 2001 16:46:19 -0400 (EDT) From: jtrostel@snapserver.com Subject: problem in "make install" for xfsdump To: XFS list Reply-to: jtrostel@snapserver.com Message-id: Organization: Snap Appliances MIME-version: 1.0 X-Mailer: XFMail 1.5.1 on Linux Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Priority: 3 (Normal) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Anyone else see this compiling todays CVS of ../cmds/xfsdump? (using gcc-2.96-81 on RH7.1 ...sorta) attr.c: In function `attr_multi_by_handle': attr.c:57: `attr_op_t' undeclared (first use in this function) attr.c:57: (Each undeclared identifier is reported only once attr.c:57: for each function it appears in.) attr.c:57: `ops' undeclared (first use in this function) attr.c:57: warning: statement with no effect attr.c:58: parse error before `int' attr.c:75: `i' undeclared (first use in this function) attr.c:83: `fsfd' undeclared (first use in this function) attr.c:88: `hreq' undeclared (first use in this function) attr.c:96: `attr_hreq' undeclared (first use in this function) attr.c: In function `attr_list_by_handle': attr.c:123: `attr_op_t' undeclared (first use in this function) attr.c:123: parse error before `op' attr.c:128: `op' undeclared (first use in this function) attr.c:129: `ATTR_OP_IRIX_LIST' undeclared (first use in this function) make[1]: *** [attr.o] Error 1 make: *** [default] Error 2 -- John M. Trostel Senior Software Engineer Quantum / SnapAppliances jtrostel@snapserver.com From owner-linux-xfs@oss.sgi.com Tue Sep 25 18:22:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8Q1MoS08572 for linux-xfs-outgoing; Tue, 25 Sep 2001 18:22:50 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8Q1MiD08553 for ; Tue, 25 Sep 2001 18:22:45 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id SAA03082 for ; Tue, 25 Sep 2001 18:21:29 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id LAA11222; Wed, 26 Sep 2001 11:21:24 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id MAA51397; Wed, 26 Sep 2001 12:21:11 +1100 (AEDT) Date: Wed, 26 Sep 2001 12:21:10 +1100 From: Nathan Scott To: jtrostel@snapserver.com Cc: XFS list Subject: Re: problem in "make install" for xfsdump Message-ID: <20010926122110.B463360@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 jtrostel@snapserver.com on Tue, Sep 25, 2001 at 04:46:19PM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi John, You've done a "make install install-dev" in the cmd/attr2 directory right? Don't do that - its development code and uses syscalls which don't exist yet in the kernel - you'll need to use cmd/attr still (a "make install install-dev" in that directory should fix the problem). When the new attr code is ready, it will simply replace the cmd/attr code and cmd/attr2 will go away. I need attr2 to help my discussions with the ext2 extended attribute project, otherwise you wouldn't have seen it at all yet - sorry about the confusion. cheers. ps: any luck with that Samba issue I sent you the other day? On Tue, Sep 25, 2001 at 04:46:19PM -0400, jtrostel@snapserver.com wrote: > Anyone else see this compiling todays CVS of ../cmds/xfsdump? > > (using gcc-2.96-81 on RH7.1 ...sorta) > > attr.c: In function > `attr_multi_by_handle': > attr.c:57: `attr_op_t' undeclared (first use in this function) > attr.c:57: (Each undeclared identifier is reported only once > attr.c:57: for each function it appears in.) > attr.c:57: `ops' undeclared (first use in this function) > attr.c:57: warning: statement with no effect > attr.c:58: parse error before `int' > attr.c:75: `i' undeclared (first use in this function) > attr.c:83: `fsfd' undeclared (first use in this function) > attr.c:88: `hreq' undeclared (first use in this function) > attr.c:96: `attr_hreq' undeclared (first use in this function) > attr.c: In function `attr_list_by_handle': > attr.c:123: `attr_op_t' undeclared (first use in this function) > attr.c:123: parse error before `op' > attr.c:128: `op' undeclared (first use in this function) > attr.c:129: `ATTR_OP_IRIX_LIST' undeclared (first use in this function) > make[1]: *** [attr.o] Error 1 > make: *** [default] Error 2 > > -- > John M. Trostel > Senior Software Engineer > Quantum / SnapAppliances > jtrostel@snapserver.com > -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 25 19:33:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8Q2XlF09666 for linux-xfs-outgoing; Tue, 25 Sep 2001 19:33:47 -0700 Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8Q2XgD09646 for ; Tue, 25 Sep 2001 19:33:43 -0700 Received: from walt400.localhost (user-uini7lc.dialup.mindspring.com [165.121.30.172]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id WAA22424 for ; Tue, 25 Sep 2001 22:33:42 -0400 (EDT) Received: from mindspring.com (localhost.localdomain [127.0.0.1]) by walt400.localhost (Postfix) with ESMTP id 666BB810CB5 for ; Tue, 25 Sep 2001 19:24:13 -0700 (PDT) Message-ID: <3BB13C4C.6060800@mindspring.com> Date: Tue, 25 Sep 2001 19:24:12 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Preemptive patch w/ 2.4.10 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, Before I hose my linux box, I've got a quick question regarding the preemptive patches. According to the changelog for the preemptive patches: This is a ChangeLog for patch-rml-preempt Currently synced with 2.4.10-pre14 and 2.4.9-ac14 SMP is now considered stable, but YMMV 20010919 - push XFS fix into XFS CVS Does this mean that there is just the one needed to create preemptive XFS kernel? I've applied the current preemptive patch against the 2.4.10-xfs kernel and it applies (although with a few offsets) and compiles cleanly. If I'm not mistaken, that patch process used to be: Apply preemptive patches Apply XFS patches Apply XFS fixes Am I correct? Sorry about the slightly OT message here, it's just that the entry in the Changelog made me think the fix was already within the CVS tree (which I almost always use to compile kernels from) and all I needed was the preemptive patch against the current CVS - as it's nearly a clean Linus + XFS kernel (I think). Thanks for any help. PS. Thanks to all for the great FS. I still can't believe how awesome it is to run a FREE OS with such awesome capabilities. I really appreciate everyone's hard work. Thanks, -Walt From owner-linux-xfs@oss.sgi.com Tue Sep 25 20:28:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8Q3S0Q10632 for linux-xfs-outgoing; Tue, 25 Sep 2001 20:28:00 -0700 Received: from rj.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8Q3RwD10613 for ; Tue, 25 Sep 2001 20:27:58 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8Q3RqL23005 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 25 Sep 2001 20:27:52 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id FAA1129620 for ; Wed, 26 Sep 2001 05:27:47 +0200 (CEST) mail_from (kaos@melbourne.sgi.com) Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by nodin.corp.sgi.com (8.11.4/8.11.2/nodin-1.0) with ESMTP id f8Q3Qms1378784; Tue, 25 Sep 2001 20:26:48 -0700 (PDT) Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id 8A62E3000B7; Wed, 26 Sep 2001 13:26:47 +1000 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id 69361B8; Wed, 26 Sep 2001 13:26:47 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Walt H Cc: linux-xfs@oss.sgi.com Subject: Re: Preemptive patch w/ 2.4.10 In-reply-to: Your message of "Tue, 25 Sep 2001 19:24:12 MST." <3BB13C4C.6060800@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Sep 2001 13:26:42 +1000 Message-ID: <25579.1001474802@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 25 Sep 2001 19:24:12 -0700, Walt H wrote: >20010919 >- push XFS fix into XFS CVS They sent me the required changes to XFS and they are now included in the XFS CVS tree. It was just adding #include to two files. AFAIK XFS in CVS is preemtible ready. From owner-linux-xfs@oss.sgi.com Tue Sep 25 20:34:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8Q3Y8Q10858 for linux-xfs-outgoing; Tue, 25 Sep 2001 20:34:08 -0700 Received: from hall.mail.mindspring.net (hall.mail.mindspring.net [207.69.200.60]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8Q3Y4D10839 for ; Tue, 25 Sep 2001 20:34:04 -0700 Received: from walt400.localhost (user-uini7lc.dialup.mindspring.com [165.121.30.172]) by hall.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA31037 for ; Tue, 25 Sep 2001 23:34:03 -0400 (EDT) Received: from mindspring.com (localhost.localdomain [127.0.0.1]) by walt400.localhost (Postfix) with ESMTP id C6D4B8194C0; Tue, 25 Sep 2001 20:32:31 -0700 (PDT) Message-ID: <3BB14C4F.4020701@mindspring.com> Date: Tue, 25 Sep 2001 20:32:31 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914 X-Accept-Language: en-us MIME-Version: 1.0 To: Keith Owens Cc: linux-xfs@oss.sgi.com Subject: Re: Preemptive patch w/ 2.4.10 References: <25579.1001474802@kao2.melbourne.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thanks Keith - I'm running it now and all seems OK. Between 2.4.10 with its VM changes and the preemptive patch, the system feels rather snappy. Definitely an improvement over previous 2.4 kernels. Thanks again, -Walt Keith Owens wrote: > On Tue, 25 Sep 2001 19:24:12 -0700, > Walt H wrote: > >>20010919 >>- push XFS fix into XFS CVS >> > > They sent me the required changes to XFS and they are now included in > the XFS CVS tree. It was just adding #include to two > files. AFAIK XFS in CVS is preemtible ready. > > From owner-linux-xfs@oss.sgi.com Tue Sep 25 20:51:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8Q3p7511269 for linux-xfs-outgoing; Tue, 25 Sep 2001 20:51:07 -0700 Received: from rj.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8Q3owD11250 for ; Tue, 25 Sep 2001 20:50:58 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8Q3oqL23399 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Tue, 25 Sep 2001 20:50:52 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id FAA1144061 for ; Wed, 26 Sep 2001 05:50:48 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id NAA11940; Wed, 26 Sep 2001 13:49:32 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id OAA39103; Wed, 26 Sep 2001 14:49:31 +1100 (AEDT) Date: Wed, 26 Sep 2001 14:49:30 +1100 From: Nathan Scott To: Russ Ingram Cc: linux-xfs@oss.sgi.com Subject: Re: .deb kernel packages Message-ID: <20010926144930.D463360@wobbly.melbourne.sgi.com> References: <3BAF55CC.B35ED24@uwyo.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BAF55CC.B35ED24@uwyo.edu>; from ringram@uwyo.edu on Mon, Sep 24, 2001 at 09:48:28AM -0600 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Mon, Sep 24, 2001 at 09:48:28AM -0600, Russ Ingram wrote: > I was just wondering how many people on this list are running > debian and would be interested in having .deb kernel packages. I > just learned how to make kernel packages on debian and would be > willing to provide them if there is enough interest. > There are patches in the archive already - the only complaint I've seen of these is that they are not frequently updated (but thats because we don't make point releases as frequently as some people would like). # apt-cache search patch-xfs kernel-patch-xfs - XFS Filesystem support for Linux 2.4.5 kernel-patch-xfs-core - Necessary kernel infrastructure to support XFS As you likely already know, all the user tools can also be retrieved from the archive. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 25 23:14:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8Q6EMQ13366 for linux-xfs-outgoing; Tue, 25 Sep 2001 23:14:22 -0700 Received: from roujin.gargoylecc.com (mail@roujin.gargoylecc.com [65.100.85.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8Q6ECD13339 for ; Tue, 25 Sep 2001 23:14:13 -0700 Received: from ringram by roujin.gargoylecc.com with local (Exim 3.32 #1) id 15m3V2-00012Z-00 for linux-xfs@oss.sgi.com; Wed, 26 Sep 2001 01:28:32 +0000 Date: Wed, 26 Sep 2001 01:28:32 +0000 To: linux-xfs@oss.sgi.com Subject: Re: .deb kernel packages Message-ID: <20010926012832.A3996@roujin.gargoylecc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.20i From: Russel Ingram Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 26 Sep 2001, Nathan Scott wrote: > hi, > > On Mon, Sep 24, 2001 at 09:48:28AM -0600, Russ Ingram wrote: > > I was just wondering how many people on this list are running > > debian and would be interested in having .deb kernel packages. I > > just learned how to make kernel packages on debian and would be > > willing to provide them if there is enough interest. > > > > There are patches in the archive already - the only complaint I've > seen of these is that they are not frequently updated (but thats > because we don't make point releases as frequently as some people > would like). > > # apt-cache search patch-xfs > kernel-patch-xfs - XFS Filesystem support for Linux 2.4.5 > kernel-patch-xfs-core - Necessary kernel infrastructure to support XFS > > As you likely already know, all the user tools can also be retrieved > from the archive. > I know there are patches there already but they are for 2.4.5. The XFS group makes patches every time there is a major kernel release, though. Besides, it's way easier(not to mention faster) to just install a kernel-image package than to go through the entire process of installing the kernel-patch-xfs* packages then having to download the 2.4.5 source tarball from kernel.org (the kernel-source-2.4.5 package isn't available in woody anymore), apply the patches, configure, make and install the new kernel yourself or run make-kpkg and still have to install the resulting kernel-image package. I'm already doing most of that process for myself anyway so it might as well be made available to other interested debian users. On another note: I do have the 2.4.10 kernel-image packages for XFS available for download for anyone who's interested in giving them a try. A word of warning -- I have not even tried these myself yet so make sure you have a backup kernel option to boot into before you reboot into the new kernel. ftp://monsterzero.uwyo.edu/XFS/kernel-doc-2.4.10-xfs-1.0.1_2.4.10-1_all.deb ftp://monsterzero.uwyo.edu/XFS/kernel-headers-2.4.10-xfs-1.0.1_2.4.10-1_i386.deb ftp://monsterzero.uwyo.edu/XFS/kernel-image-2.4.10-xfs-1.0.1_2.4.10-1_i386.deb Finally, in reply to Alan Eldridge's message earlier: Alan, if you would like to put your rpms on monsterzero with my debs, let me know. I'll set you up with a way to upload them. Russ -- Russel H. Ingram Gargoyle Computer Consulting (307)742-1361 or (307)760-1317 www.gargoylecc.com From owner-linux-xfs@oss.sgi.com Tue Sep 25 23:46:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8Q6k7G13976 for linux-xfs-outgoing; Tue, 25 Sep 2001 23:46:07 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8Q6k2D13957 for ; Tue, 25 Sep 2001 23:46:03 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA12941; Wed, 26 Sep 2001 08:45:59 +0200 (CEST) Message-Id: <4.3.2.7.2.20010926084223.03331188@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 26 Sep 2001 08:45:24 +0200 To: Murthy Kambhampaty , "'Linux-Xfs (E-mail)" From: Seth Mos Subject: Re: Installing to Mylex Acceleraid 352 In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 14:44 25-9-2001 -0400, Murthy Kambhampaty wrote: >I am having a problem installing with the XFS 1.0.1. installer to a RAID5 >array on a Mylex Acceleraid 352: the install goes fine, but when I reboot >LILO hangs LI > >My system is a SuperMicro server with ServerWorks HE chipset, one SCSI HDD >on channel A and Mylex card at PCI slot 4. All partitions >(/,/boot,/var,/home) are formatted XFS, swap is on /dev/sda. If I install >the entire system on /dev/sda, I have no problems. You will have to flip the LBA addressing switch back and forth to see if it is correct. If your lilo.conf has the linear option included you might try removing it and running lilo again. It has to do with the LBA translation or lack of it. Sometimes it is also called Large disk support or something to do with DOS. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Sep 26 00:57:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8Q7vqd15329 for linux-xfs-outgoing; Wed, 26 Sep 2001 00:57:52 -0700 Received: from mail.spylog.com (mail.spylog.com [194.67.35.220]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8Q7vkD15309 for ; Wed, 26 Sep 2001 00:57:48 -0700 Received: from an.local (an.local [192.168.4.50]) by mail.spylog.com (Postfix) with ESMTP id BC84A2C2A7 for ; Wed, 26 Sep 2001 02:01:08 +0400 (MSD) Received: by an.local (Postfix, from userid 1000) id 3113114296; Wed, 26 Sep 2001 02:01:08 +0400 (MSD) Date: Wed, 26 Sep 2001 02:01:08 +0400 From: Andrey Nekrasov To: XFS list Subject: Re: problem in "make install" for xfsdump Message-ID: <20010926020108.B10270@spylog.ru> Mail-Followup-To: XFS list References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.20i Organization: SpyLOG ltd. Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, Debian unstable/kernel-2.4.10-xfs from CVS. Try compile "xfsprogs": #debian/rules binary ... ... ../install-sh -o root -g root -m 644 changelog /usr/share/doc/xfsprogs/../xfsprogs-bf/changelog.Debian ../install-sh -o root -g root -m 755 ../mkfs/mkfs.xfs-xfsprogs-bf /sbin/mkfs.xfs cp: cannot stat `../mkfs/mkfs.xfs-xfsprogs-bf': No such file or directory make[1]: *** [install-boot] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4-xfs/cmd/xfsprogs/debian' make: *** [binary-arch] Error 2 # ? -- bye. Andrey Nekrasov, SpyLOG. From owner-linux-xfs@oss.sgi.com Wed Sep 26 07:34:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8QEY0u22052 for linux-xfs-outgoing; Wed, 26 Sep 2001 07:34:00 -0700 Received: from chimta01.algx.net (chimta01.algx.net [216.99.233.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8QEXuD22033 for ; Wed, 26 Sep 2001 07:33:56 -0700 Received: from jtsdell (66-2-81-28.customer.algx.net [66.2.81.28]) by chimmx01.algx.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GK900CXNWNFFH@chimmx01.algx.net> for linux-xfs@oss.sgi.com; Wed, 26 Sep 2001 09:09:16 -0500 (CDT) Date: Wed, 26 Sep 2001 10:09:58 -0400 (EDT) From: jtrostel@snapserver.com Subject: Re: problem in "make install" for xfsdump In-reply-to: <20010926122110.B463360@wobbly.melbourne.sgi.com> To: Nathan Scott Cc: XFS list Reply-to: jtrostel@snapserver.com Message-id: Organization: Snap Appliances MIME-version: 1.0 X-Mailer: XFMail 1.5.1 on Linux Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Priority: 3 (Normal) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Yup... you're right. When I go back and remake /cmd/attr and then /cmd/xfsdump (without doing /cmd/attr2) it works just fine. I (now) remember you warning about that 'attr2' directory a while ago.... i just forgot. On 26-Sep-2001 Nathan Scott wrote: > hi John, > > You've done a "make install install-dev" in the cmd/attr2 > directory right? Don't do that - its development code and > uses syscalls which don't exist yet in the kernel - you'll > need to use cmd/attr still (a "make install install-dev" > in that directory should fix the problem). > > When the new attr code is ready, it will simply replace the > cmd/attr code and cmd/attr2 will go away. I need attr2 to > help my discussions with the ext2 extended attribute project, > otherwise you wouldn't have seen it at all yet - sorry about > the confusion. -- John M. Trostel Senior Software Engineer Quantum / SnapAppliances jtrostel@snapserver.com From owner-linux-xfs@oss.sgi.com Wed Sep 26 08:09:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8QF9ub22994 for linux-xfs-outgoing; Wed, 26 Sep 2001 08:09:56 -0700 Received: from exchange.concordia.ab.ca (dns.concordia.ab.ca [199.185.120.34] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8QF9qD22970 for ; Wed, 26 Sep 2001 08:09:52 -0700 Received: from STROBE ([199.185.121.61]) by exchange.concordia.ab.ca with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id TQAV5DV1; Wed, 26 Sep 2001 09:13:50 -0600 Message-ID: <015301c1469d$26b39e40$3d79b9c7@admin.concordia.ab.ca> From: "Ed Boraas" To: "Nathan Scott" , "Russ Ingram" Cc: References: <3BAF55CC.B35ED24@uwyo.edu> <20010926144930.D463360@wobbly.melbourne.sgi.com> Subject: Re: .deb kernel packages Date: Wed, 26 Sep 2001 09:08:37 -0600 Organization: http://www.ed.boraas.ca 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > hi, > > On Mon, Sep 24, 2001 at 09:48:28AM -0600, Russ Ingram wrote: > > I was just wondering how many people on this list are running > > debian and would be interested in having .deb kernel packages. I > > just learned how to make kernel packages on debian and would be > > willing to provide them if there is enough interest. > > > > There are patches in the archive already - the only complaint I've > seen of these is that they are not frequently updated (but thats > because we don't make point releases as frequently as some people > would like). [snip] Just as a note, I've added the development patches (for Linux 2.4.6 - 2.4.10) to the package. After today's dinstall run, they'll be in sid. I'm hoping this is the right move... Some people have complained about lack of updates, and I can't say I totally blame them. In the near future, I may drop the patches for the older kernels, if I get positive feedback on the development patches. This would have the added benefit of deprecating the kernel-patch-xfs-core patch package, assuming 1.0.1++ won't be using the two-patch model. -Ed (Debian XFS patch package guy) From owner-linux-xfs@oss.sgi.com Wed Sep 26 08:23:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8QFNam23420 for linux-xfs-outgoing; Wed, 26 Sep 2001 08:23:36 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8QFN5D23397 for ; Wed, 26 Sep 2001 08:23:05 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id IAA04546 for ; Wed, 26 Sep 2001 08:23:03 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA3067575; Wed, 26 Sep 2001 10:21:48 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA78963; Wed, 26 Sep 2001 10:21:47 -0500 (CDT) Message-ID: <3BB1F21A.47D82953@sgi.com> Date: Wed, 26 Sep 2001 10:19:54 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Ed Boraas CC: linux-xfs@oss.sgi.com Subject: Re: .deb kernel packages References: <3BAF55CC.B35ED24@uwyo.edu> <20010926144930.D463360@wobbly.melbourne.sgi.com> <015301c1469d$26b39e40$3d79b9c7@admin.concordia.ab.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ed Boraas wrote: > [snip] > > Just as a note, I've added the development patches (for Linux 2.4.6 - > 2.4.10) to the package. After today's dinstall run, they'll be in sid. > > I'm hoping this is the right move... Some people have complained about lack > of updates, and I can't say I totally blame them. If you mean lack of updates by SGI, I'll address that. Or perhaps you mean Debian updates? :) Depends on what you mean by updates... we release a patch within days of every kernel point release, but our "official" releases are a bit few and far between. Perhaps it's just semantics - our "official" releases are run through the wringer and get heavy testing, whereas the kernel patches don't, necessarily - however, despite the dire warnings, I generally do have a lot of confidence in the "snapshot" patches. In fact, Mandrake is essentially releasing our 2.4.8 "snapshot" in their next distro - of course they tested it heavily, and it didn't fall down. So in short, adding our snapshot patches to Debian is probably a good move. > In the near future, I may drop the patches for the older kernels, if I get > positive feedback on the development patches. This would have the added > benefit of deprecating the kernel-patch-xfs-core patch package, assuming > 1.0.1++ won't be using the two-patch model. Hm, that's something we'll have to talk about. I'm not sure the two-patch model has any real benefits for the general public... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Sep 26 09:36:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8QGaRJ24801 for linux-xfs-outgoing; Wed, 26 Sep 2001 09:36:27 -0700 Received: from exchange.concordia.ab.ca (exchange.concordia.ab.ca [199.185.120.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8QGaLD24782 for ; Wed, 26 Sep 2001 09:36:21 -0700 Received: from STROBE ([199.185.121.61]) by exchange.concordia.ab.ca with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id TQAV5DYA; Wed, 26 Sep 2001 10:40:18 -0600 Message-ID: <01bc01c146a9$3b46d640$3d79b9c7@admin.concordia.ab.ca> From: "Ed Boraas" To: "Eric Sandeen" Cc: References: <3BAF55CC.B35ED24@uwyo.edu> <20010926144930.D463360@wobbly.melbourne.sgi.com> <015301c1469d$26b39e40$3d79b9c7@admin.concordia.ab.ca> <3BB1F21A.47D82953@sgi.com> Subject: Re: .deb kernel packages Date: Wed, 26 Sep 2001 10:35:04 -0600 Organization: http://www.ed.boraas.ca 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Ed Boraas wrote: > > > [snip] > > > > Just as a note, I've added the development patches (for Linux 2.4.6 - > > 2.4.10) to the package. After today's dinstall run, they'll be in sid. > > > > I'm hoping this is the right move... Some people have complained about lack > > of updates, and I can't say I totally blame them. > > If you mean lack of updates by SGI, I'll address that. Or perhaps you mean > Debian updates? :) Well, lack of Debian updates, which are in turn due to the fact that my (former) policy was to package only the "release" patches. > Depends on what you mean by updates... we release a patch within days of every > kernel point release, but our "official" releases are a bit few and far > between. Perhaps it's just semantics - our "official" releases are run through > the wringer and get heavy testing, whereas the kernel patches don't, necessarily > - however, despite the dire warnings, I generally do have a lot of confidence in > the "snapshot" patches. In fact, Mandrake is essentially releasing our 2.4.8 > "snapshot" in their next distro - of course they tested it heavily, and it > didn't fall down. Well, that's good to know. That was the heart of the question -- I wasn't sure to what degree the interim patches could be relied upon. I do understand that "unofficial" just means "not run through the immense battery of tests that the 'release' patches are" and not "just pulled at random out of cvs", yet I did have some internal reluctance to package something labelled "unofficial". > So in short, adding our snapshot patches to Debian is probably a good move. I'll carry on with this approach, then. > > In the near future, I may drop the patches for the older kernels, if I get > > positive feedback on the development patches. This would have the added > > benefit of deprecating the kernel-patch-xfs-core patch package, assuming > > 1.0.1++ won't be using the two-patch model. > > Hm, that's something we'll have to talk about. I'm not sure the two-patch model > has any real benefits for the general public... Well, do you have any ideas if 1.0.1++ will use split packages? I'll need to plan my package upgrade strategy (moving from two packages to one is fairly straight-forward, but splitting them back out again can be less simple). Also, the source to linux 2.4.5 isn't available in the debian archives (at time of writing, I believe we have 2.4.8 - 2.4.10 in the archive). Do any of you have any opinion on whether the 2.4.5 patch should stay in by virtue of its "official" status? Take care, Ed. From owner-linux-xfs@oss.sgi.com Wed Sep 26 10:43:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8QHhVF26084 for linux-xfs-outgoing; Wed, 26 Sep 2001 10:43:31 -0700 Received: from gateway1.brets.elevating.com (adsl-216-63-236-137.dsl.tulsok.swbell.net [216.63.236.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8QHhRD26064 for ; Wed, 26 Sep 2001 10:43:27 -0700 Received: from elevating.com (bretdell.brets.elevating.com [192.168.0.128]) by gateway1.brets.elevating.com (8.9.3/8.8.7) with ESMTP id MAA22083; Wed, 26 Sep 2001 12:43:27 -0500 Message-ID: <3BB213BF.C5994820@elevating.com> Date: Wed, 26 Sep 2001 12:43:27 -0500 From: Bret Hughes X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, ja MIME-Version: 1.0 To: linux-xfs Subject: /tmp dir hosed after reboot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk After a reboot of an XFS 1.0.1 kernel based machine I have a problem with the /tmp partition. files seem to be created but accessing them results in file not found even ls yields the following ( I have rebooted the machine without mounting the /tmp partition at boot): [root@ele5b /root]# mount -t xfs /dev/hda10 /mnt [root@ele5b /root]# cd mnt bash: cd: mnt: No such file or directory [root@ele5b /root]# cd /mnt [root@ele5b /mnt]# ls ls: : No such file or directory ls: n.jpeg: No such file or directory ls: : No such file or directory ls: : No such file or directory ls: jAEe.jpeg: No such file or directory ls: : No such file or directory ls: : No such file or directory ls: yMQG.jpeg: No such file or directory ls: : No such file or directory ls: : No such file or directory ls: O0wV.jpeg: No such file or directory ls: : No such file or directory not sure what is happening but I thought I would ask before doing anything else. Any ideas? Bret From owner-linux-xfs@oss.sgi.com Wed Sep 26 10:48:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8QHmZ726350 for linux-xfs-outgoing; Wed, 26 Sep 2001 10:48:35 -0700 Received: from codon.com (gingerstamp.com [64.78.130.125]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8QHmWD26331 for ; Wed, 26 Sep 2001 10:48:32 -0700 Received: (qmail 25494 invoked by uid 516); 26 Sep 2001 18:07:41 -0000 Received: from nw@codon.com by helix with qmail-scanner-0.96 (. Clean. Processed in 0.052099 secs); 26 Sep 2001 18:07:41 -0000 Received: from weasel.local.iboats.com (HELO weasel) (64.78.130.80) by codon.com with SMTP; 26 Sep 2001 18:07:40 -0000 Message-ID: <002f01c146b2$7b4ab0a0$50824e40@iboats.com> From: "Steve Wolfe" To: "linux-xfs" References: <3BB213BF.C5994820@elevating.com> Subject: Re: /tmp dir hosed after reboot Date: Wed, 26 Sep 2001 11:41:30 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > After a reboot of an XFS 1.0.1 kernel based machine I have a problem > with the /tmp partition. files seem to be created but accessing them > results in file not found even ls yields the following ( I have rebooted > the machine without mounting the /tmp partition at boot): (snip) > not sure what is happening but I thought I would ask before doing > anything else. > > Any ideas? If it were any other partition, I'd suggest the use of xfs_repair, but since it's /tmp, I'd probably just use mkfs.xfs. ; ) steve From owner-linux-xfs@oss.sgi.com Wed Sep 26 10:55:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8QHtC326541 for linux-xfs-outgoing; Wed, 26 Sep 2001 10:55:12 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8QHtAD26522 for ; Wed, 26 Sep 2001 10:55:10 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8QHt4K09560 for ; Wed, 26 Sep 2001 10:55:04 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2926579; Wed, 26 Sep 2001 12:53:48 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id MAA74373; Wed, 26 Sep 2001 12:53:47 -0500 (CDT) Message-ID: <3BB215B9.6032C7EB@sgi.com> Date: Wed, 26 Sep 2001 12:51:53 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Wolfe CC: linux-xfs Subject: Re: /tmp dir hosed after reboot References: <3BB213BF.C5994820@elevating.com> <002f01c146b2$7b4ab0a0$50824e40@iboats.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Wolfe wrote: > > Any ideas? > > If it were any other partition, I'd suggest the use of xfs_repair, but > since it's /tmp, I'd probably just use mkfs.xfs. ; ) although the output of xfs_repair might offer some clues as to what went wrong... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Sep 26 11:01:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8QI14k26783 for linux-xfs-outgoing; Wed, 26 Sep 2001 11:01:04 -0700 Received: from gateway1.brets.elevating.com (adsl-216-63-236-137.dsl.tulsok.swbell.net [216.63.236.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8QI11D26759 for ; Wed, 26 Sep 2001 11:01:01 -0700 Received: from elevating.com (bretdell.brets.elevating.com [192.168.0.128]) by gateway1.brets.elevating.com (8.9.3/8.8.7) with ESMTP id NAA22142; Wed, 26 Sep 2001 13:01:00 -0500 Message-ID: <3BB217DC.43C94147@elevating.com> Date: Wed, 26 Sep 2001 13:01:00 -0500 From: Bret Hughes X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, ja MIME-Version: 1.0 To: linux-xfs Subject: Re: /tmp dir hosed after reboot References: <3BB213BF.C5994820@elevating.com> <002f01c146b2$7b4ab0a0$50824e40@iboats.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Wolfe wrote: > > > After a reboot of an XFS 1.0.1 kernel based machine I have a problem > > with the /tmp partition. files seem to be created but accessing them > > results in file not found even ls yields the following ( I have rebooted > > the machine without mounting the /tmp partition at boot): > > (snip) > > > not sure what is happening but I thought I would ask before doing > > anything else. > > > > Any ideas? > > If it were any other partition, I'd suggest the use of xfs_repair, but > since it's /tmp, I'd probably just use mkfs.xfs. ; ) > > steve That is what I figured too. Any way to track down what caused it? Makes me nervous. Bret From owner-linux-xfs@oss.sgi.com Wed Sep 26 12:14:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8QJEWY28300 for linux-xfs-outgoing; Wed, 26 Sep 2001 12:14:32 -0700 Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8QJERD28281 for ; Wed, 26 Sep 2001 12:14:27 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8QJELK14023 for ; Wed, 26 Sep 2001 12:14:21 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA3074227 for ; Wed, 26 Sep 2001 14:13:05 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA66840 for ; Wed, 26 Sep 2001 14:13:05 -0500 (CDT) Received: by stout.americas.sgi.com (8.11.2/SGI-client-1.7) id f8QJBAC30253; Wed, 26 Sep 2001 14:11:10 -0500 Message-Id: <200109261911.f8QJBAC30253@stout.americas.sgi.com> Date: Wed, 26 Sep 2001 14:11:10 -0500 From: Eric Sandeen Subject: TAKE - Add sysctl to tune nfs refcache Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Wed Sep 26 12:08:38 PDT 2001 Workarea: stout.americas.sgi.com:/localhome/eric/2.4.x-xfs/workarea The nfs refcache was taking a fairly long time to empty on Linux, which led to some unexpected results due to extra space allocation. This mod makes both the size of the refcache, and the number of entries purged on each sync tuneable via /proc/sys/fs/xfs/refcache_size and /proc/sys/fs/xfs/refcache_purge. The defaults are also smaller than they were, so without any fiddling, the refcache will drain more quickly. There is now a sysctl framework for XFS parameters. The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103457a linux/fs/xfs/linux/xfs_sysctl.h - 1.1 linux/fs/xfs/linux/xfs_sysctl.c - 1.1 - New file for xfs sysctls linux/include/linux/sysctl.h - 1.38 - Add sysctl entry for fs/xfs linux/fs/xfs/xfs_rw.h - 1.61 - Define XFS_REFCACHE_SIZE_MAX Prototype for xfs_refcache_resize linux/fs/xfs/xfs_rw.c - 1.346 - Make refcache size and purge quantity sysctl tuneable Add xfs_refcache_resize function to handle resizing linux/fs/xfs/xfs_vfsops.c - 1.326 - Register and unregister sysctl interface linux/fs/xfs/linux/xfs_linux.h - 1.55 - include xfs_sysctl.h linux/fs/xfs/linux/Makefile - 1.43 - Add xfs_sysctl linux/fs/xfs/linux/Makefile.in - 1.2 - add xfs_sysctl From owner-linux-xfs@oss.sgi.com Wed Sep 26 17:36:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8R0aFZ02234 for linux-xfs-outgoing; Wed, 26 Sep 2001 17:36:15 -0700 Received: from roujin.gargoylecc.com (mail@roujin.gargoylecc.com [65.100.85.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8R0aBD02215 for ; Wed, 26 Sep 2001 17:36:12 -0700 Received: from ringram by roujin.gargoylecc.com with local (Exim 3.32 #1) id 15mKha-0003Ao-00 for linux-xfs@oss.sgi.com; Wed, 26 Sep 2001 19:50:38 +0000 Date: Wed, 26 Sep 2001 19:50:38 +0000 To: linux-xfs@oss.sgi.com Subject: Re: .deb kernel packages Message-ID: <20010926195038.A12195@roujin.gargoylecc.com> References: <3BAF55CC.B35ED24@uwyo.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22i From: Russel Ingram Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Just a short update on the debian kernel packages: I have now tested them with no problems on my system. I have also set up the ftp server so that debian users can more easily access those packages with dselect or apt-get. All you will need to do is add the following to your /etc/apt/sources.list file: deb ftp://monsterzero.uwyo.edu/XFS ./ On a slightly different note, the latest version of boot-floppies has full support for creating a disk set to install Debian on top of XFS. I hope these are helpful. Cheers, Russ -- Russel H. Ingram Gargoyle Computer Consulting (307)742-1361 or (307)760-1317 www.gargoylecc.com From owner-linux-xfs@oss.sgi.com Wed Sep 26 18:41:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8R1fVB02834 for linux-xfs-outgoing; Wed, 26 Sep 2001 18:41:31 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8R1fTD02815 for ; Wed, 26 Sep 2001 18:41:29 -0700 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id SAA03192 for ; Wed, 26 Sep 2001 18:40:16 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by nodin.corp.sgi.com (8.11.4/8.11.2/nodin-1.0) with ESMTP id f8R1eSs1548430 for ; Wed, 26 Sep 2001 18:40:28 -0700 (PDT) Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id 1DC04300095; Thu, 27 Sep 2001 11:40:25 +1000 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id 9DDAEB8 for ; Thu, 27 Sep 2001 11:40:25 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: linux-xfs@oss.sgi.com Subject: XFS on laptops Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Sep 2001 11:40:20 +1000 Message-ID: <8064.1001554820@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Can anybody recommend tuning parameters for XFS on laptops? Since converting my laptop to XFS, the disk never spins down so the machine never suspends. From owner-linux-xfs@oss.sgi.com Wed Sep 26 20:54:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8R3sL104547 for linux-xfs-outgoing; Wed, 26 Sep 2001 20:54:21 -0700 Received: from rj.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8R3sHD04527 for ; Wed, 26 Sep 2001 20:54:17 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8R3sBL18778 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Wed, 26 Sep 2001 20:54:11 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id FAA1266900 for ; Thu, 27 Sep 2001 05:54:07 +0200 (CEST) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id NAA21591; Thu, 27 Sep 2001 13:53:54 +1000 Date: Thu, 27 Sep 2001 13:53:54 +1000 From: Keith Owens Message-Id: <200109270353.NAA21591@sherman.melbourne.sgi.com> Subject: TAKE - Upgrade to kdb v1.9 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Upgrade to kdb v1.9 Date: Wed Sep 26 20:50:57 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103508a linux/arch/i386/config.in - 1.61 linux/Documentation/Configure.help - 1.102 linux/kdb/modules/kdbm_vm.c - 1.13 linux/kdb/Makefile - 1.10 linux/include/linux/kdbprivate.h - 1.12 linux/Documentation/kdb/kdb_md.man - 1.6 linux/include/linux/kdb.h - 1.18 linux/kdb/modules/Makefile - 1.11 linux/kdb/kdbmain.c - 1.21 linux/include/linux/dis-asm.h - 1.9 linux/kdb/kdb_io.c - 1.9 linux/arch/i386/kdb/kdba_id.c - 1.9 linux/Documentation/kdb/kdb.mm - 1.12 linux/kdb/kdb_id.c - 1.10 linux/arch/i386/kdb/kdba_bp.c - 1.10 linux/kdb/modules/kdbm_pg.c - 1.40 linux/kdb/ChangeLog - 1.7 From owner-linux-xfs@oss.sgi.com Wed Sep 26 23:51:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8R6p8v06502 for linux-xfs-outgoing; Wed, 26 Sep 2001 23:51:08 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8R6p5D06483 for ; Wed, 26 Sep 2001 23:51:05 -0700 Received: (qmail 29627 invoked by uid 8); 27 Sep 2001 06:51:03 -0000 From: thomas graichen Reply-To: thomas graichen X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: XFS on laptops Date: Thu, 27 Sep 2001 08:38:38 +0200 Organization: spoiled dot org Lines: 21 Distribution: local Message-ID: References: <8064.1001554820@kao2.melbourne.sgi.com> Reply-To: thomas graichen X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.10-xfs (i686)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Keith Owens wrote: > Can anybody recommend tuning parameters for XFS on laptops? Since > converting my laptop to XFS, the disk never spins down so the machine > never suspends. see the thread from the same question i asked here some weeks ago called "xfs on notebooks (noflushd etc.)" - what came up there was that it should work as long as / is mounted with noatime which seems to require some work with initrd because noatime seems to be ignored as a root mount option ... did not find the time to play around with this until now if anyone has some more detailed informatin about this i'm inter- ested in it too t -- thomas graichen ... perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. --- antoine de saint-exupery From owner-linux-xfs@oss.sgi.com Thu Sep 27 00:20:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8R7KoZ07048 for linux-xfs-outgoing; Thu, 27 Sep 2001 00:20:50 -0700 Received: from ii.uib.no (eik.ii.uib.no [129.177.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8R7KlD07027 for ; Thu, 27 Sep 2001 00:20:47 -0700 Received: from apal-192.ii.uib.no (apal.ii.uib.no) [129.177.192.27] by ii.uib.no with esmtp (Exim 3.03) id 15mVTS-0001Tw-00 ; Thu, 27 Sep 2001 09:20:46 +0200 Received: (from janfrode@localhost) by apal.ii.uib.no (8.10.2+Sun/8.10.2) id f8R7Kjx26390; Thu, 27 Sep 2001 09:20:45 +0200 (MEST) Date: Thu, 27 Sep 2001 09:20:45 +0200 From: Jan-Frode Myklebust To: thomas graichen Cc: linux-xfs@oss.sgi.com Subject: Re: XFS on laptops Message-ID: <20010927092044.B24118@ii.uib.no> References: <8064.1001554820@kao2.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from list-linux.sgi.xfs@spoiled.org on Thu, Sep 27, 2001 at 08:38:38AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > see the thread from the same question i asked here some weeks ago > called "xfs on notebooks (noflushd etc.)" - what came up there was > that it should work as long as / is mounted with noatime which > seems to require some work with initrd because noatime seems to be > ignored as a root mount option ... did not find the time to play > around with this until now Can't you just issue a 'mount -o noatime,remount /' after the machine is booted? -jf From owner-linux-xfs@oss.sgi.com Thu Sep 27 01:07:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8R87Xu07771 for linux-xfs-outgoing; Thu, 27 Sep 2001 01:07:33 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8R87TD07752 for ; Thu, 27 Sep 2001 01:07:30 -0700 Received: (qmail 1913 invoked by uid 8); 27 Sep 2001 08:07:28 -0000 From: thomas graichen Reply-To: thomas graichen X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: XFS on laptops Date: Thu, 27 Sep 2001 10:06:35 +0200 Organization: spoiled dot org Lines: 21 Distribution: local Message-ID: References: <8064.1001554820@kao2.melbourne.sgi.com> <20010927092044.B24118@ii.uib.no> Reply-To: thomas graichen X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.10-xfs (i686)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jan-Frode Myklebust wrote: >> >> see the thread from the same question i asked here some weeks ago >> called "xfs on notebooks (noflushd etc.)" - what came up there was >> that it should work as long as / is mounted with noatime which >> seems to require some work with initrd because noatime seems to be >> ignored as a root mount option ... did not find the time to play >> around with this until now > Can't you just issue a 'mount -o noatime,remount /' > after the machine is booted? iirc it does not work as expected for / mounts - but maybe i'm wrong here (just remembering what i think of having read somethere) t -- thomas graichen ... perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. --- antoine de saint-exupery From owner-linux-xfs@oss.sgi.com Thu Sep 27 01:22:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8R8Mpp08034 for linux-xfs-outgoing; Thu, 27 Sep 2001 01:22:51 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8R8MdD08012 for ; Thu, 27 Sep 2001 01:22:39 -0700 Received: (qmail 17900 invoked by uid 0); 27 Sep 2001 08:22:32 -0000 Received: from pd9512998.dip.t-dialin.net (HELO 2xs) (217.81.41.152) by mail.gmx.net (mp009-rz3) with SMTP; 27 Sep 2001 08:22:32 -0000 Message-ID: <001101c1472d$c3e43d60$0a00a8c0@2xs> From: "Christian Tilche" To: Subject: Date: Thu, 27 Sep 2001 10:24:01 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C1473E.869C01C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C1473E.869C01C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I downloaded a few days ago the image but found a problem due to the = installation. After copying all rpms on the new PC it is showing a error message Runtimerror. "usr/sbin/usermod can not be run ! the anaconda.txt has this infos : raceback (innermost last): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py", = line 19, in run rc =3D self.todo.doInstall () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1966, in = doInstall self.writeConfiguration () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1660, in = writeConfiguration self.writeRootPassword () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 904, in = writeRootPassword self.setPassword("root", pure) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1482, in = setPassword stdout =3D '/dev/null', stderr =3D None) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iutil.py", line 48, in = execWithRedirect raise RuntimeError, command + " can not be run" RuntimeError: /usr/sbin/usermod can not be run Local variables in innermost frame: argv: ['/usr/sbin/usermod', '-p', '$1$VHqb5J0n$dPO6YMA.L5DmsjnVb/twU0', = 'root'] root: /mnt/sysimage stdin: 0 newPgrp: 0 stdout: 20 stderr: 21 command: /usr/sbin/usermod searchPath: 0 ignoreTermSigs: 0 ToDo object: (itodo ToDo p1 (dp2 S'resState' p3 S'1024x768' p4 sS'progressWindow' p5 (igui ProgressWindow (dp6 S'total' p7 I480 sS'window' p8 (igtk GtkWindow (dp9 S'_o' p10 =20 My hardware. P2 Celeron 450Mhz,64MB RAM, 100MBIT 8139 Realtek onboard, = I810 Graphic 17" 1785 ctx screen. ------=_NextPart_000_000E_01C1473E.869C01C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I downloaded a few days ago the image = but found a=20 problem due to the installation.
 
After copying all rpms on the new PC it = is showing=20 a error message
Runtimerror.  "usr/sbin/usermod = can not be run=20 !
 
the anaconda.txt has this infos = :
 
raceback (innermost last):
  = File=20 "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py", line 19, = in=20 run
    rc =3D self.todo.doInstall ()
  File=20 "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1966, in=20 doInstall
    self.writeConfiguration ()
  = File=20 "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1660, in=20 writeConfiguration
    self.writeRootPassword = ()
 =20 File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 904, in=20 writeRootPassword
    self.setPassword("root", = pure)
 =20 File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1482, in=20 setPassword
    stdout =3D '/dev/null', stderr =3D = None)
 =20 File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iutil.py", line 48, in=20 execWithRedirect
    raise RuntimeError, command + " = can not=20 be run"
RuntimeError: /usr/sbin/usermod can not be run
 
Local variables in innermost = frame:
argv:=20 ['/usr/sbin/usermod', '-p', '$1$VHqb5J0n$dPO6YMA.L5DmsjnVb/twU0',=20 'root']
root: /mnt/sysimage
stdin: 0
newPgrp: 0
stdout:=20 20
stderr: 21
command: /usr/sbin/usermod
searchPath:=20 0
ignoreTermSigs: 0
 
ToDo=20 object:
(itodo
ToDo
p1
(dp2
S'resState'
p3
S'1024x76= 8'
p4
sS'progressWindow'
p5
(igui
ProgressWindow
(dp6S'total'
p7
I480
sS'window'
p8
(igtk
GtkWindow
(dp= 9
S'_o'
p10
 
<failed>        &n= bsp; 
 
 
My hardware. P2 Celeron 450Mhz,64MB = RAM, 100MBIT=20 8139 Realtek onboard, I810 Graphic 17" 1785 ctx screen.
 
------=_NextPart_000_000E_01C1473E.869C01C0-- From owner-linux-xfs@oss.sgi.com Thu Sep 27 03:42:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RAg0j09854 for linux-xfs-outgoing; Thu, 27 Sep 2001 03:42:00 -0700 Received: from com.esnaola.org (aboukir-101-1-5-ldarnis.adsl.nerim.net [80.65.225.199]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RAfvD09834 for ; Thu, 27 Sep 2001 03:41:57 -0700 Received: from localhost (localhost [127.0.0.1]) by com.esnaola.org (Postfix) with ESMTP id 4DF11AC442 for ; Thu, 27 Sep 2001 12:26:55 +0200 (CEST) Received: from irun (unknown [192.168.33.64]) by com.esnaola.org (Postfix) with SMTP id 27C08ABB59 for ; Thu, 27 Sep 2001 12:26:38 +0200 (CEST) Date: Thu, 27 Sep 2001 12:42:13 +0200 From: Lionel To: linux-xfs@oss.sgi.com Subject: xfs + woody Message-Id: <20010927124213.3e835f87.lionel@esnaola.org> Organization: Esnaola X-Mailer: Sylpheed version 0.6.1 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi EveryBody ! Is there any personn who have some experience woody + xfs installation ? I installed two machines with floppies disks from Zoltan and it work, but I have problems with daemon. Each time I want to lauch gdm, proftpd, sshd, ... by /etc/init.d/xxxx start it say nothing and the daemon doesn't run. If I directly lauche sshd for example it work !!! I don't have the problem with a woody installed from the upgrade of a potato. Have you some ideas or answers ?!! Thanx in advance. Lionel From owner-linux-xfs@oss.sgi.com Thu Sep 27 04:21:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RBL8j10760 for linux-xfs-outgoing; Thu, 27 Sep 2001 04:21:08 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RBL5D10741 for ; Thu, 27 Sep 2001 04:21:05 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id NAA13191; Thu, 27 Sep 2001 13:21:01 +0200 (CEST) Message-Id: <4.3.2.7.2.20010927131901.03e25000@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 27 Sep 2001 13:20:20 +0200 To: Lionel , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: xfs + woody In-Reply-To: <20010927124213.3e835f87.lionel@esnaola.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 12:42 27-9-2001 +0200, Lionel wrote: >Hi EveryBody ! > >Is there any personn who have some experience woody + xfs installation ? >I installed two machines with floppies disks from Zoltan and it work, but >I have problems with daemon. >Each time I want to lauch gdm, proftpd, sshd, ... by /etc/init.d/xxxx >start it say nothing and the daemon doesn't run. If I directly lauche sshd >for example it work !!! I don't have the problem with a woody installed >from the upgrade of a potato. > >Have you some ideas or answers ?!! What does /var/log/messages say about the startup scripts failing? Perhaps you mounted the / fs with the noexec option? That would make the initscripts fail. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Sep 27 04:56:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RBu1h11566 for linux-xfs-outgoing; Thu, 27 Sep 2001 04:56:01 -0700 Received: from smtp.cistron-office.nl (mail@10fwd.cistron-office.nl [195.64.65.197]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RBttD11547 for ; Thu, 27 Sep 2001 04:55:56 -0700 Received: from subspace.cistron-office.nl ([195.64.65.200]) by smtp.cistron-office.nl with esmtp (Exim 3.22 #1 (Debian)) id 15mZle-0004oE-00; Thu, 27 Sep 2001 13:55:50 +0200 Received: (from jigal@localhost) by subspace.cistron-office.nl (8.9.3/8.9.3/Debian 8.9.3-6) id NAA11891; Thu, 27 Sep 2001 13:55:50 +0200 Date: Thu, 27 Sep 2001 13:55:50 +0200 From: Jigal Weinberg To: Lionel Cc: linux-xfs@oss.sgi.com Subject: Re: xfs + woody Message-ID: <20010927135549.B27851@cistron-office.nl> References: <20010927124213.3e835f87.lionel@esnaola.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010927124213.3e835f87.lionel@esnaola.org>; from lionel@esnaola.org on Thu, Sep 27, 2001 at 12:42:13PM +0200 X-Disclaimer: Include standard disclaimer here. Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 27 Sep 2001, Lionel wrote: > Hi EveryBody ! > > Is there any personn who have some experience woody + xfs installation ? > I installed two machines with floppies disks from Zoltan and it work, but I have problems with daemon. > Each time I want to lauch gdm, proftpd, sshd, ... by /etc/init.d/xxxx start it say nothing and the daemon doesn't run. If I directly lauche sshd for example it work !!! I don't have the problem with a woody installed from the upgrade of a potato. This is what I experienced also. The problem lies in the fact that the start-stop deamon is worngfully installed. You find 2 version in /sbin/ the one who is currentlu in use is the wrong one. Just move it to old and rename the other. Greets Jigal -- No flesh shall be spared : Mark 13 - From owner-linux-xfs@oss.sgi.com Thu Sep 27 04:55:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RBtaN11522 for linux-xfs-outgoing; Thu, 27 Sep 2001 04:55:36 -0700 Received: from com.esnaola.org (aboukir-101-1-5-ldarnis.adsl.nerim.net [80.65.225.199]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RBtUD11503 for ; Thu, 27 Sep 2001 04:55:31 -0700 Received: from localhost (localhost [127.0.0.1]) by com.esnaola.org (Postfix) with ESMTP id 5AB4EAC441; Thu, 27 Sep 2001 13:40:28 +0200 (CEST) Received: from irun (unknown [192.168.33.64]) by com.esnaola.org (Postfix) with SMTP id 7545BABB59; Thu, 27 Sep 2001 13:40:12 +0200 (CEST) Date: Thu, 27 Sep 2001 13:55:47 +0200 From: Lionel To: Seth Mos Cc: linux-xfs@oss.sgi.com Subject: Re: xfs + woody Message-Id: <20010927135547.717beb9a.lionel@esnaola.org> In-Reply-To: <4.3.2.7.2.20010927131901.03e25000@pop.xs4all.nl> References: <20010927124213.3e835f87.lionel@esnaola.org> <4.3.2.7.2.20010927131901.03e25000@pop.xs4all.nl> Organization: Esnaola X-Mailer: Sylpheed version 0.6.1 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Dear Seth, Thanx for your answer but nothing happen in the /var/log/messages when I try to lauch daemons. For example I try this ( the same for gdm or ssh) : irun:~# /etc/init.d/proftpd start Starting professional ftp daemon: proftpd. Here is my fstab : # /etc/fstab: static file system information. # # /dev/hda1 / xfs defaults 0 0 /dev/hda2 none swap sw 0 0 proc /proc proc defaults 0 /dev/fd0 /floppy auto defaults,user,noauto 0 /dev/cdrom /cdrom iso9660 defaults,ro,user,noauto 0 /dev/hda3 /var xfs defaults 0 2 /dev/hda4 /home xfs defaults 0 2 Thanx to help me. Lionel On Thu, 27 Sep 2001 13:20:20 +0200 Seth Mos wrote: > At 12:42 27-9-2001 +0200, Lionel wrote: > >Hi EveryBody ! > > > >Is there any personn who have some experience woody + xfs installation ? > >I installed two machines with floppies disks from Zoltan and it work, but > >I have problems with daemon. > >Each time I want to lauch gdm, proftpd, sshd, ... by /etc/init.d/xxxx > >start it say nothing and the daemon doesn't run. If I directly lauche sshd > >for example it work !!! I don't have the problem with a woody installed > >from the upgrade of a potato. > > > >Have you some ideas or answers ?!! > > What does /var/log/messages say about the startup scripts failing? > Perhaps you mounted the / fs with the noexec option? That would make the > initscripts fail. > > Cheers > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. > From owner-linux-xfs@oss.sgi.com Thu Sep 27 05:00:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RC0dg11876 for linux-xfs-outgoing; Thu, 27 Sep 2001 05:00:39 -0700 Received: from com.esnaola.org (aboukir-101-1-5-ldarnis.adsl.nerim.net [80.65.225.199]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RC0YD11854 for ; Thu, 27 Sep 2001 05:00:35 -0700 Received: from localhost (localhost [127.0.0.1]) by com.esnaola.org (Postfix) with ESMTP id 832A9AC441; Thu, 27 Sep 2001 13:45:32 +0200 (CEST) Received: from irun (unknown [192.168.33.64]) by com.esnaola.org (Postfix) with SMTP id 204E4ABB59; Thu, 27 Sep 2001 13:45:18 +0200 (CEST) Date: Thu, 27 Sep 2001 14:00:53 +0200 From: Lionel To: Jigal Weinberg Cc: linux-xfs@oss.sgi.com Subject: Re: xfs + woody Message-Id: <20010927140053.37008448.lionel@esnaola.org> In-Reply-To: <20010927135549.B27851@cistron-office.nl> References: <20010927124213.3e835f87.lionel@esnaola.org> <20010927135549.B27851@cistron-office.nl> Organization: Esnaola X-Mailer: Sylpheed version 0.6.1 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk THANX A LOT !!!! Thanx Jigal it work fine now ! Regards, Lionel > On Thu, 27 Sep 2001, Lionel wrote: > > > Hi EveryBody ! > > > > Is there any personn who have some experience woody + xfs installation ? > > I installed two machines with floppies disks from Zoltan and it work, but I have problems with daemon. > > Each time I want to lauch gdm, proftpd, sshd, ... by /etc/init.d/xxxx start it say nothing and the daemon doesn't run. If I directly lauche sshd for example it work !!! I don't have the problem with a woody installed from the upgrade of a potato. > > > This is what I experienced also. > The problem lies in the fact that the start-stop deamon is worngfully > installed. You find 2 version in /sbin/ the one who is currentlu in use > is the wrong one. Just move it to old and rename the other. > > > Greets > > > Jigal > > -- > No flesh shall be spared : Mark 13 > - > From owner-linux-xfs@oss.sgi.com Thu Sep 27 05:20:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RCK9N12270 for linux-xfs-outgoing; Thu, 27 Sep 2001 05:20:09 -0700 Received: from alaska.net (sephiroth.nwc.alaska.net [209.112.130.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RCK5D12248 for ; Thu, 27 Sep 2001 05:20:05 -0700 Received: from erbenson.alaska.net (70-pm18.nwc.alaska.net [209.112.142.70]) by alaska.net (8.11.5/8.11.5) with ESMTP id f8RCK3t23946 for ; Thu, 27 Sep 2001 04:20:03 -0800 (AKDT) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 6B4A7397B for ; Thu, 27 Sep 2001 04:20:01 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 6696C10253; Thu, 27 Sep 2001 04:20:01 -0800 (AKDT) Date: Thu, 27 Sep 2001 04:20:01 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: xfs + woody Message-ID: <20010927042001.Q21719@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010927124213.3e835f87.lionel@esnaola.org> <20010927135549.B27851@cistron-office.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3mUD2hqWbnBptYHy" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010927135549.B27851@cistron-office.nl>; from jigal@cistron-office.nl on Thu, Sep 27, 2001 at 01:55:50PM +0200 X-OS: Debian GNU Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --3mUD2hqWbnBptYHy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 27, 2001 at 01:55:50PM +0200, Jigal Weinberg wrote: >=20 > This is what I experienced also. > The problem lies in the fact that the start-stop deamon is worngfully > installed. You find 2 version in /sbin/ the one who is currentlu in use > is the wrong one. Just move it to old and rename the other. for the curious... this happens if debootstrap (the base system installer) fails or aborts in the middle. before it starts installing the base packages it moves start-stop-daemon and replaces it with /bin/true, this is to avoid daemons being started in the chrooted environment (like syslog). its supposed to undo that at the end, but if it fails midway that doesn't happen obviously. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --3mUD2hqWbnBptYHy 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 iEYEARECAAYFAjuzGXEACgkQJKx7GixEevy9pQCbBBe4OpvHj3S+KrC2Z8J57Uva 9S4AnRsc82tbpeX6lBgayMIFIODZEkXm =Jx+u -----END PGP SIGNATURE----- --3mUD2hqWbnBptYHy-- From owner-linux-xfs@oss.sgi.com Thu Sep 27 06:30:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RDUk613660 for linux-xfs-outgoing; Thu, 27 Sep 2001 06:30:46 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RDUOD13636 for ; Thu, 27 Sep 2001 06:30:24 -0700 Received: from mail.swdata.com (mail.mninter.net [208.142.244.17]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id GAA01797 for ; Thu, 27 Sep 2001 06:30:14 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (30-48-196-206.in-addr.infinetivity.com [206.196.48.30]) by mail.swdata.com (8.11.2/8.11.2) with ESMTP id f8RDJvh07450; Thu, 27 Sep 2001 08:19:57 -0500 Message-ID: <3BB326AC.F0B54CF3@sgi.com> Date: Thu, 27 Sep 2001 08:16:28 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.5-xfs-1.0.1 i586) X-Accept-Language: en MIME-Version: 1.0 To: Christian Tilche CC: linux-xfs@oss.sgi.com Subject: Re: References: <001101c1472d$c3e43d60$0a00a8c0@2xs> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Christian Tilche wrote: > > I downloaded a few days ago the image but found a problem due to the > installation. > > After copying all rpms on the new PC it is showing a error message > Runtimerror. "usr/sbin/usermod can not be run ! Hi Christian - I'm not sure that it has anything to do with the XFS modifications... it's saying that it's unable to set the root password. How did you set up your filesystems? Is there any reason that usermod wouldn't be able to modify /etc/password...? Your system may be mostly installed anyway; if you reboot the installer and type "linux rescue", then set your root password, you might have a mostly useable system, depending on how much other configuration was going to be done after the crash. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Sep 27 07:48:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8REmSt15187 for linux-xfs-outgoing; Thu, 27 Sep 2001 07:48:28 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8REmOD15168 for ; Thu, 27 Sep 2001 07:48:25 -0700 Received: (qmail 7777 invoked by uid 8); 27 Sep 2001 14:48:23 -0000 From: Juri Haberland Reply-To: Juri Haberland X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: XFS on laptops Date: Thu, 27 Sep 2001 14:48:22 +0000 (UTC) Organization: spoiled dot org Lines: 25 Distribution: local Message-ID: References: <8064.1001554820@kao2.melbourne.sgi.com> <20010927092044.B24118@ii.uib.no> X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (OpenBSD/2.9 (i386)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk thomas graichen wrote: > Jan-Frode Myklebust wrote: >>> >>> see the thread from the same question i asked here some weeks ago >>> called "xfs on notebooks (noflushd etc.)" - what came up there was >>> that it should work as long as / is mounted with noatime which >>> seems to require some work with initrd because noatime seems to be >>> ignored as a root mount option ... did not find the time to play >>> around with this until now > >> Can't you just issue a 'mount -o noatime,remount /' >> after the machine is booted? > > iirc it does not work as expected for / mounts - but maybe i'm wrong > here (just remembering what i think of having read somethere) Well, doing so definitely changed the access patterns from my HD, so I would say that 'mount / -o remount,noatime' works... (though it didn't help me with getting my HD spin down with ext3 as my FS) Juri -- Juri Haberland From owner-linux-xfs@oss.sgi.com Thu Sep 27 08:22:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RFM8d16264 for linux-xfs-outgoing; Thu, 27 Sep 2001 08:22:08 -0700 Received: from mailnet.consensys.com ([209.47.40.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RFM3D16239 for ; Thu, 27 Sep 2001 08:22:04 -0700 Received: from sebastian ([209.47.40.10]) by mailnet.consensys.com (8.11.2/8.11.2) with SMTP id f8RB9ZO24678; Thu, 27 Sep 2001 11:09:35 GMT Message-ID: <006301c14769$4413a1c0$4902a8c0@consensys.com> From: "Sebastian Kun" To: Cc: Subject: Re: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? Date: Thu, 27 Sep 2001 11:29:57 -0400 Organization: Consensys Corp. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk You need some mechanism to ensure mutual exclusion amongst the two machines, or else they will trash each other's data. There's a piece of software called GFS (http://www.sistina.com/gfs). I haven't tried it out, but it promises: The Global File System (GFS) is a shared disk cluster file system for Linux. GFS supports journaling and recovery from client failures. GFS cluster nodes physically share the same storage by means of Fibre Channel or shared SCSI devices. The file system appears to be local on each node and GFS synchronizes file access across the cluster. GFS is fully symmetric, that is, all nodes are equal and there is no server which may be a bottleneck or single point of failure. GFS uses read and write caching while maintaining full UNIX file system semantics. I'm not sure if GFS can work on top of XFS, or if it's a replacement for it. I also don't know if it'll run on IRIX. There are probably other commercial applications that'll do what you want, but they'd be pretty expensive.. Sebastian >I envision to make a filesystem, such that when a file is created >on either one system, it is visible directly on the other opposite >system.... Your FAQ indicate that it is possible to bring over XFS disks >from IRIX environment to the Linux environment, so, From owner-linux-xfs@oss.sgi.com Thu Sep 27 08:30:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RFU2i16589 for linux-xfs-outgoing; Thu, 27 Sep 2001 08:30:02 -0700 Received: from aquaman.rsp.com.au (unused.rsp.com.au [150.101.94.74] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RFTvD16557 for ; Thu, 27 Sep 2001 08:29:57 -0700 Received: from [10.5.0.31] (borat.rsp.com.au [10.5.0.31]) by aquaman.rsp.com.au (8.11.2/8.11.2) with ESMTP id f8RFTsI05296 for ; Fri, 28 Sep 2001 00:59:54 +0930 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Fri, 28 Sep 2001 00:59:55 +0930 Subject: I20 and XFS 1.0 - any known issues? From: Tony Clark To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi there, We're beavering away at 1am Australian time trying to get RH7.1 / XFS 1.0 to play nicely on an I20 RAID controller. The controller is an Intel SRCU21, on an Intel 440GX+ Motherboard. We'd previously tried the 1.0.1 + update combo but it kept dying part way through the install. The 1.0 gets all the way through the install, but hangs at the point where it's trying to mount the file systems. Any ideas or experiences shared would be appreciated - I could use some sleep... Thanks, Tony -- Tony Clark e: tony@rsp.com.au Rising Sun Pictures t: +61 8 8364 6074 Adelaide / Sydney f: +61 8 8364 6075 Australia w: http://www.rsp.com.au/ From owner-linux-xfs@oss.sgi.com Thu Sep 27 08:37:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RFb6U16819 for linux-xfs-outgoing; Thu, 27 Sep 2001 08:37:06 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RFb1D16800 for ; Thu, 27 Sep 2001 08:37:01 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id IAA00835 for ; Thu, 27 Sep 2001 08:35:49 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA3082536; Thu, 27 Sep 2001 10:35:44 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA30008; Thu, 27 Sep 2001 10:35:44 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8RFZf908442; Thu, 27 Sep 2001 10:35:41 -0500 Message-Id: <200109271535.f8RFZf908442@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Sebastian Kun" cc: shyberts@plato.med.harvard.edu, linux-xfs@oss.sgi.com Subject: Re: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? In-Reply-To: Message from "Sebastian Kun" of "Thu, 27 Sep 2001 11:29:57 EDT." <006301c14769$4413a1c0$4902a8c0@consensys.com> Date: Thu, 27 Sep 2001 10:35:41 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Woops, I missed the initial message on this thread. There is no way with XFS - or almost all filesystems to share a disk between multiple machines in parallel. Yes, the Linux XFS is on disk compatible with Irix XFS, but that just means you can mount the disk on one OR the other, not both at once. Remember filesystems keep a lot of state in memory for speed, unless the machines cooperate on the cached state you will corrupt your disk very quickly (a read write mount on one machine and readonly on a second does not work either by the way). GFS is one filesystem which is capable of this - it is a complete filesystem, not a layer which sits on top of another filesystem. It does cache coherency by locking regions of the disk using a semaphore device (can be a software device). GFS was initially developed on Irix, but I am pretty sure the latest stuff is linux only - they also just removed it from under the GPL. Another filesystem - which is available for Irix, but not Linux yet is CXFS, this is a layer on top of XFS which does coherency and allows direct disk access for file data. This will also not be GPLed and will cost money. Your only other options are things like NFS, AFS etc. Steve > You need some mechanism to ensure mutual exclusion amongst the two machines, > or else they will trash each other's data. > > There's a piece of software called GFS (http://www.sistina.com/gfs). I > haven't tried it out, but it promises: > > The Global File System (GFS) is a shared disk cluster file system for Linux. > GFS supports journaling and recovery from client failures. GFS cluster nodes > physically share the same storage by means of Fibre Channel or shared SCSI > devices. The file system appears to be local on each node and GFS > synchronizes file access across the cluster. GFS is fully symmetric, that > is, all nodes are equal and there is no server which may be a bottleneck or > single point of failure. GFS uses read and write caching while maintaining > full UNIX file system semantics. > > I'm not sure if GFS can work on top of XFS, or if it's a replacement for it. > I also don't know if it'll run on IRIX. There are probably other commercial > applications that'll do what you want, but they'd be pretty expensive.. > > Sebastian > > >I envision to make a filesystem, such that when a file is created > >on either one system, it is visible directly on the other opposite > >system.... Your FAQ indicate that it is possible to bring over XFS disks > >from IRIX environment to the Linux environment, so, > From owner-linux-xfs@oss.sgi.com Thu Sep 27 09:18:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RGIj517713 for linux-xfs-outgoing; Thu, 27 Sep 2001 09:18:45 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RGIaD17692 for ; Thu, 27 Sep 2001 09:18:37 -0700 Received: (qmail 31749 invoked by uid 8); 27 Sep 2001 16:18:35 -0000 From: thomas graichen Reply-To: thomas graichen X-Newsgroups: spoiled.linux.sgi.xfs Subject: uml with xfs support Date: Thu, 27 Sep 2001 18:17:11 +0200 Organization: spoiled dot org Lines: 95 Distribution: local Message-ID: References: Reply-To: thomas graichen X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.10-xfs (i686)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk maybe someone here has an idea (but this is low priority - just tried to get the xfs tree together with uml - user-mode-linux (.sourceforge.net) running) - this mail originally went to the uml-devel mailinglist ... --- snip --- maybe some more datails about this: 2.4.10-xfs plus uml-2.4.10-3 and when loading the xfs module i get the following backtrace running in debug (gdb) mode: (gdb) bt #0 panic (fmt=0xa01ba1a0 "Kernel mode fault at addr 0x%lx, ip 0x%lx") at panic.c:52 #1 0xa011844b in segv (address=12, ip=2684487610, is_write=0, is_user=0) at trap_kern.c:74 #2 0xa0118ffc in segv_handler (sig=11, sc=0xa46ffb78, usermode=0) at trap_user.c:309 #3 0xa0119124 in sig_handler (sig=11, sc= {gs = 0, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 0, edi = 3, esi = 0, ebp = 2758803044, esp = 2758803024, ebx = 2694052000, edx = 0, ecx = 0, eax = 2692755456, trapno = 14, err = 4, eip = 2684487610, cs = 35, __csh = 0, eflags = 534, esp_at_signal = 2758803024, ss = 43, __ssh = 0, fpstate = 0xa46ffbd0, oldmask = 268435456, cr2 = 12}) at trap_user.c:354 #4 #5 kfree (objp=0xa093f8a0) at slab.c:1430 #6 0xa000c76e in sys_init_module (name_user=0x80d9e30 "xfs", mod_user=0x403bf008) at module.c:574 #7 0xa0117445 in execute_syscall (regs= {regs = {135110192, 1077669896, 25, 134519728, 135195456, 2684342216, 4294967258, 43, 43, 0, 0, 128, 134765230, 35, 646, 2684342160, 43}}) at syscall_kern.c:325 #8 0xa011756b in syscall_handler (unused=0x0) at syscall_user.c:82 (gdb) maybe this helps - also it might be of interest that the xfs.o module compiled with debugging is 20+ mb in size :-) t thomas graichen wrote: > i just tried to get uml and the xfs tree from sgi to work together > but it hangs as soon as xfs filesystem gets loaded (either on boot > if statically compiled in or loaded as a module) ... is there any > idea where this might come from befroe looking deeper? > > so far the uml patch went cleanly into the xfs tree (top of the > cvs tree) with only one very easy to fix reject ... to get it to > compile i used the following small patch: > > --- ./arch/um/kernel/ksyms.c.org Wed Sep 26 14:47:01 2001 > +++ ./arch/um/kernel/ksyms.c Wed Sep 26 14:47:13 2001 > @@ -21,3 +21,4 @@ > EXPORT_SYMBOL(__do_strncpy_from_user); > EXPORT_SYMBOL(flush_tlb_range); > EXPORT_SYMBOL(__do_clear_user); > +EXPORT_SYMBOL(__do_strnlen_user); > --- ./fs/xfs/linux/xfs_globals.c.org Wed Sep 26 17:31:15 2001 > +++ ./fs/xfs/linux/xfs_globals.c Wed Sep 26 17:31:30 2001 > @@ -45,5 +45,5 @@ > int restricted_chown = 0; > int scache_linemask = 0x1f; /* second level cache line size mask */ > prid_t dfltprid; > -unsigned long physmem; > +extern unsigned long physmem; > int ndquot; > --- ./include/asm-um/uaccess.h.org Wed Sep 26 14:45:03 2001 > +++ ./include/asm-um/uaccess.h Wed Sep 26 14:45:19 2001 > @@ -153,6 +153,14 @@ > ¤t->thread.fault_catcher) : len); > } > > +static inline int __clear_user(void *mem, int len) > +{ > + return(access_ok(VERIFY_WRITE, mem, len) ? > + __do_clear_user(mem, len, > + ¤t->thread.fault_addr, > + ¤t->thread.fault_catcher) : len); > +} > + > extern int __do_strnlen_user(const char *str, unsigned long n, > void **fault_addr, void **fault_catcher); > > maybe something is wrong with it too (but i don't think so) ... > > any ideas? - thanks in advance > > t -- thomas graichen ... perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. --- antoine de saint-exupery From owner-linux-xfs@oss.sgi.com Thu Sep 27 10:08:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RH8AJ19247 for linux-xfs-outgoing; Thu, 27 Sep 2001 10:08:10 -0700 Received: from phobos.pop-star.net (phobos.pop-star.net [64.85.83.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RH88D19227 for ; Thu, 27 Sep 2001 10:08:08 -0700 Received: from zerowing.pop-star.net ([208.181.22.52]) by phobos.pop-star.net with asmtp (Exim 3.167 #4) id 15mefj-0002GF-00 for linux-xfs@oss.sgi.com; Thu, 27 Sep 2001 10:10:03 -0700 Subject: XFS cvs + Preempt Problem From: Andy Kwong To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13.99+cvs.2001.09.05.07.08 (Preview Release) Date: 27 Sep 2001 10:09:33 -0700 Message-Id: <1001610574.2402.39.camel@zerowing.pop-star.net> Mime-Version: 1.0 X-Authenticated-Sender: andy.kwong@pop-star.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk A XFS kernel from the cvs tree plus the preempt patches yielded the following error. (From a RPM build) fs/fs.o: In function `dput': fs/fs.o(.text+0x16498): undefined reference to `atomic_dec_and_lock' fs/fs.o(.text+0x194d7): more undefined references to `atomic_dec_and_lock' follow make[1]: *** [kallsyms] Error 1 make: *** [vmlinux] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.80358 (%build) I tried compiling the tree manually and it came up with the same error. Anyone have any ideas? --Andy From owner-linux-xfs@oss.sgi.com Thu Sep 27 10:20:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RHK2m19606 for linux-xfs-outgoing; Thu, 27 Sep 2001 10:20:02 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RHJxD19582 for ; Thu, 27 Sep 2001 10:19:59 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8RHJsK20242 for ; Thu, 27 Sep 2001 10:19:54 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA3082260; Thu, 27 Sep 2001 12:18:38 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA96394; Thu, 27 Sep 2001 12:18:37 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8RHIYs09809; Thu, 27 Sep 2001 12:18:34 -0500 Message-Id: <200109271718.f8RHIYs09809@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andy Kwong cc: linux-xfs@oss.sgi.com Subject: Re: XFS cvs + Preempt Problem In-Reply-To: Message from Andy Kwong of "27 Sep 2001 10:09:33 PDT." <1001610574.2402.39.camel@zerowing.pop-star.net> Date: Thu, 27 Sep 2001 12:18:34 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > A XFS kernel from the cvs tree plus the preempt patches yielded the > following error. (From a RPM build) > > fs/fs.o: In function `dput': > fs/fs.o(.text+0x16498): undefined reference to `atomic_dec_and_lock' > fs/fs.o(.text+0x194d7): more undefined references to > `atomic_dec_and_lock' follow > make[1]: *** [kallsyms] Error 1 > make: *** [vmlinux] Error 2 > error: Bad exit status from /var/tmp/rpm-tmp.80358 (%build) > > I tried compiling the tree manually and it came up with the same error. > Anyone have any ideas? This is not code which xfs has changed, it is core kernel code, atomic_dec_and_lock is in arch/i386/lib/dec_and_lock.c Steve > > --Andy From owner-linux-xfs@oss.sgi.com Thu Sep 27 12:56:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RJuGo22602 for linux-xfs-outgoing; Thu, 27 Sep 2001 12:56:16 -0700 Received: from umbi3.umbi.umd.edu (umbi3.umbi.umd.edu [136.160.7.51]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RJuDD22583 for ; Thu, 27 Sep 2001 12:56:14 -0700 Received: from umbi.umd.edu (amanda.carb.nist.gov [129.6.113.5]) by umbi3.umbi.umd.edu (Netscape Messaging Server 4.15) with ESMTP id GKC7FQ00.NVU for ; Thu, 27 Sep 2001 15:57:26 -0400 Message-ID: <3BB3845C.E7BE4E3D@umbi.umd.edu> Date: Thu, 27 Sep 2001 15:56:12 -0400 From: Jonathan Dill Organization: CARB X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: how to truncate XFS filesystem? References: <200109271718.f8RHIYs09809@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have an XFS filesystem on a 50 GB disk that "thinks" that it's a 170 GB filesystem due to weirdness with a hot swap drive bay at a remote site where data was collected. When I try to mount this FS I get "filesystem too large for device." I'm making an image of the FS onto a second disk for backup purposes and may take a stab at it with xfs_db. Does anybody know how to "truncate" the filesystem to fit the size of the device? The next thing I might try is to dump the image onto a 170 GB disk and see if xfs_repair can do something with it. Thanks, -- "Jonathan F. Dill" (dill@umbi.umd.edu) CARB IT Coordinator Experimental Support Site http://concept.umbi.umd.edu From owner-linux-xfs@oss.sgi.com Thu Sep 27 15:51:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8RMpiC26371 for linux-xfs-outgoing; Thu, 27 Sep 2001 15:51:44 -0700 Received: from phobos.pop-star.net (phobos.pop-star.net [64.85.83.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8RMpeD26347 for ; Thu, 27 Sep 2001 15:51:40 -0700 Received: from zerowing.pop-star.net ([208.181.22.52]) by phobos.pop-star.net with asmtp (Exim 3.167 #4) id 15mk29-0006Fh-00; Thu, 27 Sep 2001 15:53:33 -0700 Subject: Re: XFS cvs + Preempt Problem From: Andy Kwong To: Steve Lord Cc: linux-xfs@oss.sgi.com In-Reply-To: <200109271718.f8RHIYs09809@jen.americas.sgi.com> References: <200109271718.f8RHIYs09809@jen.americas.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13.99+cvs.2001.09.05.07.08 (Preview Release) Date: 27 Sep 2001 15:53:03 -0700 Message-Id: <1001631184.2397.58.camel@zerowing.pop-star.net> Mime-Version: 1.0 X-Authenticated-Sender: andy.kwong@pop-star.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sorry, this problems seems to manifest itself when preempt is compiled for i386. If I compile it for i686, the problem goes away. On Thu, 2001-09-27 at 10:18, Steve Lord wrote: > > A XFS kernel from the cvs tree plus the preempt patches yielded the > > following error. (From a RPM build) > > > > fs/fs.o: In function `dput': > > fs/fs.o(.text+0x16498): undefined reference to `atomic_dec_and_lock' > > fs/fs.o(.text+0x194d7): more undefined references to > > `atomic_dec_and_lock' follow > > make[1]: *** [kallsyms] Error 1 > > make: *** [vmlinux] Error 2 > > error: Bad exit status from /var/tmp/rpm-tmp.80358 (%build) > > > > I tried compiling the tree manually and it came up with the same error. > > Anyone have any ideas? > > This is not code which xfs has changed, it is core kernel code, > atomic_dec_and_lock is in arch/i386/lib/dec_and_lock.c > > Steve > > > > > --Andy > > From owner-linux-xfs@oss.sgi.com Thu Sep 27 17:32:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8S0WjH28191 for linux-xfs-outgoing; Thu, 27 Sep 2001 17:32:45 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8S0WhD28172 for ; Thu, 27 Sep 2001 17:32:43 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8S0WZK07231 for ; Thu, 27 Sep 2001 17:32:35 -0700 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA14169; Fri, 28 Sep 2001 10:31:14 +1000 (EST) Date: Fri, 28 Sep 2001 10:31:14 +1000 (EST) From: Nathan Scott Message-Id: <200109280031.KAA14169@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Cc: chip.christian@storageapps.com Subject: TAKE - repair Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Thu Sep 27 17:30:25 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103550a cmd/xfsprogs/repair/phase4.c - 1.4 cmd/xfsprogs/doc/CHANGES - 1.38 - fix xfs_repair bug in handling a corrupt root directory inode with multiple "lost+found" entries. From owner-linux-xfs@oss.sgi.com Thu Sep 27 23:56:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8S6uLJ01383 for linux-xfs-outgoing; Thu, 27 Sep 2001 23:56:21 -0700 Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.131]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8S6uED01363 for ; Thu, 27 Sep 2001 23:56:14 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA05653; Fri, 28 Sep 2001 08:56:05 +0200 (CEST) Message-Id: <4.3.2.7.2.20010928085122.03342320@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 28 Sep 2001 08:55:25 +0200 To: Edward Cates , seth.mos@xs4all.nl From: Seth Mos Subject: Re: XFS + NFS + UMASK Cc: linux-xfs@oss.sgi.com In-Reply-To: <200109271830.f8RIUTNM006799@mxzilla4.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk CC'ing the list At 11:29 27-9-2001 -0700, Edward Cates wrote: >I'm running Linxux 2.4.8-xfs with NFS v3 on: >dual 1 GHz PIII >2 GB RAM >Mylex DAC960 RAID card >5 Seagate Cheetah 73.4 GB hard drives >blah blah blah blah blah > >It all works beautifully, EXCEPT we can't get NFS to use any UMASK besides >022. Is this an known XFS issue, or do I need to go bother someone else? You just get permission Denied Errors? >And yes, I read the entry in the FAQ, but it said the problem was fixed after >2.4.5, which doesn't seem to be the case. I believe the actual problem with pre 2.4.5 was that it would occasionally have some NFS problems. Either bad speed or wrong modes. All those fixes went into the 2.4.2 and 2.4.3 kernel that are shipped on XFS 1.0.1 AFAIK. I think yours is entirely different. The combination of NFS and ACLs is still unknown terrain and has some loopholes. I gather that the umask on the NFS client is correctly set? Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Sep 28 00:07:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8S77Su01664 for linux-xfs-outgoing; Fri, 28 Sep 2001 00:07:28 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8S77ND01644 for ; Fri, 28 Sep 2001 00:07:24 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id JAA28383; Fri, 28 Sep 2001 09:05:59 +0200 (CEST) Message-Id: <4.3.2.7.2.20010928085950.03342e30@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 28 Sep 2001 09:05:19 +0200 To: Tony Clark , From: Seth Mos Subject: Re: I20 and XFS 1.0 - any known issues? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 00:59 28-9-2001 +0930, Tony Clark wrote: >Hi there, > >We're beavering away at 1am Australian time trying to get RH7.1 / XFS 1.0 to >play nicely on an I20 RAID controller. The controller is an Intel SRCU21, >on an Intel 440GX+ Motherboard. No experience with that combination. >We'd previously tried the 1.0.1 + update combo but it kept dying part way >through the install. You are sure that the hardware is correct. >The 1.0 gets all the way through the install, but hangs at the point where >it's trying to mount the file systems. Any errors in the log or the second console? Is this in the installer or after installing? If it is in the installer you could switch to the 4th or 5th console to see what might be going wrong. >Any ideas or experiences shared would be appreciated - I could use some >sleep... I just had some. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Sep 28 00:31:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8S7Vof02273 for linux-xfs-outgoing; Fri, 28 Sep 2001 00:31:50 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8S7VhD02254 for ; Fri, 28 Sep 2001 00:31:43 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id AAA09210 for ; Fri, 28 Sep 2001 00:30:30 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id HAA08871; Fri, 28 Sep 2001 07:29:47 GMT Date: Fri, 28 Sep 2001 07:29:47 +0000 From: Timothy Shimmin To: Seth Mos Cc: Edward Cates , seth.mos@xs4all.nl, linux-xfs@oss.sgi.com Subject: Re: XFS + NFS + UMASK Message-ID: <20010928072947.G10761@boing.melbourne.sgi.com> References: <200109271830.f8RIUTNM006799@mxzilla4.xs4all.nl> <4.3.2.7.2.20010928085122.03342320@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <4.3.2.7.2.20010928085122.03342320@pop.xs4all.nl>; from knuffie@xs4all.nl on Fri, Sep 28, 2001 at 08:55:25AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Sep 28, 2001 at 08:55:25AM +0200, Seth Mos wrote: > CC'ing the list > > At 11:29 27-9-2001 -0700, Edward Cates wrote: > >I'm running Linxux 2.4.8-xfs with NFS v3 on: > >dual 1 GHz PIII > >2 GB RAM > >Mylex DAC960 RAID card > >5 Seagate Cheetah 73.4 GB hard drives > >blah blah blah blah blah > > > >It all works beautifully, EXCEPT we can't get NFS to use any UMASK besides > >022. Is this an known XFS issue, or do I need to go bother someone else? > Yes this would be a known unresolved issue, I'm afraid. We will look at resolving this while merging kernel changes with Andreas G.'s ACL/EA patch. This problem is that we can't apply the umask if we have the chance of having a default ACL on the dir. In xfs acl code if we find out that it wasn't a default ACL after all, then we apply the umask as usually is intended. But in the case of nfsd, we shouldn't be applying the umask. (Steve's hack solution for nfsd) Andi also had a possible solution (mentioned below). More details are in an email I sent in mid August: ==================================================================== Date: Thu, 16 Aug 2001 14:07:19 +1000 From: Timothy Shimmin To: Steve Lord Cc: Andi Kleen , Ken Cross , Linux XFS Subject: Re: SPEC failures On Wed, Aug 15, 2001 at 02:34:21PM -0500, Steve Lord wrote: > > On Wed, Aug 15, 2001 at 10:30:46AM -0500, Steve Lord wrote: > > > Andrew had the approach of setting the umask of the nfsd process to 0 at > > > startup, there was some other reason for this not being popular. > > > > He did it for init_task, which disturbed all other kernel threads too > > and opened tons of security holes. > > The right way IMHO is to give nfsd an own fs_struct and set umask there, > > as in this patch. > > > > -Andi > > Thanks, > > Care to try this one on Neil Brown or Trond? > I wonder if the acl project > has run into the same issue? I would say the answer is yes. On Aug 2, Andreas released a new patch, 0.7.15, for the 2.4.7 kernel. Having a quick scan of the patch he has definitely changed where the umask is applied in the case of no default ACL. He has also patched some nfsd code. It would be worth going through this patch carefully...:) > The tricky part in justifying this is nothing > in the main kernel needs this change right now. > Just to be sure I understand what is going on... Previously, the umask was applied to the mode in vfs_mkdir(), vfs_mknod() and vfs_create(). In 2.4.7, the umask code was moved to sys_mkdir(), sys_mknod() and open_namei() respectively, to just before where the vfs_*() calls are being made. The other caller of these particular vfs_*() calls is nfsd_create [linux/fs/nfsd/vfs.c]. So by moving the umask code out it means that nfsd_create() will no longer be calling the vfs functions which were setting the umask. But in the XFS inode operations, where we set up linvfs_create(), linvfs_mkdir() and linvfs_mknod(), we are still applying the umask if no default ACL exists. --Tim ==================================================================== From owner-linux-xfs@oss.sgi.com Fri Sep 28 01:00:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8S80dF03154 for linux-xfs-outgoing; Fri, 28 Sep 2001 01:00:39 -0700 Received: from aquaman.rsp.com.au (unused.rsp.com.au [150.101.94.74] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8S80WD03132 for ; Fri, 28 Sep 2001 01:00:32 -0700 Received: from [10.5.0.31] (borat.rsp.com.au [10.5.0.31]) by aquaman.rsp.com.au (8.11.2/8.11.2) with ESMTP id f8S80LI11304; Fri, 28 Sep 2001 17:30:21 +0930 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Fri, 28 Sep 2001 17:30:22 +0930 Subject: Re: I20 and XFS 1.0 - any known issues? From: Tony Clark To: Seth Mos , Message-ID: In-Reply-To: <4.3.2.7.2.20010928085950.03342e30@pop.xs4all.nl> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello: on 28/9/01 4:35 PM, Seth Mos at knuffie@xs4all.nl wrote: > At 00:59 28-9-2001 +0930, Tony Clark wrote: >> Hi there, >> >> We're beavering away at 1am Australian time trying to get RH7.1 / XFS 1.0 to >> play nicely on an I20 RAID controller. The controller is an Intel SRCU21, >> on an Intel 440GX+ Motherboard. > > No experience with that combination. > >> We'd previously tried the 1.0.1 + update combo but it kept dying part way >> through the install. > > You are sure that the hardware is correct. We'd previously had it working under 6.2 with the I2O Kernel that Intel released with the board. It was based on 2.2.16, and seemed to behave OK with that combo. It's now up and working, but we ended up using the 1.0 XFS CD, and setting the filesystems to be EXT2 (yuck) rather than XFS ( happines ). > >> The 1.0 gets all the way through the install, but hangs at the point where >> it's trying to mount the file systems. > > Any errors in the log or the second console? Is this in the installer or > after installing? If it is in the installer you could switch to the 4th or > 5th console to see what might be going wrong. Couldn't really tell due to frustration at about our 8th install attempt. Now it's up again, we'll start to figure out what was going wrong and hopefully isolate it to something more definate. We'll have a go at making some filesystems XFS, which may show us what's up. > >> Any ideas or experiences shared would be appreciated - I could use some >> sleep... > > I just had some. Well, I got at least 2&1/2 last night, so it's home time for more. Thanks to those who responded. TOny > > Cheers > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. > -- Tony Clark e: tony@rsp.com.au Rising Sun Pictures t: +61 8 8364 6074 Adelaide / Sydney f: +61 8 8364 6075 Australia w: http://www.rsp.com.au/ From owner-linux-xfs@oss.sgi.com Fri Sep 28 01:47:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8S8lg304536 for linux-xfs-outgoing; Fri, 28 Sep 2001 01:47:42 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8S8laD04512 for ; Fri, 28 Sep 2001 01:47:36 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id KAA09695; Fri, 28 Sep 2001 10:46:13 +0200 (CEST) Message-Id: <4.3.2.7.2.20010928101757.03f29f78@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 28 Sep 2001 10:45:32 +0200 To: Tony Clark , From: Seth Mos Subject: Re: I20 and XFS 1.0 - any known issues? In-Reply-To: References: <4.3.2.7.2.20010928085950.03342e30@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:30 28-9-2001 +0930, Tony Clark wrote: >on 28/9/01 4:35 PM, Seth Mos at knuffie@xs4all.nl wrote: > > At 00:59 28-9-2001 +0930, Tony Clark wrote: > >> We'd previously tried the 1.0.1 + update combo but it kept dying part way > >> through the install. > > > > You are sure that the hardware is correct. > >We'd previously had it working under 6.2 with the I2O Kernel that Intel >released with the board. It was based on 2.2.16, and seemed to behave OK >with that combo. It's now up and working, but we ended up using the 1.0 XFS >CD, and setting the filesystems to be EXT2 (yuck) rather than XFS ( happines >). Hmmm, I have never encountered this raid adapter before. Would you need a seperate patch for getting it to work? I have tried getting the AMI Megaraid in I2O mode which always resulted in a kernel panic. What you could try is build a cvs kernel (currently 2.4.10) which might not have this problem. There is no installer yet with a kernel later then 2.4.5 so a bit of time is needed before this can be used. There is no word yet on a RedHat 7.2 installer disk although this would probably be started after 7.2 is officially released. Anyone wishing to participate or contribute may contact the list. >> The 1.0 gets all the way through the install, but hangs at the point where > >> it's trying to mount the file systems. > > > > Any errors in the log or the second console? Is this in the installer or > > after installing? If it is in the installer you could switch to the 4th or > > 5th console to see what might be going wrong. >Couldn't really tell due to frustration at about our 8th install attempt. ! >Now it's up again, we'll start to figure out what was going wrong and >hopefully isolate it to something more definate. We'll have a go at making >some filesystems XFS, which may show us what's up. If you have a working system complete with logging it might be a bit simpler to debug. > >> Any ideas or experiences shared would be appreciated - I could use some > >> sleep... > > > > I just had some. > >Well, I got at least 2&1/2 last night, so it's home time for more. Thanks >to those who responded. You're welcome. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Sep 28 02:09:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8S99Fa05194 for linux-xfs-outgoing; Fri, 28 Sep 2001 02:09:15 -0700 Received: from TYO201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.214]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8S99AD05175 for ; Fri, 28 Sep 2001 02:09:10 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.197]) by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8S992a08967 for ; Fri, 28 Sep 2001 18:09:03 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.196]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8S992Z16603 for ; Fri, 28 Sep 2001 18:09:02 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id f8S97jF10796 for ; Fri, 28 Sep 2001 18:07:51 +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 AAA495 for ; Fri, 28 Sep 2001 18:07:44 +0900 Received: FROM mailsv.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Fri Sep 28 18:07:43 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by mailsv.tnes.nec.co.jp (8.9.3/3.7W01031510) with ESMTP id SAA23703 for ; Fri, 28 Sep 2001 18:07:43 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f8S97ai02510 for ; Fri, 28 Sep 2001 18:07:40 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id SAA21946; Fri, 28 Sep 2001 18:07:32 +0900 (JST) Message-Id: <200109280907.SAA21946@tagajo.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: 2.4.10-xfs with dmapi option panic Date: Fri, 28 Sep 2001 18:07:32 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi there, While testing the XFS filesystem with dmapi option, I encountered panic with the following operations: # mkfs.xfs /dev/foo # mount -t xfs -o dmapi /dev/foo /mnt/foo # umount /mnt/foo kernel panic: dm_change_fsys_entry: can't find DMAPI fsrp for vfsp c6965860 backtrace process using KDB is: schedule+0x520 (0xc048fa40,0x0,0x0,0xc0382580) notifier_caller_chain+0x23(0xc0508da0,0x0,0x0,0x0) panic+0x87 (0xc0382580,0xc303e65c,0xc303e584) dm_change_fsys_entry+0x30 (0xc303e65c) dm_send_namesp_event+0x60 (0x2, 0xc1b26260,0x0,0xc1b26260,0x0) xfs_unmount+0x74 (0xc1248400,0x0,0xc05132c0) fs_dounmount+0x59 linvfs_put_super+0x36 kill_super+0x14d __mntput+0x39 path_release+0x2a sys_umount+0x194 sys_oldumount+0xe system_call+0x33 Kernel: linux-2.4.10-xfs (20010925 CVS Tree) gcc: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) Box: Pentium III (Coppermine) 733MHz + SiS 630 chip set + 128MB RAM This is not critical issue so far for me, however, I couldn't find same errors in the archive, so report to the list. Cheers, Takayuki From owner-linux-xfs@oss.sgi.com Fri Sep 28 02:38:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8S9cgH05932 for linux-xfs-outgoing; Fri, 28 Sep 2001 02:38:42 -0700 Received: from TYO201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.214]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8S9cZD05912 for ; Fri, 28 Sep 2001 02:38:36 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.195]) by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8S9cSa29021 for ; Fri, 28 Sep 2001 18:38:29 +0900 (JST) Received: from mailsv.nec.co.jp (mailgate51.nec.co.jp [10.7.69.196]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8S9cSc07329 for ; Fri, 28 Sep 2001 18:38:28 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv.nec.co.jp (8.11.6/3.7W-MAILSV-NEC) with ESMTP id f8S9cPl28953 for ; Fri, 28 Sep 2001 18:38:26 +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 AAA377 for ; Fri, 28 Sep 2001 18:38:24 +0900 Received: FROM mailsv.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Fri Sep 28 18:38:23 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by mailsv.tnes.nec.co.jp (8.9.3/3.7W01031510) with ESMTP id SAA27735 for ; Fri, 28 Sep 2001 18:38:23 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f8S9cNi04417 for ; Fri, 28 Sep 2001 18:38:23 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id SAA22075; Fri, 28 Sep 2001 18:38:23 +0900 (JST) Message-Id: <200109280938.SAA22075@tagajo.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: migout (sample_hsm) dumped core Date: Fri, 28 Sep 2001 18:38:23 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi there, While testing XFS dmapi functions with a CVS kernel which is compiled several weeks ago, linux-2.4-xfs/cmd/xfstests/dmapi/src/sample_hsm/migout dumped core, so I made a patch as follows: --- migout.c 2001/03/07 22:43:23 1.2 +++ migout.c 2001/09/28 09:25:55 @@ -469,6 +469,7 @@ char *cp, *start; size_t len; char *hanp; + char *hanpp=NULL; /* * Skip any leading white space, and check the length @@ -505,8 +506,8 @@ cp += len*2; *cp = '\0'; - atohan( hanp, (void**)&handle_buf, &len ); - + atohan( hanp, (void**)&hanpp, &len ); + memcpy( handle_buf, hanpp, len); /* skip over white space */ while (!isalnum(*cp)) It works for me, but could anybody on the list check this patch? Cheers, Takayuki From owner-linux-xfs@oss.sgi.com Fri Sep 28 02:48:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8S9mKk06277 for linux-xfs-outgoing; Fri, 28 Sep 2001 02:48:20 -0700 Received: from atlas.cc.itu.edu.tr (atlas.cc.itu.edu.tr [160.75.2.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8S9m7D06194 for ; Fri, 28 Sep 2001 02:48:08 -0700 Received: from aontws4044 (AONTWS4044.cc.itu.edu.tr [160.75.5.44]) by atlas.cc.itu.edu.tr (8.11.2/8.11.2) with SMTP id f8S9lev21494 for ; Fri, 28 Sep 2001 12:47:40 +0300 From: =?iso-8859-9?Q?=DEeref_Tufan_=DEen?= To: Subject: NFSD problems Date: Fri, 28 Sep 2001 12:53:52 +0300 Message-ID: <00a901c14803$7b623520$2c054ba0@aontws4044> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-9" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am using Linux Kernel 2.4.3 (smp) + XFS 1.0.1 (rpm from SGI). I have a NFS server , and exported file systems are on XFS. The machine worked fine for two days then stopped giving response to NFS requests. When I looked to kernel logs I saw the first log below. All nfs daemons were at "DW" state so I could not kill them.. I rebooted the server then after a few hours I got the second log , and nfs stopped working again. Does anyone have an idea?? PS: Exported file system is on an Raidtech SAN device..I am using Qlogic 2100 HBA for accessing the storage. And I use LVM (0.9.1 beta 6 I remember). ------------------------------------------------------------ Sep 27 19:58:48 lnxsrv1 kernel: invalid operand: 0000 Sep 27 19:58:48 lnxsrv1 kernel: CPU: 1 Sep 27 19:58:48 lnxsrv1 kernel: EIP: 0010:[dput+20/364] Sep 27 19:58:48 lnxsrv1 kernel: EIP: 0010:[] Sep 27 19:58:48 lnxsrv1 kernel: EFLAGS: 00010246 Sep 27 19:58:48 lnxsrv1 kernel: eax: 00000000 ebx: c63c0120 ecx: c63c08a0 edx: 00000003 Sep 27 19:58:48 lnxsrv1 kernel: esi: c63c0120 edi: c63c08a0 ebp: c63c08a0 esp: cee75e78 Sep 27 19:58:48 lnxsrv1 kernel: ds: 0018 es: 0018 ss: 0018 Sep 27 19:58:48 lnxsrv1 kernel: Process nfsd (pid: 1135, stackpage=cee75000) Sep 27 19:58:48 lnxsrv1 kernel: Stack: ffffffea c63c0120 d0a12005 c63c0120 00000003 1d55f8b1 d0a123c6 c63c08a0 Sep 27 19:58:48 lnxsrv1 kernel: 00000003 c6292410 46000000 c6292400 c1624e00 cf4949f8 cee75f38 ffffff8c Sep 27 19:58:48 lnxsrv1 kernel: 00000000 d0a12754 cf494800 1d55f8b1 00000000 00000000 00000001 c6292400 Sep 27 19:58:48 lnxsrv1 kernel: Call Trace: [usbcore:usb_devfs_handle_Rsmp_e9c5f87f+1301797/256597015] [usbcore:usb_devfs_handle_Rsmp_e9c5f87f$ Sep 27 19:58:48 lnxsrv1 kernel: Call Trace: [] [] [] [] [] Sep 27 19:58:48 lnxsrv1 kernel: [usbcore:usb_devfs_handle_Rsmp_e9c5f87f+1296956/256601856] [usbcore:usb_devfs_handle_Rsmp_e9c5f87f+1358176/$ Sep 27 19:58:48 lnxsrv1 kernel: [] [] [] [] [] [] Sep 27 19:58:48 lnxsrv1 kernel: [usbcore:usb_devfs_handle_Rsmp_e9c5f87f+1357896/256540916] [usbcore:usb_devfs_handle_Rsmp_e9c5f87f+1294441/$ Sep 27 19:58:48 lnxsrv1 kernel: [] [] [] Sep 27 19:58:48 lnxsrv1 kernel: Sep 27 19:58:48 lnxsrv1 kernel: Code: 0f 0b 68 80 0c 36 c0 53 e8 7f ba 13 00 83 c4 08 85 c0 0f 84 -------------------------------------------------------------------------- ------------------------------------------------------------ Sep 28 12:24:58 lnxsrv1 kernel: invalid operand: 0000 Sep 28 12:24:58 lnxsrv1 kernel: CPU: 1 Sep 28 12:24:58 lnxsrv1 kernel: EIP: 0010:[dput+20/364] Sep 28 12:24:58 lnxsrv1 kernel: EIP: 0010:[] Sep 28 12:24:58 lnxsrv1 kernel: EFLAGS: 00010246 Sep 28 12:24:58 lnxsrv1 kernel: eax: 00000000 ebx: c7540560 ecx: c75402e0 edx: 00000003 Sep 28 12:24:58 lnxsrv1 kernel: esi: c7540560 edi: c75402e0 ebp: c75402e0 esp: c18e7e78 Sep 28 12:24:58 lnxsrv1 kernel: ds: 0018 es: 0018 ss: 0018 Sep 28 12:24:58 lnxsrv1 kernel: Process nfsd (pid: 972, stackpage=c18e7000) Sep 28 12:24:58 lnxsrv1 kernel: Stack: ffffffea c7540560 d0a04005 c7540560 00000003 04179db8 d0a043c6 c75402e0 Sep 28 12:24:58 lnxsrv1 kernel: 00000003 c4fb6c10 46000000 c4fb6c00 c0239ab3 cc45bdf8 c96c07a0 ffffff8c Sep 28 12:24:58 lnxsrv1 kernel: 00000000 d0a04754 cc45bc00 04179db8 00000000 00000000 00000001 c4fb6c00 Sep 28 12:24:58 lnxsrv1 kernel: Call Trace: [aic7xxx:__insmod_aic7xxx_S.bss_L256+1848229/210353819] [aic7xxx:__insmod_aic7xxx_S.bss_L256+18491$ Sep 28 12:24:58 lnxsrv1 kernel: Call Trace: [] [] [] [] [] Sep 28 12:24:58 lnxsrv1 kernel: [aic7xxx:__insmod_aic7xxx_S.bss_L256+1870173/210331875] [aic7xxx:__insmod_aic7xxx_S.bss_L256+1843388/210358$ Sep 28 12:24:58 lnxsrv1 kernel: [] [] [] [] [] [] Sep 28 12:24:58 lnxsrv1 kernel: [aic7xxx:__insmod_aic7xxx_S.bss_L256+1905632/210296416] [aic7xxx:__insmod_aic7xxx_S.bss_L256+1904328/210297$ Sep 28 12:24:58 lnxsrv1 kernel: [] [] [] [] Sep 28 12:24:58 lnxsrv1 kernel: Sep 28 12:24:58 lnxsrv1 kernel: Code: 0f 0b 68 80 0c 36 c0 53 e8 7f ba 13 00 83 c4 08 85 c0 0f 84 -------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Fri Sep 28 02:51:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8S9pvC06450 for linux-xfs-outgoing; Fri, 28 Sep 2001 02:51:57 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8S9pnD06430 for ; Fri, 28 Sep 2001 02:51:49 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8S9phL21922 for ; Fri, 28 Sep 2001 02:51:43 -0700 Received: (from fsgqa@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id TAA36050 for linux-xfs@oss.sgi.com; Fri, 28 Sep 2001 19:50:25 +1000 (EST) Date: Fri, 28 Sep 2001 19:50:25 +1000 (EST) From: FSG QA Message-Id: <200109280950.TAA36050@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump/restore changes for ia64 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Fri Sep 28 02:49:27 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/fsgqa/isms/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103560a cmd/xfstests/src/dumpfile - 1.1 - An IRIX xfsdump dump-file for test 061. cmd/xfstests/061.out - 1.1 - comparison output for 061 cmd/xfstests/061 - 1.1 - Test restoring of a dump created on IRIX. cmd/xfsdump/restore/win.c - 1.2 - Get rid of w_lasttouched since it is never used and it is an uneccessary overhead. cmd/xfsdump/inventory/inventory.h - 1.2 cmd/xfsdump/inventory/inv_mgr.c - 1.2 cmd/xfsdump/inventory/inv_idx.c - 1.2 cmd/xfsdump/inventory/inv_api.c - 1.3 cmd/xfsdump/dump/inomap.h - 1.2 cmd/xfsdump/dump/inomap.c - 1.8 cmd/xfsdump/dump/content.c - 1.13 cmd/xfsdump/common/util.h - 1.2 cmd/xfsdump/common/util.c - 1.6 cmd/xfsdump/common/types.h - 1.3 - time32_t changes cmd/xfsdump/common/stkchk.c - 1.2 - make a size long so comparison works for ia32/ia64 with ptr cmd/xfsdump/common/ring.h - 1.2 cmd/xfsdump/common/main.c - 1.11 cmd/xfsdump/common/inventory_priv.h - 1.2 cmd/xfsdump/common/inventory_priv.c - 1.2 cmd/xfsdump/common/inventory.h - 1.2 cmd/xfsdump/common/inventory.c - 1.2 cmd/xfsdump/common/global.h - 1.2 cmd/xfsdump/common/global.c - 1.2 - time32_t changes cmd/xfsdump/common/getdents.c - 1.4 - bring over the latest getdents from glibc so that it works on ia64 without unaligned access messages. cmd/xfsdump/common/drive_simple.c - 1.2 - get rid of unecessary assert and simplify a test. cmd/xfsdump/common/drive_scsitape.c - 1.3 - changes for testing strategy for devfs mounted tape drives cmd/xfsdump/common/dlog.h - 1.2 cmd/xfsdump/common/dlog.c - 1.3 cmd/xfsdump/common/content_inode.h - 1.2 cmd/xfsdump/restore/dirattr.h - 1.2 cmd/xfsdump/restore/dirattr.c - 1.2 cmd/xfsdump/restore/content.c - 1.15 cmd/xfsdump/inventory/inv_stobj.c - 1.4 cmd/xfsdump/inventory/inv_priv.h - 1.2 cmd/xfsdump/inventory/inv_oref.c - 1.2 cmd/xfsdump/invutil/invutil.c - 1.4 - time32_t changes cmd/xfsdump/librmt/rmtioctl.c - 1.4 - mtget conversion code needed to handle difference of structure on ia32 and ia64 b/c fields defined as longs. cmd/xfsdump/VERSION - 1.18 - Bump version for ia64 changes. cmd/xfsdump/doc/CHANGES - 1.21 - time32_t changes Also forgot to bring over bs_dmstate from bulkstat now that it has come on the scene. cmd/xfstests/new - 1.2 - Get rid of leading zero as awk now treats it as octal. cmd/xfstests/group - 1.13 - Add 061. cmd/xfstests/common.dump - 1.15 - Add some stuff to help 061. For IRIX chmod, it needs set gid on dirs as symbolic form. cmd/xfstests/common.config - 1.8 - Add surly - ia64 melbourne test machine. cmd/xfstests/common - 1.2 - Get rid of leading zero as awk now treats it as octal. cmd/xfstests/024 - 1.3 - Add diagnostic output of bulkstat to 024.full file. From owner-linux-xfs@oss.sgi.com Fri Sep 28 03:17:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SAHmS07018 for linux-xfs-outgoing; Fri, 28 Sep 2001 03:17:48 -0700 Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SAHgD06999 for ; Fri, 28 Sep 2001 03:17:42 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.195]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8SAHfQ18661 for ; Fri, 28 Sep 2001 19:17:41 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8SAHdc09830 for ; Fri, 28 Sep 2001 19:17:39 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id f8SAHZF28882 for ; Fri, 28 Sep 2001 19:17:35 +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 AAA291 for ; Fri, 28 Sep 2001 19:17:33 +0900 Received: FROM tnesgate.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Fri Sep 28 19:17:32 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by tnesgate.tnes.nec.co.jp (8.9.3/3.7W00091816) with ESMTP id TAA42085 for ; Fri, 28 Sep 2001 19:17:32 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f8SAHWi06353 for ; Fri, 28 Sep 2001 19:17:32 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id TAA22268; Fri, 28 Sep 2001 19:17:32 +0900 (JST) Message-Id: <200109281017.TAA22268@tagajo.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: Re: migout (sample_hsm) dumped core In-reply-to: Your message of Fri, 28 Sep 2001 18:38:23 +0900. <200109280938.SAA22075@tagajo.bsd.tnes.nec.co.jp> Date: Fri, 28 Sep 2001 19:17:32 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, migout did not dumped core. It returned an error EBADF. Sorry for the wrong information. Takayuki > Hi there, > > While testing XFS dmapi functions with a CVS kernel which is > compiled several weeks ago, > linux-2.4-xfs/cmd/xfstests/dmapi/src/sample_hsm/migout dumped > core, so I made a patch as follows: > > --- migout.c 2001/03/07 22:43:23 1.2 > +++ migout.c 2001/09/28 09:25:55 > @@ -469,6 +469,7 @@ > char *cp, *start; > size_t len; > char *hanp; > + char *hanpp=NULL; > > /* > * Skip any leading white space, and check the length > @@ -505,8 +506,8 @@ > cp += len*2; > *cp = '\0'; > > - atohan( hanp, (void**)&handle_buf, &len ); > - > + atohan( hanp, (void**)&hanpp, &len ); > + memcpy( handle_buf, hanpp, len); > > /* skip over white space */ > while (!isalnum(*cp)) > > > > It works for me, but could anybody on the list check this patch? > > Cheers, > > Takayuki From owner-linux-xfs@oss.sgi.com Fri Sep 28 03:39:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SAdjj07537 for linux-xfs-outgoing; Fri, 28 Sep 2001 03:39:45 -0700 Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SAddD07515 for ; Fri, 28 Sep 2001 03:39:40 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.197]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8SAdcQ01489 for ; Fri, 28 Sep 2001 19:39:38 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.196]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8SAdbZ04863 for ; Fri, 28 Sep 2001 19:39:37 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id f8SAdbF20045 for ; Fri, 28 Sep 2001 19:39:37 +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 AAA77 for ; Fri, 28 Sep 2001 19:39:36 +0900 Received: FROM mailsv.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Fri Sep 28 19:39:35 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by mailsv.tnes.nec.co.jp (8.9.3/3.7W01031510) with ESMTP id TAA33284 for ; Fri, 28 Sep 2001 19:39:35 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f8SAdZi07304 for ; Fri, 28 Sep 2001 19:39:35 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id TAA22370; Fri, 28 Sep 2001 19:39:35 +0900 (JST) Message-Id: <200109281039.TAA22370@tagajo.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: migin (sample_hsm) returns EBADF too Date: Fri, 28 Sep 2001 19:39:34 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi there, I could migrate the file data using migout ( see previous my mail ), so try to stage the data in with linux-2.4-xfs/cmd/xfstests/dmapi/src/sample_hsm/migin daemon, but it returned EBADF too. # ./migout -l dmapi_log /migfs It seems that it closes a file descriptor for /dev/dmapi when starting up. Here is the patch, also it works for me :) --- migin.c 2001/03/07 22:43:23 1.2 +++ migin.c 2001/09/28 10:37:25 @@ -112,6 +112,13 @@ /* + * Turn ourselves into a daemon + */ + error = mk_daemon(logfile); + if (error) + exit(1); + + /* * Now we have our filesystem name and possibly a size threshold * to look for. Init the dmapi, and get a filesystem handle so * we can set up our events @@ -125,13 +132,6 @@ exit(1); } - /* - * Turn ourselves into a daemon - */ - error = mk_daemon(logfile); - if (error) - exit(1); - /* * Set the event disposition so that our session will receive cheers, Takayuki From owner-linux-xfs@oss.sgi.com Fri Sep 28 03:51:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SApnn07977 for linux-xfs-outgoing; Fri, 28 Sep 2001 03:51:49 -0700 Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SApkD07957 for ; Fri, 28 Sep 2001 03:51:46 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.193]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8SApiQ07519 for ; Fri, 28 Sep 2001 19:51:44 +0900 (JST) Received: from mailsv.nec.co.jp (mailgate51.nec.co.jp [10.7.69.196]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8SApbI10864 for ; Fri, 28 Sep 2001 19:51:42 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv.nec.co.jp (8.11.6/3.7W-MAILSV-NEC) with ESMTP id f8SApZl19265 for ; Fri, 28 Sep 2001 19:51:36 +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 AAA363 for ; Fri, 28 Sep 2001 19:51:33 +0900 Received: FROM noshiro.bsd.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Fri Sep 28 19:51:32 2001 +0900 Received: from localhost (localhost [127.0.0.1]) by noshiro.bsd.tnes.nec.co.jp (Postfix) with ESMTP id 3F128660C for ; Fri, 28 Sep 2001 19:51:32 +0900 (JST) To: linux-xfs@oss.sgi.com Subject: XFS recovery X-Mailer: Mew version 1.94.2 on XEmacs 21.4 (Artificial Intelligence) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010928195132P.masano@tnes.nec.co.jp> Date: Fri, 28 Sep 2001 19:51:32 +0900 (JST) From: ASANO Masahiro X-Dispatcher: imput version 20000228(IM140) Lines: 25 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I encountered an accident; mounting a XFS filesystem caused log recovery with a message "Starting XFS recovery on filesystem..." in spite of it had been unmounted normally. With my hack :), it seems that mount process searches the `log head' from the out of range. Here is a patch for 20010928 CVS tree. --- linux/fs/xfs/xfs_log_recover.c.sv Thu Sep 27 11:19:58 2001 +++ linux/fs/xfs/xfs_log_recover.c Thu Sep 27 11:13:12 2001 @@ -310,6 +310,8 @@ buf = XFS_BUF_PTR(bp); for (j = 0; j < bufblks; j++) { + if (i + j >= start_blk + nbblks) + break; cycle = GET_CYCLE(buf, ARCH_CONVERT); if (cycle == stop_on_cycle_no) { error = i; -- masano From owner-linux-xfs@oss.sgi.com Fri Sep 28 04:01:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SB1xT08366 for linux-xfs-outgoing; Fri, 28 Sep 2001 04:01:59 -0700 Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SB1uD08346 for ; Fri, 28 Sep 2001 04:01:57 -0700 Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 15mvP0-000BYX-0C for linux-xfs@oss.sgi.com; Fri, 28 Sep 2001 11:01:54 +0000 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id 0D49F27EF for ; Fri, 28 Sep 2001 09:20:25 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id 21126125E6; Fri, 28 Sep 2001 09:17:44 +0100 (BST) Date: Fri, 28 Sep 2001 09:17:42 +0100 (BST) From: Keith Matthews Subject: XFS and OpenAFS (was Re[2]: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? ) To: linux-xfs@oss.sgi.com In-Reply-To: <200109271535.f8RFZf908442@jen.americas.sgi.com> References: <200109271535.f8RFZf908442@jen.americas.sgi.com> X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010928081744.21126125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f8SB1vD08347 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 27 Sep 2001 10:35:41 -0500 Steve Lord > wrote: > Another filesystem - which is available for Irix, but not Linux yet is CXFS, > this is a layer on top of XFS which does coherency and allows direct disk > access for file data. This will also not be GPLed and will cost money. > Your only other options are things like NFS, AFS etc. On which subject, has anyone got OpenAFS to work reliably with XFS yet ? -- Keith Matthews Spam trap - my real account at this node is keith_m Frequentous Consultants - Linux Services, Oracle development & database administration From owner-linux-xfs@oss.sgi.com Fri Sep 28 04:19:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SBJSA08923 for linux-xfs-outgoing; Fri, 28 Sep 2001 04:19:28 -0700 Received: from zeta.qmw.ac.uk (zeta.qmw.ac.uk [138.37.6.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SBJMD08904 for ; Fri, 28 Sep 2001 04:19:23 -0700 Received: from heppcl.ph.qmw.ac.uk ([138.37.50.187]) by zeta.qmw.ac.uk with esmtp (Exim 3.32 #1) id 15mvev-0003Kk-00; Fri, 28 Sep 2001 12:18:21 +0100 Received: from heppct.ph.qmw.ac.uk (heppct.ph.qmw.ac.uk [138.37.50.246]) by heppcl.ph.qmw.ac.uk (8.9.3/8.9.3) with ESMTP id MAA25294; Fri, 28 Sep 2001 12:18:22 +0100 Received: from localhost (pd@localhost) by heppct.ph.qmw.ac.uk (8.11.2/8.9.3) with ESMTP id f8SBIMQ19715; Fri, 28 Sep 2001 12:18:22 +0100 X-Authentication-Warning: heppct.ph.qmw.ac.uk: pd owned process doing -bs Date: Fri, 28 Sep 2001 12:18:22 +0100 (BST) From: "P.Dixon" To: Keith Matthews cc: Subject: Re: XFS and OpenAFS (was Re[2]: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? ) In-Reply-To: <20010928081744.21126125E6@rebutia.sweeney.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On which subject, has anyone got OpenAFS to work reliably with XFS yet ? > Yes - both smp and single CPU versions - although I had to build it myself from the openafs-kernel-source RPM and the openafs src rpm. btw, I am using kernel 2.4.5-SGI_XFS_1.0.1. basically, install the XFS kernel source, install the openafs kernel source and src RPM and then cd /usr/src/redhat/SPECS, edit openafs-1.0.4.spec and set the kernel version to 24: %define kernvers 24 Then run rpm -ba openafs-1.0.4.spec - RPMs should then appear in /usr/src/redhat/RPMS/... (I also had to fudge the directory name of the XFS kernel source in /usr/src to match the kernel name given by uname -a). # ls /usr/src lrwxr-xr-x 1 Jul 25 12:42 linux -> linux-2.4 lrwxr-xr-x 1 Jul 12 11:49 linux-2.4 -> linux-2.4.5-SGI_XFS_1.0.1 drwxr-xr-x 3 Jul 12 11:03 openafs-kernel-1.0.4/ drwxr-xr-x 7 May 3 11:33 redhat/ So far, openafs-1.0.4a-22 has been the version of choice - earlier and later versions just hung the system (on ext2 systems also). So my advice would be to avoid them. Because of odd naming conventions in the built kernel modules, I had to do the following after installing: cd /usr/vice/etc/modload ln -sf libafs-2.4.5-SGI_XFS_1.0.1.mp.o libafs-2.4.5-SGI_XFS_1.0.1smp.mp.o I also reccomend patching the init script: cd /etc/init.d patch -N -b /etc/init.d/afs < /usr/vice/etc/afsd -shutdown EOF Hope this helps, Paul From owner-linux-xfs@oss.sgi.com Fri Sep 28 04:26:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SBQY409138 for linux-xfs-outgoing; Fri, 28 Sep 2001 04:26:34 -0700 Received: from TYO201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.214]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SBQTD09119 for ; Fri, 28 Sep 2001 04:26:29 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.197]) by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f8SBQMa25570 for ; Fri, 28 Sep 2001 20:26:23 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.196]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f8SBQMZ06275 for ; Fri, 28 Sep 2001 20:26:22 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id f8SBQLF27294 for ; Fri, 28 Sep 2001 20:26:21 +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 AAA484 for ; Fri, 28 Sep 2001 20:26:19 +0900 Received: FROM mailsv.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Fri Sep 28 20:26:18 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by mailsv.tnes.nec.co.jp (8.9.3/3.7W01031510) with ESMTP id UAA36854 for ; Fri, 28 Sep 2001 20:26:18 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f8SBQIi09161 for ; Fri, 28 Sep 2001 20:26:18 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id UAA22550; Fri, 28 Sep 2001 20:26:17 +0900 (JST) Message-Id: <200109281126.UAA22550@tagajo.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: wbee (sample_hsm) dumped core Date: Fri, 28 Sep 2001 20:26:17 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, migin daemon in sample_hsm started with the patch which I posted, but if I try to read the migrated file then it stalled. It was caused by linux-2.4-xfs/cmd/xfstests/dmapi/src/sample_hsm/wbee which was dispatched by migin dumped core. I looked into wbee.c and found that handling a pointer is wrong. Here is the patch. --- wbee.c 2001/03/07 22:43:23 1.2 +++ wbee.c 2001/09/28 11:05:02 @@ -453,7 +453,7 @@ size_t hlen, dm_token_t token) { - dm_region_t *rgn; + dm_region_t *rgn, *sv_rgn; u_int nregions, nret; u_int exact_flag; int i; @@ -502,6 +502,8 @@ } } + sv_rgn = rgn; + /* * Clear all the managed regions */ @@ -511,6 +513,8 @@ rgn->rg_flags = DM_REGION_NOEVENT; rgn++; } + rgn = sv_rgn; + error = dm_set_region(sid, hanp, hlen, token, nregions, rgn, &exact_flag); if (error == -1) { And, finally, I should like to report that I could migrate / recall the file data on the XFS filesystem using sample_hsm tools with these 3 patches. Cheers, Takayuki From owner-linux-xfs@oss.sgi.com Fri Sep 28 04:28:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SBSkZ09285 for linux-xfs-outgoing; Fri, 28 Sep 2001 04:28:46 -0700 Received: from ns.caldera.de (ns.caldera.de [212.34.180.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SBSgD09266 for ; Fri, 28 Sep 2001 04:28:43 -0700 Received: (from hch@localhost) by ns.caldera.de (8.11.1/8.11.1) id f8SBRqq29723; Fri, 28 Sep 2001 13:27:52 +0200 Date: Fri, 28 Sep 2001 13:27:52 +0200 From: Christoph Hellwig To: Steve Lord Cc: Sebastian Kun , shyberts@plato.med.harvard.edu, linux-xfs@oss.sgi.com Subject: Re: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? Message-ID: <20010928132752.A29429@caldera.de> References: <200109271535.f8RFZf908442@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: <200109271535.f8RFZf908442@jen.americas.sgi.com>; from lord@sgi.com on Thu, Sep 27, 2001 at 10:35:41AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Sep 27, 2001 at 10:35:41AM -0500, Steve Lord wrote: > GFS is one filesystem which is capable of this - it is a complete filesystem, > not a layer which sits on top of another filesystem. It does cache coherency > by locking regions of the disk using a semaphore device (can be a software > device). GFS was initially developed on Irix, but I am pretty sure the latest > stuff is linux only - they also just removed it from under the GPL. We, the OpenGFS group (http://www.opengfs.org) are working on OpenGFS which is a free fork of GFS. Currently we are working on OpenGFS 0.1 which is GFS 4.1 minus the truckload of bugs Sistina has in it's code base. After that OpenGFS will diverged more, but trying to stay ondisk and - if possible - protocol compatible to GFS 4.x Christoph -- Of course it doesn't work. We've performed a software upgrade. From owner-linux-xfs@oss.sgi.com Fri Sep 28 06:42:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SDgrs11660 for linux-xfs-outgoing; Fri, 28 Sep 2001 06:42:53 -0700 Received: from obelix.hrz.tu-chemnitz.de (obelix.hrz.tu-chemnitz.de [134.109.132.55]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SDgnD11640 for ; Fri, 28 Sep 2001 06:42:50 -0700 Received: from pat.hrz.tu-chemnitz.de ([134.109.132.143] ident=mail) by obelix.hrz.tu-chemnitz.de with esmtp (Exim 3.32 #1) id 15mxui-0004xf-00 for linux-xfs@oss.sgi.com; Fri, 28 Sep 2001 15:42:48 +0200 Received: from janus.hrz.tu-chemnitz.de ([134.109.132.79] ident=root) by pat.hrz.tu-chemnitz.de with esmtp (Exim 3.32 #2) id 15mxui-00035r-00 for linux-xfs@oss.sgi.com; Fri, 28 Sep 2001 15:42:48 +0200 Received: from hrz.tu-chemnitz.de (chrad@localhost.localdomain [127.0.0.1]) by janus.hrz.tu-chemnitz.de (8.9.3/8.9.3) with ESMTP id PAA24664 for ; Fri, 28 Sep 2001 15:42:48 +0200 Message-ID: <3BB47E57.4F936128@hrz.tu-chemnitz.de> Date: Fri, 28 Sep 2001 15:42:47 +0200 From: Charles Radeke X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.17-14smp i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: xfsdump/restore from cd Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi my problem is the following: I would like to backup a partition of some GB by burning cd's with splitted xfsdump , each is 650MB. Is it possible to use a cdrom-drive as a tape (like/dev/rmt)? and if, how to simulate the tape change? I saw that is not possible to xfsrestore splitted dumps step by step, only the first succseeded (what is clear to me). I wont copy 7 cd's on an empty drive bevor I can do cat | xfsrestore - / Or ist there another solution in general for my problem? I saw that the -d option is not available for xfsdump like at IRIX-xfsdump where I can set the size of the media. tnk for help c. radeke From owner-linux-xfs@oss.sgi.com Fri Sep 28 06:52:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SDq7U12074 for linux-xfs-outgoing; Fri, 28 Sep 2001 06:52:07 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SDptD12055 for ; Fri, 28 Sep 2001 06:51:55 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id GAB09885 for ; Fri, 28 Sep 2001 06:51:39 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2958153; Fri, 28 Sep 2001 08:50:23 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA74136; Fri, 28 Sep 2001 08:50:22 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8SDoAS19975; Fri, 28 Sep 2001 08:50:10 -0500 Message-Id: <200109281350.f8SDoAS19975@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: ASANO Masahiro cc: linux-xfs@oss.sgi.com Subject: Re: XFS recovery In-Reply-To: Message from ASANO Masahiro of "Fri, 28 Sep 2001 19:51:32 +0900." <20010928195132P.masano@tnes.nec.co.jp> Date: Fri, 28 Sep 2001 08:50:10 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thanks, This code was changed in the linux port - to avoid a case where we needed 256K of memory in one chunk. Looks like there was a hole in the new logic to me. I will incorporate a different fix - since we are also reading blocks of the end of the log in this case. Steve > Hi, > > I encountered an accident; mounting a XFS filesystem caused log > recovery with a message "Starting XFS recovery on filesystem..." > in spite of it had been unmounted normally. > > With my hack :), it seems that mount process searches the `log head' > from the out of range. > > Here is a patch for 20010928 CVS tree. > > --- linux/fs/xfs/xfs_log_recover.c.sv Thu Sep 27 11:19:58 2001 > +++ linux/fs/xfs/xfs_log_recover.c Thu Sep 27 11:13:12 2001 > @@ -310,6 +310,8 @@ > > buf = XFS_BUF_PTR(bp); > for (j = 0; j < bufblks; j++) { > + if (i + j >= start_blk + nbblks) > + break; > cycle = GET_CYCLE(buf, ARCH_CONVERT); > if (cycle == stop_on_cycle_no) { > error = i; > > -- > masano From owner-linux-xfs@oss.sgi.com Fri Sep 28 07:19:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SEJtr12928 for linux-xfs-outgoing; Fri, 28 Sep 2001 07:19:55 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SEJnD12907 for ; Fri, 28 Sep 2001 07:19:49 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id HAA07112 for ; Fri, 28 Sep 2001 07:18:38 -0700 (PDT) mail_from (roehrich@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA3089753; Fri, 28 Sep 2001 09:18:32 -0500 (CDT) Received: from slobber.americas.sgi.com (slobber.americas.sgi.com [128.162.187.52]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA53047; Fri, 28 Sep 2001 09:18:32 -0500 (CDT) Received: from slobber.americas.sgi.com by slobber.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) via ESMTP id JAA21550; Fri, 28 Sep 2001 09:18:31 -0500 (CDT) Message-Id: <200109281418.JAA21550@slobber.americas.sgi.com> To: Takayuki Sasaki cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.10-xfs with dmapi option panic Date: Fri, 28 Sep 2001 09:18:31 -0500 From: Dean Roehrich Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk A few weeks ago fs/super.c underwent a major reorganization. As a result, the DMAPI mount code was broken. I was wondering how long we'd go before someone noticed it :) I'll try to get to it next week. Dean >From: Takayuki Sasaki >Hi there, > >While testing the XFS filesystem with dmapi option, >I encountered panic with the following operations: > ># mkfs.xfs /dev/foo ># mount -t xfs -o dmapi /dev/foo /mnt/foo ># umount /mnt/foo > >kernel panic: dm_change_fsys_entry: can't find DMAPI fsrp for vfsp c6965860 > >backtrace process using KDB is: > schedule+0x520 (0xc048fa40,0x0,0x0,0xc0382580) > notifier_caller_chain+0x23(0xc0508da0,0x0,0x0,0x0) > panic+0x87 (0xc0382580,0xc303e65c,0xc303e584) > dm_change_fsys_entry+0x30 (0xc303e65c) > dm_send_namesp_event+0x60 (0x2, 0xc1b26260,0x0,0xc1b26260,0x0) > xfs_unmount+0x74 (0xc1248400,0x0,0xc05132c0) > fs_dounmount+0x59 > linvfs_put_super+0x36 > kill_super+0x14d > __mntput+0x39 > path_release+0x2a > sys_umount+0x194 > sys_oldumount+0xe > system_call+0x33 > >Kernel: linux-2.4.10-xfs (20010925 CVS Tree) >gcc: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) >Box: Pentium III (Coppermine) 733MHz + SiS 630 chip set + 128MB RAM > >This is not critical issue so far for me, however, I couldn't >find same errors in the archive, so report to the list. > >Cheers, > >Takayuki > From owner-linux-xfs@oss.sgi.com Fri Sep 28 07:33:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SEXr713291 for linux-xfs-outgoing; Fri, 28 Sep 2001 07:33:53 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SEXnD13272 for ; Fri, 28 Sep 2001 07:33:50 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8SEXgL11822 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Fri, 28 Sep 2001 07:33:42 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA1327183 for ; Fri, 28 Sep 2001 16:33:39 +0200 (CEST) mail_from (roehrich@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA3090032; Fri, 28 Sep 2001 09:32:22 -0500 (CDT) Received: from slobber.americas.sgi.com (slobber.americas.sgi.com [128.162.187.52]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA95816; Fri, 28 Sep 2001 09:32:22 -0500 (CDT) Received: from slobber.americas.sgi.com by slobber.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) via ESMTP id JAA24904; Fri, 28 Sep 2001 09:32:21 -0500 (CDT) Message-Id: <200109281432.JAA24904@slobber.americas.sgi.com> To: Takayuki Sasaki cc: linux-xfs@oss.sgi.com Subject: Re: wbee (sample_hsm) dumped core Date: Fri, 28 Sep 2001 09:32:21 -0500 From: Dean Roehrich Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >From: Takayuki Sasaki >And, finally, I should like to report that I could migrate / >recall the file data on the XFS filesystem using sample_hsm >tools with these 3 patches. Great. I'll put these into the tree. Some history on these: The sample_hsm stuff is probably the granddaddy of all the dmapi tests. I inherited these and nobody I know has ever used them, let alone worried about whether or not they worked (even on Irix). They were deemed as having no value and it was suggested that I throw them out (then why did they exist long enough for me to inherit them?). Anyway, I decided to keep them, thinking that maybe one day they'd be dusted off and given a tune-up. Note that the test tool 'print_event' exists in two places in the test tree. The version in sample_hsm is _not_ the one I use, and I really haven't looked at why they are different, or whether sample_hsm/print_event would even work. At this moment, you are the expert on the sample_hsm stuff (congrats), so tell me what you think: should we just remove sample_hsm/print_event and rely on the other print_event? Thanks, Dean From owner-linux-xfs@oss.sgi.com Fri Sep 28 07:58:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SEwGI14024 for linux-xfs-outgoing; Fri, 28 Sep 2001 07:58:16 -0700 Received: from zeta.qmw.ac.uk (zeta.qmw.ac.uk [138.37.6.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SEwDD14005 for ; Fri, 28 Sep 2001 07:58:13 -0700 Received: from heppcl.ph.qmw.ac.uk ([138.37.50.187]) by zeta.qmw.ac.uk with esmtp (Exim 3.32 #1) id 15mz5f-00061S-00 for linux-xfs@oss.sgi.com; Fri, 28 Sep 2001 15:58:11 +0100 Received: from heppct.ph.qmw.ac.uk (heppct.ph.qmw.ac.uk [138.37.50.246]) by heppcl.ph.qmw.ac.uk (8.9.3/8.9.3) with ESMTP id PAA28109 for ; Fri, 28 Sep 2001 15:58:12 +0100 Received: from localhost (pd@localhost) by heppct.ph.qmw.ac.uk (8.11.2/8.9.3) with ESMTP id f8SEwCx25135 for ; Fri, 28 Sep 2001 15:58:12 +0100 X-Authentication-Warning: heppct.ph.qmw.ac.uk: pd owned process doing -bs Date: Fri, 28 Sep 2001 15:58:12 +0100 (BST) From: "P.Dixon" To: Subject: AFS RPMS for 2.4.5-SGI_XFS_1.0.1 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I've put my openafs RPMs here: http://hepwww.ph.qmw.ac.uk/~pd/rpms/ Cheerio, Paul ------------------------------------------------------------------------------- Paul Dixon Email: P.Dixon@qmw.ac.uk Department of Physics Phone: (020) 7882 5054 Queen Mary, University of London Fax : (020) 7882 5054 Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd ------------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Fri Sep 28 09:08:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SG8js15555 for linux-xfs-outgoing; Fri, 28 Sep 2001 09:08:45 -0700 Received: from public.tpt.tj.cn ([202.99.64.80]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SG8XD15535 for ; Fri, 28 Sep 2001 09:08:36 -0700 Date: Fri, 28 Sep 2001 09:08:36 -0700 Message-Id: <200109281608.f8SG8XD15535@oss.sgi.com> Received: from qgqg.net([205.133.156.67]) by (AIMC 2.9.5.1) with SMTP id jmf73bb4bb71; Sat, 29 Sep 2001 00:00:28 +0800 From: To: Subject: $0.00/min Long Distance MIME-Version: 1.0 Content-Type: multipart/mixed;boundary= "----=_NextPart_000_00ED_B82AC9C8.C01CBC6D" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk ------=_NextPart_000_00ED_B82AC9C8.C01CBC6D Content-Type: text/html Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMC8vRU4iPg0KPCEt LSBzYXZlZCBmcm9tIHVybD0oMDAyMilodHRwOi8vaW50ZXJuZXQuZS1tYWlsIC0tPg0KPGh0 bWw+DQo8aGVhZD4NCjx0aXRsZT5GbGF0IFJhdGUgTG9uZyBEaXN0YW5jZTwvdGl0bGU+DQo8 bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hh cnNldD1pc28tODg1OS0xIj4NCjxNRVRBIG5hbWU9IkdFTkVSQVRPUiIgY29udGVudD0iSUJN IE5ldE9iamVjdHMgVG9wUGFnZSBWNC4wLjMgIGZvciBXaW5kb3dzIj4NCjwvaGVhZD4NCjxC T0RZIGJnY29sb3I9IiMwMDAwMDAiIHRleHQ9IiNmZmZmZmYiPg0KPFRBQkxFIHdpZHRoPSI1 MDAiIGJvcmRlcj0iMCIgY2VsbHNwYWNpbmc9IjAiIGNlbGxwYWRkaW5nPSIwIiBhbGlnbj0i bGVmdCIgYmdjb2xvcj0iI2ZmZmZmZiI+DQogIA0KICAgIDxUUiBiZ2NvbG9yPSIjZmZmZjgw Ij4NCiAgICAgIDxURCBoZWlnaHQ9IjEyMyIgd2lkdGg9IjUwMSI+PGRpdiBhbGlnbj0iY2Vu dGVyIj48Rk9OVCBzaXplPSIzIiBmYWNlPSJBcmlhbCwgSGVsdmV0aWNhLCBzYW5zLXNlcmlm IiBjb2xvcj0iIzAwMDAwMCI+PEI+PEZPTlQgc2l6ZT0iNSI+VW5saW1pdGVkIExvbmcgRGlz dGFuY2U8YnI+DQogICAgICA8L0ZPTlQ+PEZPTlQgc2l6ZT0iNCI+DQogICAgICAkMzkuOTUg cGVyIG1vbnRoPC9mb250PjxGT05UIHNpemU9IjUiPjxCUj4NCiAgICAgIDwvRk9OVD48L0I+ PEZPTlQgY29sb3I9IiNmZjAwMDAiPjxCPjxGT05UIHNpemU9IjUiPg0KICAgICAgPEZPTlQg c2l6ZT0iMyI+T05FIEZFRSwgT05DRSBBIE1PTlRIPGJyPg0KICAgICAgTk8gTU9SRSBPVVRS QUdFT1VTIFBIT05FIEJJTExTPC9mb250PjwvRk9OVD48L0I+PC9GT05UPjwvRk9OVD48QlI+ DQogICAgICA8Rk9OVCBjb2xvcj0iIzAwMDAwMCI+PEI+PEJSPg0KICAgICAgPEZPTlQgZmFj ZT0iQXJpYWwiPg0KICAgICAgSXQncyB5b3VyIE1vbmV5IFlvdSBDaG9vc2UhPC9GT05UPjwv Qj48L0ZPTlQ+PC9kaXY+DQogICAgPC90ZD4NCiAgICA8L3RyPg0KICAgIDx0cj4gDQogICAg PHRkIGhlaWdodD0iMjIiPg0KICAgICAgPERJViBhbGlnbj0iY2VudGVyIiBzdHlsZT0idG9w IDogMTM5cHg7bGVmdCA6IDEwcHg7Ij4gPGZvbnQgY29sb3I9IiMwMDAwOTkiIGZhY2U9IkFy aWFsLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWYiPjxicj4NCiAgICAgICAgUmVzaWRlbnRpYWwg YW5kIEJ1c2luZXNzIEZsYXQgUmF0ZSBMb25nIERpc3RhbmNlIC08Yj4gPGZvbnQgY29sb3I9 IiM5OTAwMDAiPk9ORSANCiAgICAgICAgTU9OVEhMWSBGRUU8L2ZvbnQ+PC9iPjxCPiA8L0I+ c3RhcnRpbmcgYXQ8Qj4gPGZvbnQgY29sb3I9IiM5OTAwMDAiPiQzOS45NTwvZm9udD48L0I+ PC9mb250PiANCiAgICAgICAgPEJSPg0KICAgICAgPHA+PEZPTlQgZmFjZT0iQXJpYWwsIEhl bHZldGljYSwgc2Fucy1zZXJpZiIgc2l6ZT0iMiIgY29sb3I9IiMwMDAwMDAiPjxCPklmIHdv dWxkIGxpa2UgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIGZpbGwNCiAgICAgIG91dCB0aGUg Zm9sbG93aW5nIGZvcm0gYW5kIGEgcmVwcmVzZW50YXRpdmUNCiAgICAgIHdpbGwgdGVsbCB5 b3UgYWxsIGFib3V0IGl0LjwvQj48L0ZPTlQ+PC9wPg0KICAgICAgICA8cD48Rk9OVCBmYWNl PSJBcmlhbCwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmIiBzaXplPSIyIiBjb2xvcj0iIzAwMDAw MCI+PGI+Tm8gaGFzc2xlcy4gTm8gDQogICAgICAgICAgaGFyZCBzZWxsIHRhY3RpY3MuIEp1 c3QgdGhlIGZhY3RzITwvYj48L2ZvbnQ+PC9wPg0KICAgICAgPC9kaXY+DQogICAgICA8L3Rk Pg0KICA8L3RyPg0KICA8dHI+IA0KICAgIDx0ZD4gDQogICAgICA8Zm9ybSBtZXRob2Q9InBv c3QiIGVuY1R5cGU9dGV4dC9wbGFpbg0KYWN0aW9uPSJtYWlsdG86cmV2ZWFsc3lzQGV4Y2l0 ZS5jb20/c3ViamVjdD1GbGF0IFJhdGUgTG9uZyBEaXN0YW5jZSBJbnF1aXJ5Ij4NCiAgICAg ICAgPHRhYmxlIHdpZHRoPSI1MDAiIGJvcmRlcj0iMCIgY2VsbHNwYWNpbmc9IjAiIGNlbGxw YWRkaW5nPSIzIj4NCiAgICAgICAgICA8dHI+IA0KICAgICAgICAgICAgPHRkIHdpZHRoPSI1 MCUiPjxGT05UIGZhY2U9IkFyaWFsLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWYiIHNpemU9IjIi IGNvbG9yPSIjMDAwMDAwIj5OYW1lOjwvZm9udD48L3RkPg0KICAgICAgICAgICAgPHRkPjxG T05UIGZhY2U9IkFyaWFsLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWYiIHNpemU9IjIiIGNvbG9y PSIjMDAwMDAwIj4gDQogICAgICAgICAgICAgIDxpbnB1dCB0eXBlPSJ0ZXh0IiBuYW1lPSJu YW1lIj4NCiAgICAgICAgICAgICAgPC9mb250PjwvdGQ+DQogICAgICAgICAgPC90cj4NCiAg ICAgICAgICA8dHI+IA0KICAgICAgICAgICAgPHRkIHdpZHRoPSI1MCUiPjxGT05UIGZhY2U9 IkFyaWFsLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWYiIHNpemU9IjIiIGNvbG9yPSIjMDAwMDAw Ij5QaG9uZSANCiAgICAgICAgICAgICAgTnVtYmVyOjwvZm9udD48L3RkPg0KICAgICAgICAg ICAgPHRkPjxGT05UIGZhY2U9IkFyaWFsLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWYiIHNpemU9 IjIiIGNvbG9yPSIjMDAwMDAwIj4NCiAgICAgICAgICAgICAgPGlucHV0IHR5cGU9InRleHQi IG5hbWU9InBob25lIj4NCiAgICAgICAgICAgICAgPC9mb250PjwvdGQ+DQogICAgICAgICAg PC90cj4NCiAgICAgICAgICA8dHI+IA0KICAgICAgICAgICAgPHRkIHdpZHRoPSI1MCUiPjxG T05UIGZhY2U9IkFyaWFsLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWYiIHNpemU9IjIiIGNvbG9y PSIjMDAwMDAwIj5FbWFpbCANCiAgICAgICAgICAgICAgQWRkcmVzczo8L2ZvbnQ+PC90ZD4N CiAgICAgICAgICAgIDx0ZD48Rk9OVCBmYWNlPSJBcmlhbCwgSGVsdmV0aWNhLCBzYW5zLXNl cmlmIiBzaXplPSIyIiBjb2xvcj0iIzAwMDAwMCI+DQogICAgICAgICAgICAgIDxpbnB1dCB0 eXBlPSJ0ZXh0IiBuYW1lPSJlbWFpbCI+DQogICAgICAgICAgICAgIDwvZm9udD48L3RkPg0K ICAgICAgICAgIDwvdHI+DQogICAgICAgICAgPHRyPiANCiAgICAgICAgICAgIDx0ZCB3aWR0 aD0iNTAlIj48Rk9OVCBmYWNlPSJBcmlhbCwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmIiBzaXpl PSIyIiBjb2xvcj0iIzAwMDAwMCI+QmVzdCANCiAgICAgICAgICAgICAgVGltZSB0byBDb250 YWN0OjwvZm9udD48L3RkPg0KICAgICAgICAgICAgPHRkPjxGT05UIGZhY2U9IkFyaWFsLCBI ZWx2ZXRpY2EsIHNhbnMtc2VyaWYiIHNpemU9IjIiIGNvbG9yPSIjMDAwMDAwIj4NCiAgICAg ICAgICAgICAgPGlucHV0IHR5cGU9InRleHQiIG5hbWU9ImJlc3R0aW1lIj4NCiAgICAgICAg ICAgICAgPC9mb250PjwvdGQ+DQogICAgICAgICAgPC90cj4NCiAgICAgICAgICA8dHI+DQog ICAgICAgICAgICA8VEQgY29sc3Bhbj0iMiIgaGVpZ2h0PSI0NSIgYWxpZ249ImNlbnRlciI+ IA0KICAgICAgICAgICAgICA8ZGl2IGFsaWduPSJjZW50ZXIiPjxGT05UIGZhY2U9IkFyaWFs LCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWYiIHNpemU9IjIiIGNvbG9yPSIjMDAwMDAwIj4NCiAg ICAgICAgICAgICAgICA8aW5wdXQgdHlwZT0ic3VibWl0IiBuYW1lPSJTdWJtaXQiIHZhbHVl PSJTdWJtaXQiPg0KICAgICAgICAgICAgICAgIDwvZm9udD48L2Rpdj4NCiAgICAgICAgICAg IDxCUj4NCiAgICAgICAgICAgIDxGT05UIGZhY2U9IkFyaWFsIiBjb2xvcj0iIzAwMDAwMCI+ DQogICAgICAgICAgICBZb3Ugd2lsbCBzYXZlIGh1bmRyZWRzIG9yIGV2ZW4NCiAgICAgICAg ICAgIHRob3VzYW5kcw0KICAgICAgICAgICAgb2YgZG9sbGFycyBlYWNoIHllYXIhIEhvbWUg YW5kDQogICAgICAgICAgICBzbWFsbCBidXNpbmVzcw0KICAgICAgICAgICAgcGxhbnMgYXJl IGhlcmUhPC9GT05UPjxCUj4NCiAgICAgICAgICAgIDxCUj4NCiAgICAgICAgICAgIDxGT05U IGNvbG9yPSIjZmYwMDAwIiBmYWNlPSJBcmlhbCI+SGF2ZSBhIGNvbXBhbnkgd2l0aCBhIGxh cmdlIHBob25lIGJpbGw/IElmDQogICAgICAgICAgICB0aGUgYW5zd2VyIGlzIHllcywgd2Ug YXNrIFdoeT88L0ZPTlQ+PC90ZD4NCiAgICAgICAgICA8L3RyPg0KICAgICAgICA8L3RhYmxl Pg0KICAgICAgPC9mb3JtPg0KICAgIDwvdGQ+DQogIDwvdHI+DQogIDx0cj4NCiAgICAgIDxU RCB3aWR0aD0iNTAwIiBoZWlnaHQ9Ijg4Ij4NCiAgICAgIDxkaXYgYWxpZ249ImNlbnRlciI+ DQogICAgICAgIDxwPjxGT05UIGNvbG9yPSIjMDAwMDAwIj4mbmJzcDs8L0ZPTlQ+PC9wPg0K ICAgICAgICA8cD48Rk9OVCBmYWNlPSJBcmlhbCwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmIiBz aXplPSIyIiBjb2xvcj0iIzAwMDAwMCI+SWYgeW91IHdvdWxkIGxpa2UgDQogICAgICAgICAg dG8gYmUgcmVtb3ZlZCBmcm9tIG91ciBsaXN0LCBwbGVhc2Ugc2VuZCBhbiBlbWFpbCB0byA8 YSBocmVmPSJtYWlsdG86Y2Vhc2VmaXJlMDIxQG1haWwuY29tICI+cnBmbGF0cmF0ZWxvbmdk aXN0bm93QGV4Y2l0ZS5jb20uPC9hPiANCiAgICAgICAgICA8L2ZvbnQ+PC9wPg0KICAgICAg PC9kaXY+DQogICAgPC90ZD4NCiAgICA8L3RyPg0KPC90YWJsZT4NCjwvYm9keT4NCjwvaHRt bD4NCiAgICANCiAgICA= ------=_NextPart_000_00ED_B82AC9C8.C01CBC6D-- From owner-linux-xfs@oss.sgi.com Fri Sep 28 09:57:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SGvxE16381 for linux-xfs-outgoing; Fri, 28 Sep 2001 09:57:59 -0700 Received: from ns1.ltc.com (ns1.ltc.com [38.149.17.165]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SGvuD16359 for ; Fri, 28 Sep 2001 09:57:56 -0700 Received: from prefect (gw1.ltc.com [38.149.17.163]) by ns1.ltc.com (Postfix) with SMTP id 98B85590A9 for ; Fri, 28 Sep 2001 08:57:02 -0400 (EDT) Message-ID: <003201c1483e$b788e9a0$3501010a@ltc.com> From: "Bradley D. LaRonde" To: Subject: cvsweb instructions appear to be borked Date: Fri, 28 Sep 2001 12:57:54 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seems like a bad link on: http://oss.sgi.com/projects/xfs/cvsup.html Regards, Brad From owner-linux-xfs@oss.sgi.com Fri Sep 28 10:05:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SH5Mp16743 for linux-xfs-outgoing; Fri, 28 Sep 2001 10:05:22 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SH5JD16724 for ; Fri, 28 Sep 2001 10:05:19 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id KAA03616 for ; Fri, 28 Sep 2001 10:04:08 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA3096178; Fri, 28 Sep 2001 12:04:03 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id MAA53637; Fri, 28 Sep 2001 12:04:02 -0500 (CDT) Message-ID: <3BB4ACFE.59ED6759@sgi.com> Date: Fri, 28 Sep 2001 12:01:50 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.8-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: "Bradley D. LaRonde" CC: linux-xfs@oss.sgi.com Subject: Re: cvsweb instructions appear to be borked References: <003201c1483e$b788e9a0$3501010a@ltc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Bradley D. LaRonde" wrote: > > Seems like a bad link on: > > http://oss.sgi.com/projects/xfs/cvsup.html > > Regards, > Brad Yep, should link to: http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.4-xfs/ Fixed it; thanks! -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Sep 28 10:45:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SHjX217625 for linux-xfs-outgoing; Fri, 28 Sep 2001 10:45:33 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SHjUD17606 for ; Fri, 28 Sep 2001 10:45:30 -0700 Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f8SHjOL31551 for <@rj.corp.sgi.com:linux-xfs@oss.sgi.com>; Fri, 28 Sep 2001 10:45:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id TAA1383712 for ; Fri, 28 Sep 2001 19:45:21 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA3082605 for ; Fri, 28 Sep 2001 12:44:05 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA08907 for ; Fri, 28 Sep 2001 12:44:05 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id f8SHhqh21736; Fri, 28 Sep 2001 12:43:52 -0500 Message-Id: <200109281743.f8SHhqh21736@jen.americas.sgi.com> Date: Fri, 28 Sep 2001 12:43:52 -0500 Subject: TAKE - ensure log recovery does not look at data outside log Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thanks to ASANO Masahiro for finding the problem, I used a different fix than his suggestion, this version will avoid reading extra data off the disk, possibly off the end of a device if an external log is used. Date: Fri Sep 28 10:40:46 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103579a linux/fs/xfs/xfs_log_recover.c - 1.212 - Avoid scanning off the end of the log when looking for the head and tail. From owner-linux-xfs@oss.sgi.com Fri Sep 28 12:51:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SJpPU19762 for linux-xfs-outgoing; Fri, 28 Sep 2001 12:51:25 -0700 Received: from avqimail2.paq.av.com (avqimail2.corp.altavista.com [209.73.174.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SJpND19743 for ; Fri, 28 Sep 2001 12:51:23 -0700 Received: from LADAKH [10.28.4.17] by avqimail2.paq.av.com - SuperScout Email Filter ; Friday, 28 September 2001, 12:50:29 Received: from av.com (england.smo.av.com [10.6.5.128]) by smo.av.com (8.9.3/8.9.3) with ESMTP id MAA29284 for ; Fri, 28 Sep 2001 12:50:28 -0700 (PDT) Message-ID: <3BB4D484.3020806@av.com> Date: Fri, 28 Sep 2001 12:50:28 -0700 From: Jim Cistaro User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010915 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: recover file after cat /dev/null > file Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk if /dev/null has been catted over an existing file, is there any way to recover data based on inodes (or anything else)? Nothing else has been written to disk since so data should still exist. -- Jim Cistaro - jim.cistaro@av.com Senior Engineer - AltaVista Company w: 650-320-6340 c: 650-444-8385 From owner-linux-xfs@oss.sgi.com Fri Sep 28 12:56:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SJuC419957 for linux-xfs-outgoing; Fri, 28 Sep 2001 12:56:12 -0700 Received: from ente.berdmann.de (frnk-d514e121.dsl.mediaWays.net [213.20.225.33]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SJuAD19938 for ; Fri, 28 Sep 2001 12:56:11 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.22 #1) id 15n3jw-0005wU-00; Fri, 28 Sep 2001 21:56:04 +0200 Message-ID: <3BB4D5D4.9DC3F7D0@berdmann.de> Date: Fri, 28 Sep 2001 21:56:04 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.10-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Jim Cistaro CC: linux-xfs@oss.sgi.com Subject: Re: recover file after cat /dev/null > file References: <3BB4D484.3020806@av.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jim Cistaro wrote: > > if /dev/null has been catted over an existing file, > is there any way to recover data based on inodes (or anything else)? your backup tapes? From owner-linux-xfs@oss.sgi.com Fri Sep 28 13:06:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SK60k20286 for linux-xfs-outgoing; Fri, 28 Sep 2001 13:06:00 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SK5wD20264 for ; Fri, 28 Sep 2001 13:05:58 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id NAA08813 for ; Fri, 28 Sep 2001 13:04:46 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA3068567; Fri, 28 Sep 2001 15:04:41 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA90766; Fri, 28 Sep 2001 15:04:40 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.6/SGI-client-1.7) via ESMTP id f8SK4Q128211; Fri, 28 Sep 2001 15:04:26 -0500 Message-Id: <200109282004.f8SK4Q128211@jen.americas.sgi.com> To: Jim Cistaro cc: linux-xfs@oss.sgi.com Subject: Re: recover file after cat /dev/null > file References: <3BB4D484.3020806@av.com> Comments: In-reply-to Jim Cistaro message dated "Fri, 28 Sep 2001 12:50:28 -0700." Date: Fri, 28 Sep 2001 15:04:26 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > if /dev/null has been catted over an existing file, > is there any way to recover data based on inodes (or anything else)? > > Nothing else has been written to disk since so data should still exist. > Yes, but the tricky part is where. You overwrote the inode and freed it's extents, the data is somewhere in the freespace on the filesystem, but locating it is not going to be easy. Unless the file was very large, or the filesystem fairly full, the chances are the data is located in the same allocation group as the inode, but really I cannot tell you more than that. Sorry Steve From owner-linux-xfs@oss.sgi.com Fri Sep 28 13:15:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SKFFr20639 for linux-xfs-outgoing; Fri, 28 Sep 2001 13:15:15 -0700 Received: from avqimail2.paq.av.com (avqimail2.corp.altavista.com [209.73.174.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SKFBD20620 for ; Fri, 28 Sep 2001 13:15:11 -0700 Received: from LADAKH [10.28.4.17] by avqimail2.paq.av.com - SuperScout Email Filter ; Friday, 28 September 2001, 13:13:28 Received: from av.com (england.smo.av.com [10.6.5.128]) by smo.av.com (8.9.3/8.9.3) with ESMTP id NAA31050; Fri, 28 Sep 2001 13:13:28 -0700 (PDT) Message-ID: <3BB4D9E8.6030100@av.com> Date: Fri, 28 Sep 2001 13:13:28 -0700 From: Jim Cistaro User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010915 X-Accept-Language: en-us MIME-Version: 1.0 To: Steve Lord CC: linux-xfs@oss.sgi.com Subject: Re: recover file after cat /dev/null > file References: <3BB4D484.3020806@av.com> <200109282004.f8SK4Q128211@jen.americas.sgi.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The file is large ~8GB. By catting the partition I could determine the offset of the start of the data for the first inode. Would this help. Can you point me to any documention that might discuss this? Thanks, JIm --- Steve Lord wrote: >>if /dev/null has been catted over an existing file, >>is there any way to recover data based on inodes (or anything else)? >> >>Nothing else has been written to disk since so data should still exist. >> > >Yes, but the tricky part is where. You overwrote the inode and >freed it's extents, the data is somewhere in the freespace on >the filesystem, but locating it is not going to be easy. > >Unless the file was very large, or the filesystem fairly full, >the chances are the data is located in the same allocation >group as the inode, but really I cannot tell you more than >that. > >Sorry > > Steve > -- Jim Cistaro - jim.cistaro@av.com Senior Engineer - AltaVista Company w: 650-320-6340 c: 650-444-8385 From owner-linux-xfs@oss.sgi.com Fri Sep 28 13:44:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SKiwc21157 for linux-xfs-outgoing; Fri, 28 Sep 2001 13:44:58 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SKitD21138 for ; Fri, 28 Sep 2001 13:44:55 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id ; Fri, 28 Sep 2001 15:44:00 -0500 Message-ID: <85063BBE668FD411944400D0B744267A888604@AUSMAIL> From: "Gonyou, Austin" To: "'Bernhard R. Erdmann'" , Jim Cistaro Cc: linux-xfs@oss.sgi.com Subject: RE: recover file after cat /dev/null > file Date: Fri, 28 Sep 2001 15:43:59 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Agreed. If the fs_sync() has already occurred, and data , even zeros or null space, have replaced the original contents, I don't see how you could actually get "all" of the data back, but perhaps the part which hasn't been over-written, if the full extent of the contents weren't affected, could be intact. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Bernhard R. Erdmann [mailto:be@berdmann.de] > Sent: Friday, September 28, 2001 2:56 PM > To: Jim Cistaro > Cc: linux-xfs@oss.sgi.com > Subject: Re: recover file after cat /dev/null > file > > > Jim Cistaro wrote: > > > > if /dev/null has been catted over an existing file, > > is there any way to recover data based on inodes (or anything else)? > > your backup tapes? > From owner-linux-xfs@oss.sgi.com Fri Sep 28 13:59:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SKx0421492 for linux-xfs-outgoing; Fri, 28 Sep 2001 13:59:00 -0700 Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SKwvD21473 for ; Fri, 28 Sep 2001 13:58:57 -0700 Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 15n4id-000Kog-0B for linux-xfs@oss.sgi.com; Fri, 28 Sep 2001 20:58:53 +0000 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id A463227EF for ; Fri, 28 Sep 2001 21:57:49 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id 4F0C5125E6; Fri, 28 Sep 2001 21:57:49 +0100 (BST) Date: Fri, 28 Sep 2001 21:57:49 +0100 (BST) From: Keith Matthews Subject: Re[2]: recover file after cat /dev/null > file To: linux-xfs@oss.sgi.com In-Reply-To: <3BB4D9E8.6030100@av.com> References: <3BB4D484.3020806@av.com> <200109282004.f8SK4Q128211@jen.americas.sgi.com>, <3BB4D9E8.6030100@av.com> X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010928205749.4F0C5125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f8SKwwD21474 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 28 Sep 2001 13:13:28 -0700 Jim Cistaro > wrote: > The file is large ~8GB. > By catting the partition I could determine the offset of the start of > the data for the first inode. > Would this help. > Can you point me to any documention that might discuss this? You can do better than that. There are tools that will allow you to browse filsystems at a low level. I tried one and it did work on XFS (at a byte level so it should have). Have a hunt on freshmeat. -- Keith Matthews Spam trap - my real account at this node is keith_m Frequentous Consultants - Linux Services, Oracle development & database administration From owner-linux-xfs@oss.sgi.com Fri Sep 28 16:24:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8SNOXi24027 for linux-xfs-outgoing; Fri, 28 Sep 2001 16:24:33 -0700 Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8SNOUD24008 for ; Fri, 28 Sep 2001 16:24:30 -0700 Received: from scare ([63.231.179.33]) by lips.thebarn.com (8.12.0/8.12.0) with ESMTP id f8SNPWRP031999; Fri, 28 Sep 2001 18:25:38 -0500 (CDT) Subject: Re: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? From: Russell Cattelan To: Christoph Hellwig Cc: linux-xfs@oss.sgi.com In-Reply-To: <20010928132752.A29429@caldera.de> References: <200109271535.f8RFZf908442@jen.americas.sgi.com> <20010928132752.A29429@caldera.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 28 Sep 2001 18:28:07 -0500 Message-Id: <1001719696.2686.7.camel@scare> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 2001-09-28 at 06:27, Christoph Hellwig wrote: > On Thu, Sep 27, 2001 at 10:35:41AM -0500, Steve Lord wrote: > > GFS is one filesystem which is capable of this - it is a complete filesystem, > > not a layer which sits on top of another filesystem. It does cache coherency > > by locking regions of the disk using a semaphore device (can be a software > > device). GFS was initially developed on Irix, but I am pretty sure the latest > > stuff is linux only - they also just removed it from under the GPL. > > We, the OpenGFS group (http://www.opengfs.org) are working on OpenGFS which is > a free fork of GFS. Currently we are working on OpenGFS 0.1 which is GFS 4.1 > minus the truckload of bugs Sistina has in it's code base. Interesting ... I was under the impression the stuff is fairly stable? What kind of bugs did you find? > > After that OpenGFS will diverged more, but trying to stay ondisk and - if > possible - protocol compatible to GFS 4.x > > Christoph > From owner-linux-xfs@oss.sgi.com Fri Sep 28 18:37:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8T1bhM25876 for linux-xfs-outgoing; Fri, 28 Sep 2001 18:37:43 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8T1bYD25853 for ; Fri, 28 Sep 2001 18:37:34 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id SAA02279 for ; Fri, 28 Sep 2001 18:36:23 -0700 (PDT) mail_from (tbd@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id UAA3029162; Fri, 28 Sep 2001 20:36:17 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id UAA48711; Fri, 28 Sep 2001 20:36:16 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id UAA56955; Fri, 28 Sep 2001 20:36:15 -0500 (CDT) Message-Id: <200109290136.UAA56955@fsgi158.americas.sgi.com> Subject: Re: NFSD problems To: tufan@itu.edu.tr (=?iso-8859-9?Q?=DEeref_Tufan_=DEen?=) Date: Fri, 28 Sep 2001 20:36:14 -0500 (CDT) Cc: linux-xfs@oss.sgi.com In-Reply-To: <00a901c14803$7b623520$2c054ba0@aontws4044> from "=?iso-8859-9?Q?=DEeref_Tufan_=DEen?=" at Sep 28, 2001 12:53:52 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk We have an internal user who consistently had nfsd hangs with 2.4.3 and 2.4.5. The hangs went away after upgrading to 2.4.9. Tad > > I am using Linux Kernel 2.4.3 (smp) + XFS 1.0.1 (rpm from SGI). I have a NFS > server , and exported file systems are on XFS. The machine worked fine for > two days then stopped giving response to NFS requests. When I looked to > kernel logs I saw the first log below. All nfs daemons were at "DW" state so > I could not kill them.. I rebooted the server then after a few hours I got > the second log , and nfs stopped working again. Does anyone have an idea?? > > PS: Exported file system is on an Raidtech SAN device..I am using Qlogic > 2100 HBA for accessing the storage. And I use LVM (0.9.1 beta 6 I remember). > > ------------------------------------------------------------ > Sep 27 19:58:48 lnxsrv1 kernel: invalid operand: 0000 > Sep 27 19:58:48 lnxsrv1 kernel: CPU: 1 > Sep 27 19:58:48 lnxsrv1 kernel: EIP: 0010:[dput+20/364] > Sep 27 19:58:48 lnxsrv1 kernel: EIP: 0010:[] > Sep 27 19:58:48 lnxsrv1 kernel: EFLAGS: 00010246 > Sep 27 19:58:48 lnxsrv1 kernel: eax: 00000000 ebx: c63c0120 ecx: > c63c08a0 edx: 00000003 > Sep 27 19:58:48 lnxsrv1 kernel: esi: c63c0120 edi: c63c08a0 ebp: > c63c08a0 esp: cee75e78 > Sep 27 19:58:48 lnxsrv1 kernel: ds: 0018 es: 0018 ss: 0018 > Sep 27 19:58:48 lnxsrv1 kernel: Process nfsd (pid: 1135, stackpage=cee75000) > Sep 27 19:58:48 lnxsrv1 kernel: Stack: ffffffea c63c0120 d0a12005 c63c0120 > 00000003 1d55f8b1 d0a123c6 c63c08a0 > Sep 27 19:58:48 lnxsrv1 kernel: 00000003 c6292410 46000000 c6292400 > c1624e00 cf4949f8 cee75f38 ffffff8c > Sep 27 19:58:48 lnxsrv1 kernel: 00000000 d0a12754 cf494800 1d55f8b1 > 00000000 00000000 00000001 c6292400 > Sep 27 19:58:48 lnxsrv1 kernel: Call Trace: > [usbcore:usb_devfs_handle_Rsmp_e9c5f87f+1301797/256597015] > [usbcore:usb_devfs_handle_Rsmp_e9c5f87f$ > Sep 27 19:58:48 lnxsrv1 kernel: Call Trace: [] [] > [] [] [] > Sep 27 19:58:48 lnxsrv1 kernel: > [usbcore:usb_devfs_handle_Rsmp_e9c5f87f+1296956/256601856] > [usbcore:usb_devfs_handle_Rsmp_e9c5f87f+1358176/$ > Sep 27 19:58:48 lnxsrv1 kernel: [] [] [] > [] [] [] > Sep 27 19:58:48 lnxsrv1 kernel: > [usbcore:usb_devfs_handle_Rsmp_e9c5f87f+1357896/256540916] > [usbcore:usb_devfs_handle_Rsmp_e9c5f87f+1294441/$ > Sep 27 19:58:48 lnxsrv1 kernel: [] [] [] > Sep 27 19:58:48 lnxsrv1 kernel: > Sep 27 19:58:48 lnxsrv1 kernel: Code: 0f 0b 68 80 0c 36 c0 53 e8 7f ba 13 00 > 83 c4 08 85 c0 0f 84 > -------------------------------------------------------------------------- > > ------------------------------------------------------------ > Sep 28 12:24:58 lnxsrv1 kernel: invalid operand: 0000 > Sep 28 12:24:58 lnxsrv1 kernel: CPU: 1 > Sep 28 12:24:58 lnxsrv1 kernel: EIP: 0010:[dput+20/364] > Sep 28 12:24:58 lnxsrv1 kernel: EIP: 0010:[] > Sep 28 12:24:58 lnxsrv1 kernel: EFLAGS: 00010246 > Sep 28 12:24:58 lnxsrv1 kernel: eax: 00000000 ebx: c7540560 ecx: > c75402e0 edx: 00000003 > Sep 28 12:24:58 lnxsrv1 kernel: esi: c7540560 edi: c75402e0 ebp: > c75402e0 esp: c18e7e78 > Sep 28 12:24:58 lnxsrv1 kernel: ds: 0018 es: 0018 ss: 0018 > Sep 28 12:24:58 lnxsrv1 kernel: Process nfsd (pid: 972, stackpage=c18e7000) > Sep 28 12:24:58 lnxsrv1 kernel: Stack: ffffffea c7540560 d0a04005 c7540560 > 00000003 04179db8 d0a043c6 c75402e0 > Sep 28 12:24:58 lnxsrv1 kernel: 00000003 c4fb6c10 46000000 c4fb6c00 > c0239ab3 cc45bdf8 c96c07a0 ffffff8c > Sep 28 12:24:58 lnxsrv1 kernel: 00000000 d0a04754 cc45bc00 04179db8 > 00000000 00000000 00000001 c4fb6c00 > Sep 28 12:24:58 lnxsrv1 kernel: Call Trace: > [aic7xxx:__insmod_aic7xxx_S.bss_L256+1848229/210353819] > [aic7xxx:__insmod_aic7xxx_S.bss_L256+18491$ > Sep 28 12:24:58 lnxsrv1 kernel: Call Trace: [] [] > [] [] [] > Sep 28 12:24:58 lnxsrv1 kernel: > [aic7xxx:__insmod_aic7xxx_S.bss_L256+1870173/210331875] > [aic7xxx:__insmod_aic7xxx_S.bss_L256+1843388/210358$ > Sep 28 12:24:58 lnxsrv1 kernel: [] [] [] > [] [] [] > Sep 28 12:24:58 lnxsrv1 kernel: > [aic7xxx:__insmod_aic7xxx_S.bss_L256+1905632/210296416] > [aic7xxx:__insmod_aic7xxx_S.bss_L256+1904328/210297$ > Sep 28 12:24:58 lnxsrv1 kernel: [] [] [] > [] > Sep 28 12:24:58 lnxsrv1 kernel: > Sep 28 12:24:58 lnxsrv1 kernel: Code: 0f 0b 68 80 0c 36 c0 53 e8 7f ba 13 00 > 83 c4 08 85 c0 0f 84 > -------------------------------------------------------------------------- > From owner-linux-xfs@oss.sgi.com Sat Sep 29 08:47:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8TFlXF04338 for linux-xfs-outgoing; Sat, 29 Sep 2001 08:47:33 -0700 Received: from ente.berdmann.de (frnk-d514e1e7.dsl.mediaWays.net [213.20.225.231]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8TFlSD04319 for ; Sat, 29 Sep 2001 08:47:29 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.22 #1) id 15nMKn-0001ux-00 for linux-xfs@oss.sgi.com; Sat, 29 Sep 2001 17:47:21 +0200 Message-ID: <3BB5ED09.FAF43F6E@berdmann.de> Date: Sat, 29 Sep 2001 17:47:21 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.10-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: TAKE - xfsdump/restore changes for ia64 References: <200109280950.TAA36050@snort.melbourne.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk FSG QA wrote: > > Date: Fri Sep 28 02:49:27 PDT 2001 > Workarea: snort.melbourne.sgi.com:/diskb/build4/fsgqa/isms/2.4.x-xfs [...] > cmd/xfsdump/common/getdents.c - 1.4 > - bring over the latest getdents from glibc so that > it works on ia64 without unaligned access messages. Seems to break on my non-ia64 box (i386, RHL 6.1 + 2.4.10-xfs): # ./Makepkgs rpm == clean, log is Logs/clean == configure, log is Logs/configure == default, log is Logs/default "make default" failed, see log in Logs/default gcc -O1 -g -DDEBUG -funsigned-char -Wall -DDUMP -DRMT -DBASED -DDOSOCKS -DINVCONVFIX -DSIZEEST -DPIPEINVFIX -DEXTATTR -DDMEXTATTR -I/usr/include/xfs -I/usr/include/attr '-DVERSION="1.1.5"' -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DXFS_BIG_FILES=1 -DXFS_BIG_FILESYSTEMS=1 -I/usr/include/xfs -I/usr/include/attr -c fs.c -o fs.o gcc -O1 -g -DDEBUG -funsigned-char -Wall -DDUMP -DRMT -DBASED -DDOSOCKS -DINVCONVFIX -DSIZEEST -DPIPEINVFIX -DEXTATTR -DDMEXTATTR -I/usr/include/xfs -I/usr/include/attr '-DVERSION="1.1.5"' -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DXFS_BIG_FILES=1 -DXFS_BIG_FILESYSTEMS=1 -I/usr/include/xfs -I/usr/include/attr -c getdents.c -o getdents.o getdents.c:87: parse error before `buf' getdents.c:88: parse error before `buf' getdents.c: In function `getdents_wrap': getdents.c:154: `SYS_getdents64' undeclared (first use in this function) getdents.c:154: (Each undeclared identifier is reported only once getdents.c:154: for each function it appears in.) make[1]: *** [getdents.o] Error 1 make: *** [default] Error 2 From owner-linux-xfs@oss.sgi.com Sat Sep 29 09:35:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8TGZY405025 for linux-xfs-outgoing; Sat, 29 Sep 2001 09:35:34 -0700 Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8TGZUD05006 for ; Sat, 29 Sep 2001 09:35:30 -0700 Received: (qmail 5793 invoked by uid 0); 29 Sep 2001 16:35:23 -0000 Received: from adsl-4-222.adsl.easynet.fr (HELO mail.gmx.de) (195.114.94.222) by mail.gmx.net (mp007-rz3) with SMTP; 29 Sep 2001 16:35:23 -0000 Message-ID: <200109291833180796.1351172E@mail.gmx.de> X-Mailer: Calypso Version 3.20.02.00 (4) Date: Sat, 29 Sep 2001 18:33:18 +0200 From: "linux" To: linux-xfs@oss.sgi.com Subject: compiling Linux Kernel v2.4.5-xfs-1.0.1 Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8TGZUD05007 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, before having kernel v2.4.10, i want to migrate my linux 2.4.4-xfs to the xfs release 1.0.1 so i do a make menuconfig to choose a config. i make a 'make dep' and it goes wrong make[4]: Quitte le répertoire `/usr/src/xfs/linux-2.4.5/fs/ntfs' make -C openpromfs fastdep make[4]: Entre dans le répertoire `/usr/src/xfs/linux-2.4.5/fs/openpromfs' /usr/src/xfs/linux-2.4.5/scripts/mkdep -D__KERNEL__ -I/usr/src/xfs/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=athlon -- inode.c > .depend make[4]: Quitte le répertoire `/usr/src/xfs/linux-2.4.5/fs/openpromfs' make -C pagebuf fastdep make: Entre dans un répertoire inconnu make: *** pagebuf: Aucun fichier ou répertoire de ce type. Arrêt. make: Quitte un répertoire inconnu make[3]: *** [_sfdep_pagebuf] Erreur 2 make[3]: Quitte le répertoire `/usr/src/xfs/linux-2.4.5/fs' make[2]: *** [fastdep] Erreur 2 make[2]: Quitte le répertoire `/usr/src/xfs/linux-2.4.5/fs' make[1]: *** [_sfdep_fs] Erreur 2 make[1]: Quitte le répertoire `/usr/src/xfs/linux-2.4.5' make: *** [dep-files] Erreur 2 it's a problem with pagebuf... i downloaded a fresh vanilla kernel v2.4.5 and applied : patch-2.4.5-bdev-ioctl and patch-2.4.5-xfs-1.0.1-core thanks for your help @++ nico From owner-linux-xfs@oss.sgi.com Sat Sep 29 09:50:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8TGotK05503 for linux-xfs-outgoing; Sat, 29 Sep 2001 09:50:55 -0700 Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8TGonD05483 for ; Sat, 29 Sep 2001 09:50:49 -0700 Received: (qmail 26508 invoked by uid 0); 29 Sep 2001 16:50:43 -0000 Received: from adsl-4-222.adsl.easynet.fr (HELO mail.gmx.de) (195.114.94.222) by mail.gmx.net (mp005-rz3) with SMTP; 29 Sep 2001 16:50:43 -0000 Message-ID: <200109291848380778.135F20DD@mail.gmx.de> In-Reply-To: <200109291833180796.1351172E@mail.gmx.de> References: <200109291833180796.1351172E@mail.gmx.de> X-Mailer: Calypso Version 3.20.02.00 (4) Date: Sat, 29 Sep 2001 18:48:38 +0200 From: "linux" To: linux-xfs@oss.sgi.com Subject: Re: compiling Linux Kernel v2.4.5-xfs-1.0.1 Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f8TGooD05484 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Sorry for this mail, i've forgot to patch with the patch-xfs-1.0.1-only but i've two questions : - if i upgrade my kernel, must i upgradethe cmd ? - what do you think about the v2.4.10 kernel ? thanks and sorry again with this mail @++ nico Le 29/09/2001 à 18:33 linux a écrit : >Hi, > >before having kernel v2.4.10, i want to migrate >my linux 2.4.4-xfs to the xfs release 1.0.1 > >so i do a make menuconfig >to choose a config. > >i make a 'make dep' and it goes wrong >make[4]: Quitte le répertoire `/usr/src/xfs/linux-2.4.5/fs/ntfs' >make -C openpromfs fastdep >make[4]: Entre dans le répertoire `/usr/src/xfs/linux-2.4.5/fs/openpromfs' >/usr/src/xfs/linux-2.4.5/scripts/mkdep -D__KERNEL__ >-I/usr/src/xfs/linux-2.4.5/include -Wall -Wstrict-prototypes -O2 >-fomit-frame-pointer -fno-strict-aliasing -pipe >-mpreferred-stack-boundary=2 -march=athlon -- inode.c > .depend >make[4]: Quitte le répertoire `/usr/src/xfs/linux-2.4.5/fs/openpromfs' >make -C pagebuf fastdep >make: Entre dans un répertoire inconnu >make: *** pagebuf: Aucun fichier ou répertoire de ce type. Arrêt. >make: Quitte un répertoire inconnu >make[3]: *** [_sfdep_pagebuf] Erreur 2 >make[3]: Quitte le répertoire `/usr/src/xfs/linux-2.4.5/fs' >make[2]: *** [fastdep] Erreur 2 >make[2]: Quitte le répertoire `/usr/src/xfs/linux-2.4.5/fs' >make[1]: *** [_sfdep_fs] Erreur 2 >make[1]: Quitte le répertoire `/usr/src/xfs/linux-2.4.5' >make: *** [dep-files] Erreur 2 > >it's a problem with pagebuf... > >i downloaded a fresh vanilla kernel v2.4.5 >and applied : patch-2.4.5-bdev-ioctl and patch-2.4.5-xfs-1.0.1-core > >thanks for your help > >@++ >nico c From owner-linux-xfs@oss.sgi.com Sat Sep 29 10:43:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8THhqS06329 for linux-xfs-outgoing; Sat, 29 Sep 2001 10:43:52 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8THhmD06309 for ; Sat, 29 Sep 2001 10:43:48 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id TAA21565; Sat, 29 Sep 2001 19:43:45 +0200 (CEST) Message-Id: <4.3.2.7.2.20010929194135.0303d518@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 29 Sep 2001 19:42:57 +0200 To: "linux" , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: compiling Linux Kernel v2.4.5-xfs-1.0.1 In-Reply-To: <200109291848380778.135F20DD@mail.gmx.de> References: <200109291833180796.1351172E@mail.gmx.de> <200109291833180796.1351172E@mail.gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 18:48 29-9-2001 +0200, linux wrote: >Hi, > >Sorry for this mail, >i've forgot to patch with the patch-xfs-1.0.1-only > >but i've two questions : > >- if i upgrade my kernel, must i upgradethe cmd ? No, it's in the FAQ >- what do you think about the v2.4.10 kernel ? No big reports of problems yet. The usual small breakage that should be expected from a CVS kernel and a kernel update. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sat Sep 29 11:37:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8TIbjP07309 for linux-xfs-outgoing; Sat, 29 Sep 2001 11:37:45 -0700 Received: from ente.berdmann.de (frnk-d514e1e7.dsl.mediaWays.net [213.20.225.231]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8TIbZD07290 for ; Sat, 29 Sep 2001 11:37:35 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.22 #1) id 15nOzQ-0002pC-00 for linux-xfs@oss.sgi.com; Sat, 29 Sep 2001 20:37:28 +0200 Message-ID: <3BB614E8.1F247033@berdmann.de> Date: Sat, 29 Sep 2001 20:37:28 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.10-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List Subject: torture-testing xfsdump/xfsrestore Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I did it again - torture-testing xfsdump/xfsrestore with Elisabeth D. Zwicky's "Torture-testing Backup and Archive Programs: Things You Ought to Know But Probably Would Rather Not". The previous URL (http://reality.sgi.com/zwicky_neu/testdump.doc.html) of that article is no longer available :-( "Reality has left the building. As of September 15, 2001, Reality.sgi.com has been discontinued." [blabla] So I provide an archived version of it on http://berdmann.dyndns.org/zwicky/testdump.doc.html and for the other files you might want to check http://berdmann.dyndns.org/zwicky/ First of all, I hacked xfsrestore/content.c to get rid of it's check for filenames up to 255 char length to up to and including 255 char length: /sbin/xfsdump: dumping non-directory files /sbin/xfsrestore: reading directories xfsrestore: content.c:2960: applydirdump: Assertion `namelen < 255' failed. /sbin/xfsdump: ending media file Here's the patch: --- /usr/src/xfsdump-test2/linux-2.4-xfs/cmd/xfsdump/restore/content.c Tue Sep 4 06:31:55 2001 +++ /usr/src/xfsdump-test/linux-2.4-xfs/cmd/xfsdump/restore/content.c Sat Sep 29 19:30:37 2001 @@ -2957,7 +2957,7 @@ applydirdump( drive_t *drivep, break; } namelen = strlen( dhdrp->dh_name ); - ASSERT( namelen < NAME_MAX ); + ASSERT( namelen <= NAME_MAX ); /* add this dirent to the tree. */ @@ -3075,7 +3075,7 @@ eatdirdump( drive_t *drivep, break; } namelen = strlen( dhdrp->dh_name ); - ASSERT( namelen < NAME_MAX ); + ASSERT( namelen <= NAME_MAX ); } } At a first shot, xfsdump/xfsrestore do their jobs well: # ~be/torture-new/torture.perl First guess at max component length is 255 max path length appears to be 4095 Type a command line which will run a backup program on the dump test directory: /sbin/xfsdump -J - /mnt/test1 | (cd /mnt/test2; /sbin/xfsrestore - .) Child 1 /sbin/xfsrestore: version 3.0 - Running single-threaded /sbin/xfsdump: version 3.0 - Running single-threaded /sbin/xfsrestore: searching media for dump /sbin/xfsdump: level 0 dump of apollo:/mnt/test1 /sbin/xfsdump: dump date: Sat Sep 29 19:39:35 2001 /sbin/xfsdump: session id: 1fa00278-09b1-4c37-bfb2-1d7d3e781843 /sbin/xfsdump: session label: "" /sbin/xfsdump: ino map phase 1: skipping (no subtrees specified) /sbin/xfsdump: ino map phase 2: constructing initial dump list /sbin/xfsdump: ino map phase 3: skipping (no pruning necessary) /sbin/xfsdump: ino map phase 4: skipping (size estimated in phase 2) /sbin/xfsdump: ino map phase 5: skipping (only one dump stream) /sbin/xfsdump: ino map construction complete /sbin/xfsdump: estimated dump size: 1349696 bytes /sbin/xfsdump: creating dump session media file 0 (media 0, file 0) /sbin/xfsdump: dumping ino map /sbin/xfsdump: dumping directories /sbin/xfsrestore: examining media file 0 /sbin/xfsrestore: dump description: /sbin/xfsrestore: hostname: apollo /sbin/xfsrestore: mount point: /mnt/test1 /sbin/xfsrestore: volume: /dev/vg01/test1 /sbin/xfsrestore: session time: Sat Sep 29 19:39:35 2001 /sbin/xfsrestore: level: 0 /sbin/xfsrestore: session label: "" /sbin/xfsrestore: media label: "" /sbin/xfsrestore: file system id: 0174fd6a-02a1-4cb0-85f3-90219087d7b6 /sbin/xfsrestore: session id: 1fa00278-09b1-4c37-bfb2-1d7d3e781843 /sbin/xfsrestore: media id: 7a04cd3d-ec20-4420-bf33-f44bcf459abb /sbin/xfsrestore: searching media for directory dump /sbin/xfsrestore: reading directories /sbin/xfsdump: dumping non-directory files /sbin/xfsrestore: directory post-processing /sbin/xfsrestore: restoring non-directory files /sbin/xfsrestore: WARNING: unable restore ino 131573 gen 4: relative pathname too long (partial DumpTestDir/longfilenames/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd/244(4095)xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx!) /sbin/xfsdump: WARNING: failed to get bulkstat information for inode 786848 /sbin/xfsdump: ending media file /sbin/xfsdump: media file size 2468312 bytes /sbin/xfsdump: dump size (non-dir files) : 910512 bytes /sbin/xfsdump: dump complete: 51 seconds elapsed /sbin/xfsdump: Dump Status: SUCCESS /sbin/xfsrestore: restore complete: 54 seconds elapsed /sbin/xfsrestore: Restore Status: SUCCESS Backup took 54.00 seconds of clock time and 0.00 seconds of cpu time Just some missing files with pathnames > 4085 char length were found by diff: # ~be/torture-new/diff/diff -r -b -Q -X DumpTestDir /mnt/test2/DumpTestDir > /tmp/res1 2>/tmp/res2 You can get the files res1 and res2 from http://berdmann.dyndns.org/torture-testing/xfsdump/ From owner-linux-xfs@oss.sgi.com Sat Sep 29 13:37:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8TKbFx09052 for linux-xfs-outgoing; Sat, 29 Sep 2001 13:37:15 -0700 Received: from ws3-7.us4.outblaze.com (205-158-62-71.outblaze.com [205.158.62.71]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8TKbCD09030 for ; Sat, 29 Sep 2001 13:37:12 -0700 Received: (qmail 414 invoked by uid 1001); 29 Sep 2001 20:37:05 -0000 Message-ID: <20010929203705.413.qmail@migration.iname.com> 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 ws3-7.us4.outblaze.com for [63.193.123.26] via web-mailer on Sun, 30 Sep 2001 04:37:05 +0800 From: "Magnus Johansson" To: linux-xfs@oss.sgi.com Date: Sun, 30 Sep 2001 04:37:05 +0800 Subject: "can't handle dep_bool/dep_mbool/dep_tristate condition" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I checked out the latest CVS today (2001-09-29). I get the following error message when doing 'make xconfig' [root@magnus2 linux]# make xconfig rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts kconfig.tk make[1]: Entering directory `/usr/src/linux-2.4.10-xfs/scripts' cat header.tk >> ./kconfig.tk ./tkparse < ../arch/i386/config.in >> kconfig.tk -: 402: can't handle dep_bool/dep_mbool/dep_tristate condition make[1]: *** [kconfig.tk] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.10-xfs/scripts' make: *** [xconfig] Error 2 No such problems occured with 2.4.10-pre9-xfs CVS. It seems that arch/i386/config.in was updated for the kdb v1.9 upgrade. The work-around was to use 'make oldconfig' Other than that, everything is stable. Regards Magnus -- _______________________________________________ Get your free email from http://mymail.migration.iname.com Powered by Outblaze From owner-linux-xfs@oss.sgi.com Sun Sep 30 13:14:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8UKEBh31693 for linux-xfs-outgoing; Sun, 30 Sep 2001 13:14:11 -0700 Received: from web11706.mail.yahoo.com (web11706.mail.yahoo.com [216.136.172.72]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8UKE8D31673 for ; Sun, 30 Sep 2001 13:14:08 -0700 Message-ID: <20010930201408.26924.qmail@web11706.mail.yahoo.com> Received: from [24.151.81.31] by web11706.mail.yahoo.com via HTTP; Sun, 30 Sep 2001 13:14:08 PDT Date: Sun, 30 Sep 2001 13:14:08 -0700 (PDT) From: Sean Elble Subject: IRIX 6.5.6m/XFS CVS: Any problems? To: linux-xfs@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, I have a Silicon Graphics Indigo2 here with IRIX 6.5.6m installed (love it, BTW), and a Linux server that is about to have the latest CVS version of the XFS kernel installed, along with the kernel-level NFS server. Are there any known problems, or catches, using NFS on IRIX with a Linux 2.4.10 server? I would like to use NFS3, if possible, but I would appreciate any comments any users may have. Thanks, in advance! ===== ------------------------------ Sean Elble MaximumLinux.org Voice Mail: 1-800-699-2466; Voice Mail Box 8603550213 E-Mail: S_Elble@yahoo.com ------------------------------ __________________________________________________ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com From owner-linux-xfs@oss.sgi.com Sun Sep 30 13:47:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8UKlxw32340 for linux-xfs-outgoing; Sun, 30 Sep 2001 13:47:59 -0700 Received: from femail14.sdc1.sfba.home.com (femail14.sdc1.sfba.home.com [24.0.95.141]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8UKlqD32319 for ; Sun, 30 Sep 2001 13:47:52 -0700 Received: from acm.org ([24.100.161.53]) by femail14.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010930204746.LYDC24292.femail14.sdc1.sfba.home.com@acm.org>; Sun, 30 Sep 2001 13:47:46 -0700 Message-ID: <3BB7854D.3A6F8765@acm.org> Date: Sun, 30 Sep 2001 16:49:17 -0400 From: Andrew Ho X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.10-xfs i686) X-Accept-Language: en, zh MIME-Version: 1.0 To: Sean Elble , linux-xfs@oss.sgi.com Subject: Re: IRIX 6.5.6m/XFS CVS: Any problems? References: <20010930201408.26924.qmail@web11706.mail.yahoo.com> Content-Type: multipart/alternative; boundary="------------C4382CA46BB002D1B1C4146E" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --------------C4382CA46BB002D1B1C4146E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I don't find there is any problem at all. Try it. Andrew Ho Sean Elble wrote: > Hello, > > I have a Silicon Graphics Indigo2 here with IRIX > 6.5.6m installed (love it, BTW), and a Linux server > that is about to have the latest CVS version of the > XFS kernel installed, along with the kernel-level NFS > server. > > Are there any known problems, or catches, using NFS on > IRIX with a Linux 2.4.10 server? I would like to use > NFS3, if possible, but I would appreciate any comments > any users may have. Thanks, in advance! > > ===== > ------------------------------ > Sean Elble > MaximumLinux.org > Voice Mail: 1-800-699-2466; Voice Mail Box 8603550213 > E-Mail: S_Elble@yahoo.com > ------------------------------ > > __________________________________________________ > Do You Yahoo!? > Listen to your Yahoo! Mail messages from any phone. > http://phone.yahoo.com -- **************************************************** "You should not ask what other people want. You should ask what you need and just do it, even completely clueless people can do things." Linus Torvalds **************************************************** --------------C4382CA46BB002D1B1C4146E Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit I don't find there is any problem at all.

Try it.

Andrew Ho

Sean Elble wrote:

Hello,

I have a Silicon Graphics Indigo2 here with IRIX
6.5.6m installed (love it, BTW), and a Linux server
that is about to have the latest CVS version of the
XFS kernel installed, along with the kernel-level NFS
server.

Are there any known problems, or catches, using NFS on
IRIX with a Linux 2.4.10 server? I would like to use
NFS3, if possible, but I would appreciate any comments
any users may have. Thanks, in advance!

=====
------------------------------
Sean Elble
MaximumLinux.org
Voice Mail: 1-800-699-2466; Voice Mail Box 8603550213
E-Mail: S_Elble@yahoo.com
------------------------------

__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com

-- 
****************************************************

"You should not ask what other people want. 
 You should ask what you need and just do it,
 even completely clueless people can do things." 
        Linus Torvalds

****************************************************
  --------------C4382CA46BB002D1B1C4146E-- From owner-linux-xfs@oss.sgi.com Sun Sep 30 14:40:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8ULe4R00852 for linux-xfs-outgoing; Sun, 30 Sep 2001 14:40:04 -0700 Received: from web11702.mail.yahoo.com (web11702.mail.yahoo.com [216.136.172.68]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8ULdwD00831 for ; Sun, 30 Sep 2001 14:39:58 -0700 Message-ID: <20010930213957.36649.qmail@web11702.mail.yahoo.com> Received: from [24.151.81.31] by web11702.mail.yahoo.com via HTTP; Sun, 30 Sep 2001 14:39:57 PDT Date: Sun, 30 Sep 2001 14:39:57 -0700 (PDT) From: Sean Elble Subject: Re: IRIX 6.5.6m/XFS CVS: Any problems? To: Andrew Ho , linux-xfs@oss.sgi.com In-Reply-To: <3BB7854D.3A6F8765@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'll probably do just that, after reading up on NFS for a couple minutes . . . been a while since I've used it. :-) Thanks for the info! Sean Elble --- Andrew Ho wrote: > I don't find there is any problem at all. > > Try it. > > Andrew Ho > > Sean Elble wrote: > > > Hello, > > > > I have a Silicon Graphics Indigo2 here with IRIX > > 6.5.6m installed (love it, BTW), and a Linux > server > > that is about to have the latest CVS version of > the > > XFS kernel installed, along with the kernel-level > NFS > > server. > > > > Are there any known problems, or catches, using > NFS on > > IRIX with a Linux 2.4.10 server? I would like to > use > > NFS3, if possible, but I would appreciate any > comments > > any users may have. Thanks, in advance! > > > > ===== > > ------------------------------ > > Sean Elble > > MaximumLinux.org > > Voice Mail: 1-800-699-2466; Voice Mail Box > 8603550213 > > E-Mail: S_Elble@yahoo.com > > ------------------------------ > > > > __________________________________________________ > > Do You Yahoo!? > > Listen to your Yahoo! Mail messages from any > phone. > > http://phone.yahoo.com > > -- > **************************************************** > > "You should not ask what other people want. > You should ask what you need and just do it, > even completely clueless people can do things." > Linus Torvalds > > **************************************************** > > > ===== ------------------------------ Sean Elble MaximumLinux.org Voice Mail: 1-800-699-2466; Voice Mail Box 8603550213 E-Mail: S_Elble@yahoo.com ------------------------------ __________________________________________________ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com From owner-linux-xfs@oss.sgi.com Sun Sep 30 17:29:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f910Tlw03247 for linux-xfs-outgoing; Sun, 30 Sep 2001 17:29:47 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f910TgD03228 for ; Sun, 30 Sep 2001 17:29:42 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f910TaK02437 for ; Sun, 30 Sep 2001 17:29:36 -0700 Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id AAA32490; Mon, 1 Oct 2001 00:28:09 GMT Date: Mon, 1 Oct 2001 00:28:09 +0000 From: Timothy Shimmin To: "Bernhard R. Erdmann" Cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - xfsdump/restore changes for ia64 Message-ID: <20011001002809.I10761@boing.melbourne.sgi.com> References: <200109280950.TAA36050@snort.melbourne.sgi.com> <3BB5ED09.FAF43F6E@berdmann.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <3BB5ED09.FAF43F6E@berdmann.de>; from be@berdmann.de on Sat, Sep 29, 2001 at 05:47:21PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Damn. I tested this on ia32, found the problem and made the change but forgot to copy it back to my ia64 workarea. Check in shortly. Thanks, --Tim On Sat, Sep 29, 2001 at 05:47:21PM +0200, Bernhard R. Erdmann wrote: > FSG QA wrote: > > > > Date: Fri Sep 28 02:49:27 PDT 2001 > > Workarea: snort.melbourne.sgi.com:/diskb/build4/fsgqa/isms/2.4.x-xfs > [...] > > cmd/xfsdump/common/getdents.c - 1.4 > > - bring over the latest getdents from glibc so that > > it works on ia64 without unaligned access messages. > > Seems to break on my non-ia64 box (i386, RHL 6.1 + 2.4.10-xfs): > > # ./Makepkgs rpm > == clean, log is Logs/clean > > == configure, log is Logs/configure > > == default, log is Logs/default > "make default" failed, see log in Logs/default > gcc -O1 -g -DDEBUG -funsigned-char -Wall -DDUMP -DRMT -DBASED -DDOSOCKS > -DINVCONVFIX -DSIZEEST -DPIPEINVFIX -DEXTATTR -DDMEXTATTR > -I/usr/include/xfs -I/usr/include/attr '-DVERSION="1.1.5"' > -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DXFS_BIG_FILES=1 > -DXFS_BIG_FILESYSTEMS=1 -I/usr/include/xfs -I/usr/include/attr -c fs.c > -o fs.o > gcc -O1 -g -DDEBUG -funsigned-char -Wall -DDUMP -DRMT -DBASED -DDOSOCKS > -DINVCONVFIX -DSIZEEST -DPIPEINVFIX -DEXTATTR -DDMEXTATTR > -I/usr/include/xfs -I/usr/include/attr '-DVERSION="1.1.5"' > -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DXFS_BIG_FILES=1 > -DXFS_BIG_FILESYSTEMS=1 -I/usr/include/xfs -I/usr/include/attr -c > getdents.c -o getdents.o > getdents.c:87: parse error before `buf' > getdents.c:88: parse error before `buf' > getdents.c: In function `getdents_wrap': > getdents.c:154: `SYS_getdents64' undeclared (first use in this function) > getdents.c:154: (Each undeclared identifier is reported only once > getdents.c:154: for each function it appears in.) > make[1]: *** [getdents.o] Error 1 > make: *** [default] Error 2 > From owner-linux-xfs@oss.sgi.com Sun Sep 30 17:41:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f910flD03531 for linux-xfs-outgoing; Sun, 30 Sep 2001 17:41:47 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f910fiD03512 for ; Sun, 30 Sep 2001 17:41:44 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id RAA04502 for ; Sun, 30 Sep 2001 17:40:35 -0700 (PDT) mail_from (fsgqa@snort.melbourne.sgi.com) Received: (from fsgqa@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA37593 for linux-xfs@oss.sgi.com; Mon, 1 Oct 2001 10:40:26 +1000 (EST) Date: Mon, 1 Oct 2001 10:40:26 +1000 (EST) From: FSG QA Message-Id: <200110010040.KAA37593@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump/xfsrestore ia32/ia64 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Okay, did a "p_rdiff `p_list -c`" in my ia32 workarea. So this now reflects the src which works in ia32 and ia64. Thanks for letting me know, Bernhard. --Tim Date: Sun Sep 30 17:36:05 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/fsgqa/isms/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103639a cmd/xfsdump/common/getdents.c - 1.5 - Fix for ia32 - forgot to copy over this change from my ia32 workarea. From owner-linux-xfs@oss.sgi.com Sun Sep 30 18:53:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f911raN04784 for linux-xfs-outgoing; Sun, 30 Sep 2001 18:53:36 -0700 Received: from rj.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f911rYD04762 for ; Sun, 30 Sep 2001 18:53:34 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f911rSL15941 for ; Sun, 30 Sep 2001 18:53:28 -0700 Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id LAA22127; Mon, 1 Oct 2001 11:53:23 +1000 Date: Mon, 1 Oct 2001 11:53:23 +1000 From: Keith Owens Message-Id: <200110010153.LAA22127@sherman.melbourne.sgi.com> Subject: TAKE - Correct kdb config.in Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Correct kdb config.in Date: Sun Sep 30 18:52:17 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:103640a linux/arch/i386/config.in - 1.62 From owner-linux-xfs@oss.sgi.com Sun Sep 30 18:53:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f911rB204729 for linux-xfs-outgoing; Sun, 30 Sep 2001 18:53:11 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f911r9D04710 for ; Sun, 30 Sep 2001 18:53:09 -0700 Received: from nodin.corp.sgi.com ([198.29.75.193]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id SAA08221 for ; Sun, 30 Sep 2001 18:53:00 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by nodin.corp.sgi.com (8.11.4/8.11.2/nodin-1.0) with ESMTP id f911pus2163106; Sun, 30 Sep 2001 18:51:56 -0700 (PDT) Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id 66509300095; Mon, 1 Oct 2001 11:51:53 +1000 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id B9429B8; Mon, 1 Oct 2001 11:51:53 +1000 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 From: Keith Owens To: "Magnus Johansson" Cc: linux-xfs@oss.sgi.com Subject: Re: "can't handle dep_bool/dep_mbool/dep_tristate condition" In-reply-to: Your message of "Sun, 30 Sep 2001 04:37:05 +0800." <20010929203705.413.qmail@migration.iname.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Oct 2001 11:51:48 +1000 Message-ID: <1929.1001901108@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 30 Sep 2001 04:37:05 +0800, "Magnus Johansson" wrote: >./tkparse < ../arch/i386/config.in >> kconfig.tk >-: 402: can't handle dep_bool/dep_mbool/dep_tristate condition In arch/i386/config.in, the line dep_tristate ' KDB modules' CONFIG_KDB_MODULES should read dep_tristate ' KDB modules' CONFIG_KDB_MODULES $CONFIG_KDB I have checked the change in, it will propagate to CVS in an hour or so. From owner-linux-xfs@oss.sgi.com Sun Sep 30 20:11:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f913Buq06115 for linux-xfs-outgoing; Sun, 30 Sep 2001 20:11:56 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f913BqD06096 for ; Sun, 30 Sep 2001 20:11:52 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id UAA06740 for ; Sun, 30 Sep 2001 20:10:38 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id DAA35633; Mon, 1 Oct 2001 03:10:26 GMT Date: Mon, 1 Oct 2001 03:10:26 +0000 From: Timothy Shimmin To: Charles Radeke Cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump/restore from cd Message-ID: <20011001031026.L10761@boing.melbourne.sgi.com> References: <3BB47E57.4F936128@hrz.tu-chemnitz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <3BB47E57.4F936128@hrz.tu-chemnitz.de>; from charles.radeke@hrz.tu-chemnitz.de on Fri, Sep 28, 2001 at 03:42:47PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Charles, On Fri, Sep 28, 2001 at 03:42:47PM +0200, Charles Radeke wrote: > > my problem is the following: > > I would like to backup a partition of some GB by burning cd's with > splitted xfsdump , each is 650MB. Is it possible to use a cdrom-drive as > a tape (like/dev/rmt)? and if, how to simulate the tape change? Can't really do this. When dumping to a tape (which uses the drive_scsitape strategy) it send mt commands to the tape device to do tape operations and get status. This aint going to work for a non-tape device. > I saw > that is not possible to xfsrestore splitted dumps step by step, only the > first succseeded (what is clear to me). I wont copy 7 cd's on an empty > drive bevor I can do cat | xfsrestore - / > > Or ist there another solution in general for my problem? I saw that the > -d option is not available for xfsdump like at IRIX-xfsdump where I can > set the size of the media. > This option is available in Linux/XFS too but I don't think this is of use to you. It is for the drive_scsitape strategy where a dump is split into multiple files on tape (media-files). This is so that a bad tape can have the good media files still restored. So what are possible solutions ? (a) try using split(1) to split up the dump output from stdout But this would require room for the split files. (b) write your own drive strategy for xfsdump/xfsrestore :) --Tim From owner-linux-xfs@oss.sgi.com Sun Sep 30 20:45:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f913jTb06635 for linux-xfs-outgoing; Sun, 30 Sep 2001 20:45:29 -0700 Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f913jOD06615 for ; Sun, 30 Sep 2001 20:45:24 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f913jHK04405 for ; Sun, 30 Sep 2001 20:45:17 -0700 Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id NAA14954; Mon, 1 Oct 2001 13:44:00 +1000 From: ivanr@sgi.com Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id NAA15793; Mon, 1 Oct 2001 13:44:00 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Mon, 1 Oct 2001 13:44:00 +1000 X-X-Sender: ivanr@omen.melbourne.sgi.com To: Charles Radeke cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump/restore from cd In-Reply-To: <20011001031026.L10761@boing.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 1 Oct 2001, Timothy Shimmin wrote: > Hi Charles, > > On Fri, Sep 28, 2001 at 03:42:47PM +0200, Charles Radeke wrote: > > I would like to backup a partition of some GB by burning cd's with > > splitted xfsdump , each is 650MB. Is it possible to use a cdrom-drive as > > a tape (like/dev/rmt)? and if, how to simulate the tape change? ... > So what are possible solutions ? > (b) write your own drive strategy for xfsdump/xfsrestore :) This option might not be as hard as it looks. All you really want is to be able to specify the media file size and to allow for a prompt for new media when you get ENOSP in the drive_simple strategy. So - copy the drive_simple.c to drive_cdrom.c - modify it so that references to drive_simple become drive_cdrom - insert the new strategy into strategypp[] in drive.c (before drive_simple) - modify drive_cdrom.c:ds_match() to do something clever like check we're writing to a device - work out how you can incorporate the change media stuff that's in drive_scsitape.c (or perhaps drive_minrmt.c might be simpler?). Do a search on "changemedia" in dump/content.c, do_get_device_class() in drive_simple.c and DEVICE_DISK_REMOVABLE in drive.h. Note: I haven't looked into this at all, so I'm very probably missing some fundamental problems. In other words, don't blame me if you waste weeks of your life on this... :) Ivan -- Ivan Rayner ivanr@sgi.com From owner-linux-xfs@oss.sgi.com Sun Sep 30 21:53:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f914rej07735 for linux-xfs-outgoing; Sun, 30 Sep 2001 21:53:40 -0700 Received: from TYO201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.214]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f914rZD07714 for ; Sun, 30 Sep 2001 21:53:36 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.195]) by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f914rSa14876 for ; Mon, 1 Oct 2001 13:53:28 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.196]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f914rSP13273 for ; Mon, 1 Oct 2001 13:53:28 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id f914rRX13186 for ; Mon, 1 Oct 2001 13:53:27 +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 AAA505 for ; Mon, 1 Oct 2001 13:53:24 +0900 Received: FROM tnesgate.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Mon Oct 01 13:53:23 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by tnesgate.tnes.nec.co.jp (8.9.3/3.7W00091816) with ESMTP id NAA73272; Mon, 1 Oct 2001 13:53:24 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f914rOi18959; Mon, 1 Oct 2001 13:53:24 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id NAA25653; Mon, 1 Oct 2001 13:53:23 +0900 (JST) Message-Id: <200110010453.NAA25653@tagajo.bsd.tnes.nec.co.jp> To: Dean Roehrich cc: linux-xfs@oss.sgi.com Subject: Re: wbee (sample_hsm) dumped core In-reply-to: Your message of Fri, 28 Sep 2001 09:32:21 -0500. <200109281432.JAA24904@slobber.americas.sgi.com> Date: Mon, 01 Oct 2001 13:53:23 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Dean Roehrich wrote: > > Some history on these: The sample_hsm stuff is probably the granddaddy of all > the dmapi tests. I inherited these and nobody I know has ever used them, let > alone worried about whether or not they worked (even on Irix). They were > deemed as having no value and it was suggested that I throw them out (then why > did they exist long enough for me to inherit them?). Anyway, I decided to > keep them, thinking that maybe one day they'd be dusted off and given a > tune-up. That's sound very nice :) > Note that the test tool 'print_event' exists in two places in the test tree. > The version in sample_hsm is _not_ the one I use, and I really haven't looked > at why they are different, or whether sample_hsm/print_event would even work. > At this moment, you are the expert on the sample_hsm stuff (congrats), so tell > me what you think: should we just remove sample_hsm/print_event and rely on > the other print_event? I think so because sample_hsm/print_eventry was not compiled here by make :) then I made it by hand and run it. It seemed work successfully, however, there is no document of sample_hsm/print_event except itself, so I'm not sure about it. Could you tell me what are you using or should I use to evaluate dmapi of XFS filesystem? Is there any good tools / documents besides cvs tree? Thanks in advance, Takayuki From owner-linux-xfs@oss.sgi.com Sun Sep 30 22:45:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f915jmZ08606 for linux-xfs-outgoing; Sun, 30 Sep 2001 22:45:48 -0700 Received: from gwyn.tux.org (ident-user@gwyn.tux.org [207.96.122.8]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f915jkD08587 for ; Sun, 30 Sep 2001 22:45:46 -0700 Received: (from timball@localhost) by gwyn.tux.org (8.9.3/8.9.1) id BAA28136 for linux-xfs@oss.sgi.com; Mon, 1 Oct 2001 01:45:45 -0400 Date: Mon, 1 Oct 2001 01:45:45 -0400 From: Timothy Ball To: XFS Mailing List Subject: lvm + xfs / Message-ID: <20011001014544.B27657@gwyn.tux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.20i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk so is it me or does this not work? It seems the initrd loses badly... --timball -- GPG key available on pgpkeys.mit.edu pub 1024R/CFF85605 1999-06-10 Timothy L. Ball Key fingerprint = 8A 8E 64 D6 21 C0 90 29 9F D6 1E DC F8 18 CB CD From owner-linux-xfs@oss.sgi.com Sun Sep 30 23:06:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f9166c709083 for linux-xfs-outgoing; Sun, 30 Sep 2001 23:06:38 -0700 Received: from TYO201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.214]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f9166XD09063 for ; Sun, 30 Sep 2001 23:06:33 -0700 Received: from mailgate4.nec.co.jp ([10.7.69.197]) by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id f9166Qa04674 for ; Mon, 1 Oct 2001 15:06:26 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id f9166PV23295 for ; Mon, 1 Oct 2001 15:06:25 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (THKTNES98740.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id f9166OX07766 for ; Mon, 1 Oct 2001 15:06:25 +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 AAA506 for ; Mon, 1 Oct 2001 15:06:22 +0900 Received: FROM mailsv.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Mon Oct 01 15:06:19 2001 +0900 Received: from rifu.bsd.tnes.nec.co.jp (IDENT:root@rifu.bsd.tnes.nec.co.jp [10.1.101.142]) by mailsv.tnes.nec.co.jp (8.9.3/3.7W01031510) with ESMTP id PAA76337 for ; Mon, 1 Oct 2001 15:06:20 +0900 (JST) Received: from tagajo.bsd.tnes.nec.co.jp (tagajo.bsd.tnes.nec.co.jp [10.1.101.146]) by rifu.bsd.tnes.nec.co.jp (8.10.2+3.3W/3.7W/BSD-TNES-MX01) with ESMTP id f9166Li23735 for ; Mon, 1 Oct 2001 15:06:21 +0900 Received: (from sasaki@localhost) by tagajo.bsd.tnes.nec.co.jp (8.8.5+2.7Wbeta5/3.5Wpl1-97090809) id PAA26141; Mon, 1 Oct 2001 15:06:20 +0900 (JST) Message-Id: <200110010606.PAA26141@tagajo.bsd.tnes.nec.co.jp> To: linux-xfs@oss.sgi.com Subject: Re: TAKE - xfsdump/restore changes for ia64 In-reply-to: Your message of Fri, 28 Sep 2001 19:50:25 +1000. <200109280950.TAA36050@snort.melbourne.sgi.com> Date: Mon, 01 Oct 2001 15:06:20 +0900 From: Takayuki Sasaki Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, FSG QA wrote: > Date: Fri Sep 28 02:49:27 PDT 2001 > Workarea: snort.melbourne.sgi.com:/diskb/build4/fsgqa/isms/2.4.x-xfs (snip) > cmd/xfsdump/common/stkchk.c - 1.2 > - make a size long so comparison works for ia32/ia64 with ptr I have a question. The type of sc_sz in struct stkchk is changed to long from int, but get_stacksz() is left decrare to return int. stkchk.c line 90: stkchkp->sc_sz = get_stacksz( ); Further more, I'm wondering because it seems that rlim_cur is defined as unsigned long. [My box is RedHat 7.1] $ grep rlim_cur /usr/include/*/*.h /usr/include/bits/resource.h: rlim_t rlim_cur; /usr/include/bits/resource.h: rlim64_t rlim_cur; (snip) /usr/include/linux/resource.h: unsigned long rlim_cur; $ grep rlim_t /usr/include/*/*.h /usr/include/bits/resource.h:typedef __rlim_t rlim_t; /usr/include/bits/resource.h:typedef __rlim64_t rlim_t; /usr/include/bits/resource.h: rlim_t rlim_cur; /usr/include/bits/resource.h: rlim_t rlim_max; /usr/include/bits/types.h:typedef __u_long __rlim_t; /* Type of resource counts. */ Which is correct? Takayuki