From: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
To: Chris Mason <chris.mason@fusionio.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: (3.9-rc5) WARNING: at fs/btrfs/super.c:255 __btrfs_abort_transaction
Date: Thu, 04 Apr 2013 09:21:17 +0900 [thread overview]
Message-ID: <515CC77D.9040502@jp.fujitsu.com> (raw)
In-Reply-To: <20130403130541.27335.23925@localhost.localdomain>
On 2013/04/03 22:05, Chris Mason wrote:
> Quoting Tsutomu Itoh (2013-04-02 21:19:06)
>> Hi,
>>
>> When inode_cache was specified for the mount option, I encountered the
>> following messages at umount.
>>
>> Step to reproduce:
>>
>> mkfs.btrfs -f /dev/sdc4
>> mount -o compress=lzo,autodefrag,inode_cache /dev/sdc4 /test1
>> dd if=/dev/zero of=/test1/file1 bs=1M count=8192
>> dd if=/test1/file1 of=/dev/null bs=1M
>> rm -f /test1/file1
>> umount /test1
>> Apr 3 09:43:12 luna kernel: [ 554.639149] BTRFS error (device sdc4) in btrfs_save_ino_cache:471: error 28
>
> We're running out of space while saving the inode cache. Strictly
> speaking this should not abort the FS. I'll take a look.
Umm, 8GB was only written in the filesystem of 20GB...
When only inode_cache was specified for the mount option
('mount -o inode_cache /dev/sdc4 /test1'), the error message was not output.
Is this information useful for any investigations?
Thanks,
Tsutomu
next prev parent reply other threads:[~2013-04-04 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 1:19 (3.9-rc5) WARNING: at fs/btrfs/super.c:255 __btrfs_abort_transaction Tsutomu Itoh
2013-04-03 8:42 ` Tsutomu Itoh
2013-04-03 13:05 ` Chris Mason
2013-04-04 0:21 ` Tsutomu Itoh [this message]
[not found] <CAEct+bDZi1rzOPOL_Zeoi=fEPsyAen67OJ+t71K8VZy8BLYvVw@mail.gmail.com>
2013-04-07 11:55 ` Kurt Huwig
2013-04-09 12:01 ` David Sterba
2013-04-19 8:52 ` Anand Jain
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=515CC77D.9040502@jp.fujitsu.com \
--to=t-itoh@jp.fujitsu.com \
--cc=chris.mason@fusionio.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