linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Blanke <felixblanke@gmail.com>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: How to see raid level?!
Date: Mon, 1 Nov 2010 13:14:08 +0100	[thread overview]
Message-ID: <20101101121408.GA2837@scooter> (raw)
In-Reply-To: <AANLkTinc0zL1hmLOD0YpHShu5Jg8eiZwZtJdcVZaG5QO@mail.gmail.com>

Ah, the magic one :)

Is that a patch for the kernel or the btrfs progs?


If you know where to get that patch it would be nice. It isn't an important issue but it
would be nice to see if my home really uses raid1 for data :)


Regards,
FElix


On 01. November 2010 - 04:33, cwillu wrote:
> Date: Mon, 1 Nov 2010 04:33:30 -0600
> From: cwillu <cwillu@cwillu.com>
> To: Felix Blanke <felixblanke@gmail.com>
> Cc: linux-btrfs@vger.kernel.org
> Subject: Re: How to see raid level?!
> 
> On Mon, Nov 1, 2010 at 4:17 AM, Felix Blanke <felixblanke@gmail.com> wrote:
> > Hi,
> >
> > I saw some reports of ppl in this list who did a "btrfs fi df /path" and saw the
> > raidlevel of the data, metadata etc.
> >
> > How? :)
> >
> > I'm using the git version of the btrfs progs and 2.6.36, but I don't see those
> > informations.
> >
> > Btrfs v0.19-35-g1b444cd-dirty
> >
> >
> > What am I doing wrong? :(
> 
> You didn't include the magic patch.  :p
> 
> Raid level reporting was broken for a while, josef sent some patches
> recently that fixed it, which I saw in cmason's pull request for
> 2.6.37.
---end quoted text---

  reply	other threads:[~2010-11-01 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 10:17 How to see raid level?! Felix Blanke
2010-11-01 10:33 ` cwillu
2010-11-01 12:14   ` Felix Blanke [this message]
2010-11-01 12:24     ` cwillu

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=20101101121408.GA2837@scooter \
    --to=felixblanke@gmail.com \
    --cc=cwillu@cwillu.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).