From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from static.198.36.40.188.clients.your-server.de ([188.40.36.198]:38477 "EHLO mail.render-wahnsinn.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751620AbbKJKa2 (ORCPT ); Tue, 10 Nov 2015 05:30:28 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.render-wahnsinn.de (Postfix) with ESMTP id 2EC6C2239B3 for ; Tue, 10 Nov 2015 11:22:32 +0100 (CET) Received: from mail.render-wahnsinn.de ([127.0.0.1]) by localhost (render-wahnsinn.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id E2-0RPPPp4p6 for ; Tue, 10 Nov 2015 11:22:31 +0100 (CET) Received: from [192.168.192.248] (ip-178-200-54-61.hsi07.unitymediagroup.de [178.200.54.61]) by mail.render-wahnsinn.de (Postfix) with ESMTPSA id 2DF282200D9 for ; Tue, 10 Nov 2015 11:22:31 +0100 (CET) Message-ID: <5641C566.7030309@render-wahnsinn.de> Date: Tue, 10 Nov 2015 11:22:30 +0100 From: Robert Krig MIME-Version: 1.0 To: linux-btrfs Subject: btrfs-balance convert from raid1 to single on specific device? Content-Type: text/plain; charset=utf-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: Hi, I'm running Kernel 4.3 and Btrfs-tools 4.3 on Debian Jessie. I compiled the tools and kernel myself. Recently I added a new disk to my btrfs volume and wanted to proceed to convert from single to raid1. Unfortunately the new disk seems to be faulty and started throwing a lot of errors. The balance convert operation didn't manage to finish, and now I'm trying to get my btrfs volume back to single mode so that I can mount it read/write. If I try to mount it degraded, then it complains that there are too few devices to mount writeable. So it will only allow me to mount read-only. So far, so bad. I have managed to boot and mount the volume once, with the faulty disk and cancel the balance operation. Now I would like to convert it all to single again, so that I can finally remove that faulty drive. However, if I simply say btrfs fi balance start -dconvert=single -mconvert=single /btrfs-volume Wouldn't that theoretically move some blocks to the faulty drive? Can I somehow specify to rebalance only the working drive? I was thinking by specifying the device id, which seems possible according to the manpage. I just wanted to check with you guys first, if that should work as expected, or will I run into further trouble? Also, I understand -dconvert is for data, and -mconvert is for metadata, but is -sconvert? Is that data and metadata combined, or are system chunks something else entirely? Thanks for your help.