All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@ORACLE.COM>
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Warning and BUG using btrfs-vol -b
Date: Wed, 7 Oct 2009 10:33:09 -0400	[thread overview]
Message-ID: <20091007143309.GF3757@think> (raw)
In-Reply-To: <200910071551.46430.diegocg@gmail.com>

On Wed, Oct 07, 2009 at 03:51:46PM +0200, Diego Calleja wrote:
> On Wednesday 07 October 2009 05:17:54 Chris Mason escribi=F3:
>=20
> > Thanks, I'll try to reproduce.  Which raid level did you use for da=
ta?
> > If not raid1, could you try with raid1? ;)
>=20
> I'm not sure, since the utils won't tell. I mkfs'ed and mounted one o=
f the 3.5GB
> files with no special options, and copied some files on it. I mkfs'ed=
 the second
> file, put it in a loop device, and added it to the pool with btrfs-vo=
l -a. Then
> I run btrfs-vol -b and I copied more files and rebalanced several tim=
es.
>=20
> Then I zeroed one of the files used as disks, and tried to read the f=
iles in
> the volume (unsucessfully). Then I rebalanced, and I hit the oops. It=
 seems to
> be very reproducible.

Ok, in this case you ended up with raid0 on the data.  If you:

mkfs.btrfs -d raid1 /dev/loop0 /dev/loop1 you'll get data raid1.

-chris

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-10-07 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 18:48 Warning and BUG using btrfs-vol -b Diego Calleja
2009-10-07  3:17 ` Chris Mason
2009-10-07 13:51   ` Diego Calleja
2009-10-07 14:33     ` Chris Mason [this message]
2009-10-07 19:10       ` Diego Calleja
2009-10-07 19:45         ` Chris Mason
2009-10-07 21:12           ` Diego Calleja
2009-10-07 21:27           ` Diego Calleja

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=20091007143309.GF3757@think \
    --to=chris.mason@oracle.com \
    --cc=diegocg@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.