Re: raid1: cannot add disk to replace faulty because can only mount fs as read-only.

2017-01-31 Thread Hans Deragon
On 2017-01-30 07:18, Austin S. Hemmelgarn wrote: > On 2017-01-28 04:17, Andrei Borzenkov wrote: >> 27.01.2017 23:03, Austin S. Hemmelgarn пишет: >>> On 2017-01-27 11:47, Hans Deragon wrote: >>>> On 2017-01-24 14:48, Adam Borowski wrote: >>>> >>&g

Re: raid1: cannot add disk to replace faulty because can only mount fs as read-only.

2017-02-07 Thread Hans Deragon
ld erase data by mistake. Let people do what they want and let them live with the consequences. hdparm has a --yes-i-know-what-i-am-doing flag. btrfs needs one. Whoever decides about btrfs features to add, please consider this one. Best regards, Hans Deragon -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

raid1: cannot add disk to replace faulty because can only mount fs as read-only.

2017-01-24 Thread Hans Deragon
of affair. Am I right? Best regards and thank you for your contribution to the open source movement, Hans Deragon -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.

Re: raid1: cannot add disk to replace faulty because can only mount fs as read-only.

2017-01-27 Thread Hans Deragon
On 2017-01-24 14:48, Adam Borowski wrote: On Tue, Jan 24, 2017 at 01:57:24PM -0500, Hans Deragon wrote: If I remove 'ro' from the option, I cannot get the filesystem mounted because of the following error: BTRFS: missing devices(1) exceeds the limit(0), writeable mount is not allowed So I am