XFS: possible memory allocation deadlock in kmem_alloc

[陈宗志]

can we change the existing file's extent size?


On Tue, May 31, 2016 at 11:10 AM, Dave Chinner <david at fromorbit.com> 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
> david at fromorbit.com
>



-- 
---
Blog: http://www.chenzongzhi.info
Twitter: https://twitter.com/baotiao <https://twitter.com/#%21/baotiao>
Git: https://github.com/baotiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20160531/0bef6472/attachment.html>