From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id A40EB7CA2 for ; Tue, 31 May 2016 06:00:28 -0500 (CDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay1.corp.sgi.com (Postfix) with ESMTP id 61DF28F8033 for ; Tue, 31 May 2016 04:00:25 -0700 (PDT) Received: from mail-qk0-f178.google.com (mail-qk0-f178.google.com [209.85.220.178]) by cuda.sgi.com with ESMTP id LWhgK496emAMYaSF (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 31 May 2016 04:00:23 -0700 (PDT) Received: by mail-qk0-f178.google.com with SMTP id c140so7155898qke.2 for ; Tue, 31 May 2016 04:00:23 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20160531031010.GB12670@dastard> References: <20160530050452.GM26977@dastard> <9BD371B3-8A44-481C-B9E4-381BAE0B6B79@gmail.com> <20160531031010.GB12670@dastard> Date: Tue, 31 May 2016 19:00:22 +0800 Message-ID: Subject: Re: XFS: possible memory allocation deadlock in kmem_alloc From: =?UTF-8?B?6ZmI5a6X5b+X?= List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0737719996636041463==" Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: xfs@oss.sgi.com --===============0737719996636041463== Content-Type: multipart/alternative; boundary=94eb2c1249c686895a05342147cc --94eb2c1249c686895a05342147cc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable can we change the existing file's extent size? On Tue, May 31, 2016 at 11:10 AM, Dave Chinner wrote: > On Tue, May 31, 2016 at 10:43:36AM +0800, =E9=99=88=E5=AE=97=E5=BF=97 wro= te: > > I have fint the way to change the extent size hint > > mkfs.xfs -r extsize=3D40960 /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@fromorbit.com > --=20 --- Blog: http://www.chenzongzhi.info Twitter: https://twitter.com/baotiao Git: https://github.com/baotiao --94eb2c1249c686895a05342147cc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
can we change the existing file's extent size?

=

On Tue, May= 31, 2016 at 11:10 AM, Dave Chinner <david@fromorbit.com> = wrote:
On Tue, May 31, 2= 016 at 10:43:36AM +0800, =E9=99=88=E5=AE=97=E5=BF=97 wrote:
> I have fint the way to change the extent size hint
> mkfs.xfs -r extsize=3D40960 /dev/sda1

Ah, no, that isn't the extsize I'm refering to. That's f= or 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@fromorbit.com



--
--94eb2c1249c686895a05342147cc-- --===============0737719996636041463== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs --===============0737719996636041463==--