|Skip Navigation Links|
|Exit Print View|
| Oracle VTS 7.0 Software
User's Guide for Patch Set 8 and Subsequent Compatible Releases
Media subtest: The Media subtest selects the biggest partition on the disk and runs either the ReadOnly test or the WriteRead test on the biggest partition. The ReadOnly test is selected if any partition on the disk has a file system on it. The WriteRead test is selected if the disk is raw and unsafe testing is enabled. By default all the read and write operations are completed using the asynchronous I/O method.
Caution - Disk test can only recognize file systems that Solaris supports or recognizes. If the fstyp command on the disk partition reports the file system type as "Unknown", Disk test may write data to the partition if the safe testing is disabled.
Disk test runs the ReadOnly test by default. To run the Write/Read test on the disks, you must enable the unsafe testing option. The Unsafe option should be used with care. Unsafe testing will overwrite existing data on the hard disks. If the unsafe testing is enabled, the test automatically selects the largest partition for running the Write/Read test. The selection is based on the following rules:
The disk should be raw.
No partition should have a file system on it.
The disk should not have an SVM or Veritas volume on it.
If any of the above conditions are not met, Disk test runs ReadOnly test on the disk partition. For more information about Unsafe test options.
Note - To run the Write/Read test, remove the file system on all the partitions of the disk.
File system subtest: The file system subtest verifies the disk file system integrity. The test auto detects all mounted disk partitions in the system and runs the file system subtest. On each mounted disk partition, the test will:
Create multiple threads.
Enable each thread to create new temporary test directories and test files under /<mount point>/Vts_Disk_Fileset.
Enable each thread to create a new test file and perform the default I/O operations.
Delete all temporary test directories and files on completion.
Adjacent Track Interference (ATI) subtest: When multiple and continuous writes are performed on a particular track of the disk, there is a possiblity that the data on an adjacent track might get corrupted. This subtest verifies the ATI issue on the disk. ATI subtest is disabled by default. Once ATI subtest runs, no other diskmedia subtest will run in parallel. ATI subtest runs only in unsafe mode on disks which have write-read permission.
User patterns support for DiskTest: The diskmedia test supports user patterns in two different ways:
patternfile: The user can use this option to provide details of a pattern file. The diskmediatest reads the pattern files and prepares the pattern. The pattern file content will be read directly into the buffer without any change. The pattern file can be any of any file type. If the complete path of the pattern file is not specified, then by default the pattern file will be searched in the present working directory. The following is the syntax for specifying the pattern file.
where filename is the file containing the user patterns.
pattern: The user can use this option to specify the pattern to be used for write/write-read tests. By default the P0 pattern is enabled, if no option is specified. You can also specify, create, and write list of different patterns in the /etc/sunvts/conf/disk_io_pattern file.The following is the syntax for an user pattern entry.
name: Is the pattern name.
pattern[hex value]: Is the pattern in hexadecimal format. The maximum value is 64 bits.
repetition: Is the number of occurences of a pattern. By default the value is 1.
SMART Logs capability for DiskTest: The SMART logs help in identifying probable failures of the disk drives. The diskmedia test can capture the SMART logs for all the intended disks in a system. The test can dump the Vital Device Data and Diagnostics Data for each disk in the system. This feature is disabled by default.
To add the capability of collecting SMART Logs after diskmediatest, the following entry has to be present in the /etc/sunvts/conf/sunvts.conf file.
When this entry is present in the sunvts.conf file, the diskmediatest is executed on the disks and before exiting , the test dumps all the SMART Logs into a file in the /var/sunvts/logs/smart_log directory.
To enable SMART logs without Diskmedia testing, the following entry has to be present in the /etc/sunvts/conf/sunvts.conf file.
SSD Wear Levelling: The diskmedia test implements the SSD Wear Level Calculation feature, where the test dumps the Wear Information for INTEL and SanDisk SSDs. You can use this feature from the LT as well as the command line.
For INTEL SSDs, the test resets the SMART Wear attributes, then tests the SSD and dumps the wear information in a log file in the /var/sunvts/logs/smart_logs directory.
For SanDisk SSDs, the snapshot of the SMART Attributes are dumped before and after the test into a log file.Currently , the SSD Wear Calculation Module is enabled only for INTEL and SanDisk SSDs.
To enable this feature from the sunvts.conf file, the following entry has to be present in the /etc/sunvts/conf/sunvts.conf file.
Axiom Disk LT Profile: The diskmedia test LT has been added with a profile to test Axiom (Oracle Flash Storage System), where in the iosizes within the range of 4k to 128k are used. This profile is mainly introduced to test the disks which are used in database applications wherein the iosizes are lower and the number of transactions are more in number.
To use the Axiom Disk LT profile, the following entry has to be present in the /etc/sunvts/conf/sunvts.conf file.
By default, the test creates 20 threads on each mounted partition. To change the default number of threads, use the fsthrcnt=<n> option. For example,
./diskmediatest -fv -o fsth
By default, the File system subtest do not run on NFS mounted filesystems. To enable filesystem subtest on NFS mounted filesystems, you should update /etc/sunvts/conf/sunvts.conf file with the following entry.
NFS_Disk_Testing <NFS mount path1>=Enable NFS_Disk_Testing <NFS mount path2>=Enable
You can use the cleanup option to remove the files left uncleaned by the Diskmedia test.
To have a similar functionality as sq_inquiry, support has been added to the diskmediatest to test the disks (HDDs and SSDs) against extended inquiry requests which are greater than 36 bytes.