On Mon, Mar 07, 2016 at 07:15:24PM +0100, Garmine 42 wrote:
> According to the manpage duplicate -s is valid and the high CPU usage is
> intended. Although a warning could be valid in case of -ss.
Or use a different letter. Anyway, that was my stupidity and no
developer time should be wasted for
On Mon, Mar 07, 2016 at 11:09:57AM -0700, Chris Murphy wrote:
> On Mon, Mar 7, 2016 at 10:38 AM, Marc Haber
> wrote:
> > On Mon, Mar 07, 2016 at 06:27:17PM +0100, Marc Haber wrote:
> >> how long is btrfs-image taking to run on a 400 GiB filesystem?
> >>
> >> I have
On Mon, Mar 7, 2016 at 10:38 AM, Marc Haber wrote:
> On Mon, Mar 07, 2016 at 06:27:17PM +0100, Marc Haber wrote:
>> how long is btrfs-image taking to run on a 400 GiB filesystem?
>>
>> I have /bin/btrfs-image -s -t 8 -s /dev/mapper/mydevice - | pixz -9 >
>>
On Mon, Mar 07, 2016 at 06:27:17PM +0100, Marc Haber wrote:
> how long is btrfs-image taking to run on a 400 GiB filesystem?
>
> I have /bin/btrfs-image -s -t 8 -s /dev/mapper/mydevice - | pixz -9 >
> file.on.other.fs running for four hours now
Strike my question please, I didn't see that I had
Hi,
how long is btrfs-image taking to run on a 400 GiB filesystem?
I have /bin/btrfs-image -s -t 8 -s /dev/mapper/mydevice - | pixz -9 >
file.on.other.fs running for four hours now, and it's constantly
taking a single core, but is neither reading from the disk nor writing
to its output.
Is that