From: Josef Bacik <jbacik@fusionio.com>
To: Hugo Mills <hugo@carfax.org.uk>,
Sandy McArthur <sandymac@gmail.com>,
<linux-btrfs@vger.kernel.org>
Subject: Re: bug: corrupt filesystem, cannot delete tmp files created just before crash.
Date: Thu, 18 Jul 2013 12:33:42 -0400 [thread overview]
Message-ID: <20130718163342.GB2322@localhost.localdomain> (raw)
In-Reply-To: <20130718152128.GB20517@carfax.org.uk>
On Thu, Jul 18, 2013 at 04:21:28PM +0100, Hugo Mills wrote:
> On Thu, Jul 18, 2013 at 11:11:03AM -0400, Sandy McArthur wrote:
> > Should I interpret the different used amounts (902.01GB vs 902.03GB)
> > on my recovered RAID1 filesystem as that not all data is actually
> > mirrored and so I should run a balance? The devices in the filesystem
> > below are the same make/model drives.
> >
> > # btrfs fi show
> > Label: 'mcmedia' uuid: 92b3345e-2589-423c-a228-d569bf94ab58
> > Total devices 2 FS bytes used 905.33GB
> > devid 2 size 2.73TB used 902.01GB path /dev/sdc1
> > devid 1 size 2.73TB used 902.03GB path /dev/sdb1
> >
> > Btrfs v0.20-rc1-358-g194aa4a
> >
> > # btrfs fi df /mnt/media/
> > Data, RAID1: total=894.00GB, used=892.99GB
> > Data: total=12.01GB, used=11.56GB
>
> ^^^^^^^ This is unmirrored data.
>
> # btrfs balance start -dconvert=raid1,soft /mountpoint
>
> is the incantation you need: convert your data to RAID-1, and ignore
> anything which has already been converted.
>
Build btrfs-next and boot into that first if you can before you do this as there
is a slight bug with balance that will corrupt data if you crash. Thanks,
Josef
next prev parent reply other threads:[~2013-07-18 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPs0Bij+BQZArDJuXmKF0S25=wGgdMq6otXmrLJtQYRoMAjQFw@mail.gmail. com>
2013-07-17 23:38 ` bug: corrupt filesystem, cannot delete tmp files created just before crash Duncan
2013-07-18 14:19 ` Sandy McArthur
2013-07-18 15:11 ` Sandy McArthur
2013-07-18 15:21 ` Hugo Mills
2013-07-18 16:33 ` Josef Bacik [this message]
2013-07-17 14:06 Sandy McArthur
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=20130718163342.GB2322@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandymac@gmail.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).