All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moviuro <moviuro@gmail.com>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs and btrfs(8) inconsistencies
Date: Thu, 4 Feb 2016 13:04:35 +0100	[thread overview]
Message-ID: <CAM=f9=XYdeLDUUMgnCOGePJSaV3yh4Zi8CpjoPo33yqQU=8xZg@mail.gmail.com> (raw)
In-Reply-To: <1724218.nF6PTv1Cei@merkaba>

On Thu, Feb 4, 2016 at 11:14 AM, Martin Steigerwald <martin@lichtvoll.de> wrote:
> Am Donnerstag, 4. Februar 2016, 09:57:54 CET schrieb Moviuro:
>> > Although personally I like to let all the backward compatibility
>> > things go hell, but that's definitely not how things work. :(
>> >
>> > 2) End-user taste.
>> > Some end-users like such info as feedback of success.
>> > Of course other users like it act as silent as possible.
>>
>> I'm pretty sure that's... not the case. Almost everything on GNU/Linux
>> is silent. cd(1) is silent, cp(1) is silent, rm(1)...
>> What they all have though is a -v|--verbose switch.
>
> The various mkfs commands are not. Not one of them I know of. Additionally
> each one gives a different output.
>
> pvcreate, vgcreate, lvcreate and as well as the remove commands and probably
> other LVM commands are not (no one could argue, that from their ideas they
> come from HP/UX, but thats a Unix as well):
>
> merkaba:~> lvcreate -L 1G -n bla sata
>   Logical volume "bla" created.
>
> And I think, not testing right now, that also mdadm is not silent on creating
> a softraid.
>
> So while I agree with you that regular shell commands (coreutils, util-linux)
> are silent on success usually this does not appear to be the case with storage
> related commands in GNU/Linux.
To be perfectly honnest, my inspiration comes from zfs(8) on FreeBSD.
I'm pretty sure there is some inspiration we can find in its behavior.
(see https://www.freebsd.org/cgi/man.cgi?zfs(8) )
The output has both a human-readable form (using column(1)) and a
machine-parseable form (e.g. zfs get -o value used /zroot).
The output is limited to what is truly useful, etc.
I have not had any previous experience with any other FS or softraid
solutions, so I'm not familiar with those commands you gave, Martin.

Also, making silence a default option helps spare some typing:
>/dev/null : 11 char (force silence)
-v : 3 char (force verbose) (it's also far more readable)

I should start working on said guidelines.md later today or this weekend.

> I don´t have a clear oppinion about it other than I´d like to see some
> standard too. coreutils / util-linux both them to have some kind of standard,
> although not necessarily the same standard I bet. And I am not sure whether it
> is documented somewhere.

  reply	other threads:[~2016-02-04 12:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 21:54 btrfs-progs and btrfs(8) inconsistencies Moviuro
2016-02-04  1:33 ` Qu Wenruo
2016-02-04  8:57   ` Moviuro
2016-02-04  9:15     ` Qu Wenruo
2016-02-04 10:14     ` Martin Steigerwald
2016-02-04 12:04       ` Moviuro [this message]
2016-02-04 12:53       ` Austin S. Hemmelgarn
2016-02-04 19:40         ` Chris Murphy
2016-02-04 20:19           ` Austin S. Hemmelgarn
2016-02-04 20:40             ` Moviuro
2016-02-05 13:04               ` Austin S. Hemmelgarn
2016-02-04 17:17   ` Goffredo Baroncelli
2016-02-04 19:48     ` Hugo Mills
2016-02-04 20:10     ` Chris Murphy
2016-02-04 18:22 ` Chris Murphy
2016-02-05  3:11 ` Anand Jain
2016-02-05 12:59   ` Austin S. Hemmelgarn
2016-02-06 21:35   ` Chris Murphy
2016-02-07 10:07   ` Qu Wenruo
2016-02-07 20:26     ` Goffredo Baroncelli
2016-03-08 16:02 ` David Sterba
2016-03-09 10:02   ` Moviuro

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='CAM=f9=XYdeLDUUMgnCOGePJSaV3yh4Zi8CpjoPo33yqQU=8xZg@mail.gmail.com' \
    --to=moviuro@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=martin@lichtvoll.de \
    --cc=quwenruo@cn.fujitsu.com \
    /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.