From: Arnd Hannemann <arnd@arndnet.de>
To: dave@jikos.cz
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 3.4.0-rc6: WARNING: at fs/btrfs/super.c:219 __btrfs_abort_transaction+0xae/0xc0 [btrfs]()
Date: Mon, 14 May 2012 18:16:33 +0200 [thread overview]
Message-ID: <4FB12FE1.2070909@arndnet.de> (raw)
In-Reply-To: <20120514150509.GJ25501@twin.jikos.cz>
Hello David,
Am 14.05.2012 17:05, schrieb David Sterba:
> On Mon, May 14, 2012 at 03:18:46PM +0200, Arnd Hannemann wrote:
>> I just got the following warning on a compressed btrfs filesystem, while writing on it
>> until no remaining space was available.
>> Looks like a bit verbose "disk full" message, is it expected behavior?
>
> Shouldn't be the case for regular ENOSPC (ie. when the space is reserved
> in advance and with the possibility to fail early). If the transaction
> is aborted, it means it's too late and there was some logic error.
>
> Can you please describe more the fs and how did you fill it? Like single
> process or multiple, dd or whatever.
the particular filesystem is used for chroots (/opt/chroots). It got full while
installing texlive-extra on a debian squeeze (i386) chroot.
It was probably a single process, but it involed a lot of small files.
Best regards
Arnd
next prev parent reply other threads:[~2012-05-14 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 13:18 3.4.0-rc6: WARNING: at fs/btrfs/super.c:219 __btrfs_abort_transaction+0xae/0xc0 [btrfs]() Arnd Hannemann
2012-05-14 13:18 ` Arnd Hannemann
2012-05-14 15:05 ` David Sterba
2012-05-14 16:16 ` Arnd Hannemann [this message]
2012-05-17 9:06 ` Martin Mailand
2012-05-22 16:07 ` Arnd Hannemann
2012-06-25 16:12 ` 3.5.0-rc4: WARNING: at fs/btrfs/super.c:221 __btrfs_abort_transaction+0xae/0xc0 (was: Re: 3.4.0-rc6:...) Arnd Hannemann
2012-05-15 1:39 ` 3.4.0-rc6: WARNING: at fs/btrfs/super.c:219 __btrfs_abort_transaction+0xae/0xc0 [btrfs]() Liu Bo
2012-05-15 1:39 ` Liu Bo
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=4FB12FE1.2070909@arndnet.de \
--to=arnd@arndnet.de \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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.