14%
03.02.2022
,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25,57
26,58
27,59
28,60
29,61
30,62
31,63
The lstopo tool
14%
21.01.2020
8 2 488383488 sda2
12 8 16 6836191232 sdb
13 8 64 6836191232 sde
14 8 80 39078144 sdf
15 8 48 6836191232 sdd
16 8 32 6836191232 sdc
17 11 0 1048575 sr0
14%
25.03.2020
8 2 488383488 sda2
12 8 16 6836191232 sdb
13 8 64 6836191232 sde
14 8 80 39078144 sdf
15 8 48 6836191232 sdd
16 8 32 6836191232 sdc
17 11
14%
18.06.2014
Size Intervals (KB):
[ 0- 1 KB]: 156455 ( 40.31%) ( 40.31% cumulative)
[ 1- 2 KB]: 38278 ( 9.86%) ( 50.18% cumulative)
[ 2- 4 KB]: 30822 ( 7.94%) ( 58.12% cumulative)
[ 4- 8
14%
25.01.2022
_notes.txt
4 ext2_notes.txt.gz 12 md_article_2.tar.gz 4 squashfs_notes.txt~
4 EXT4_JOURNAL_ARTICLE 4 METARATES 4 STORAGE038
424 ext4_journal_article.tar.gz 48
14%
05.08.2024
= [size][size]int {{0},{0},}
08
09 for i := 0; i < size; i++ {
10 for j := 0; j < size; j++ {
11 array[i][j]++
12 }
13 }
14
15
14%
29.09.2020
SQL docs [12] and check that the database container is running in Docker Engine, as well:
$ docker run --name test-mysql -e MYSQL_ROOT_PASSWORD=nothingtoseehere-d mysql
$ docker ps | grep mysql
48f5b3719cd0
14%
01.08.2019
CREATED SIZE
nginx f09fe80eb0e7 12 days ago 109MB
nginx latest 35640fed495c 12 days ago 109MB
Backdoor Access
Considering how well Docker Scan handled
14%
27.08.2014
provide useful information beyond how ioprof works. The benchmark I will use is IOzone.
IOzone Example
The ioprof test ran while I was running iozone three ways: (1) sequential write testing with 1MB
14%
12.05.2021
of read and write commands whose size > segment size = 12
Vendor (Seagate/Hitachi) factory information
number of hours powered up = 264.67
number of minutes until next internal SMART test = 48
Error counter log:
Errors
