README VERSION : 1.1 README CREATION DATE : 2013-01-29 PATCH-ID : 6.0.300.000 PATCH NAME : VRTSodm 6.0.300.000 BASE PACKAGE NAME : VRTSodm BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol11_x64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : YES ID : NONE REBOOT REQUIRED : YES REQUIRE APPLICATION DOWNTIME : Yes PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Release Notes for install instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Release Notes for uninstall instructions SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:6.0.300.000 3018873 (3018869) On Solaris 11 update 1 fsadm command shows that the mountpoint is not a vxfs file system SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: ---------------- PATCH ID:6.0.300.000 * INCIDENT NO:3018873 TRACKING ID:3018869 SYMPTOM: fsadm command shows that the mountpoint is not a vxfs file system DESCRIPTION: The Solaris11 update1 has some changes in function fstatvfs() [VFS layer] which breaks VxFS's previous assumptions. The statvfs.f_basetype gets populated with some garbage value instead of "vxfs". So, during the fsadm, when we check for the file system type, the check fails and so we get the error. RESOLUTION: Made changes to fetch correct value for fstype using OS provided API's so that the statvfs.f_basetype field gets valid i.e. "vxfs" value. INCIDENTS FROM OLD PATCHES: --------------------------- NONE