From: 陈宗志 <baotiao@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS: possible memory allocation deadlock in kmem_alloc
Date: Tue, 31 May 2016 10:43:36 +0800 [thread overview]
Message-ID: <CAGbZs7i66XWt3PF1_-L-WeBtdH80nfAOv+-Ary+ORKHxFGOLFg@mail.gmail.com> (raw)
In-Reply-To: <9BD371B3-8A44-481C-B9E4-381BAE0B6B79@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1670 bytes --]
I have fint the way to change the extent size hint
mkfs.xfs -r extsize=40960 /dev/sda1
but I should rebuild the disk, do you have a way more smooth?
On Mon, May 30, 2016 at 4:48 PM, baotiao <baotiao@gmail.com> wrote:
> how can I set the extent size hint to a file with command line?
> I have google for a lot, but I can't find a answer
>
> ----------------------------------------
>
> Github: https://github.com/baotiao
> Blog: http://baotiao.github.io
> Stackoverflow: http://stackoverflow.com/users/634415/baotiao
> Linkedin: http://www.linkedin.com/profile/view?id=145231990
>
> On May 30, 2016, at 13:04, Dave Chinner <david@fromorbit.com> wrote:
>
> On Mon, May 30, 2016 at 12:45:07PM +0800, baotiao wrote:
>
> This machine is running for qemu, the file is qemu qcow file type
>
> [root@w-openstack20
> /data/nova/instances/7898b630-c4ef-49ab-9ce9-3735e090c282]# file disk
> disk: QEMU QCOW Image (v3), has backing file (path
> /data/nova/instances/_base/3f27393376152ac352b2d85703011e38517e),
> 429496729600 bytes
>
>
> Oh, you're using delta/snapshot based qcow images. That, by it's
> very nature, generates fragmented image files as they are a delta
> over the backing file.
>
> ....
>
> actual 48421430, ideal 20716, fragmentation factor 99.96%
>
> How can I solve this problem, what do you suggest me to do?
>
>
> Use a extent size hint (say 1-8MB) for your qcow2 image files so that
> they don't fragment badly as they are written to.
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
>
>
>
--
---
Blog: http://www.chenzongzhi.info
Twitter: https://twitter.com/baotiao <https://twitter.com/#%21/baotiao>
Git: https://github.com/baotiao
[-- Attachment #1.2: Type: text/html, Size: 3913 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-05-31 2:43 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 ` 陈宗志 [this message]
2016-05-31 3:10 ` Dave Chinner
2016-05-31 11:00 ` 陈宗志
2016-05-31 12:14 ` Carlos Maiolino
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=CAGbZs7i66XWt3PF1_-L-WeBtdH80nfAOv+-Ary+ORKHxFGOLFg@mail.gmail.com \
--to=baotiao@gmail.com \
--cc=david@fromorbit.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).