From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID1 disk upgrade method
Date: Thu, 28 Jan 2016 22:51:57 +0000 (UTC) [thread overview]
Message-ID: <pan$76889$d2dd6b74$a38ccc40$d082f0f6@cox.net> (raw)
In-Reply-To: CAJCQCtT3in9KS1zrQ7B7mTeAK1ODFKUBKXsR7Pz-zbgoduN0XQ@mail.gmail.com
Chris Murphy posted on Thu, 28 Jan 2016 12:39:20 -0700 as excerpted:
> I've gotten tripped by this more than once myself, and have to keep
> coming back to the man page; is it max:2 or 2:max or? Actually the
> easier thing to do is skip important info and you get a mini cheat sheet
> instead of the full man page, so you can do
>
> [chris@f23m ~]$ btrfs fi resize btrfs filesystem resize: too few
> arguments usage: btrfs filesystem resize
> [devid:][+/-]<newsize>[kKmMgGtTpPeE]|[devid:]max <path>
>
> While you don't get the devid 1 is default clue with this, you get the
> syntax formatting.
When I first started with btrfs, I setup a helper script, that checks for
command and subcommand and a reasonable number of parameters. If it gets
them, it passes everything on as-is. If it doesn't, or if they don't
look like commands/subcommands that btrfs will understand, it gives you
the list of commands/subcommands for that level, or prints the --help
output and asks for additional parameters. Then it prints the assembled
command for you and asks for a final OK before running it.
Later, I modified it to handle mkfs.btrfs as well, taking info from my
fstab, etc, so I can recreate the backup filesystems and it'll set label,
raid1, devices, btrfs feature options, etc, then again print the
assembled btrfs.mkfs and ask for final OK before running it.
That way I don't have to keep track of all the parameter details for the
various commands and subcommands. If I happen to remember them I can add
them to the initial commandline. If not, I get prompted for them as
appropriate. =:^) That, or creating a bunch of separate scriptlet stubs
or aliases that take care of most of the details (the solution I used for
emerge, the default gentoo package manager), are the two ways I've found
to deal with these all-in-one commands, which otherwise tend to be way
too complex for me to work with, without constantly referencing the
manpage as I try to enter the command.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-01-28 22:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 3:45 RAID1 disk upgrade method Sean Greenslade
2016-01-22 4:37 ` Chris Murphy
2016-01-22 10:54 ` Duncan
2016-01-23 21:41 ` Sean Greenslade
2016-01-24 0:03 ` Chris Murphy
2016-01-27 22:45 ` Sean Greenslade
2016-01-27 23:55 ` Sean Greenslade
2016-01-28 12:31 ` Austin S. Hemmelgarn
2016-01-28 15:37 ` Sean Greenslade
2016-01-28 16:18 ` Chris Murphy
2016-01-28 18:47 ` Sean Greenslade
2016-01-28 19:37 ` Austin S. Hemmelgarn
2016-01-28 19:46 ` Chris Murphy
2016-01-28 19:49 ` Austin S. Hemmelgarn
2016-01-28 20:24 ` Chris Murphy
2016-01-28 20:41 ` Sean Greenslade
2016-01-28 20:44 ` Austin S. Hemmelgarn
2016-01-28 23:01 ` Chris Murphy
2016-01-29 12:14 ` Austin S. Hemmelgarn
2016-01-29 20:27 ` Henk Slager
2016-01-29 20:40 ` Austin S. Hemmelgarn
2016-01-29 22:06 ` Henk Slager
2016-02-01 12:08 ` Austin S. Hemmelgarn
2016-01-29 20:41 ` Chris Murphy
2016-01-30 14:50 ` Patrik Lundquist
2016-01-30 19:44 ` Chris Murphy
2016-02-04 19:20 ` Patrik Lundquist
2016-01-28 19:39 ` Chris Murphy
2016-01-28 22:51 ` Duncan [this message]
2016-02-14 0:44 ` Sean Greenslade
2016-01-22 14:27 ` Austin S. Hemmelgarn
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='pan$76889$d2dd6b74$a38ccc40$d082f0f6@cox.net' \
--to=1i5t5.duncan@cox.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;
as well as URLs for NNTP newsgroup(s).