From: Diego Calleja <diegocg@gmail.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: "linux-btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: Warning and BUG using btrfs-vol -b
Date: Wed, 7 Oct 2009 15:51:46 +0200 [thread overview]
Message-ID: <200910071551.46430.diegocg@gmail.com> (raw)
In-Reply-To: <20091007031754.GB3757@think>
On Wednesday 07 October 2009 05:17:54 Chris Mason escribi=F3:
> Thanks, I'll try to reproduce. Which raid level did you use for data=
?
> If not raid1, could you try with raid1? ;)
I'm not sure, since the utils won't tell. I mkfs'ed and mounted one of =
the 3.5GB
files with no special options, and copied some files on it. I mkfs'ed t=
he second
file, put it in a loop device, and added it to the pool with btrfs-vol =
-a. Then
I run btrfs-vol -b and I copied more files and rebalanced several times=
=2E
Then I zeroed one of the files used as disks, and tried to read the fil=
es in
the volume (unsucessfully). Then I rebalanced, and I hit the oops. It s=
eems to
be very reproducible.
--
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
next prev parent reply other threads:[~2009-10-07 13:51 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 [this message]
2009-10-07 14:33 ` Chris Mason
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=200910071551.46430.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=chris.mason@oracle.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