On 2016-05-25 21:03, Duncan wrote:
> Dmitry Katsubo posted on Wed, 25 May 2016 16:45:41 +0200 as excerpted:
>> * Would be nice if 'btrfs scrub status' shows estimated finishing time
>> (ETA) and throughput (in Mb/s).
>
> That might not be so easy to implement. (Caveat, I'm not a dev, just a
>
Nicholas D Steeves posted on Wed, 25 May 2016 16:36:13 -0400 as excerpted:
> On 25 May 2016 at 15:03, Duncan <1i5t5.dun...@cox.net> wrote:
>> Dmitry Katsubo posted on Wed, 25 May 2016 16:45:41 +0200 as excerpted:
>>> btrfs-restore [needs an o]ption that applies (y) to all questions
>>>
On 25 May 2016 at 15:03, Duncan <1i5t5.dun...@cox.net> wrote:
> Dmitry Katsubo posted on Wed, 25 May 2016 16:45:41 +0200 as excerpted:
>> btrfs-restore:
>>
>> * It does not restore special files like named pipes and devices.
>> * Hard-linked files are not correctly restored (they all turn into
>>
Dmitry Katsubo posted on Wed, 25 May 2016 16:45:41 +0200 as excerpted:
> Dear btrfs community,
>
> I hope btrfs developers are open for suggestions.
>
> btrfs-scrub:
>
> * Would be nice if 'btrfs scrub status' shows estimated finishing time
> (ETA) and throughput (in Mb/s).
That might not be
Dear btrfs community,
I hope btrfs developers are open for suggestions.
btrfs-scrub:
* Would be nice if 'btrfs scrub status' shows estimated finishing time
(ETA) and throughput (in Mb/s).
* Not possible to start scrub for all devices in the volume without
mounting it.
btrfs-restore:
* It