Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Increasing\s+number\s+of\s+inodes\s+after\s+format\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Increasing\s+number\s+of\s+inodes\s+after\s+format\?\s*$/: 9 ]

Total 9 documents matching your query.

1. Re: Increasing number of inodes after format? (score: 1): Author: ans@xxxxxxx>; Date: Wed, 9 Jun 2004 10:32:52 +1000; XFS does dynamic inode allocation, there is no preallocated set. Steve also recently implemented dynamic space reclaim for ondisk inode clusters too, once they're no longer used. XFS puts a cap on th; /archives/xfs/2004-06/msg00071.html (8,461 bytes)
2. Re: Increasing number of inodes after format? (score: 1): Author: x>; Date: Wed, 9 Jun 2004 09:15:39 +0200 (CEST); Sorry, I'd like to understand the following: - XFS does allocate (automagically) more inode as needed by the File Systems; or - a explicit "xfs_growfs" command (to enlarge the FS) is required? Thank; /archives/xfs/2004-06/msg00074.html (9,236 bytes)
3. Re: Increasing number of inodes after format? (score: 1): Author: xxxxxxx>; Date: Wed, 9 Jun 2004 18:22:14 +1000; Both. :) See mkfs.xfs(8)... The option maxpct=value specifies the maximum percentage of space in the filesystem that can be allocated to inodes. The default value is 25%. Setting the value to 0 means; /archives/xfs/2004-06/msg00076.html (8,591 bytes)
4. Re: Increasing number of inodes after format? (score: 1): Author: ndeen <sandeen@xxxxxxx>; Date: Wed, 9 Jun 2004 10:32:52 +1000; XFS does dynamic inode allocation, there is no preallocated set. Steve also recently implemented dynamic space reclaim for ondisk inode clusters too, once they're no longer used. XFS puts a cap on th; /archives/xfs/2004-06/msg00357.html (8,461 bytes)
5. Re: Increasing number of inodes after format? (score: 1): Author: ninja@xxxxxxx>; Date: Wed, 9 Jun 2004 09:15:39 +0200 (CEST); Sorry, I'd like to understand the following: - XFS does allocate (automagically) more inode as needed by the File Systems; or - a explicit "xfs_growfs" command (to enlarge the FS) is required? Thank; /archives/xfs/2004-06/msg00360.html (9,236 bytes)
6. Re: Increasing number of inodes after format? (score: 1): Author: ns@xxxxxxx>; Date: Wed, 9 Jun 2004 18:22:14 +1000; Both. :) See mkfs.xfs(8)... The option maxpct=value specifies the maximum percentage of space in the filesystem that can be allocated to inodes. The default value is 25%. Setting the value to 0 means; /archives/xfs/2004-06/msg00362.html (8,591 bytes)
7. Re: Increasing number of inodes after format? (score: 1): Author: Nathan Scott <nathans@xxxxxxx>; Date: Wed, 9 Jun 2004 10:32:52 +1000; XFS does dynamic inode allocation, there is no preallocated set. Steve also recently implemented dynamic space reclaim for ondisk inode clusters too, once they're no longer used. XFS puts a cap on th; /archives/xfs/2004-06/msg00643.html (8,607 bytes)
8. Re: Increasing number of inodes after format? (score: 1): Author: roberto@xxxxxxxx; Date: Wed, 9 Jun 2004 09:15:39 +0200 (CEST); Sorry, I'd like to understand the following: - XFS does allocate (automagically) more inode as needed by the File Systems; or - a explicit "xfs_growfs" command (to enlarge the FS) is required? Thank; /archives/xfs/2004-06/msg00646.html (9,350 bytes)
9. Re: Increasing number of inodes after format? (score: 1): Author: Nathan Scott <nathans@xxxxxxx>; Date: Wed, 9 Jun 2004 18:22:14 +1000; Both. :) See mkfs.xfs(8)... The option maxpct=value specifies the maximum percentage of space in the filesystem that can be allocated to inodes. The default value is 25%. Setting the value to 0 means; /archives/xfs/2004-06/msg00648.html (8,766 bytes)

Current List: 1 - 9
Page: [1]