This is a very easy-to-manipulate system, of course, with perfect functionality. The gaps in Linux systems can be weighed in the future.
When the disk is full, due to the asynchronous read and write operation, the application layer does not know that the disk is full, this time continue to the memory of the page table box, continue to populate, there is a problem, the Write function will detect the disk space, In fact, only when the disk driver is aware of its own space is not enough enospec to be able to exit read and write, this time there is a problem:
How to handle the extra data in memory????????????????????
This is our test direction for this experiment!!!!!!!!!!!!
The following questions are raised at two points:
1) in the process of reading and writing (asynchronous read-write), when to detect the disk space, in fact, due to asynchronous read and write, there are the following drawbacks: A large number of data accumulation in memory, memory space 4GB, the actual mountain operating system occupies a memory space of 2GB, that is, about 2GB of space is the disk of stale data (waiting for
2) Trial STATVFS function test disk space is accurate, this disk space in the process of reading and writing how much space is not available, visible but not touch, because the disk is about to run out, if the disk seek time will gradually increase. So it is very dangerous to haggle over a few grams of space, and in practical applications, a large amount of data accumulates in memory, causing memory tension and is also very dangerous.
Tentative idea of Andri as domestic control system