linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: kathleen.hodge@emc.com
Cc: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs w/ckd
Date: Thu, 2 Jun 2011 21:43:06 +0100	[thread overview]
Message-ID: <20110602204306.GD8002@carfax.org.uk> (raw)
In-Reply-To: <47C68B986D117D40A7E109AE2FC85C291128DB4A33@MX01A.corp.emc.com>

[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]

   Hi, Kathleen,

On Thu, Jun 02, 2011 at 04:20:55PM -0400, kathleen.hodge@emc.com wrote:
> Hi Hugo, I don't seem to have mkfs.btrfs.  Here is the Red Hat 6.0 version I'm running, should it be included?
> 
> Linux LN164088.LSS.EMC.COM 2.6.32-71.el6.s390x #1 SMP Wed Sep 1 01:38:33 EDT 2010 s390x s390x s390x GNU/Linux

   OK, first -- kernel 2.6.32 is *massively* old in btrfs terms. There
are a whole bunch of pretty serious bugs that have been fixed between
then and now. You should really be running a kernel no earlier than
2.6.38: version 2.6.39 is preferable.

   You should also be using the latest btrfs-progs from the git
repository:

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git
$ git co tmp
$ make
$ sudo make install

   (You may need the libuuid-devel package to get this to build.
There's also a problem with the most recent gcc, but that probably
won't apply to you; it's easily dealt with if you do hit it).

   Once you've made and installed btrfs-progs, you will have
mkfs.btrfs, and the btrfs tool, which is used for managing your
filesystem.

   You should also ensure that you're keeping good and regular backups
of the data in your filesystem, and be prepared to use them -- btrfs
is still considered experimental, and if things go wrong, the fastest
way at the moment to get your data back is often to restore from
backups.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
     --- "I don't like the look of it,  I tell you." "Well, stop ---     
                          looking at it, then."                          

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

      parent reply	other threads:[~2011-06-02 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 19:45 btrfs w/ckd kathleen.hodge
2011-06-02 19:59 ` Hugo Mills
     [not found]   ` <47C68B986D117D40A7E109AE2FC85C291128DB4A33@MX01A.corp.emc.com>
2011-06-02 20:43     ` Hugo Mills [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=20110602204306.GD8002@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=kathleen.hodge@emc.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;
as well as URLs for NNTP newsgroup(s).