On Tue, Aug 11, 2015 at 3:47 PM, Chris Murphy <li...@colorremedies.com> wrote:
> > Huh. I thought nodatacow applies to an entire volume only, not per > subvolume unless you use chattr +C (in which case it can be per > subvolume, directory or per file). I could be confused, but I think > you have mutually exclusive mount options. Well, at the time I set up this system, I asked on IRC, and people said it should work. I've never seen any errors from this. >> >> [94312.091613] BTRFS info (device sdc): allowing degraded mounts >> [94312.091618] BTRFS info (device sdc): disk space caching is enabled >> [94312.194513] BTRFS: bdev (null) errs: wr 1724, rd 305, flush 45, >> corrupt 0, gen 2 >> [94319.824563] BTRFS: checking UUID tree > > I don't see any mount failure message. It worked then? Yes and no. It's mounted, but a scrub aborts silently: # btrfs scrub status /mnt/btrfs/ scrub status for ecdff84d-b4a2-4286-a1c1-cd7e5396901c scrub started at Tue Aug 11 13:56:36 2015 and was aborted after 01:31:55 total bytes scrubbed: 2.19TiB with 0 errors No new messages appeared in dmesg, so I can't tell why it aborted. It's also odd that it reports zero errors, given that it aborted. -- Timothy Normand Miller, PhD Assistant Professor of Computer Science, Binghamton University http://www.cs.binghamton.edu/~millerti/ Open Graphics Project -- 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
