luvar posted on Fri, 02 Jan 2015 15:42:29 +0100 as excerpted: > root@blackdawn:/home/luvar# uname -a > [...] 3.13.0-30-generic [...] > > root@blackdawn:/home/luvar# btrfs v > Btrfs v0.20-rc1-189-g704a08c > > > Am I doing something forbidden [...]
Those versions are your problem. Do you know how fast btrfs is improving, how old those are (hint, there are about five kernel release series a year and we're now on the 3.19 development series with 3.18 stable, so 3.13 is... about five releases back and thus about a year old! ), and how many bugs have been fixed since then? Try something newer than the paleolithic age, say a current 3.18.x stable series kernel or a 3.19-rc, and the recent btrfs-progs 3.18.0, and you should see rather better results. There are valid reasons to stick to old and stable, but they simply don't mix well with a new and still not completely stable filesystem that still sees regular bug fixes, and not just for code introduced in the last kernel, either! Therefore, if you want old and stable, choose a different filesystem; while if you want to run btrfs, staying current is strongly recommended. Meanwhile, if you haven't yet, you may want to spend some time on the wiki reading up. Take a look at the stuff under section 5.1, Guides and usage information, especially. It'll answer a lot of questions and could save your data too. =:^) https://btrfs.wiki.kernel.org -- 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
