Let vnconfig select an unused device as opposed of unconditionally
assume vnd0 is available.

unreferneced -> unreferenced

Remove echo headlines. Makefile cleanup.

The unmount-nested test creates 15 partitions with file systems.
Use FFS1 for newfs as the file system size is below the FFS2 minimum.

Add a smarter test that opens a file, unlinks it, and remounts the
file system read-only. After unmounting this should result in a
dirty file system that is not marked clean. Disable both tests
with dangling vnodes for now as they fail.

Add tests that unmount a file system while it is busy. On a vnd
device "cp -r" and "rm -rf" are working in the background while
"umount -f" or "mount -ur" are executed. Then "fsck -f" is used
to verify that the file system is clean.
Currently this triggers a bug quite reliably. After the mount point
has been changed to read-only, the file system check shows that not
everything was flushed and synced properly.

Add comment what the test does.

Do not unconfigure mount points, vnd devices and NFS daemons during
"make clean". "make build" does a recursive "make cleandir" and
there this behavior is undesired unexpected.
reported by naddy@

Make mount points and makefiles for file system tests consistent.
Link tests to the build.

branches: 1.1.1;
Initial revision

unreferneced -> unreferenced

Remove echo headlines. Makefile cleanup.

The unmount-nested test creates 15 partitions with file systems.
Use FFS1 for newfs as the file system size is below the FFS2 minimum.

Add a smarter test that opens a file, unlinks it, and remounts the
file system read-only. After unmounting this should result in a
dirty file system that is not marked clean. Disable both tests
with dangling vnodes for now as they fail.

Add tests that unmount a file system while it is busy. On a vnd
device "cp -r" and "rm -rf" are working in the background while
"umount -f" or "mount -ur" are executed. Then "fsck -f" is used
to verify that the file system is clean.
Currently this triggers a bug quite reliably. After the mount point
has been changed to read-only, the file system check shows that not
everything was flushed and synced properly.

Add comment what the test does.

Do not unconfigure mount points, vnd devices and NFS daemons during
"make clean". "make build" does a recursive "make cleandir" and
there this behavior is undesired unexpected.
reported by naddy@

Make mount points and makefiles for file system tests consistent.
Link tests to the build.

branches: 1.1.1;
Initial revision

Remove echo headlines. Makefile cleanup.

The unmount-nested test creates 15 partitions with file systems.
Use FFS1 for newfs as the file system size is below the FFS2 minimum.

Add a smarter test that opens a file, unlinks it, and remounts the
file system read-only. After unmounting this should result in a
dirty file system that is not marked clean. Disable both tests
with dangling vnodes for now as they fail.

Add tests that unmount a file system while it is busy. On a vnd
device "cp -r" and "rm -rf" are working in the background while
"umount -f" or "mount -ur" are executed. Then "fsck -f" is used
to verify that the file system is clean.
Currently this triggers a bug quite reliably. After the mount point
has been changed to read-only, the file system check shows that not
everything was flushed and synced properly.

Add comment what the test does.

Do not unconfigure mount points, vnd devices and NFS daemons during
"make clean". "make build" does a recursive "make cleandir" and
there this behavior is undesired unexpected.
reported by naddy@

Make mount points and makefiles for file system tests consistent.
Link tests to the build.

branches: 1.1.1;
Initial revision

The unmount-nested test creates 15 partitions with file systems.
Use FFS1 for newfs as the file system size is below the FFS2 minimum.

Add a smarter test that opens a file, unlinks it, and remounts the
file system read-only. After unmounting this should result in a
dirty file system that is not marked clean. Disable both tests
with dangling vnodes for now as they fail.

Add tests that unmount a file system while it is busy. On a vnd
device "cp -r" and "rm -rf" are working in the background while
"umount -f" or "mount -ur" are executed. Then "fsck -f" is used
to verify that the file system is clean.
Currently this triggers a bug quite reliably. After the mount point
has been changed to read-only, the file system check shows that not
everything was flushed and synced properly.

Add comment what the test does.

Do not unconfigure mount points, vnd devices and NFS daemons during
"make clean". "make build" does a recursive "make cleandir" and
there this behavior is undesired unexpected.
reported by naddy@

Make mount points and makefiles for file system tests consistent.
Link tests to the build.

branches: 1.1.1;
Initial revision

Add a smarter test that opens a file, unlinks it, and remounts the
file system read-only. After unmounting this should result in a
dirty file system that is not marked clean. Disable both tests
with dangling vnodes for now as they fail.

Add tests that unmount a file system while it is busy. On a vnd
device "cp -r" and "rm -rf" are working in the background while
"umount -f" or "mount -ur" are executed. Then "fsck -f" is used
to verify that the file system is clean.
Currently this triggers a bug quite reliably. After the mount point
has been changed to read-only, the file system check shows that not
everything was flushed and synced properly.

Add comment what the test does.

Do not unconfigure mount points, vnd devices and NFS daemons during
"make clean". "make build" does a recursive "make cleandir" and
there this behavior is undesired unexpected.
reported by naddy@

Make mount points and makefiles for file system tests consistent.
Link tests to the build.

branches: 1.1.1;
Initial revision

Add tests that unmount a file system while it is busy. On a vnd
device "cp -r" and "rm -rf" are working in the background while
"umount -f" or "mount -ur" are executed. Then "fsck -f" is used
to verify that the file system is clean.
Currently this triggers a bug quite reliably. After the mount point
has been changed to read-only, the file system check shows that not
everything was flushed and synced properly.

Add comment what the test does.

Do not unconfigure mount points, vnd devices and NFS daemons during
"make clean". "make build" does a recursive "make cleandir" and
there this behavior is undesired unexpected.
reported by naddy@

Make mount points and makefiles for file system tests consistent.
Link tests to the build.

branches: 1.1.1;
Initial revision