From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Kernel panic from "btrfs subvolume delete"
Date: Fri, 29 Jun 2012 11:17:17 +0000 (UTC) [thread overview]
Message-ID: <pan.2012.06.29.11.17.17@cox.net> (raw)
In-Reply-To: CAG1y0seoS2c7d=jQgrZNF0aAJPrgTKbL1v6JzFigCk9ZMZ7H+w@mail.gmail.com
Fajar A. Nugraha posted on Fri, 29 Jun 2012 17:42:26 +0700 as excerpted:
> On Fri, Jun 29, 2012 at 5:11 PM, Richard Cooper
> <richard@richardcooper.net> wrote:
>> Hi All,
>>
>> I have two machines where I've been testing various btrfs based backup
>> strategies. They are both Cent OS 6 with the standard kernel and
>> btrfs-progs RPMs from the CentOS repos.
>>
>> - kernel-2.6.32-220.17.1.el6.x86_64 - btrfs-progs-0.19-12.el6.x86_64
>
> In btrfs terms, 2.6.32 is ... stone age :P
Indeed! As both the kernel option and the btrfs wiki state, btrfs is an
experimental filesystem under heavy development and fit for testing, not
operational use. Oracle and I believe SuSE have paid support now if you
want it, but to some extent that's by locking down your options, and
otherwise, it's simply offering to let you pay them for recovery efforts
if something does go wrong.
Meanwhile, "under heavy development" in practice means that if you're
using a kernel older than the last upstream release or two (so 3.3 at the
very oldest!), you're testing extremely outdated code and the value of
those tests both in reporting problems and in conclusions you yourself
may draw from them is extremely limited.
Latest upstream release, now 3.4, is really the oldest you should be
running for btrfs testing, and many people run the development kernel rcs,
3.5-rc4 currently, or git-kernels, either Linus or btrfs-next (see the
wiki).
So 2.6.32... Do you still run kernel 2.2 on your non-btrfs machines, by
any chance? Because that's what's comparable, in terms of btrfs
development vs kernel development.
>> What should I do now? Do I need to upgrade to a more recent btrfs?
>
> Yep
>
>> If so, how?
>
> https://blogs.oracle.com/linux/entry/
oracle_unbreakable_enterprise_kernel_release
> http://elrepo.org/tiki/kernel-ml
Or read up on the wiki and go mainline kernel:
https://btrfs.wiki.kernel.org/
https://btrfs.wiki.kernel.org/index.php/Main_Page#Documentation
https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories
--
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
next prev parent reply other threads:[~2012-06-29 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 10:11 Kernel panic from "btrfs subvolume delete" Richard Cooper
2012-06-29 10:42 ` Fajar A. Nugraha
2012-06-29 11:17 ` Duncan [this message]
2012-06-29 14:23 ` Richard Cooper
2012-06-29 14:29 ` Fajar A. Nugraha
2012-06-29 14:29 ` Hugo Mills
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2012.06.29.11.17.17@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).