27%
30.11.2025
.network.type = veth
04 lxc.network.flags = up
05 lxc.network.link = br0
06 lxc.network.hwaddr = 08:00:12:34:56:78
07 #lxc.network.ipv4 = 0.0.0.0
08 lxc.network.ipv4 = 192.168.1.69
09 lxc.network.name = eth0
10 lxc
27%
30.11.2025
Model";
11 $work = "ebiz-tx";
12 $node1 = "WebServer";
13 $node2 = "AppServer";
14 $node3 = "DBMServer";
15 $think = 0.0 * 1e-3; # as per test system
16 $dtime = 2.2 * 1e-3; # dummy service time
17
18
27%
30.11.2025
, the MAC address (e.g., 00:11:22:33:44:55) is split down the middle, and two bytes containing FF:FE are inserted. This gives you 64 bits. If the basis is a globally unique address (which should be the case
27%
30.11.2025
/0K /s] [4137 /0 iops] [eta 00m:06s]
In the example, the first job is performing a sequential read, marked as r in square brackets, while Fio hasn't initialized the second job, marked as P
26%
30.11.2025
VALUES ('$hostname', '$ip', 'A', 86400, $time, 1, 0)/;
21 } else {
22 $sql = qq/UPDATE records SET content = '$ip' WHERE name = '$hostname'/;
23 }
24 $sth->finish();
25 $dbh->do($sql) or warn $dbh
26%
30.11.2025
. In the test scenario, I defined a backup schedule with the following settings:
Schedule: weekly
Daily full backup: Monday – Friday 20:00
Daily incremental backup: Monday – Friday 08:00--18:00, 30
26%
30.11.2025
:31:40: [6694] DEBUG: (lifebyte = 0:0)
04 2011-01-28 17:31:40: [6694] DEBUG: enctype = 7:7
05 2011-01-28 17:31:40: [6694] DEBUG: (encklen = 128:128)
06 2011-01-28 17:31:40: [6694] DEBUG: hashtype = SHA:SHA
07
26%
30.11.2025
: all cores
0x40: core: this core
0x30: prefetch: all inclusive
0x10: prefetch: Hardware prefetch only
0x00: prefetch: exclude hardware prefetch
0x08: (M)ESI: Modified
0x04: M
26%
30.11.2025
resource:
sudo mkfs.gfs2 -p lock_dlm -j2 -t pcmk:pcmk resource
resource
is the DRBD resource device node – for example, /dev/drbd/by-res/disk0/0
.
What's missing now is the filesystem resource
26%
30.11.2025
.33
164.69
0.75
rand_mat_stat
3.37
39.34
11.64
54.54
22.07
8.12
rand_mat_mul
1.00
1.18
0.70
1.65
8
