On Sun, Mar 03, 2013 at 06:57:41AM -0700, Michael Schmitt wrote: > Hi list, > > some rather unexpected btrfs-oopses for my taste. I use btrfs for some > time now (mostly on external harddisks) and these "oopses" happened > during some simple file and folder deletion operation on that device. It > is a luks-encrypted 80GB drive. Anything like that known? And the fs was > created just yesterday, how come there is a message like... > > [91491.919358] btrfs: mismatching generation and generation_v2 found in root item. This root was probably mounted with an older kernel. Resetting all new fields. This may be from first mount after mkfs. It depends on your tools. > > ... but the kernel used (3.7.3 from Debian experimental on Debian sid) > was installed several days ago. What kind of oopses are these? As of now > there is no real data on that device. But if there were, would I need to > be concerned about the integrity of those files? > > [93283.762006] WARNING: at /build/buildd-linux_3.7.3-1~experimental.1-i386-eX5kUQ/linux-3.7.3/fs/btrfs/extent-tree.c:6297 btrfs_alloc_free_block+0xcd/0x2a4 [btrfs]() These are not oopsen but warnings. It's an ENOSPC warning as we try to delete the extents. It did happen sometimes in this kernel, but it is only a warning. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
