Hi, Dave,
Thanks for the answer, it's great, and I apologize for the terrible format.
>You can't, directly. If you have enough contiguous free space in the
>AG that you are allocating in, then you will get contiguous files if
>the allocation size lines up with the filesystem geometry:
>
>$ for i in `seq 1 10` ; do sudo xfs_io -f -c "truncate 512m" -c "resvsp 0 512m" foo.$i ; done
>$ sudo xfs_bmap -vp foo.[1-9] foo.10 |grep " 0:"
> EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL FLAGS
> sudo xfs_bmap -vp foo.[1-9] foo.10 |grep " 0:"
> 0: [0..1048575]: 8096..1056671 0 (8096..1056671) 1048576 10000
> 0: [0..1048575]: 1056672..2105247 0 (1056672..2105247) 1048576 10000
> 0: [0..1048575]: 2105248..3153823 0 (2105248..3153823) 1048576 10000
> 0: [0..1048575]: 3153824..4202399 0 (3153824..4202399) 1048576 10000
> 0: [0..1048575]: 4202400..5250975 0 (4202400..5250975) 1048576 10000
> 0: [0..1048575]: 5250976..6299551 0 (5250976..6299551) 1048576 10000
> 0: [0..1048575]: 6299552..7348127 0 (6299552..7348127) 1048576 10000
> 0: [0..1048575]: 7348128..8396703 0 (7348128..8396703) 1048576 10000
> 0: [0..1048575]: 8396704..9445279 0 (8396704..9445279) 1048576 10000
> 0: [0..1048575]: 9445280..10493855 0 (9445280..10493855) 1048576 10000
>
>So all those files are contiguous both internally and externally. If
>there isn't sufficient contiguous freespace, or there is allocator
>contention, this won't happen - it's best effort behaviour....
I believe you got these in a single AG, but I do the allocation in filesystem
with multi-AGs, specifically, it is a 6T storage space, and I run the mkfs.xfs
without setting the AG number/size, it ends up with 32 AGs.
My files layout:
- 0 - dir
| - 0 - dir
| | - 1 - file
| | - 2 - file
| | - 3 - file
| | - 4 - file
| | - 5 - file
| | - ... - file
| | - 128 - file
| - 1 - dir
| | - 1 - file
| | - 2 - file
| | - 3 - file
| | - 4 - file
| | - 5 - file
| | - ... - file
| | - 128 - file
| - ... - dir
Every file is 512MB, every directory holds 512MB*128=64GB.
According to your advice and XFS document, I tried to set the AG size to 64GB,
for avoiding the allocator contention and keeping all files in single directory
fall in the same AG, but it didn't work. The files are still in different AGs.
My xfs_info:
meta-data="" isize=256 agcount=96, agsize=16777216 blks
= sectsz=512 attr=0
data = bsize=4096 blocks=1610116329, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=1
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0
The files:
$ for i in `seq 1 10` ; do sudo xfs_io -f -c "truncate 512m" -c "resvsp 0 512m" foo.$i ; done
$ sudo xfs_bmap -vp *| grep " 0:"
0: [0..1048575]: 2147483712..2148532287 16 (64..1048639) 1048576 10000
0: [0..1048575]: 3355443264..3356491839 25 (64..1048639) 1048576 10000
0: [0..1048575]: 2281701440..2282750015 17 (64..1048639) 1048576 10000
0: [0..1048575]: 2415919168..2416967743 18 (64..1048639) 1048576 10000
0: [0..1048575]: 2550136896..2551185471 19 (64..1048639) 1048576 10000
0: [0..1048575]: 2684354624..2685403199 20 (64..1048639) 1048576 10000
0: [0..1048575]: 2818572352..2819620927 21 (64..1048639) 1048576 10000
0: [0..1048575]: 2952790080..2953838655 22 (64..1048639) 1048576 10000
0: [0..1048575]: 3087007808..3088056383 23 (64..1048639) 1048576 10000
0: [0..1048575]: 3221225536..3222274111 24 (64..1048639) 1048576 10000
Any way I can specify which AG a file should be allocated?
Again, Thanks for your time.
On Wed, Nov 7, 2012 at 11:19 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
On Wed, Nov 07, 2012 at 09:02:11AM +0800, huubby zhou wrote:> I'm using *CentOS5.8*, with *XFS* filesystem extend storage disks. What I
> Hi, folks,
>
> want to do is, pre-allocating many files, with continuous blocks in> I could do space pre-allocation by *posix_allocate()*, problem is the API
> filesystem, both single file and crossing files. That is the start block ID
> of the next file is following the end block ID of current file.
>
> zeros all disk space, I can't afford time consuming(I'm not sure if thisit doesn't on more recent releases - it uses fallocate() in the back
> API could make the blocks continuous).
end, which does the same as:
> then I tried
> *xfsctl()*<http://linux.die.net/man/3/xfsctl>,
> with *XFS_IOC_RESVSP* flag, I can reserve space faster.
This command.
> The problem with *xfsctl()* is, it could make the blocks continuous for
> individual file, but the blocks over files are *not* continuous. For
> example, 10 files, a/b/c/d/e/f... reserved. After I do the real writing toYou can't, directly. If you have enough contiguous free space in the
> these files, it turns out the file 'b' isn't next to file 'a', and some
> file could be far from both previous one and next one, though other files
> may be neighboring with each other, rarely.
>
> I use the following code to do the pre-allocation:
>
> ftruncate(fd, FILE_SIZE);
>
> xfs_flock_t flag = {0};
> flag.l_whence = SEEK_SET;
> flag.l_start = 0;
> flag.l_len = 512*1024*1024;
> xfsctl(fileName, fd, XFS_IOC_RESVSP64, &flag);
>
> My question is, how can I guarantee the file system blocks over files
> continuous? Thanks for your time and appreciate your answer.
AG that you are allocating in, then you will get contiguous files if
the allocation size lines up with the filesystem geometry:
$ for i in `seq 1 10` ; do sudo xfs_io -f -c "truncate 512m" -c "resvsp 0 512m" foo.$i ; done
$ sudo xfs_bmap -vp foo.[1-9] foo.10 |grep " 0:"
EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL FLAGS
sudo xfs_bmap -vp foo.[1-9] foo.10 |grep " 0:"
0: [0..1048575]: 8096..1056671 0 (8096..1056671) 1048576 10000
0: [0..1048575]: 1056672..2105247 0 (1056672..2105247) 1048576 10000
0: [0..1048575]: 2105248..3153823 0 (2105248..3153823) 1048576 10000
0: [0..1048575]: 3153824..4202399 0 (3153824..4202399) 1048576 10000
0: [0..1048575]: 4202400..5250975 0 (4202400..5250975) 1048576 10000
0: [0..1048575]: 5250976..6299551 0 (5250976..6299551) 1048576 10000
0: [0..1048575]: 6299552..7348127 0 (6299552..7348127) 1048576 10000
0: [0..1048575]: 7348128..8396703 0 (7348128..8396703) 1048576 10000
0: [0..1048575]: 8396704..9445279 0 (8396704..9445279) 1048576 10000
0: [0..1048575]: 9445280..10493855 0 (9445280..10493855) 1048576 10000
So all those files are contiguous both internally and externally. If
there isn't sufficient contiguous freespace, or there is allocator
contention, this won't happen - it's best effort behaviour....
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
