From: Stefan Behrens <sbehrens@giantdisaster.de>
To: dsterba@suse.cz, George Amvrosiadis <gamvrosi@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: filebench varmail + scrubber = btrfs_update_root bug
Date: Tue, 16 Jul 2013 15:25:26 +0200 [thread overview]
Message-ID: <51E549C6.1090303@giantdisaster.de> (raw)
In-Reply-To: <20130716113745.GI24343@twin.jikos.cz>
On Tue, 16 Jul 2013 13:37:45 +0200, David Sterba wrote:
> On Mon, Jul 15, 2013 at 12:56:29AM -0400, George Amvrosiadis wrote:
>> I'm trying to run the varmail personality in filebench, on a 50GB btrfs
>> filesystem. I am also starting the scrubber at the same time. I have
>> applied the latest patches for 3.8.13 (hoping to fix log tree issues).
>
> There's a bugreport that looks the same,
> https://bugzilla.kernel.org/show_bug.cgi?id=60051
>
>> Every time, after the scrubber completes, however, I get the following:
>>
>> [ 2558.688026] ------------[ cut here ]------------
>> [ 2558.688055] WARNING: at fs/btrfs/tree-log.c:3882
>> btrfs_log_inode_parent+0x41e/0x480 [btrfs]()
>> [ 2558.688061] Hardware name: ProLiant DL160 Gen8
>> [ 2558.688065] Modules linked in: btrfs zlib_deflate libcrc32c psmouse
>> sb_edac serio_raw edac_core hpilo ioatdma hpwdt acpi_power_meter
>> mac_hid lp parport igb dca ptp pps_core be2iscsi iscsi_boot_sysfs
>> mpt2sas libiscsi scsi_transport_sas scsi_transport_iscsi raid_class
>> be2net
>> [ 2558.688109] Pid: 13631, comm: filebench Tainted: G D W 3.8.13 #9
>> [ 2558.688115] Call Trace:
>> [ 2558.688128] [<ffffffff8105824f>] warn_slowpath_common+0x7f/0xc0
>> [ 2558.688137] [<ffffffff810582aa>] warn_slowpath_null+0x1a/0x20
>> [ 2558.688161] [<ffffffffa020fcce>] btrfs_log_inode_parent+0x41e/0x480 [btrfs]
>> [ 2558.688182] [<ffffffffa020fd76>] btrfs_log_dentry_safe+0x46/0x70 [btrfs]
>> [ 2558.688206] [<ffffffffa01e527c>] btrfs_sync_file+0x18c/0x230 [btrfs]
>> [ 2558.688214] [<ffffffff811b642d>] do_fsync+0x5d/0x90
>> [ 2558.688222] [<ffffffff8115a9c9>] ? vm_munmap+0x59/0x70
>> [ 2558.688230] [<ffffffff811b6810>] sys_fsync+0x10/0x20
>> [ 2558.688239] [<ffffffff8168a959>] system_call_fastpath+0x16/0x1b
>> [ 2558.688245] ---[ end trace 1cf4adc709e16e0b ]---
>>
>> And that root key (18446744073709551610) looks very suspicious. Any ideas?
>
> It translates to key type 250 which is BTRFS_DEV_REPLACE_KEY, plus the
> parent transid error this looks like broken/unfinished device replace.
> Have you used the 'btrfs device replace' recently?
>
Where do you see the key type 250?
> item 0 key (18446744073709551606 80 6597246976)
Is (objectid = -10 = BTRFS_EXTENT_CSUM_OBJECTID, type = 0x80 =
BTRFS_EXTENT_CSUM_KEY)
> unable to update root key 18446744073709551610 132 5
Is (objectid = -6 = BTRFS_TREE_LOG_OBJECTID, type = 132 =
BTRFS_ROOT_ITEM_KEY, offset = 5)
next prev parent reply other threads:[~2013-07-16 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 4:56 filebench varmail + scrubber = btrfs_update_root bug George Amvrosiadis
2013-07-16 11:37 ` David Sterba
2013-07-16 13:25 ` Stefan Behrens [this message]
2013-07-16 15:10 ` George Amvrosiadis
2013-07-18 17:36 ` David Sterba
[not found] <CABF9=8i1Bd6mVOR8kNZmQJa2UJLg9tiCojWHbN1HLVWhEh7_0g@mail.gmail. com>
2013-07-15 12:20 ` Duncan
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=51E549C6.1090303@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=dsterba@suse.cz \
--cc=gamvrosi@gmail.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;
as well as URLs for NNTP newsgroup(s).