linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karl-Philipp Richter <krichter@posteo.de>
To: Justin Maggard <jmaggard10@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: How to skip "looping a lot" question of btrfs restore 3.15?
Date: Sun, 17 Aug 2014 00:35:30 +0200	[thread overview]
Message-ID: <53EFDCB2.5030701@posteo.de> (raw)
In-Reply-To: <53D6F2F5.9080107@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]

Hi,
I saw that the `a` answer in the `remotes/origin/integration-20140729`
branch only allows to skip the following question/interaction, for the
next after the next, the question is asked again.

-Kalle

Am 29.07.2014 um 03:03 schrieb Karl-Philipp Richter:
> Hi Justin,
> thanks for your help. I guess the patch will be available in the repos,
> soon, so I'll work with `yes` in the meantime because I'm not too
> familiar with patching in this form.
> 
> Best regards,
> Karl-P. Richter
> 
> Am 29.07.2014 um 02:09 schrieb Justin Maggard:
>> On Mon, Jul 28, 2014 at 3:35 PM, Karl-Philipp Richter
>> <krichter@posteo.de> wrote:
>>> 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
>>>
>>
>> I just posted the patch we use to get around that.  Or, if you don't
>> want to build a modified btrfs-progs, you could always use the `yes`
>> command to press y for you.
>>
>> -Justin
>>
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2014-08-16 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28 22:35 How to skip "looping a lot" question of btrfs restore 3.15? Karl-Philipp Richter
2014-07-29  0:09 ` Justin Maggard
2014-07-29  1:03   ` Karl-Philipp Richter
2014-08-16 22:35     ` Karl-Philipp Richter [this message]

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=53EFDCB2.5030701@posteo.de \
    --to=krichter@posteo.de \
    --cc=jmaggard10@gmail.com \
    --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).