On Tue, Jan 30, 2018 at 08:46:32 -0500, Austin S. Hemmelgarn wrote: >> I personally think the degraded mount option is a mistake as this >> assumes that a lightly degraded system is not able to work which is false. >> If the system can mount to some working state then it should mount >> regardless if it is fully operative or not. If the array is in a bad >> state you need to learn about it by issuing a command or something. The >> same goes for a MD array (and yes, I am aware of the block layer vs >> filesystem thing here). > The problem with this is that right now, it is not safe to run a BTRFS > volume degraded and writable, but for an even remotely usable system Mounting read-only is still better than not mounting at all. For example, my emergency.target has limited network access and starts ssh server so I could recover from this situation remotely. > with pretty much any modern distro, you need your root filesystem to be > writable (or you need to have jumped through the hoops to make sure /var > and /tmp are writable even if / isn't). Easy to handle by systemd. Not only this, but much more is planned: http://0pointer.net/blog/projects/stateless.html -- Tomasz Pala <gotar@xxxxxxxxxxxxx> -- 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
