Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs\s+and\s+openafs\s+problem\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs\s+and\s+openafs\s+problem\s*$/: 12 ]

Total 12 documents matching your query.

1. ure (score: 1): Author: <tom@xxxxxxx>; Date: Tue, 23 Jul 2002 16:16:55 +0200; want us to use Linux because he didn't think very many people were using Linux :) 3% percent of 500 Million is still a lot. Cheers -- Seth It might just be your lucky day, if you only; /archives/xfs/2002-07/msg00261.html (13,417 bytes)
2. lem (score: 1): Author: xxxxxxxxxxxxx>; Date: Tue, 23 Jul 2002 15:19:36 +0100; at the last dd i did was incomplete, so i did a new one (which took over 24h) and there were more bad blocks than i thought before. about 1-2% of the hdd are bad blocks. i got xfs_check; /archives/xfs/2002-07/msg00262.html (10,210 bytes)
3. ure (score: 1): Author: fie@xxxxxxxxx>; Date: Tue, 23 Jul 2002 16:44:42 +0200; a problem creating large files when using OpenAFS (no answe; /archives/xfs/2002-07/msg00264.html (10,457 bytes)
4. lem (score: 1): Author: xxxxxxxxxxxxx>; Date: Tue, 23 Jul 2002 16:05:49 +0100; 002 +0200, thomas wrote: maybe that'd be a good idea. what is the standard xfs blocksize, 4096 no? that'd be dd conv=noerror,sync bs=4096 </dev/hdc2 >/dev/hda5 4096 is correct. it woul; /archives/xfs/2002-07/msg00265.html (11,403 bytes)
5. NFS (score: 1): Author: ndeen@xxxxxxx>; Date: Tue, 23 Jul 2002 11:50:07 -0500 (CDT); in XFS were allocating, initializing, and passing a variable to xfs_bmapi() in the read case - but that variable was never used. Yank it out; this saves a whopping 288 bytes in my ker; /archives/xfs/2002-07/msg00270.html (14,724 bytes)
6. in) (score: 1): Author: xxxxxxxxxxxxx>; Date: Wed, 24 Jul 2002 23:03:06 +0200 (CEST); uld be a problem. Anyway, some generous souls just gave me an external SCSI drive, so the case for the IDE is closed. ;-) But, for future refference, is there a way to tell if an IDE d; /archives/xfs/2002-07/msg00295.html (9,264 bytes)
7. failure (score: 1): Author: xxxxxxx>; Date: Tue, 23 Jul 2002 16:16:55 +0200; 8a linux/fs/xfs/xfsidbg.c - 1.194 linux/fs/xfs/xfs_vnodeops.c - 1.5; /archives/xfs/2002-07/msg00692.html (13,417 bytes)
8. problem (score: 1): Author: nberger <wlang@xxxxxxxxxxxxx>; Date: Tue, 23 Jul 2002 15:19:36 +0100; s (I agree) but there are examples on what ones are needed to get a; /archives/xfs/2002-07/msg00693.html (10,210 bytes)
9. failure (score: 1): Author:; Date: Tue, 23 Jul 2002 16:44:42 +0200; sauter-bc.com (Postfix) with ESMTP id B564A57306; Tue, 23 Jul 2002 14:20:15 +0200 (CEST) Cc: Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxx; /archives/xfs/2002-07/msg00695.html (10,457 bytes)
10. problem (score: 1): Author: nberger <wlang@xxxxxxxxxxxxx>; Date: Tue, 23 Jul 2002 16:05:49 +0100; very many people were using Linux :) 3% percent of 500 Million is still a lot. Cheers -- Seth It might just be your lucky day, if you only; /archives/xfs/2002-07/msg00696.html (11,403 bytes)
11. Re: NFS (score: 1): Author: ric Sandeen <sandeen@xxxxxxx>; Date: Tue, 23 Jul 2002 11:50:07 -0500 (CDT); ll so far... Anyway, what makes you sure, that it's OpenAFS' fault (besides that it; /archives/xfs/2002-07/msg00701.html (14,724 bytes)
12. (again) (score: 1): Author: nyou <austin@xxxxxxxxxxxxxxx>; Date: Wed, 24 Jul 2002 23:03:06 +0200 (CEST); ped when the buffer queue is overloaded on the NFS server. What y; /archives/xfs/2002-07/msg00726.html (9,264 bytes)

Current List: 1 - 12
Page: [1]