linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>,
	Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs updates
Date: Mon, 05 Dec 2011 16:10:49 +0800	[thread overview]
Message-ID: <4EDC7C89.6050803@cn.fujitsu.com> (raw)
In-Reply-To: <20111201153955.GL5587@shiny>

Hi, Chris and Oliva

On thu, 1 Dec 2011 10:39:55 -0500, Chris Mason wrote:
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
> 
> Has our current set of fixes.  This is fairly small, Alexandre Oliva has
> been chasing problems in our block allocator and kicked out important
> fixes.
> 
> Jan Schmidt fixed a merge error in the raid repair code, we're now
> properly repairing failed blocks (io errors or crc errors) without
> having to run a scrub.
> 
> Alexandre Oliva (5) commits (+8/-8):
>     Btrfs: skip block groups without enough space for a cluster (+1/-1)

This patch introduce a bug that we can not allocate blocks from the cluster
with enough space and it may make the block allocation fail.

This is because the check that the above patch introduced make the allocator
skip the cluster allocation, and jump to the uncluster allocation without
reclaiming all the blocks in the cluster, At this time, if all the free space
is in the cluster, and no space in the block group, the allocation will fail.
(we can trigger this bug on SSD.)

Fortunately, the following patch written by Oliva can fix this bug.

[PATCH 08/20] Btrfs: try to allocate from cluster even at LOOP_NO_EMPTY_SIZE

Thanks
Miao

>     Btrfs: start search for new cluster at the beginning (+2/-4)
>     Btrfs: reset cluster's max_size when creating bitmap (+1/-0)
>     Btrfs: skip allocation attempt from empty cluster (+3/-3)
>     Btrfs: initialize new bitmaps' list (+1/-0)
> 
> Li Zefan (1) commits (+3/-3):
>     Btrfs: fix oops when calling statfs on readonly device
> 
> Arnd Hannemann (1) commits (+2/-2):
>     Fix URL of btrfs-progs git repository in docs
> 
> Jan Schmidt (1) commits (+20/-7):
>     Btrfs: fix meta data raid-repair merge problem
> 
> Dan Carpenter (1) commits (+5/-0):
>     btrfs scrub: handle -ENOMEM from init_ipath()
> 
> Mike Fleetwood (1) commits (+1/-1):
>     Btrfs: Don't error on resizing FS to same size
> 
> Miao Xie (1) commits (+22/-5):
>     Btrfs: fix deadlock on metadata reservation when evicting a inode
> 
> Total: (11) commits (+60/-25)
> 
>  Documentation/filesystems/btrfs.txt |    4 ++--
>  fs/btrfs/ctree.h                    |    3 +++
>  fs/btrfs/extent-tree.c              |   34 +++++++++++++++++++++++-----------
>  fs/btrfs/extent_io.c                |   27 ++++++++++++++++++++-------
>  fs/btrfs/free-space-cache.c         |    2 ++
>  fs/btrfs/inode.c                    |    2 +-
>  fs/btrfs/ioctl.c                    |    2 +-
>  fs/btrfs/scrub.c                    |    5 +++++
>  fs/btrfs/super.c                    |    6 +++---
>  9 files changed, 60 insertions(+), 25 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2011-12-05  8:10 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 15:39 [GIT PULL] Btrfs updates Chris Mason
2011-12-05  8:10 ` Miao Xie [this message]
2011-12-05 13:14   ` Chris Mason
2011-12-05 14:08     ` David Sterba
2011-12-06  3:25     ` Miao Xie
  -- strict thread matches above, loose matches on Subject: below --
2013-05-18 14:30 Chris Mason
2013-03-29 17:47 Chris Mason
2013-03-09  0:38 Chris Mason
2013-02-16  1:55 Chris Mason
2012-12-17 21:44 Chris Mason
2012-12-19 18:09 ` Roy Sigurd Karlsbakk
2012-12-19 19:07   ` Hugo Mills
2012-12-17 21:28 Chris Mason
2012-08-29 16:01 Chris Mason
2012-07-05 19:55 Chris Mason
2012-06-21 15:47 Chris Mason
2012-06-15 18:09 Chris Mason
2012-06-15 23:57 ` Linus Torvalds
2012-06-16  0:21   ` Chris Mason
2012-06-01 13:18 Chris Mason
2012-04-13 13:38 Chris Mason
2012-04-16  1:19 ` Tsutomu Itoh
2012-03-10  2:01 Chris Mason
2012-02-24 16:41 Chris Mason
2011-08-18 18:04 Chris Mason
2011-08-18 21:51 ` Sage Weil
2011-08-20 14:01   ` Chris Mason
2011-07-27 22:46 Chris Mason
2011-06-27 18:15 Chris Mason
2011-06-20  1:12 Chris Mason
2011-06-12 11:57 Chris Mason
2011-06-12 18:08 ` Linus Torvalds
2011-06-13  1:02 ` Andi Kleen
2011-06-13  1:52   ` Chris Mason
2011-06-13  2:05   ` Li Zefan
2011-06-04 14:37 Chris Mason
2011-05-27 19:55 Chris Mason
2011-05-27 21:44 ` Chester
2011-05-15 14:47 Chris Mason
2011-05-15 15:41 ` kehon
2011-04-26 14:24 Chris Mason
2011-04-18 14:26 Chris Mason
2011-02-15  3:49 Chris Mason
2011-02-07 20:12 Chris Mason
2011-02-08 20:05 ` Helmut Hullen
2011-01-17 21:13 Chris Mason
2011-01-18 10:14 ` Felix Blanke
2011-01-18 15:22   ` C Anthony Risinger
2011-01-18 17:56     ` Mitch Harder
2011-01-18 18:51       ` C Anthony Risinger
2011-01-19  9:15     ` Spelic
2011-01-22 23:41       ` Clemens Eisserer
2011-01-22 23:53         ` cwillu
2011-01-18 18:55   ` Goffredo Baroncelli
2011-03-09 22:01 ` Diego Calleja
2010-12-14  1:54 Chris Mason
2010-05-27 15:15 Chris Mason
2010-05-27 17:18 ` Linus Torvalds
2010-05-27 17:32   ` Chris Mason
2010-05-27 17:47     ` Linus Torvalds
2010-06-02  2:59 ` Miao Xie
2010-09-12 12:38 ` Felipe Contreras
2010-04-05 19:36 Chris Mason
2010-04-06 15:40 ` Chris Mason
2010-03-15 19:18 Chris Mason
2010-03-16 21:01 ` Chris Mason
2010-03-18 16:59   ` Chris Mason
2009-10-15  0:06 Chris Mason

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=4EDC7C89.6050803@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=oliva@lsd.ic.unicamp.br \
    /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).