From: Carlos Maiolino <cmaiolino@redhat.com>
To: xfs@oss.sgi.com
Cc: baotiao@gmail.com
Subject: Re: XFS: possible memory allocation deadlock in kmem_alloc
Date: Tue, 31 May 2016 14:14:02 +0200 [thread overview]
Message-ID: <20160531121402.GA15274@redhat.com> (raw)
In-Reply-To: <CAGbZs7g9nfDFXKkhW-pgiVu1quRQDwMYxeAtLoky+xFcfx7WmQ@mail.gmail.com>
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@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
> [2]david@fromorbit.com
>
> --
> ---
> Blog: [3]http://www.chenzongzhi.info
> Twitter: [4]https://twitter.com/baotiao
> Git: [5]https://github.com/baotiao
>
> References
>
> 1. mailto:david@fromorbit.com
> 2. mailto:david@fromorbit.com
> 3. http://www.chenzongzhi.info/
> 4. https://twitter.com/#!/baotiao
> 5. https://github.com/baotiao
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
--
Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-05-31 12:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 4:45 XFS: possible memory allocation deadlock in kmem_alloc baotiao
2016-05-30 5:04 ` Dave Chinner
2016-05-30 8:48 ` baotiao
2016-05-30 9:20 ` Carlos Maiolino
2016-05-31 2:43 ` 陈宗志
2016-05-31 3:10 ` Dave Chinner
2016-05-31 11:00 ` 陈宗志
2016-05-31 12:14 ` Carlos Maiolino [this message]
2019-11-04 23:38 Chris Holcombe
2019-11-05 0:01 ` Darrick J. Wong
2019-11-05 0:31 ` Eric Sandeen
[not found] ` <CAC752AmahECFry9x=pvqDkwQUj1PEJjoWGa2KFG1uaTzT1Bbnw@mail.gmail.com>
2019-11-05 4:21 ` Eric Sandeen
2019-11-05 16:25 ` Chris Holcombe
2019-11-05 17:11 ` Eric Sandeen
2019-11-05 19:53 ` Chris Holcombe
2019-11-05 20:08 ` Eric Sandeen
[not found] ` <CAC752AnZ4biDGk6V17URQm5YVp=MwZBhiMH8=t733zaypxUsmA@mail.gmail.com>
2019-11-05 20:47 ` Eric Sandeen
[not found] ` <CAC752A=y9PMEQ1e4mXskha1GFeKXWi8PsdBW-nX40pgFCYp1Uw@mail.gmail.com>
2019-11-05 21:23 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160531121402.GA15274@redhat.com \
--to=cmaiolino@redhat.com \
--cc=baotiao@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).