On Sat, Mar 26, 2016 at 8:00 AM, Stephen Williams <stephenw@xxxxxxxxxxxx> wrote: > I know this is quite a rare occurrence for home use but for Data center > use this is something that will happen A LOT. > This really should be placed in the wiki while we wait for a fix. I can > see a lot of sys admins crying over this. Maybe on the gotchas page? While it's not a data loss bug, it might be viewed as an uptime bug because the dataset is stuck being ro and hence unmodifiable, until a restore to a rw volume is complete. Since we can ro mount a volume, some way to safely make it a seed device could be useful. All that's needed to make it rw is adding even a small USB stick for example, and now at least ro snapshots can be taken and migrate data off the volume. A larger device that's used for rw would allow this raid to be brought back online. And then once the new array is up and has most data restored, a short downtime to get the latest incremental changes sent over. Yeah, the alternative to this is a cluster, and you just consider this one brick a loss and move on. But most regular users don't do clusters, even with big (for them) storage. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
