On 19 Jan 2018 22:26, Peng Yu wrote:
> There are ~7000 .txt files in a directory on glusterfs. Here are the
> run time of the following two commands. Does anybody know why the find
> command is much slower than *.txt. Is there a way to change the api
> that `find` uses to search files so that it
Hi,
There are ~7000 .txt files in a directory on glusterfs. Here are the
run time of the following two commands. Does anybody know why the find
command is much slower than *.txt. Is there a way to change the api
that `find` uses to search files so that it can be more friendly to
glusterfs?
$
tag 30174 notabug
close 30174
stop
On 19/01/18 10:19, devz...@web.de wrote:
> Hi,
>
> i`m testing wear-levelling of an SLC USB Stick (cheap one i want to
> use them for long-term data-logging) and found shred to be a useful
> and fast utility to repeatedly overwrite a file's region (the
>
On 01/19/2018 10:19 AM, devz...@web.de wrote:
shred is doing
wrong.
Looks like a bug to me.
I don't see why it is a bug. It does appear to be intended behavior.
Look in the source code, at src/shred.c, and look for "Invert the first
bit of every sector."
Am 16.12.2017 um 22:14 schrieb Assaf Gordon:
> Hello,
>
> On 2017-12-16 01:52 PM, kalle wrote:
>> did you plan to respond my mail?
>
> Please remember GNU coreutils is maintained by volunteers.
> We aim for best effort in incorporating improvement suggestions
> from contributors, but there is
i tried to compare performance of shred and dd, because a colleague told, shred
-n0 -z would be faster.
the shred manpage tells:
If FILE is -, shred standard output
But:
# shred - | pv >/dev/null
shred: - invalid file type
0 B 0:00:00 [ 0 B/s] [<=>
i found
Hi,
i`m testing wear-levelling of an SLC USB Stick (cheap one i want to
use them for long-term data-logging) and found shred to be a useful
and fast utility to repeatedly overwrite a file's region (the
datalogger i'm building will use rrdtool)
As i already did some other testing before, shred
tag 30160 notabug
close 30160
stop
On 01/18/2018 01:31 PM, Rdrpenguin Minecraft and More wrote:
> If 'cat' is run with a big enough file, say /dev/sda, the terminal gets
> corrupted. This corruption may also extend beyond the terminal.
>
> Steps to reproduce:
> 1. Run '/bin/cat /dev/sda'.
> 2.
