On Tue, May 31, 2016 at 07:00:22PM +0800, éåå wrote:
> can we change the existing file's extent size?
>
No, you can only set extent hint size for empty files, or, more precisely for
files whose does not have allocated extents
> On Tue, May 31, 2016 at 11:10 AM, Dave Chinner <[1]david@xxxxxxxxxxxxx>
> wrote:
>
> On Tue, May 31, 2016 at 10:43:36AM +0800, éåå wrote:
> > I have fint the way to change the extent size hint
> > mkfs.xfs -r extsize=40960 /dev/sda1
> Ah, no, that isn't the extsize I'm refering to. That's for realtime
> device configuration at mkfs, not a per-inode extent size hint.
> When you create the image file do this:
> $ xfs_io -f -c "extsize 1m" /path/to/new/vm_image
> $ qemu-image create -f qcow2 /path/to/new/vm_image 10g
> $ xfs_io -c extsize /path/to/new/vm_image
> [1048576] /path/to/new/vm_image
> $
> And now the qcow2 image file will have extents allocated in
> multiples of 1MB.
>
> Cheers,
> Dave.
> --
> Dave Chinner
> [2]david@xxxxxxxxxxxxx
>
> --
> ---
> Blog: [3]http://www.chenzongzhi.info
> Twitter: [4]https://twitter.com/baotiao
> Git: [5]https://github.com/baotiao
>
> References
>
> 1. mailto:david@xxxxxxxxxxxxx
> 2. mailto:david@xxxxxxxxxxxxx
> 3. http://www.chenzongzhi.info/
> 4. https://twitter.com/#!/baotiao
> 5. https://github.com/baotiao
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
--
Carlos
|