From: Josef Bacik <jbacik@fusionio.com>
To: Mace Moneta <moneta.mace@gmail.com>
Cc: Josef Bacik <JBacik@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: WARNING: at fs/btrfs/extent_io.c:4718 map_private_extent_buffer+0xd4/0xe0 [btrfs]()
Date: Fri, 22 Feb 2013 13:10:17 -0500 [thread overview]
Message-ID: <20130222181017.GG2062@localhost.localdomain> (raw)
In-Reply-To: <CAMfhy92G2yGh4HeQGq1VYVZ=pr2VkH+6yT86ZwfnLvxrUY=Wyg@mail.gmail.com>
On Fri, Feb 22, 2013 at 10:52:19AM -0700, Mace Moneta wrote:
> On Fri, Feb 22, 2013 at 12:44 PM, Josef Bacik <jbacik@fusionio.com> wrote:
> > On Fri, Feb 22, 2013 at 10:22:04AM -0700, Mace Moneta wrote:
> >> On Fri, Feb 22, 2013 at 11:53 AM, Josef Bacik <jbacik@fusionio.com> wrote:
> >> > On Fri, Feb 22, 2013 at 07:46:16AM -0700, Mace Moneta wrote:
> >> >> https://bugzilla.redhat.com/show_bug.cgi?id=906142
> >> >>
> >> >> With 3.8 kernels in Fedora 18, using encfs on btrfs I get the
> >> >> following error. It can take hours of use before I get a
> >> >> reoccurrence, and I need to btrfsck, btrfs-zero-log, and/or mount with
> >> >> '-o recovery' to get the filesystem back after a reboot. No data
> >> >> appears to be lost, and a scrub runs to completion with no errors.
> >> >
> >> > Could you do
> >> >
> >> > gdb btrfs.ko
> >> > list *(btrfs_log_inode+0x3b8)
> >> >
> >> > and tell me what it says? Thanks,
> >> >
> >> > Josef
> >>
> >> # uname -r
> >> 3.8.0-0.rc7.git0.1.fc19.x86_64
> >>
> >> # gdb /usr/lib/modules/3.8.0-0.rc7.git0.1.fc19.x86_64/kernel/fs/btrfs/btrfs.ko
> >>
> >
> > Sigh sorry, I miseed the other line because of line wrapping, can you do
> >
> > list *(btrfs_log_changed_extents+0x384)
> >
> > Thanks,
> >
> > Josef
>
> (gdb) list *(btrfs_log_changed_extents+0x384)
> 0x65264 is in btrfs_log_changed_extents (fs/btrfs/ctree.h:2731).
> 2726 generation, 64);
> 2727 BTRFS_SETGET_FUNCS(file_extent_disk_num_bytes, struct
> btrfs_file_extent_item,
> 2728 disk_num_bytes, 64);
> 2729 BTRFS_SETGET_FUNCS(file_extent_offset, struct btrfs_file_extent_item,
> 2730 offset, 64);
> 2731 BTRFS_SETGET_FUNCS(file_extent_num_bytes, struct btrfs_file_extent_item,
> 2732 num_bytes, 64);
> 2733 BTRFS_SETGET_FUNCS(file_extent_ram_bytes, struct btrfs_file_extent_item,
> 2734 ram_bytes, 64);
> 2735 BTRFS_SETGET_FUNCS(file_extent_compression, struct
> btrfs_file_extent_item,
> (gdb)
Ok nothing obvious is jumping out at me, anything specifc to your btrfs setup?
Mount options, raid etc. I'm going to setup encfs up here and hammer it with
fsstress and see if I can reproduce. Thanks,
Josef
next prev parent reply other threads:[~2013-02-22 18:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 14:46 WARNING: at fs/btrfs/extent_io.c:4718 map_private_extent_buffer+0xd4/0xe0 [btrfs]() Mace Moneta
2013-02-22 16:53 ` Josef Bacik
2013-02-22 17:22 ` Mace Moneta
2013-02-22 17:44 ` Josef Bacik
2013-02-22 17:52 ` Mace Moneta
2013-02-22 18:10 ` Josef Bacik [this message]
2013-02-22 18:16 ` Mace Moneta
2013-02-22 18:31 ` Mace Moneta
2013-02-22 19:40 ` Josef Bacik
2013-02-23 4:54 ` Mace Moneta
2013-02-25 19:12 ` Josef Bacik
2013-02-25 19:21 ` Mace Moneta
2013-02-25 19:46 ` Josef Bacik
2013-02-27 20:24 ` Mace Moneta
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=20130222181017.GG2062@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=moneta.mace@gmail.com \
/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