Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS error in __btrfs_inc_extent_ref:1935: Object already exists
Date: Mon, 1 Apr 2013 21:16:16 +0600	[thread overview]
Message-ID: <20130401211616.3fedecd0@natsu> (raw)
In-Reply-To: <20130401133110.GH1876@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 608 bytes --]

On Mon, 1 Apr 2013 09:31:10 -0400
Josef Bacik <jbacik@fusionio.com> wrote:

> Can you capture an image of these broken file systems the next time it happens?
> You'll need to clone the progs here
> 
> git://github.com/josefbacik/btrfs-progs.git
> 
> and build and then run
> 
> btrfs-image -w /dev/whatever blah.img
> 
> and then upload blah.img up somewhere I can pull it down.  You can use the -t
> and -c options too, but the -w is the most important since you have extent tree
> corruption.  Thanks,

Hello,

I have sent the link privately to your E-Mail.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-04-01 15:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-31 22:15 BTRFS error in __btrfs_inc_extent_ref:1935: Object already exists Roman Mamedov
2013-03-31 22:36 ` Roman Mamedov
2013-04-01  8:12   ` Roman Mamedov
2013-04-01 13:31     ` Josef Bacik
2013-04-01 13:45       ` Chris Kastorff
2013-04-01 13:51         ` Josef Bacik
2013-04-01 15:16       ` Roman Mamedov [this message]
2013-04-01 23:00     ` anand jain
2013-04-02  0:46 ` Josef Bacik
2013-04-02  5:21   ` Roman Mamedov

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=20130401211616.3fedecd0@natsu \
    --to=rm@romanrm.ru \
    --cc=jbacik@fusionio.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