99429157e8
The previous logic was flawed in the sense that it assumed that /dev/md3 was always available. This was a caveat I noted in r306038, that I hadn't gotten around to solving before now. Cache the device for the mountpoint after executing mdmfs, then use the cached value in basic_cleanup(..) when unmounting/disconnecting the md(4) device. Apply sed expressions to use reuse logic in the NetBSD code that could also be applied to FreeBSD, just with different tools. Differential Revision: D10766 MFC after: 1 week Reviewed by: bdrewery Sponsored by: Dell EMC Isilon |
||
|---|---|---|
| .. | ||
| h_funcs.subr | ||
| h_tools.c | ||
| README | ||
| t_create.sh | ||
| t_devices.sh | ||
| t_dots.sh | ||
| t_exec.sh | ||
| t_link.sh | ||
| t_mkdir.sh | ||
| t_mknod.sh | ||
| t_mount.sh | ||
| t_pipes.sh | ||
| t_read_write.sh | ||
| t_readdir.sh | ||
| t_remove.sh | ||
| t_rename.sh | ||
| t_renamerace.c | ||
| t_rmdir.sh | ||
| t_setattr.sh | ||
| t_sizes.sh | ||
| t_sockets.sh | ||
| t_statvfs.sh | ||
| t_symlink.sh | ||
| t_times.sh | ||
| t_trail_slash.sh | ||
| t_truncate.sh | ||
| t_vnd.sh | ||
| t_vnode_leak.sh | ||
The tests in this directory where written at the same time tmpfs was developed. This is why, if you follow the order of tests in the Atffile, you will notice that they start checking the most basic things and end checking the less common ones. Furthermore, tests try not to use features tested by further tests in the lists. However, the above is not the most appropriate testing procedure when you have a working file system because some separation in test programs does not make sense afterwards. Many of the tests here are applicable to any file system. They should be refactored to be reusable on any mounted file system, which could also remove the need to do the mount/unmount steps in each and every test case. Possibly take a look at the file system tests in FreeBSD. They seem to be much more complete, even though they are written in Perl and therefore not directly usable.