From: Karl-Philipp Richter <krichter@posteo.de>
To: linux-btrfs@vger.kernel.org
Subject: How to skip "looping a lot" question of btrfs restore 3.15?
Date: Tue, 29 Jul 2014 00:35:59 +0200 [thread overview]
Message-ID: <53D6D04F.7050904@posteo.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
Hi together,
In the current HEAD (3f11e516db629f7a662bfd6376231817b4e34cc9) of
https://github.com/kdave/btrfs-progs.git (I assume this list is the
right address because I got some hints to the project from here) the
btrfs restore subcommand asks often (up to 100 time during restauration
of 400 GB)
We seem to be looping a lot on /a/path/to/our/precious, do you want
to keep going on ? (y/N):
which can't be suppressed with the `-i` option (which might be right
because it's technically not an error), but I can't see how to get
around this. Am I missing something? Otherwise it would be nice to have
an extra option maybe with an argument how often "we" are looping on a
file before the command asks for interaction.
Best regards,
Karl-P. Richter
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 538 bytes --]
next reply other threads:[~2014-07-28 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 22:35 Karl-Philipp Richter [this message]
2014-07-29 0:09 ` How to skip "looping a lot" question of btrfs restore 3.15? Justin Maggard
2014-07-29 1:03 ` Karl-Philipp Richter
2014-08-16 22:35 ` Karl-Philipp Richter
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=53D6D04F.7050904@posteo.de \
--to=krichter@posteo.de \
--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.