-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2011 04:01 PM, Ilya Dryomov wrote:
Hello,
This patch series adds an initial implementation of restriper (it's
a clever name for relocation framework that allows to do selective
profile changing and selective balancing with some goodies
On Mon, Nov 14, 2011 at 06:59:14PM -0500, Phillip Susi wrote:
I have a fs that started with the default policy of metadata=dup. I
added a second device and rebalanced, and so the metadata chunks were
converted to raid1. Now I can not remove the second device because
raid1 requires at least
On 11/15/2011 4:22 AM, Ilya Dryomov wrote:
Restriper won't let you do raid1 - dup transition because dup is only
allowed for a single-spindle FS, so you'll end up with error btrfs:
unable to start restripe
There is no way to prioritize disks during restripe. To get dup back
you'll have
On Tue, Nov 15, 2011 at 09:33:14AM -0500, Phillip Susi wrote:
On 11/15/2011 4:22 AM, Ilya Dryomov wrote:
Restriper won't let you do raid1 - dup transition because dup is only
allowed for a single-spindle FS, so you'll end up with error btrfs:
unable to start restripe
There is no way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a fs that started with the default policy of metadata=dup. I
added a second device and rebalanced, and so the metadata chunks were
converted to raid1. Now I can not remove the second device because
raid1 requires at least two devices.
If I
Hi,
I've hit a problem with restriper but under ragher unclear conditions:
[12308.210636] [ cut here ]
[12308.214185] kernel BUG at fs/btrfs/relocation.c:2047!
[12308.214185] invalid opcode: [#1] SMP
[12308.214185] CPU 0
[12308.214185] Modules linked in: loop btrfs
