On Fri, Feb 22, 2013 at 11:53 AM, Josef Bacik <jba...@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
(gdb) list *(btrfs_log_inode+0x3b8)
0x675b8 is in btrfs_log_inode (fs/btrfs/tree-log.c:3633).
3628
3629 log_extents:
3630 if (fast_search) {
3631 btrfs_release_path(dst_path);
3632 ret = btrfs_log_changed_extents(trans, root,
inode, dst_path);
3633 if (ret) {
3634 err = ret;
3635 goto out_unlock;
3636 }
3637 } else {
(gdb)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
