Latest update. 4.4.0-0.rc6.git0.1.fc24.x86_64 btrfs-progs v4.3.1
Mounted the volume normally with both devices available, no mount options, so it is a rw mount. And it mounts with only the normal kernel messages: [ 9458.290778] BTRFS info (device sdc): disk space caching is enabled [ 9458.290788] BTRFS: has skinny extents I left the volume alone for 20 minutes. After that time, btrfs-show-super still shows different generation numbers for the two devids. I did an ls -l at the top level of the fs. And btrfs-show-super now shows the same generation numbers and backup_roots information for both devids. Next, I read the most recently modified files, they all read OK, no kernel messages, no missing files. Last, I umounted the volume and did a btrfs check, and it comes up completely clean, no errors. No scrub done yet, no (user space) writes done yet. But going back to the original btrfs check with all the errors, it really doesn't give a user/admin of the volume any useful information what the problem is. After-the-fact it's relatively clear that devid 1 has generation 4924, and devid 2 has generation 4923, and that's what the btrfs check complaints are about: just a generation mismatch and the associated missing metadata on one device. By all measures it's checking out and behaving completely healthy and OK. So I'm going to play with some fire, and treat it normally for a few days: including making snapshots and writing files. I'll do a scrub in a few days and report back. 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
