On Jul 14, 2013, at 12:19 PM, Chris Murphy <[email protected]> wrote:
> > On Jul 14, 2013, at 12:13 PM, Hugo Mills <[email protected]> wrote: > >> On Sun, Jul 14, 2013 at 12:11:04PM -0600, Chris Murphy wrote: >>> On Fedora 19 with all updates, when I mkfs.btrfs and then mount the volume, >>> I'm getting this in dmesg: >>> >>> [ 280.534868] Btrfs loaded >>> [ 280.581799] device fsid 94ed05cb-89a9-4d6b-a1e2-5312687b59f5 devid 1 >>> transid 4 /dev/mapper/vg1-brick1 >>> [ 280.590140] btrfs: super block crcs don't match, older mkfs detected >>> [ 280.597746] btrfs: disk space caching is enabled >>> [ 280.661204] SELinux: initialized (dev dm-4, type btrfs), uses xattr >>> >>> btrfs-progs-0.20.rc1.20130308git704a08c-1.fc19.x86_64 >>> kernel-3.10.0-1.fc20.x86_64 >>> >>> Is this expected? Benign? >> >> Yes, I believe it's harmless and will go away after the first >> mount. > > Weird. I don't get this message on a regular partition, e.g. mkfs.btrfs > /dev/sda7, mount /dev/sda7 /data. I only get it so far when formatting an lvm > thinp LV. No error with a regular partition or LV, or a small thinp LV. But with larger thinp LVs, I get some out of memory related errors, but the mkfs still completes, then I'm getting the CRC mismatch error on mount. So this may be a real CRC mismatch problem, due to concurrent out of memory problems. So I'm going to chock this up, for now, to other thinp related issues. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
