On Fri, Mar 20, 2015 at 12:59:01PM +0800, Eryu Guan wrote: > Filling a dm/lvm snapshot triggered this btrfs WARNING, kernel is 4.0-rc3+
It's an EIO because the underlying storage does not want to write the data. > The same script can trigger warning on ext4 too, I'll file another bug > report to ext4 list. So it's likely caused by dm/lvm. > [150646.284481] device-mapper: snapshots: Invalidating snapshot: Unable to > allocate exception. ... > [150646.312739] BTRFS: bdev /dev/mapper/vg_081-snap_081 errs: wr 10, rd 0, > flush 0, corrupt 0, gen 0 > [150646.331472] BTRFS: error (device dm-3) in btrfs_commit_transaction:2019: > errno=-5 IO failure (Error while writing out transaction) > [150646.334251] BTRFS info (device dm-3): forced readonly > [150646.335365] BTRFS warning (device dm-3): Skipping commit of aborted > transaction. And this is the standard behaviour of the filesystem in such case. -- 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
