public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: <linux-btrfs@vger.kernel.org>
Subject: btrfs-progs: -q/--quiet not accepted for "btrfs subvolume" subcommands
Date: Tue, 17 Dec 2024 19:56:49 +0500	[thread overview]
Message-ID: <20241217195649.143d2c94@nvm> (raw)

Hello,

# btrfs --version
btrfs-progs v6.6.3

# btrfs sub create --help
usage: btrfs subvolume create [options] [<dest>/]<name> [[<dest2>/]<name2> ...]

    Create subvolume(s)

    Create subvolume(s) at specified destination.  If <dest> is not given
    subvolume <name> will be created in the current directory. Options apply
    to all created subvolumes.

    -i <qgroupid>             add the newly created subvolume(s) to a qgroup. This option can be given multiple times.
    -p|--parents              create any missing parent directories for each argument (like mkdir -p) 
    
    Global options:
    -q|--quiet                print only errors 

# btrfs sub create -q test
btrfs subvolume create: invalid option 'q'
Try 'btrfs subvolume create --help' for more information

# btrfs sub create --quiet test
btrfs subvolume create: unrecognized option '--quiet'
Try 'btrfs subvolume create --help' for more information

Same for "snapshot". Maybe also some or all others, did not check further.

This is the case also on btrfs-progs versions 5.10 and 6.2.

-- 
With respect,
Roman

             reply	other threads:[~2024-12-17 14:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 14:56 Roman Mamedov [this message]
2025-03-19 22:12 ` btrfs-progs: -q/--quiet not accepted for "btrfs subvolume" subcommands David Sterba
2025-03-19 22:46   ` Roman Mamedov
2025-03-20  1:18     ` David Sterba

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=20241217195649.143d2c94@nvm \
    --to=rm@romanrm.net \
    --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