From: Marc MERLIN <marc@merlins.org>
To: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
Chris Murphy <lists@colorremedies.com>,
Hugo Mills <hugo@carfax.org.uk>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: How to fix errors that check --mode lomem finds, but --mode normal doesn't?
Date: Tue, 27 Jun 2017 16:11:46 -0700 [thread overview]
Message-ID: <20170627231146.GA16192@merlins.org> (raw)
In-Reply-To: <0d93c1c4-1feb-b589-0c8f-1fced7b77686@cn.fujitsu.com>
On Mon, Jun 26, 2017 at 06:46:16PM +0800, Lu Fengqi wrote:
> Thanks for the updated information. I'm sorry that the false alert make
> you feel nervous.
If you can help me find out whether those are real errors that I need to fix
(and can't yet since there is no --repair), or whether they are not real
problems, I can ignore them as long as the other check --mode normal runs
clean (it does), we'll be good :)
> >ERROR: root 3862 EXTENT_DATA[18170706 4096] interrupt
> >ERROR: root 3862 EXTENT_DATA[18170706 16384] interrupt
> >ERROR: root 3862 EXTENT_DATA[18170706 20480] interrupt
> >ERROR: root 3862 EXTENT_DATA[18170706 135168] interrupt
> >ERROR: root 3862 EXTENT_DATA[18170706 1048576] interrupt
> >ERROR: errors found in fs roots
>
> However, this looks like another problem. Could you dump this file tree
> by the following command?
> # btrfs-debug-tree -t 3862 <dev> | grep -C 10 18170706
argamel:~# btrfs-debug-tree -t 3862 /dev/mapper/dshelf2 | grep -C 10 18170706
transid 522 data_len 0 name_len 45
name: 007b01c69a8d_9582a070_425a45d7@mindspring.com
item 89 key (835232 DIR_ITEM 1181375325) itemoff 10304 itemsize 64
location key (877605 INODE_ITEM 0) type FILE
transid 530 data_len 0 name_len 34
name: PO.5078346.7051988@codeweavers.com
item 90 key (835232 DIR_ITEM 1181489720) itemoff 10226 itemsize 78
location key (873230 INODE_ITEM 0) type FILE
transid 529 data_len 0 name_len 48
name: 8-8356087-5CruUNCbuG3Kg9zuO@mail1.fireflypro.com
item 91 key (835232 DIR_ITEM 1181707066) itemoff 10148 itemsize 78
location key (869906 INODE_ITEM 0) type FILE
transid 528 data_len 0 name_len 48
name: 7-7026088-1uLzZJuFzYD6h4rzV@max.firmalliance.biz
item 92 key (835232 DIR_ITEM 1181727135) itemoff 10084 itemsize 64
location key (877380 INODE_ITEM 0) type FILE
transid 530 data_len 0 name_len 34
name: NJ.5943286.7059518@codeweavers.com
item 93 key (835232 DIR_ITEM 1181873033) itemoff 10038 itemsize 46
location key (859092 INODE_ITEM 0) type FILE
transid 526 data_len 0 name_len 16
name: mdadm_detail.0
item 83 key (2640780 DIR_ITEM 3316050734) itemoff 12739 itemsize 39
location key (15689752 INODE_ITEM 0) type FILE
transid 8178 data_len 0 name_len 9
name: sda3.dd.0
item 84 key (2640780 DIR_ITEM 3349213389) itemoff 12697 itemsize 42
location key (2667656 INODE_ITEM 0) type FILE
transid 885 data_len 0 name_len 12
name: sdb2.dd.1.gz
item 85 key (2640780 DIR_ITEM 3351742419) itemoff 12663 itemsize 34
location key (18170706 INODE_ITEM 0) type FILE
transid 37866 data_len 0 name_len 4
name: dm-0
item 86 key (2640780 DIR_ITEM 3354578455) itemoff 12624 itemsize 39
location key (13847590 INODE_ITEM 0) type FILE
transid 2387 data_len 0 name_len 9
name: sda7.3.gz
item 87 key (2640780 DIR_ITEM 3361267344) itemoff 12586 itemsize 38
location key (2667594 INODE_ITEM 0) type FILE
transid 885 data_len 0 name_len 8
name: .profile
--
name: sdc1.dd.4.gz
item 70 key (2640780 DIR_INDEX 1685) itemoff 13162 itemsize 42
location key (17548883 INODE_ITEM 0) type FILE
transid 34469 data_len 0 name_len 12
name: sdc1.dd.5.gz
item 71 key (2640780 DIR_INDEX 1687) itemoff 13120 itemsize 42
location key (17548884 INODE_ITEM 0) type FILE
transid 34469 data_len 0 name_len 12
name: sdc1.dd.6.gz
item 72 key (2640780 DIR_INDEX 2039) itemoff 13086 itemsize 34
location key (18170706 INODE_ITEM 0) type FILE
transid 37866 data_len 0 name_len 4
name: dm-0
item 73 key (2640780 DIR_INDEX 2041) itemoff 13051 itemsize 35
location key (18170707 INODE_ITEM 0) type FILE
transid 37866 data_len 0 name_len 5
name: fdisk
item 74 key (2640780 DIR_INDEX 2043) itemoff 13007 itemsize 44
location key (18170708 INODE_ITEM 0) type FILE
transid 37866 data_len 0 name_len 14
name: mdadm_detail.0
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/
next prev parent reply other threads:[~2017-06-27 23:12 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 14:39 4.11.3: BTRFS critical (device dm-1): unable to add free space :-17 => btrfs check --repair runs clean Marc MERLIN
2017-06-20 15:23 ` Hugo Mills
2017-06-20 15:26 ` Marc MERLIN
2017-06-20 15:36 ` Hugo Mills
2017-06-20 15:44 ` Marc MERLIN
2017-06-20 23:12 ` Marc MERLIN
2017-06-20 23:58 ` Marc MERLIN
2017-06-21 3:31 ` Chris Murphy
2017-06-21 3:43 ` Marc MERLIN
2017-06-21 15:13 ` How to fix errors that check --mode lomem finds, but --mode normal doesn't? Marc MERLIN
2017-06-21 23:22 ` Chris Murphy
2017-06-22 0:48 ` Marc MERLIN
2017-06-22 2:22 ` Qu Wenruo
2017-06-22 2:53 ` Marc MERLIN
2017-06-22 4:08 ` Qu Wenruo
2017-06-23 4:06 ` Marc MERLIN
2017-06-23 8:54 ` Lu Fengqi
2017-06-23 16:17 ` Marc MERLIN
2017-06-24 2:34 ` Marc MERLIN
2017-06-26 10:46 ` Lu Fengqi
2017-06-27 23:11 ` Marc MERLIN [this message]
2017-06-28 7:10 ` Lu Fengqi
2017-06-28 14:43 ` Marc MERLIN
2017-05-01 17:06 ` 4.11 relocate crash, null pointer Marc MERLIN
2017-05-01 18:08 ` 4.11 relocate crash, null pointer + rolling back a filesystem by X hours? Marc MERLIN
2017-05-02 1:50 ` Chris Murphy
2017-05-02 3:23 ` Marc MERLIN
2017-05-02 4:56 ` Chris Murphy
2017-05-02 5:11 ` Marc MERLIN
2017-05-02 18:47 ` btrfs check --repair: failed to repair damaged filesystem, aborting Marc MERLIN
2017-05-03 6:00 ` Marc MERLIN
2017-05-03 6:17 ` Marc MERLIN
2017-05-03 6:32 ` Roman Mamedov
2017-05-03 20:40 ` Marc MERLIN
2017-07-07 5:37 ` ctree.c:197: update_ref_for_cow: BUG_ON `ret` triggered, value -5 Marc MERLIN
2017-07-07 5:39 ` Marc MERLIN
2017-07-07 9:33 ` Lu Fengqi
2017-07-07 16:38 ` Marc MERLIN
2017-07-09 4:34 ` 4.11.6 / more corruption / root 15455 has a root item with a more recent gen (33682) compared to the found root node (0) Marc MERLIN
2017-07-09 5:05 ` We really need a better/working btrfs check --repair Marc MERLIN
2017-07-09 6:34 ` 4.11.6 / more corruption / root 15455 has a root item with a more recent gen (33682) compared to the found root node (0) Marc MERLIN
2017-07-09 7:57 ` Martin Steigerwald
2017-07-09 9:16 ` Paul Jones
2017-07-09 11:17 ` Duncan
2017-07-09 13:00 ` Martin Steigerwald
2017-07-29 19:29 ` Imran Geriskovan
2017-07-29 23:38 ` Duncan
2017-07-30 14:54 ` Imran Geriskovan
2017-07-31 4:53 ` Duncan
2017-07-31 20:32 ` Imran Geriskovan
2017-08-01 1:36 ` Duncan
2017-08-01 15:18 ` Imran Geriskovan
2017-07-31 21:07 ` Ivan Sizov
2017-07-31 21:17 ` Marc MERLIN
2017-07-31 21:39 ` Ivan Sizov
2017-08-01 16:41 ` Ivan Sizov
2017-07-31 22:00 ` Justin Maggard
2017-08-01 6:38 ` Marc MERLIN
2017-05-02 19:59 ` 4.11 relocate crash, null pointer + rolling back a filesystem by X hours? Kai Krakow
2017-05-02 5:01 ` Duncan
2017-05-02 19:53 ` Kai Krakow
2017-05-23 16:58 ` Marc MERLIN
2017-05-24 10:16 ` Duncan
2017-05-05 1:19 ` Qu Wenruo
2017-05-05 2:10 ` Qu Wenruo
2017-05-05 2:40 ` Marc MERLIN
2017-05-05 5:03 ` Qu Wenruo
2017-05-05 15:43 ` Marc MERLIN
2017-05-17 18:23 ` Kai Krakow
2017-05-05 1:13 ` Qu Wenruo
2017-06-29 13:36 ` How to fix errors that check --mode lomem finds, but --mode normal doesn't? Lu Fengqi
2017-06-29 15:30 ` Marc MERLIN
2017-06-30 14:59 ` Lu Fengqi
2017-06-22 4:08 ` Qu Wenruo
2017-06-21 12:04 ` 4.11.3: BTRFS critical (device dm-1): unable to add free space :-17 => btrfs check --repair runs clean Duncan
2017-06-21 3:26 ` Chris Murphy
2017-06-21 4:06 ` Marc MERLIN
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=20170627231146.GA16192@merlins.org \
--to=marc@merlins.org \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=lufq.fnst@cn.fujitsu.com \
--cc=quwenruo@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 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).