How to skip "looping a lot" question of btrfs restore 3.15?
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
Quoted 10 lines · Karl-Philipp Richter
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):
Quoted 9 lines
which can't be suppressed with the
-ioption (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
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:
Quoted 28 lines
Quoted 10 lines · Karl-Philipp Richter
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):Quoted 9 lines
which can't be suppressed with the
-ioption (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. RichterI 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
yescommand to press y for you.-Justin
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:
Quoted 38 lines
Hi Justin,
thanks for your help. I guess the patch will be available in the repos, soon, so I'll work withyesin the meantime because I'm not too familiar with patching in this form.Best regards,
Karl-P. RichterAm 29.07.2014 um 02:09 schrieb Justin Maggard:
Quoted 28 lines
Quoted 10 lines · Karl-Philipp Richter
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):Quoted 9 lines
which can't be suppressed with the
-ioption (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. RichterI 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
yescommand to press y for you.-Justin