From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs filesystem df not working
Date: Sun, 17 Oct 2010 10:13:49 +1100 [thread overview]
Message-ID: <201010171013.54097.chris@csamuel.org> (raw)
In-Reply-To: <AANLkTinaO7p-yc=eiTOt+wLSVJuJAH3oyG0sKYxJ366y@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 921 bytes --]
On Sun, 17 Oct 2010 12:46:14 am Leonidas Spyropoulos wrote:
> Sorry, I don't understand what "backport the changes" means?
Chris means that you can take the changes that have gone into
the btrfs code since 2.6.32 and try and port them back to the
old 2.6.32 kernel code. It's a non-trivial task.
Luckily for you Mitch Harder posted a message called "Backporting
Recent Btrfs Patches to 2.6.32" yesterday where he described his
attempts to do just that, he has a git repository for the resulting
kernel here:
http://gitweb.sabayon.org/?p=linux/kernel/btrfs-backport.git;a=summary
You can find Mitch's original message here:
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/7102
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
prev parent reply other threads:[~2010-10-16 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 10:12 btrfs filesystem df not working Leonidas Spyropoulos
[not found] ` <AANLkTi=1VgjsZoJqzkp-zto3vAMUThh7TN054xQ1mpEu@mail.gmail.com>
2010-10-12 13:45 ` Leonidas Spyropoulos
2010-10-13 0:43 ` Chris Mason
2010-10-13 9:52 ` Leonidas Spyropoulos
2010-10-13 15:08 ` Chris Mason
2010-10-14 11:45 ` Leonidas Spyropoulos
2010-10-14 16:06 ` David Nicol
2010-10-14 16:42 ` Chris Mason
2010-10-16 13:46 ` Leonidas Spyropoulos
2010-10-16 15:40 ` Chester
2010-10-16 23:13 ` Chris Samuel [this message]
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=201010171013.54097.chris@csamuel.org \
--to=chris@csamuel.org \
--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).