All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Panteleev <git@thecybershadow.net>
To: linux-btrfs@vger.kernel.org
Cc: Vladimir Panteleev <git@thecybershadow.net>
Subject: [PATCH 0/1] btrfs: Add global_reserve_size mount option
Date: Sat, 10 Aug 2019 12:41:00 +0000	[thread overview]
Message-ID: <20190810124101.15440-1-git@thecybershadow.net> (raw)

Hi,

This is a follow-up to my previous thread titled ""kernel BUG" and
segmentation fault with "device delete"". Since my last message there,
I discovered that the problem I was seeing was solved merely by
increasing the size of the global reserve to 1G. I don't claim to have
anywhere near a complete understanding of btrfs, its implementation,
or the problem at hand, but I figured a bad patch is better than no
patch, so here's a patch which does allow working around my problem
without building a custom kernel. Or, if anyone has better ideas how
to understand or address this problem, I'd be happy to help or test
things.

Vladimir Panteleev (1):
  btrfs: Add global_reserve_size mount option

 fs/btrfs/block-rsv.c |  2 +-
 fs/btrfs/ctree.h     |  3 +++
 fs/btrfs/disk-io.c   |  1 +
 fs/btrfs/super.c     | 17 ++++++++++++++++-
 4 files changed, 21 insertions(+), 2 deletions(-)

-- 
2.22.0


             reply	other threads:[~2019-08-10 12:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-10 12:41 Vladimir Panteleev [this message]
2019-08-10 12:41 ` [PATCH 1/1] btrfs: Add global_reserve_size mount option Vladimir Panteleev
2019-08-12  8:37   ` Nikolay Borisov
2019-08-12 14:36     ` Vladimir Panteleev
2019-08-13  6:40       ` Nikolay Borisov

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=20190810124101.15440-1-git@thecybershadow.net \
    --to=git@thecybershadow.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.