All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stéphane Lesimple" <stephane_btrfs@lesimple.fr>
To: kreijack@inwind.it
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/1] btrfs-progs: fi usage: implement raid56
Date: Mon, 18 Mar 2019 20:12:10 +0100	[thread overview]
Message-ID: <26c40d46f4278edeb2604e26fda957ee@lesimple.fr> (raw)
In-Reply-To: <8679eb74-8c98-d54d-f69e-821a6eba1cd9@libero.it>

Le 2019-03-17 19:41, Goffredo Baroncelli a écrit :
> On 17/03/2019 13.51, stephane_btrfs@lesimple.fr wrote:
> [...]
>> -		if (!ratio)
>> -			warning("RAID56 detected, not implemented");
>> -
> 
> IIRC one of the problem which lead to this code was that the not root
> user cannot
> access to chunkinfo. So the (regular) user should be warned about
> that: the printed info may be not correct.


I think you may be referencing this other warning:

         ret = load_chunk_info(fd, chunkinfo, chunkcount);
         if (ret == -EPERM) {
                 warning("cannot read detailed chunk info, per-device 
usage will not be shown, run as root");

This one is still present, and matches exactly what you say:
it fires when btrfs fi usage is run under a non-root user.

The "RAID56 detected, not implemented" warning, on the other hand,
is displayed even under the root user, and indicates that it's normal
that most of the counters of "filesystem usage" are at zero, because
the code to compute these properly under raid5/raid6 isn't there yet,
and it's actually precisely this missing feature that my patch tries to 
add!

Thanks,

Stéphane.

  reply	other threads:[~2019-03-18 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17 12:51 [PATCH 0/1] btrfs-progs: fi usage: implement raid56 stephane_btrfs
2019-03-17 12:51 ` [PATCH 1/1] " stephane_btrfs
2019-03-17 18:41   ` Goffredo Baroncelli
2019-03-18 19:12     ` Stéphane Lesimple [this message]
2019-03-18 21:05       ` Goffredo Baroncelli
2019-03-17 23:23   ` Hans van Kranenburg
2019-03-18 19:41     ` Stéphane Lesimple
2019-03-19  1:14       ` Hans van Kranenburg

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=26c40d46f4278edeb2604e26fda957ee@lesimple.fr \
    --to=stephane_btrfs@lesimple.fr \
    --cc=kreijack@inwind.it \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.