Confused cloud test hard drive performance, resulting in hard disk is full, Baidu many practical methods do not solve, in reminding operation and maintenance of the power of God can restore the hard disk capacity of the cloud.
Background to the issue:
Disk read the script: fio --name = fio-test --direct = 1 --size = 20G --refill_buffers --norandommap --randrepeat = 0 --filename = / dev / vdb --rw = randread --bs = 4k --ioengine = aio --cgroup_nodelete = 1 --iodepth = 32
First, run the above script finished, df -h query memory is as follows:
Already filled, you can not run any commands
Solution:
1. Uninstall disk
umount /dev/vdb
2, re-format the partition to
The content of the following error messages for some of the solutions (for your own reference)
1, partition formatting step
steps:
1. Partition
the warning is noted that FIG Tip: The Re-Reading failed with error Partition Table 25:. Inappropriate Device for the ioctl
of The Kernel uses Still The Table of The Old Table Will new new AT BE Used. the Next or the After you reboot at The run partprobe (8) or kpartx (8)
Syncing Disks. (partition fails, you need to reboot, or run partprobe to take effect)
2, to see if there is a partition success
3. After the success of the partition, formatting, error
Could not STAT / dev / vdb1 - No SUCH File or Directory
at The Device Apparently does not exist; the Specify IT DID you correctly &?
Query just partition dev / dvb1 device file exists, the results showed the absence of
Method a: can be manually added, the command: mknod / dev / vdb1 b 253 17
Method Two: As shown in FIG: partprobe performed, re-read the partition
under the command executed partprobe
partprobe rpm package contained in the parted. partprobe kernel can be modified in the partition table, so kernel reread the partition table. Thus, this command can be used to create partitions and partitions in the system to recognize without restarting the machine.
4, try again following format, or unsuccessful, the display is already in use:
given: / dev / vdb1 is apparently in use by the system; will not make a filesystem here!
5. Just uninstall, dev / vdb can, umount / dev / vdb, formatted again in FIG.
6. remount, Mount dev / vdb1 / test1
df -h, check whether to mount a successful
disk capacity recovery Success!
