21%
20.02.2012
.57, 0.00, 12.76, 85, 0
2012-01-09 21:09:21, 84, 4.84, 0, 0.29, 17.36, 0.00, 5.09, 90, 0
2012-01-09 21:09:47, 80, 4
21%
07.01.2014
.
[laytonjb@home4 TEST]$ du -sh backup.0
14M backup.0
[laytonjb@home4 TEST]$ du -sh backup.1
12M backup.1
[laytonjb@home4 TEST]$ du -sh backup.2
9.2M backup.2
[laytonjb@home4 TEST]$ du -sh backup.3
7.7M backup
21%
18.07.2013
buffered disk reads: 616 MB in
3.00 seconds = 205.03 MB/sec
$ hdparm -T /dev/sda
/dev/sda:
Timing cached reads: 6292 MB in
2.00 seconds = 3153.09 MB/sec
If this were a spinning disk, you would also
21%
11.04.2016
(512 MB) copied, 49.1424 s, 10.4 MB/s
If you want to empty the read and write cache for benchmark purposes, you can do so using:
sync; echo 3 > /proc/sys/vm/drop_caches
Sequential access
21%
25.03.2020
] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sdd1[5] sde1[4] sdc1[2] sdb1[1] nvme0n1p1[0](J)
20508171264 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [UU
21%
30.11.2025
from compromised systems is John the Ripper (John). John is a free tool from Openwall [1]. System administrators should use John to perform internal password audits. It's a small (<1MB) and simple
21%
29.09.2020
sitting at less than 50MB (and using less than half the RAM of a standard cluster) the binary that runs K3s is a sight to behold and well worth getting your hands on. Especially when it's deemed production
21%
21.01.2020
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
Next, verify that the RAID configuration has been created (Listing 3). You will immediately notice that the array initializes
21%
30.11.2025
01 # zfs set volsize=3g mypool/vol1
12 02 # zfs get volsize mypool/vol1
13 03 NAME PROPERTY VALUE SOURCE
14 04 mypool/vol1 volsize 3G -
15 05 # sbdadm modify-lu -s 3g 600144f05f71070000004bc981ec0001
20%
31.10.2025
, Fedora) to postpone the move to Btrfs as the standard filesystem.
Conveniently, the latest long-term support version of Ubuntu, 12.04, was released at the end of April based on kernel version 3
