| To: | éåå <baotiao@xxxxxxxxx> |
|---|---|
| Subject: | Re: XFS: possible memory allocation deadlock in kmem_alloc |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Tue, 31 May 2016 13:10:10 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAGbZs7i66XWt3PF1_-L-WeBtdH80nfAOv+-Ary+ORKHxFGOLFg@xxxxxxxxxxxxxx> |
| References: | <AD1240BA-DB24-44F2-893D-28A824063F99@xxxxxxxxx> <20160530050452.GM26977@dastard> <9BD371B3-8A44-481C-B9E4-381BAE0B6B79@xxxxxxxxx> <CAGbZs7i66XWt3PF1_-L-WeBtdH80nfAOv+-Ary+ORKHxFGOLFg@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: shrink_active_list/try_to_release_page bug? (was Re: xfs trace in 4.4.2 / also in 4.3.3 WARNING fs/xfs/xfs_aops.c:1232 xfs_vm_releasepage), Dave Chinner |
|---|---|
| Next by Date: | Re: shrink_active_list/try_to_release_page bug? (was Re: xfs trace in 4.4.2 / also in 4.3.3 WARNING fs/xfs/xfs_aops.c:1232 xfs_vm_releasepage), Minchan Kim |
| Previous by Thread: | Re: XFS: possible memory allocation deadlock in kmem_alloc, éåå |
| Next by Thread: | Re: XFS: possible memory allocation deadlock in kmem_alloc, éåå |
| Indexes: | [Date] [Thread] [Top] [All Lists] |