From: Chris Mason <chris.mason@fusionio.com>
To: Alex Lyakas <alex.btrfs@zadarastorage.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: same EXTENT_ITEM appears twice in the extent tree
Date: Sun, 3 Mar 2013 10:28:39 -0500 [thread overview]
Message-ID: <20130303152839.GC18135@shiny.masoncoding.com> (raw)
In-Reply-To: <CAOcd+r2p9AonnEwGZCS4CPUJ8O2EuQkSAA15twERY47FtrqLEw@mail.gmail.com>
On Sun, Mar 03, 2013 at 06:40:50AM -0700, Alex Lyakas wrote:
> Greetings all,
> I have an extent tree that looks like follows:
>
> item 22 key (27059916800 EXTENT_ITEM 16384) itemoff 2656 itemsize 24
> extent refs 1 gen 164 flags 1
> item 23 key (27059916800 EXTENT_ITEM 98304) itemoff 2603 itemsize 53
> extent refs 1 gen 165 flags 1
> extent data backref root 257 objectid 257 offset 17446191104 count 1
> item 24 key (27059916800 SHARED_DATA_REF 47169536) itemoff 2599 itemsize 4
> shared data backref count 1
Have you been experimenting on this FS with snapshot deletion patches?
-chris
next prev parent reply other threads:[~2013-03-03 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 13:40 same EXTENT_ITEM appears twice in the extent tree Alex Lyakas
2013-03-03 15:28 ` Chris Mason [this message]
2013-03-03 15:44 ` Alex Lyakas
2013-03-09 22:33 ` Alex Lyakas
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=20130303152839.GC18135@shiny.masoncoding.com \
--to=chris.mason@fusionio.com \
--cc=alex.btrfs@zadarastorage.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