On 8 September 2015 at 22:28, Hugo Mills <h...@carfax.org.uk> wrote: > On Tue, Sep 08, 2015 at 02:17:55PM -0600, Chris Murphy wrote: >> On Tue, Sep 8, 2015 at 2:13 PM, Ian Kumlien <ian.kuml...@gmail.com> wrote: >> > On 8 September 2015 at 22:08, Chris Murphy <li...@colorremedies.com> wrote: >> >> On Tue, Sep 8, 2015 at 2:00 PM, Ian Kumlien <ian.kuml...@gmail.com> wrote:
[--8<--] >> > -o degraded should allow readwrite *IF* the data can be written to.... >> > My question is also, would this keep me from "adding devices"? >> > I mean, it did seem like a catch 22 earlier, but that would really >> > make a mess of things... >> >> It is not possible to add a device to an ro filesystem, so effectively >> the fs read-writeability is broken in this case. > > I thought this particular issue had already been dealt with in 4.2? > (i.e. you can still mount an FS RW if it's degraded, but there are > still some single chunks on it). Single chunks are only on sda - not on sdb... There should be no problem... > Ian: If you can still mount the FS read/write with both devices in > it, then it might be worth trying to balance away the problematic > single chunks with: > > btrfs bal start -dprofiles=single -mprofiles=single /mountpoint > > Then unmount, pull the dead drive, and remount -odegraded. It never completes, too many errors and eventually the disk disappears until the machine is turned off and on again... (normal disk reset doesn't work) -- 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
