Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: <fdmanana@kernel.org>
Cc: <linux-btrfs@vger.kernel.org>, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 0/2] Btrfs: fixes for an ENOSPC issue that left a fs unusable
Date: Fri, 13 Nov 2015 12:33:02 -0500	[thread overview]
Message-ID: <20151113173302.GB17545@ret.masoncoding.com> (raw)
In-Reply-To: <1447428032-1872-1-git-send-email-fdmanana@kernel.org>

On Fri, Nov 13, 2015 at 03:20:30PM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> The following pair of changes fix an issue observed in a production
> environment where any file operations done by a package manager failed
> with ENOSPC. Forcing a commit of the current transaction (through "sync")
> didn't help, a balance operation with the filters -dusage=0 didn't help
> either and the issue persisted even after rebooting the machine. There
> were many data blocks groups that were unused, but they weren't getting
> deleted by the cleaner kthread because whenever it tried to start a
> transaction to delete a block group it got -ENOSPC error, which it silently
> ignores (as it does for any other error).
> 
> So these just make sure we fallback to use the global reserve, if -ENOSPC
> is encountered through the standard allocation path, to delete block groups
> as we do already for inode unlink operations. Another issue fixed is hitting
> a BUG_ON() when removing a block group due to -ENSPC failure when creating
> the orphan item for its free space cache inode. This second issue has
> been reported by a few users in the mailing list and bugzilla (for example
> at http://www.spinics.net/lists/linux-btrfs/msg46070.html).
> 
> These changes are also available at:
> http://git.kernel.org/cgit/linux/kernel/git/fdmanana/linux.git/log/?h=integration-4.4

I like both of these.  I'll queue for after rc1.

-chris

  parent reply	other threads:[~2015-11-13 17:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 15:20 [PATCH 0/2] Btrfs: fixes for an ENOSPC issue that left a fs unusable fdmanana
2015-11-13 15:20 ` [PATCH 1/2] Btrfs: use global reserve when deleting unused block group after ENOSPC fdmanana
2015-11-13 15:20 ` [PATCH 2/2] Btrfs: fix the number of transaction units needed to remove a block group fdmanana
2015-11-13 17:33 ` Chris Mason [this message]
2015-11-13 23:57 ` [PATCH v2 0/2] Btrfs: fixes for an ENOSPC issue that left a fs unusable fdmanana
2015-11-13 23:57   ` [PATCH v2 1/2] Btrfs: use global reserve when deleting unused block group after ENOSPC fdmanana
2015-11-13 23:57   ` [PATCH v2 2/2] Btrfs: fix the number of transaction units needed to remove a block group fdmanana

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=20151113173302.GB17545@ret.masoncoding.com \
    --to=clm@fb.com \
    --cc=fdmanana@kernel.org \
    --cc=fdmanana@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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