Difference between revisions of "Windows zfstest"
From OpenZFS on OS X
								
												
				 (Created page with " == zfs-tester ==  Running zfstests on Windows is a bit of a bastard child, as we do not have sudo (yet?).   * Install cygwin ** With ksh  * Run cygwin terminal As Administrat...")  | 
				m (→zfs-tester)  | 
				||
| Line 3: | Line 3: | ||
Running zfstests on Windows is a bit of a bastard child, as we do not have sudo (yet?).    | Running zfstests on Windows is a bit of a bastard child, as we do not have sudo (yet?).    | ||
| + | |||
| + | * Configure 3 disks with your VM, they should be about 15G ~ 20G each.  | ||
* Install cygwin  | * Install cygwin  | ||
Revision as of 08:01, 11 April 2019
zfs-tester
Running zfstests on Windows is a bit of a bastard child, as we do not have sudo (yet?).
- Configure 3 disks with your VM, they should be about 15G ~ 20G each.
 
-  Install cygwin
- With ksh
 
 
- Run cygwin terminal As Administrator
 
- Run or set these in your .bash_profile
 
export SHELLOPTS set -o igncr
$ cd ZFSin/ZFSin/zfs/tests $ ./autogen.sh $ ./configure
You may want to check that Makefile disks points to three available disks.
$ grep DISKS Makefile
        DISKS="$(shell for i in {1..3}; do \
        DISKS="PHYSICALDRIVE1 PHYSICALDRIVE2 PHYSICALDRIVE3" \
        DISKS="/var/tmp/zfs_test-1 /var/tmp/zfs_test-2 /var/tmp/zfs_test-3" \
On my system PHYSICALDRIVE1, 2 and 3 are empty and available for testing. If your system is different, you may need to edit Makefile. (Or edit Makefile.am, and re-run configure).
If you want to make a reduced test run, you can here edit:
$ vi zfs-tests/runfiles/windows.run
(Or again, edit zfs-tests/runfiles/windows.run.in and rerun ./configure)
To run the tester:
$ make test_hw
Complete output is placed in /var/tmp/test_results/$DATE/log