NFSTEST_ALLOC(1) | nfstest_alloc 1.3 | NFSTEST_ALLOC(1) |
nfstest_alloc - Space reservation tests
nfstest_alloc --server <server> [options]
Verify correct functionality of space reservations so applications are able to reserve or unreserve space for a file. The system call fallocate is used to manipulate the allocated disk space for a file, either to preallocate or deallocate it. For filesystems which support the fallocate system call, preallocation is done quickly by allocating blocks and marking them as uninitialized, requiring no I/O to the data blocks. This is much faster than creating a file and filling it with zeros.
Basic allocate tests verify the disk space is actually preallocated or reserved for the given range by filling up the device after the allocation and make sure data can be written to the allocated range without any problems. Also, any data written outside the allocated range will fail with NFS4ERR_NOSPC when there is no more space left on the device. On the other hand, deallocating space will give the disk space back so it can be used by either the same file on regions not already preallocated or by different files without the risk of getting a no space error.
Performance testing using ALLOCATE versus initializing a file to all zeros is also included. The performance comparison is done with different file sizes.
Some tests include testing at the protocol level by taking a packet trace and inspecting the actual packets sent to the server or servers.
Negative testing is included whenever possible since some testing cannot be done at the protocol level because the fallocate system call does some error checking of its own and the NFS client won't even send an ALLOCATE or DEALLOCATE operation to the server letting the server deal with the error. Negative tests include trying to allocate an invalid range, having an invalid value for either the offset or the length, trying to allocate or deallocate a region on a file opened as read only or the file is a non-regular file type.
Run all ALLOCATE tests: alloc01, alloc02, alloc03, alloc04, alloc05, alloc06
Verify ALLOCATE succeeds on files opened as write only
Verify ALLOCATE succeeds on files opened as read and write
Verify ALLOCATE fails on files opened as read only
Verify ALLOCATE fails with EINVAL for invalid offset or length
Verify ALLOCATE fails with ESPIPE when using a named pipe file handle
Verify ALLOCATE reserves the disk space
Run all DEALLOCATE tests: dealloc01, dealloc02, dealloc03, dealloc04, dealloc05, dealloc06
Verify DEALLOCATE succeeds on files opened as write only
Verify DEALLOCATE succeeds on files opened as read and write
Verify DEALLOCATE fails on files opened as read only
Verify DEALLOCATE fails with EINVAL for invalid offset or length
Verify DEALLOCATE fails with ESPIPE when using a named pipe file handle
Verify DEALLOCATE unreserves the disk space
Verify ALLOCATE outperforms initializing the file to all zeros
Run all tests: alloc01, alloc02, alloc03, alloc04, alloc05, alloc06, dealloc01, dealloc02, dealloc03, dealloc04, dealloc05, dealloc06, perf01
The only required option is --server
$ nfstest_alloc --server 192.168.0.11
The user id in the local host must have access to run commands as root using the 'sudo' command without the need for a password.
Tests which require filling up all the disk space on the mounted device should have exclusive access to the device.
Valid only for NFS version 4.2 and above.
formatstr(3), nfstest.test_util(3), nfstest.utils(3), nfstest_cache(1), nfstest_delegation(1), nfstest_dio(1), nfstest_fcmp(1), nfstest_file(1), nfstest_interop(1), nfstest_io(1), nfstest_lock(1), nfstest_pkt(1), nfstest_pnfs(1), nfstest_posix(1), nfstest_rdma(1), nfstest_sparse(1), nfstest_ssc(1), nfstest_xattr(1), nfstest_xid(1), packet.nfs.nfs4_const(3)
No known bugs.
Jorge Mora (mora@netapp.com)
21 March 2023 | NFStest 3.2 |