Re: Reducing memory requirements for high extent xfs files

[Vlad Apostolov <vapo@sgi.com>]

Vlad Apostolov wrote:

No, Dave is right. The example worked because the extent hint was the 
same size
as the filesystem block.

Regards,
Vlad
>>
>> Note - i don't think extent size hints alone will help as they
>> don't prevent EOF truncation on close.
> Dave,
>
> I think extent hint should help in this situation. Here is an example
> of writing 4 chars in a file with extent hint of 16Kb. The file ends
> up with size of 4 and 8 basic blocks (512 bytes each) allocation in
> one extent.
>
> emu:/mnt/scratch1/temp # xfs_io -c "extsize 16384" -f foo
> emu:/mnt/scratch1/temp # ls -al foo
> -rw------- 1 root root 0 2007-06-06 12:33 foo
> emu:/mnt/scratch1/temp # xfs_bmap -l -v foo
> foo: no extents
> emu:/mnt/scratch1/temp # echo "abc" > foo
> emu:/mnt/scratch1/temp # ls -al foo
> -rw------- 1 root root 4 2007-06-06 12:35 foo
> emu:/mnt/scratch1/temp # xfs_bmap -l -v foo
> foo:
> EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL
> 0: [0..7]: 326088..326095 0 (326088..326095) 8
>
> Just a warning that the extent hint works at the moment only for
> contiguous files. There are problems for sparse files (with holes)
> and extent hint.
>
> Regards,
> Vlad
>