Error Message

# newfs /dev/vx/rdsk/oradg/3000g
newfs: construct a new file system /dev/vx/rdsk/oradg/3000g: (y/n)? y
Can not determine partition size: Inappropriate ioctl for device
 

In Solaris 10 version, newfs/mkfs_ufs(1M) uses ioctl() system calls, to identify the size of the disk or volume device, when creating UFS file system on disk or volume devices “> 2TB”. If the Operating System (OS) version is less than Solaris 10 Update 8, the above ioctl system calls are invoked on “volumes > 1TB” as well.

VxVM, Veritas Volume Manager exports the ioctl interfaces for VxVM volumes. VxVM 5.1 SP1 RP1 P1 and VxVM 5.0 MP3 RP3 introduced the support for Extensible Firmware Interface (EFI) for VxVM volumes in Solaris 9 and Solaris 10 respectively. However the corresponding EFI specific build time definition in Veritas Kernel IO driver (VXIO) was not updated in Solaris 10 in VxVM 5.1 SP1 RP1 P1 and onwards.

This issue is being tracked internally at Veritas under e2334126. Necessary code changes have been made to add the build time definition for EFI in VXIO entails in newfs/mkfs_ufs(1M) successfully creating UFS file system on VxVM volume devices “> 2TB” (“> 1TB” if OS version is less than Solaris 10 Update 8).

This issue is fixed in VxVM 5.1SP1RP2 patch and above.

Applies To

Solaris 10

UFS file system

VxVM volume > 2Tb in size

VxVM 5.1SP1RP1P1 - 5.1SP1RP1P1HF4

Creating a UFS file system on a Volume Manager (VxVM ) volume with size of 2Tb or larger may fail when running Volume Manager 5.1SP1RP1P1 - 5.1SP1RP1P1HF4 on Solaris 10. When encountered an error message will be received as follows: # newfs /dev/vx/rdsk/oradg/3000g
newfs: construct a new file system /dev/vx/rdsk/oradg/3000g: (y/n)? y
Can not determine partition size: Inappropriate ioctl for device
    The truss output of the newfs/mkfs_ufs(1M) shows that the ioctl() system calls,
to identify the size of the disk or volume device, fails with ENOTTY error.


    ioctl(3, 0x042A, ...)                    Err#25 ENOTTY
    ...
    ioctl(3, 0x0412, ...)                    Err#25 ENOTTY Note that this issue does not affect versions of VxVM prior to 5.1SP1RP1P1 (i.e. this issue is a regression introduced in this release)  

ETrack: 2334126