On Mon, Sep 19, 2011 at 04:23:31PM -0400, Greg Freemyer wrote:
I suggest it go to the kernel bugzilla, not the
Rather post it to the mailinglist or ask at IRC. kenrel bugzilla is
down and nearly nobody looks there (although there are worth reports).
Btrfs is just not yet stable enough for openSUSE to
anything but experimental.
Correct. Have backups.
Partially in hopes of convincing myself btrfs would be ready for 12.1,
I put together a wiki page explaining how to install and run the
filesystem test suite the xfs team maintains. I pointed the testing
team at it, so they have run at least some automated btrfs tests.
I have packaged xfstests,
as I use them heavily and got tired of doing manual installation, namely
for automatic testing. (The package needs xfsprogs from the same repo.)
Over time a lot of those tests have been expanded from
xfs only to
multiple filesystems or generic to linux.
I found btrfs failed 3 of the existing functional tests.
Failures: 075 112 254 (with the tumbleweed 3.0.0-rc7-4-desktop
kernel. Similar failures with older kernels.)
075 and 112 do not fail for me at 3.1.0-rc6+, although 254 reports
failure, but it's a minor one (just basic snapshot/subovl tests, this
area deserves much harder testing).
I asked on the list that maintains the xfstests script
to see if was a
test bug, or a btrfs bugs. They said the tests should be fine, so
they represent real btrfs bugs.
fyi: I don't know what those specific tests are, so maybe they should
not be considered btrfs "ship stoppers". I just assumed that until
all the pre-existing tests pass, btrfs will be considered
The failing tests are not ship-stoppers. There are 100+ commits between
3.0 and 3.1-rc, many of them stability and correctness fixes. Anybody
using btrfs should try to stick to the latest kernel. And keep backups.
The stable series received only small number of fixes.
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org