From: Marc MERLIN <marc@merlins.org>
To: Su Yue <suy.fnst@cn.fujitsu.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs@vger.kernel.org, Su Yue <Damenly_Su@gmx.com>
Subject: Re: btrfs check lowmem, take 2
Date: Tue, 10 Jul 2018 21:39:28 -0700 [thread overview]
Message-ID: <20180711043928.itffs2kt52rbatsx@merlins.org> (raw)
In-Reply-To: <e8e4b853-a20d-cd55-550e-2f2263d1984e@cn.fujitsu.com>
On Wed, Jul 11, 2018 at 12:07:05PM +0800, Su Yue wrote:
> > So, I went back to https://github.com/Damenly/btrfs-progs.git/tmp1 and
> > I'm running it without the extra options you added with hardcoded stuff:
> > gargamel:/var/local/src/btrfs-progs.sy-test# ./btrfsck --mode=lowmem --repair /dev/mapper/dshelf2
> >
> This is okay. Let's wait to see the result.
Sadly, it crashes quickly:
Starting program: /var/local/src/btrfs-progs.sy-test/btrfs check --mode=lowmem --repair /dev/mapper/dshelf2
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
enabling repair mode
WARNING: low-memory mode repair support is only partial
Checking filesystem on /dev/mapper/dshelf2
UUID: 0f1a0c9f-4e54-4fa7-8736-fd50818ff73d
checking extents
Program received signal SIGSEGV, Segmentation fault.
check_tree_block_backref (fs_info=fs_info@entry=0x555555825e10,
root_id=root_id@entry=18446744073709551607, bytenr=bytenr@entry=655589376, level=level@entry=1)
at check/mode-lowmem.c:3744
3744 if (btrfs_header_bytenr(node) != bytenr) {
(gdb) bt
#0 check_tree_block_backref (fs_info=fs_info@entry=0x555555825e10,
root_id=root_id@entry=18446744073709551607, bytenr=bytenr@entry=655589376, level=level@entry=1)
at check/mode-lowmem.c:3744
#1 0x00005555555cb1f9 in check_extent_item (fs_info=fs_info@entry=0x555555825e10,
path=path@entry=0x7fffffffdc60) at check/mode-lowmem.c:4194
#2 0x00005555555d06e9 in check_leaf_items (account_bytes=1, nrefs=0x7fffffffdb80,
path=0x7fffffffdc60, root=0x5555558262f0) at check/mode-lowmem.c:4654
#3 walk_down_tree (check_all=1, nrefs=0x7fffffffdb80, level=<synthetic pointer>,
path=0x7fffffffdc60, root=0x5555558262f0) at check/mode-lowmem.c:4790
#4 check_btrfs_root (root=root@entry=0x5555558262f0, check_all=check_all@entry=1)
at check/mode-lowmem.c:5114
#5 0x00005555555d144f in check_chunks_and_extents_lowmem (fs_info=fs_info@entry=0x555555825e10)
at check/mode-lowmem.c:5475
#6 0x00005555555b44b1 in do_check_chunks_and_extents (fs_info=0x555555825e10) at check/main.c:8369
#7 cmd_check (argc=<optimized out>, argv=<optimized out>) at check/main.c:9899
#8 0x0000555555567510 in main (argc=4, argv=0x7fffffffe390) at btrfs.c:302
Would you like anything off gdb? (feel free to Email me directly or
point me to an online chat platform you have access to)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08
next prev parent reply other threads:[~2018-07-11 4:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 18:09 btrfs check lowmem, take 2 Marc MERLIN
2018-07-11 0:53 ` Su Yue
2018-07-11 0:58 ` Marc MERLIN
2018-07-11 1:08 ` Su Yue
2018-07-11 1:44 ` Marc MERLIN
2018-07-11 1:58 ` Su Yue
2018-07-11 3:36 ` Marc MERLIN
2018-07-11 4:07 ` Su Yue
2018-07-11 4:39 ` Marc MERLIN [this message]
2018-07-11 17:09 ` Chris Murphy
2018-07-11 17:14 ` btrfs check mode normal still hard crash-hanging systems Marc MERLIN
2018-07-12 5:26 ` Why original mode doesn't use swap? (Original: Re: btrfs check lowmem, take 2) Qu Wenruo
2018-07-12 23:14 ` Marc MERLIN
2018-07-13 0:22 ` Qu Wenruo
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=20180711043928.itffs2kt52rbatsx@merlins.org \
--to=marc@merlins.org \
--cc=Damenly_Su@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=suy.fnst@cn.fujitsu.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 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.