Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Julio E. Gonzalez P." <jegp@netvision.com.py>
To: Cristian Falcas <cristi.falcas@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: downgrade from kernel 3.17 to 3.10
Date: Tue, 21 Oct 2014 13:36:48 -0300	[thread overview]
Message-ID: <54468BA0.20405@netvision.com.py> (raw)
In-Reply-To: <CAMo7R_eZo=s1Rfw6H095c9vR0Nq3NuEaNMJjRD+DF2G-cVVs=Q@mail.gmail.com>

When you say "el6" you mean "el7" right? The last kernel for el7 is 
3.10.xxxxx
But Redhat lie a little with kernel version numbers. They say you have a 
3.10 kernel, but I think they backport a lot from newers kernels.
Probably the btrfs of redhat el7 is not really a btrfs from 3.10, maybe 
is btrfs from 3.12 or 3.14....how knows...  (I want to know better about 
this too...also using btfrs in rhel7)



On 10/21/2014 12:34 PM, Cristian Falcas wrote:
> I will start investigating how can we build our own rpms from the 3.16
> sources. Until then we are stuck with the ones from the official repos
> or elrepo. Which means 3.10 is the latest for el6. We used this until
> now and seems we where lucky enough to not hit anything bad.
>
> We upgraded to 3.17 because we use ceph on the machine with openstack
> and on the ceph site they recommended >3.14. And because we need
> writable snapshots, we are forced to use btrfs under ceph.
>
> Thank you all for your advice.
>
>


  parent reply	other threads:[~2014-10-21 17:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21  8:13 downgrade from kernel 3.17 to 3.10 Cristian Falcas
2014-10-21 11:26 ` Duncan
2014-10-21 13:18   ` Cristian Falcas
2014-10-21 15:13     ` Robert White
2014-10-21 15:20     ` Robert White
2014-10-21 15:34       ` Cristian Falcas
2014-10-21 15:58         ` Austin S Hemmelgarn
2014-10-21 16:19         ` Chris Murphy
2014-10-21 16:26           ` Chris Murphy
2014-10-21 16:36         ` Julio E. Gonzalez P. [this message]
2014-10-21 17:55           ` Cristian Falcas
2014-10-21 16:07     ` Chris Murphy
2014-10-22  2:24       ` Duncan
2014-10-21 15:04 ` Robert White

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=54468BA0.20405@netvision.com.py \
    --to=jegp@netvision.com.py \
    --cc=cristi.falcas@gmail.com \
    --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