From: "Fajar A. Nugraha" <list@fajar.net>
To: Richard Cooper <richard@richardcooper.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Kernel panic from "btrfs subvolume delete"
Date: Fri, 29 Jun 2012 17:42:26 +0700 [thread overview]
Message-ID: <CAG1y0seoS2c7d=jQgrZNF0aAJPrgTKbL1v6JzFigCk9ZMZ7H+w@mail.gmail.com> (raw)
In-Reply-To: <B53F1BEB-C285-4A01-A61A-4B324CB6FA7F@richardcooper.net>
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
> 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
--
Fajar
next prev parent reply other threads:[~2012-06-29 10:42 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 [this message]
2012-06-29 11:17 ` Duncan
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='CAG1y0seoS2c7d=jQgrZNF0aAJPrgTKbL1v6JzFigCk9ZMZ7H+w@mail.gmail.com' \
--to=list@fajar.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=richard@richardcooper.net \
/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).