File system got corrupted after disk was initialized with "vxdisk -f init"
Article ID: 100008866
Updated On:
Description
Error Message
# fstyp -v /dev/vx/rdsk/testdg/vol
Unknown_fstyp (no matches)
# mount -F vxfs /dev/vx/dsk/testdg/vol /mnt
UX:vxfs mount: ERROR: V-3-20012: not a valid vxfs file system
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
Cause
Disks initialized in SF 4.x were initialized in SF 5.x without using the private and public offset values.
Resolution
When disks were initialized in SF 4.x, disks have the default private region of 2048 blocks(1024KB).
public: slice=2 offset=2304 len=54502656 disk_offset=0
private: slice=2 offset=256 len=2048 disk_offset=0
If disk is re-initialized on 5.x without specifying the private and public region details(privoffset, privlen, puboffset, publen), this will write the default private region of SF 5.x on the disk.
public: slice=2 offset=65792 len=54439168 disk_offset=0
private: slice=2 offset=256 len=65536 disk_offset=0
Private region for SF 4.x : 1024KB or 1MB
Private region for SF 5.x : 32 MB
Applies To
OS Version : Solaris 10
SF Version : 5.1SP1RP2
Issue/Introduction
