From: Josef Bacik <jbacik@fusionio.com>
To: Chris Kastorff <encryptio@gmail.com>
Cc: Josef Bacik <JBacik@fusionio.com>, Roman Mamedov <rm@romanrm.ru>,
"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 09:51:43 -0400 [thread overview]
Message-ID: <20130401135143.GI1876@localhost.localdomain> (raw)
In-Reply-To: <CAOOVQYKDyFXJPKFR-b20cMR6dWOW9MMu2Buk5644ig_45qvDWA@mail.gmail.com>
On Mon, Apr 01, 2013 at 07:45:16AM -0600, Chris Kastorff wrote:
> I have a (larger, 7x2TB at RAID10) filesystem that was recently hit by
> this. Same story; filesystem works normally, balance start, works for
> a while, then fails with similar stack traces and remounts read-only,
> after a reboot does not mount at all with similar error messages and
> stack traces.
>
> The FS is still in that state. I'll grab an image and mail a link
> privately. I don't need to do anything special for btrfs-image on a
> multi-device fs, right?
>
Right it will grab stuff from whatever mirror it's on and put it in the image.
Make sure to use -w, if the extent tree is corrupt the -w will make sure it
actually grabs all of the file system. Thanks,
Josef
next prev parent reply other threads:[~2013-04-01 13:51 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 [this message]
2013-04-01 15:16 ` Roman Mamedov
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=20130401135143.GI1876@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=encryptio@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.ru \
/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