Table 1: QIO/FDD Release Version Coverage QIO/FDD

Transcription

1 VERITAS Quick I/O for Databases (QIO) VERITAS File Device Driver (FDD) Year 2000 Compliance Test Plan 1 Purpose This document details the test plan for Year 2000 compliant releases and all subsequent releases of the VERITAS Quick I/O for Databases (QIO), previously called File Device Driver (FDD). Note: QIO is the new product name for FDD starting at version 2.0. For the purposes of this document, when addressing the product as a whole, the term QIO will be used. When dealing with a specific release of the product, the applicable name (FDD for versions up through and QIO for versions after and including 2.0) will be used. 2 Overview Table 1 describes the exact versions of QIO to be tested across the various versions of the Solaris and HP-UX operating systems. VERITAS asserts that these are the only versions of existing QIO products that are Year 2000 compliant. All future releases of QIO products will also be certified by VERITAS as Year 2000 compliant. The table uses "Y2K" to denote which versions of QIO operate on which versions of Solaris and HP-UX in addition to which versions are Year 2000 compliant. Table 1: QIO/FDD Release Version Coverage HP-UX Solaris QIO/FDD FDD 1 Y2K FDD Y2K Y2K FDD Y2K Y2K QIO Y2K Y2K QIO Y2K Y2K 1 FDD was released on HP-UX as part of VERITAS Storage Edition FDD was released with VxFS FDD was made available with VxFS via ftp. 4 QIO 2.0 was released with VxFS 3.3 as a component of Database Edition QIO will be released with VxFS as a component of Database Edition

2 Since QIO is a VxFS driver, it follows the same standard UNIX model of expressing time as the number of seconds since 00:00:00 January 1st, 1970 (EST). This model does not have any special representational problems at or around the Year 2000, although problems may surface in the Year 2038, a problem which is beyond the scope of this document. In the cases where it reads, modifies, or otherwise uses times or dates, QIO uses explicit, unambiguous date representation. Please refer to the VxFS Year 2000 Test Plan for more information regarding how the related VxFS products were tested. 2.1 Standard Library Functions The code was audited to find places where dates are expressed using month, day, and year to look for potential problems. Such code can be found by searching for the standard library functions used to retrieve times or dates, or to transform time between the two methods of representation. These functions are: ctime(), asctime(), localtime(), gmtime(), tzset(), tzsetwall() strftime(), cftime(), ascftime() strptime() getdate() mktime() gettimeofday(), settimeofday() ftime() gethrtime(), gethrvtime() wcsftime() time() times() 2.2 QIO Commands Auditing of the code shows that the following command is the only utility in QIO that uses these functions to manipulate or store dates and/or time: vxfddstat / qiostat Since the only use of standard time/date library functions in vxfddstat / qiostat is to print out the date using a printf-type function, this utility will not be explicitly tested. 2.3 QIO Kernel The fields that QIO uses to store dates internally will be tested. These fields are: di_atime (on-disk inode access time) di_ctime (on-disk inode status change time) di_mtime (on-disk inode modification/creation time)

3 These times and dates are stored as the number of seconds and microseconds since UTC 00:00:00 on January 1, Hence they are not really dates at all but quantities. In application they are added to UTC to produce the accurate date and time relative to UTC (and possibly the local time zone). VERITAS will only test this basic principle to demonstrate that internally QIO does not contain any Year 2000 related problems. 2.4 Packaging & Installation Installation and deinstallation across the key dates will be done for each version of Solaris and HP-UX. This will be done using pkgadd, pkgrm, and pkginfo. On HP-UX, the SD-UX utilities will be used. This will be done to verify that the installation and deinstallation processes for FDD point products and FDD as a component of a VERITAS Edition operate correctly and successfully before, on and after the Year Licensing QIO is a licensed feature of the VxFS File system. QIO and VxFS use Rainbow Sentinel LM to handle licensing though the vxmkcdev / qiomkfile and qioadmin utilities. These utilities will not function if the proper license is not installed. These commands will be hand-tested to ensure that they function across all of the test dates. Note: Rainbow Sentinel LM will not allow any license keys to be generated which have an expiration date past the year A future license manager software release will be provided to VERITAS before 2016 which will extend this restriction out to some further date. 3 Implementation 3.1 Test Dates VERITAS will conduct all of the tests described within this document with the time set to before and after the following Key Date and Key Date Changes: Dec 31, 1998 to Jan 01, 1999 Sep 09, 1999 to Sep 10, 1999 Dec 31, 1999 to Jan 01, 2000 Feb 28, 2000 to Feb 29, 2000 Feb 29, 2000 to Mar 01, 2000 Dec 31, 2000 to Jan 01, 2001 Dec 31, 2008 to Jan 01, 2009 Dec 31, 2037 to Jan 01, 2038 Note: HP-UX does not allow any dates to be set beyond Dec 31, Because of this, the final Key Date Change (12/31/37 to 1/1/38) will not be tested on HP-UX. 3.2 Automated Tests

4 A new fsqa test script will be added to the VxFS fsqa test suite. The script and its description is given below: fsqa/common/tests/y2k fsqa/common/tests/y2k/makefile fsqa/common/tests/y2k/run.sh fsqa/common/tests/y2k/fdd.sh # Y2K top level test directory # Y2K top level test makefile # Y2K top level run script # Y2K fdd tests The following test script descriptions assume the following setup: 1 logical volume or disk slice with a corresponding mount point. /dev/rdsk/c0t1d0s4, /mnt0 Note: This document will use disk slices in the examples, but the tests will also be run with VxVM on Solaris. The desired version of VxFS and QIO installed complete with the correct QIO feature license. The VxFS fsqa test suite installed and built on the system to be tested. Note: The fsqa test suite has no impact on the functionality of VxFS or QIO. Each test script will be repeated for all applicable VxFS disk layouts. The supported VxFS disk layout versions per platform are described in Table 2. See Table 1 for the versions of QIO corresponding to the versions of VxFS in the table below. Table 2: Supported VxFS Disk Layout Versions HP-UX Solaris VxFS , X 1, 2, 4 1, 2, X 1, 2, 4 1, 2, 4 Additionally, it should be noted that each of the test scripts will repeat the tests outlined for each of the key dates given in the list of Test Dates. Anytime the phrase "Key Date Change" is used, it is referring to a change across these dates. Anytime the phrase "Key Date" is used, it is referring to the first date in the date pairs listed (ie: the "Key Date" in "Dec 31, 1999 to Jan 01, 2000" would be Dec 31, 1999"). The UNIX user command date mmddhhmmccyy is used to set the date in all cases where a date or time

5 change is specified fdd.sh To track whether QIO is correctly representing dates internally, perform various miscellaneous tests. These tests should cover the kernel fields listed in the QIO Kernel section. Test 1: Test for di_mtime, di_atime, and di_ctime 1. Set date to before Key Date. 2. Create a file system using mkfs -Fvxfs /dev/rdsk/c0t1d0s4 3. Mount the file system using mount -Fvxfs /dev/dsk/c0t1d0s4 /mnt0 4. Create an FDD file using vxmkcdev -s 50m /mnt0/qfile or create a QIO file using qiomkfile -s 50m /mnt0/qfile, This sets the di_atime, di_ctime, and di_mtime to the current time. 5. Write to the FDD file using dd if=/dev/zero of=/mnt0/qfile bs=1024 count=30 6. Get the inode number for "qfile" using inum=`ls -lai /mnt0 grep qfile grep -v cdev awk '{print $1}'` 7. Set date to after Key Date. 8. Check the file modification/creation time (di_mtime) field for "qfile" using echo "8192B.${inum}i" fsdb -Fvxfs /dev/rdsk/c0t1d0s4 grep mtime Note the time for 'mtime'. 9. To change "qfile"'s modification time (di_mtime), use dd if=/dev/zero of=/mnt0/qfile bs=1024 count= Unmount and then mount the /mnt0 file system to sync the superblock. 11. Recheck the file modification/creation time (di_mtime) field for "qfile" using echo "8192B.${inum}i" fsdb -Fvxfs /dev/rdsk/c0t1d0s4 grep mtime Note the time for 'mtime'. See that it has changed from before. 12. Check the file access (di_atime) field for "qfile" using echo "8192B.${inum}i" fsdb -Fvxfs /dev/rdsk/c0t1d0s4 grep atime Note the time for 'atime'. 13. To change "qfile"'s access time (di_atime), use dd if=/mnt0/qfile of=/dev/null bs=1024 count= Sync the superblock. 15. Recheck the file access time (di_atime) field for "qfile" using echo "8192B.${inum}i" fsdb -Fvxfs /dev/rdsk/c0t1d0s4 grep atime Note the time for 'atime'. See that it has changed from before. 16. Check the file status change (di_ctime) field for "qfile" using echo "8192B.${inum}i" fsdb -Fvxfs /dev/rdsk/c0t1d0s4 grep ctime Note the time for 'ctime'. 17. To change "qfile"'s status change time (di_ctime), use chmod 777 /mnt0/qfile 18. Sync the superblock. 19. Recheck the file status change (di_ctime) field for "qfile" using echo "8192B.${inum}i" fsdb -Fvxfs /dev/rdsk/c0t1d0s4 grep ctime Note the time for 'ctime'. See that it has changed from before. 3.4 Installation Tests

6 Installing and de-installing QIO across the key dates using pkgadd and pkgrm on Solaris will demonstrate that the installation process is not affected by dates before, on, or after the Year These tests will be done by hand. 4 Conclusion The results from running these tests have shown that the versions of QIO given in Table 1 do not have any bugs related to Year 2000 issues in all cases where the listed standard library time-related functions are used and where times and/or dates are stored or input as data. This document was issued on February 22nd, 1999 and replaces all prior versions. Dates after 2038 are outside the scope of this document.