Also to note - zpools get really unhappy when allocation gets up above 80% - a
set of pre-allocated thick-provisioned zvols on a fresh zpool set aside for
this purpose is probably ok to take above that limit though, but you might want
to workshop that ...
On Thu, 18 Feb 2021, at 11:15, Malcolm
On Wed, 17 Feb 2021, Bob Proulx wrote:
Starting a new process that does not know how to detach from the
controlling terminal is the point where you either need it to know
how to call setsid(2) or you need something else installed on the
system which knows how to call setsid(2).
The BSDs (and
I typically use ZFS on Solaris or FreeBSD but would recommend using a different
zpool for swap if you can so you can have a different vdev layout more suited
to that load (ie, RAID1 rather than RAID5) and/or to tweak other settings as
desired independently of your data zpools
Either way,
Sad Clouds writes:
> On Wed, 17 Feb 2021 13:15:39 -0500
> Greg Troxel wrote:
>
>>
>> Suppose I create a 16G zvol on a pool that is a disklabel partition on
>> an SSD. I would expect read/write performance that is near the
>> native SSD read/write speed.
>
> Why would you expect that? In
On Wed, 17 Feb 2021 13:15:39 -0500
Greg Troxel wrote:
>
> Suppose I create a 16G zvol on a pool that is a disklabel partition on
> an SSD. I would expect read/write performance that is near the
> native SSD read/write speed.
Why would you expect that? In other words, you're expecting that a
W dniu 17.02.2021 o 21:56, Edgar Pettijohn pisze:
If you have perl available the following should do what you
need. Wouldn't be too difficult to write something similar
in C as well.
#!/usr/bin/env perl
use strict;
use warnings;
use POSIX qw//;
sub daemonize {
defined (my $pid =
If you have perl available the following should do what you
need. Wouldn't be too difficult to write something similar
in C as well.
#!/usr/bin/env perl
use strict;
use warnings;
use POSIX qw//;
sub daemonize {
defined (my $pid = fork()) or die "Can't fork: $!";
exit if $pid;
Bartek Krawczyk wrote:
> Oh I should have been more clear from the start. This is for rc.d script for
> wip/adguardhome. Probably during startup it doesn't really matter,
I believe you are correct. During boot time all processes start from
the init daemon and will not be attached to a
Suppose I create a 16G zvol on a pool that is a disklabel partition on
an SSD. I would expect read/write performance that is near the native
SSD read/write speed.
I got >400 MB/s on read, and only about 80 MB/s write. I wrote again,
guessing that the read was returning synthetic zeros and
