On Mon, Apr 3, 2017 at 10:02 PM, Robert Krig <robert.k...@render-wahnsinn.de> wrote: > > > On 03.04.2017 16:25, Robert Krig wrote: >> >> I'm gonna run a extensive memory check once I get home, since you >> mentioned corrupt memory might be an issue here. >> -- >> 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 > > > I ran a memtest over a couple of hours with no errors. Ram seems to be > fine so far.
Inconclusive. A memtest can take days to expose a problem, and even that's not conclusive. The list archive has some examples of where memory testers gave RAM a pass, but doing things like compiling the kernel would fail. > > I've looked at the link you provided. Frankly it looks very scary. (At > least to me it does) > But I've just thought of something else. > > My storage array is BTRFS Raid1 with 4x8TB Drives. > Wouldn't it be possible to simply disconnect two of those drives, mount > with -o degraded and still have access (even if read-only) to all my data? man mkfs.btrfs Btrfs raid1 supports only one device missing, no matter how many drives. Mounting -o ro,degraded is probably permitted by the file system, but chunks of the file system and certainly your data, will be missing. So it's just a matter of time before copying data off will fail. I suggest trying -o ro with all drives, not a degraded mount, and copying data off. Any failures should be logged. Metadata errors are logged without paths, whereas data corruption included path to the affected file. This is easier than scraping the file system with btrfs restore. If you can't mount ro with all drives, or ro,degraded with just one device missing, you'll need to use btrfs restore which is more tolerant of missing metadata. -- 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
