From: Sergei Trofimovich <slyich@gmail.com>
To: Sergei Trofimovich <slyich@gmail.com>
Cc: liubo <liubo2009@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org, Josef Bacik <josef@redhat.com>,
Arne Jansen <sensille@gmx.net>
Subject: Re: [PATCH] Btrfs: fix easily get into ENOSPC in mixed case
Date: Sat, 9 Apr 2011 00:19:20 +0300 [thread overview]
Message-ID: <20110409001920.089c4409@sf> (raw)
In-Reply-To: <20110409000932.6154c7b5@sf>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
> > When a btrfs disk is created by mixed data & metadata option, it will have no
> > pure data or pure metadata space info.
> >
> > In btrfs's for-linus branch, commit 78b1ea13838039cd88afdd62519b40b344d6c920
> > (Btrfs: fix OOPS of empty filesystem after balance) initializes space infos at
> > the very beginning. The problem is this initialization does not take the mixed
> > case into account, which will cause btrfs will easily get into ENOSPC in mixed
> > case.
> >
> > Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com>
> > ---
>
> Tried to apply this patch on top of 2.6.39-rc2 and booted on the same partition.
> It has 3.2 GBs free. With patch it started to report -ENOSPC right out.
> Attempt to delete some files caused OOps:
Sorry, I was too fast. The same OOps is reproducible on vanilla 2.6.39-rc2. Will retest on 2.6.39-rc1.
--
Sergei
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-04-08 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 9:19 2.6.39-rc1: kernel BUG at fs/btrfs/extent-tree.c:5479! Sergei Trofimovich
2011-04-02 9:37 ` liubo
2011-04-02 10:41 ` Sergei Trofimovich
2011-04-02 11:30 ` liubo
2011-04-02 12:55 ` Sergei Trofimovich
2011-04-08 8:44 ` [PATCH] Btrfs: fix easily get into ENOSPC in mixed case liubo
2011-04-08 21:09 ` Sergei Trofimovich
2011-04-08 21:19 ` Sergei Trofimovich [this message]
2011-04-08 21:55 ` Sergei Trofimovich
2011-04-11 6:29 ` liubo
2011-04-11 20:27 ` Sergei Trofimovich
2011-04-19 21:55 ` Sergei Trofimovich
2011-04-21 15:19 ` Sergei Trofimovich
2011-04-22 19:43 ` Sergei Trofimovich
2011-05-05 14:44 ` Sergei Trofimovich
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=20110409001920.089c4409@sf \
--to=slyich@gmail.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.com \
--cc=sensille@gmx.net \
/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).