On Thu, Jun 7, 2018 at 2:38 PM, Chris Murphy <li...@colorremedies.com> wrote:
> Your very first task right now is to mount ro, and update your > backups. Don't do anything else until you've done that. It's a > testimony to Btrfs that this file system mounts at all, even ro, so > take advantage of this fact before you can't mount it anymore. After you've done the backup, you need to find out why one of these devices is being so unreliable. That has to be fixed first. You can recreate a new Btrfs or some other file system, and you'll just run into the exact same problem down the road. Next, it might be useful to see the output from btrfs-progs 4.16.1 'btrfs check' and 'btrfs check --mode=lowmem' both of which are slow, the second one is really slow but is a different implementation so it's helpful to see both outputs. That's safe as long as you do not use --repair. Also we need to see the output from 'btrfs fi us <mountpoint>' with the volume mounted (ro). Off hand I think the most likely outcome is that you get a backup from the ro mounted file system, and you'll have to recreate it from scratch and restore from backups. In other words, no matter what you need a current backup. -- Chris Murphy -- 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
