Marc Haber posted on Mon, 07 Mar 2016 09:30:43 +0100 as excerpted: > I have dug aroud in my auth.logs, and thanks to my not working in a root > shell but using sudo for every single command I can say that the > filesystem was created on September 1, 2015, so it is not _this_ old, > and snapshot.debian.net tells me that Debian unstable had btrfs-tools > 4.1.2 uploaded on August 31, so i guess that the filesystem was either > created by the 4.0 version we had since May 2015 or by the brand new > 4.1.2. > > And it was a mkfs.btrfs with no special options. I doubted that either a convert-from-ext* or a mkfs with the bad 4.1.1 would turn out to be the cause, but those are the only things /I/ am aware of that can trigger wild behavior like we're seeing with this metadata, here. So it's certainly a bug, and not accounted for by anything know at least to me, which makes it a new and interesting bug. But not being a dev, that's about as far as I can take it. As CMurphy said, file a bug with all the various information, and hope the devs can replicate and trace it down. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
