Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+Re\:\s+Reduce\s+XFS\s+footprint\s+\(was\s+Re\:\s+TAKE\s+\-\s+remove\s+a\s+function\s+xfs\s+added\s+to\s+filemap\.c\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+Re\:\s+Reduce\s+XFS\s+footprint\s+\(was\s+Re\:\s+TAKE\s+\-\s+remove\s+a\s+function\s+xfs\s+added\s+to\s+filemap\.c\s*$/: 45 ]

Total 45 documents matching your query.

1. s on large h/w RAID fails (score: 1): Author: xxxxxxxxxxxx>; Date: Tue, 29 Jan 2002 19:40:01 +0100; This patch does it. It's very simple and clean. Saves another 18K on a xfs with BIG_FILESYSTEMS and BIG_FILES disabled. For completeness I also added BIG_FILES and BIG_FILESYSTEMS as visible CONFIG o; /archives/xfs/2002-01/msg00839.html (16,204 bytes)
2. lemap.c (score: 1): Author: deen@xxxxxxx>; Date: Tue, 29 Jan 2002 19:50:50 +0100; Could you please elaborate on what exactly it means to enable/disable this item? (Other than possibly making XFS smaller.) Thanks. -- Verkaufe Original-BMW-Raeder: L I N U X .~. http://adsl-bergs.rz.; /archives/xfs/2002-01/msg00841.html (10,736 bytes)
3. on xfs added to filemap.c (score: 1): Author: xxxxxxxxxxxx>; Date: 29 Jan 2002 13:09:17 -0600; XFS has two directory formats, V1 directories were the original, V2 was a new version written to fix problems with NFS and a few other apps. Linux always uses V2, the V1 is there for Irix compatibili; /archives/xfs/2002-01/msg00842.html (11,711 bytes)
4. s on large h/w RAID fails (score: 1): Author: xxxxxxxxxxxx>; Date: Tue, 29 Jan 2002 20:25:09 +0100; Oops. The patch had a silly mistake. The dep_mbools were missing the third parameter. It wasn't noticed by make oldconfig, but the more advanced configurators notice. Here is an update. Should probab; /archives/xfs/2002-01/msg00844.html (15,765 bytes)
5. ilemap.c (score: 1): Author: xxxxxxxxxxxx>; Date: 29 Jan 2002 13:56:41 -0600; Yep, I just saw that. And FWIW, the stated limit for the filesystem size w/o XFS_BIG_FILESYSTEMS isn't quite right*. I think these are correct (these are internal XFS limitations): File size: o Witho; /archives/xfs/2002-01/msg00846.html (12,070 bytes)
6. on xfs added to filemap.c (score: 1): Author: deen@xxxxxxx>; Date: Tue, 29 Jan 2002 20:56:53 +0100; I have a few questions. Is xfs using less 64bit arithmetics when compiled without XFS_BIG_FILESYSTEMS and/or XFS_BIG_FILES? I think this will save some cpu cyles on x86. What happends with old files; /archives/xfs/2002-01/msg00847.html (16,908 bytes)
7. on xfs added to filemap.c (score: 1): Author: s@xxxxxxxxxx>; Date: 29 Jan 2002 14:09:53 -0600; I have this same question, I'll do some benchmarking to find out. size checks kick in, and you won't be able to seek/truncate/read/write past the smaller value. -Eric -- Eric Sandeen XFS for Linux ht; /archives/xfs/2002-01/msg00848.html (10,536 bytes)
8. on xfs added to filemap.c (score: 1): Author: deen@xxxxxxx>; Date: Tue, 29 Jan 2002 21:17:58 +0100; I misread blockno in xfs_types.h as byteno. It should be 2^31 * blocksize, which would be 2^43 with 4K blocks or more with bigger block size. I don't see any other limit. How do you get to 2^40 ? Als; /archives/xfs/2002-01/msg00849.html (17,100 bytes)
9. on xfs added to filemap.c (score: 1): Author: <ak@xxxxxxx>; Date: Tue, 29 Jan 2002 21:28:04 +0100; [...] So with Andi's patch one should NOT enable V1 directories, or otherwise the XFS code can't read existing V2 filesystems anymore? Is that right? Thanks. -- Verkaufe Original-BMW-Raeder: L I N U; /archives/xfs/2002-01/msg00850.html (11,426 bytes)
10. s on large h/w RAID fails (score: 1): Author: deen@xxxxxxx>; Date: 29 Jan 2002 14:42:12 -0600; in xfs_inode.h: define XFS_MAX_FILE_OFFSET ((long long)((1ULL<<(32+PAGE_SHIFT))-1ULL)) define XFS_MAX_FILE_OFFSET ((1LL<<40)-1LL) and XFS_MAX_FILE_OFFSET is used to set sb->s_maxbytes (the latter cas; /archives/xfs/2002-01/msg00853.html (12,643 bytes)
11. on xfs added to filemap.c (score: 1): Author: deen@xxxxxxx>; Date: 29 Jan 2002 14:41:10 -0600; Noooo, I think you got your 1s and 2s crossed in there. Andi was turning off the backwards compatibility with old irix filesystems (V1) in the patch. It is not exactly a huge win spacewise, but every; /archives/xfs/2002-01/msg00854.html (12,549 bytes)
12. on xfs added to filemap.c (score: 1): Author: lord@xxxxxxx>; Date: 29 Jan 2002 14:46:11 -0600; No, with Andi's patch, you can turn V1 on and off, but V2 is always there. Oh, also, I don't think Andi's patch quite works. There are dir2 functions that call code in xfs_dir.c - which is not linked; /archives/xfs/2002-01/msg00855.html (11,445 bytes)
13. on xfs added to filemap.c (score: 1): Author: deen@xxxxxxx>; Date: Tue, 29 Jan 2002 21:56:19 +0100; The 'int' is embedded in the block device interface in 2.4. It applies to the filesystem, not the files (but will hopefully change with the 64bit sector_t in 2.5/bio) If you're sure that XFS doesn't; /archives/xfs/2002-01/msg00856.html (14,119 bytes)
14. ion" (score: 1): Author: ie@xxxxxxxxx>; Date: Wed, 30 Jan 2002 01:08:58 +0100; I loaded a module, but it looks it was the old module. I see I missed xfs_dir_startup. Oops. Here is the updated patch. I think it's not my day today, too many mistakes. Please double check it that I; /archives/xfs/2002-01/msg00860.html (17,662 bytes)
15. hould an xfs_freeze take? (score: 1): Author: xxxxxxxxxxxx>; Date: Wed, 30 Jan 2002 08:19:51 +0100; [...] XFS Oh, sorry, stupid me. :-) Thanks for setting this straight. -- Verkaufe Original-BMW-Raeder: L I N U X .~. http://adsl-bergs.rz.rwth-aachen.de/~rabe The Choice /V\ of a GNU /( )\ Generation; /archives/xfs/2002-01/msg00864.html (11,674 bytes)
16. FS bug with ftruncate, mmap and holes. (score: 1): Author: ou <austin@xxxxxxxxxxxxxxx>; Date: Tue, 29 Jan 2002 19:40:01 +0100; This patch does it. It's very simple and clean. Saves another 18K on a xfs with BIG_FILESYSTEMS and BIG_FILES disabled. For completeness I also added BIG_FILES and BIG_FILESYSTEMS as visible CONFIG o; /archives/xfs/2002-01/msg01768.html (16,204 bytes)
17. s Re: TAKE - remove a function xfs added to filemap.c (score: 1): Author: c Sandeen <sandeen@xxxxxxx>; Date: Tue, 29 Jan 2002 19:50:50 +0100; Could you please elaborate on what exactly it means to enable/disable this item? (Other than possibly making XFS smaller.) Thanks. -- Verkaufe Original-BMW-Raeder: L I N U X .~. http://adsl-bergs.rz.; /archives/xfs/2002-01/msg01770.html (10,736 bytes)
18. XFS footprint (was Re: TAKE - remove a function xfs added to filemap.c (score: 1): Author: ergs" <rabe@xxxxxxxxxxxxxx>; Date: 29 Jan 2002 13:09:17 -0600; XFS has two directory formats, V1 directories were the original, V2 was a new version written to fix problems with NFS and a few other apps. Linux always uses V2, the V1 is there for Irix compatibili; /archives/xfs/2002-01/msg01771.html (11,711 bytes)
19. e a function xfs added to filemap.c (score: 1): Author: eith_m@xxxxxxxxxxxxxxxxxxx>; Date: Tue, 29 Jan 2002 20:25:09 +0100; Oops. The patch had a silly mistake. The dep_mbools were missing the third parameter. It wasn't noticed by make oldconfig, but the more advanced configurators notice. Here is an update. Should probab; /archives/xfs/2002-01/msg01773.html (15,765 bytes)
20. as Re: TAKE - remove a function xfs added to filemap.c (score: 1): Author: ck" <gnydick@xxxxxxxxxxxxx>; Date: 29 Jan 2002 13:56:41 -0600; Yep, I just saw that. And FWIW, the stated limit for the filesystem size w/o XFS_BIG_FILESYSTEMS isn't quite right*. I think these are correct (these are internal XFS limitations): File size: o Witho; /archives/xfs/2002-01/msg01775.html (12,070 bytes)

Current List: 1 - 20
Page: [1] [2] [3]