On Mon, Jun 27, 2016 at 6:49 PM, Saint Germain <saint...@gmail.com> wrote:
> > I've tried both option and launched a replace, but I got the same error > (replace is cancelled, jernel bug). > I will let these options on and attempt a ddrescue on /dev/sda > to /dev/sdd. > Then I will disconnect /dev/sda and reboot and see if it works better. Sounds reasonable. Just make sure the file system is already unmounted when you use ddrescue because otherwise you're block copying it while it could be modified while rw mounted (generation number tends to get incremented while rw mounted). >> Last, I have no idea if the massive Btrfs write errors on sda are from >> an earlier problem where the drive data or power cable got jiggled or >> was otherwise absent temporarily? So depending on how the block >> timeout change affects your data recovery, you might end up needing to >> do a reboot to get back to a more stable state for all of this? It >> really should be able to fix things *if* at least one copy can be read >> and then written to the other drive. >> > > I have also no idea why is sda behaving like this. I haven't done > anything particular on these drives. Yeah pretty weird. At some point once things are stable, if this file system survives, you might want to use btrfs dev stat -z to wipe out those stats. -- 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
