V-5-52-2009 error code details

Details:

This problem is specific to the Red Hat and SuSe Linux operating systems.

The crux of the issue is that vxrsync issues the BLKGETSIZE64 ioctl on the block device corresponding to the data volume, which is failing with ENOTTY.

Here is a snippet of strace output:

open("/dev/vx/rdsk/testdg/vol", O_RDONLY|O_LARGEFILE) = 4

ioctl(4, BLKGETSIZE64, 0xff978b98) = -1 ENOTTY (Inappropriate ioctl for device)

This problem is seen because the ioctl in question is defined as below:

#define BLKGETSIZE64 _IOR(0x12,114, size_t)

size_t has different values in userland and in the kernel.

So the opcode corresponding to userland and in kernel are different.

0x80041272 (userland) and 0x80081272 (kernel)

Attempting to use any of the following commands on Red Hat or SuSe Linux could result in the error:

vradmin syncvol

vradmin -verify syncvol

vradmin syncrvg

vradmin -verify syncrvg

vradmin verifydata

The fix for this issue will be available in the upcoming VERITAS Volume Replicator (tm) (VVR) 5.1 release.

http://support.veritas.com/docs/329145

Severity:	Error
Component:	Volume Manager
Message:	Could not open device /dev/vx/dsk/lxxn1/vras_vol1 due to: ioctl BLKGETSIZE64 failed for block mode volume
Description:	Details: This problem is specific to the Red Hat and SuSe Linux operating systems. The crux of the issue is that vxrsync issues the BLKGETSIZE64 ioctl on the block device corresponding to the data volume, which is failing with ENOTTY. Here is a snippet of strace output: `open("/dev/vx/rdsk/testdg/vol", O_RDONLY\|O_LARGEFILE) = 4` `ioctl(4, BLKGETSIZE64, 0xff978b98) = -1 ENOTTY (Inappropriate ioctl for device)` This problem is seen because the ioctl in question is defined as below: `#define BLKGETSIZE64 _IOR(0x12,114, size_t)` `size_t` has different values in userland and in the kernel. So the opcode corresponding to userland and in kernel are different. 0x80041272 (userland) and 0x80081272 (kernel) Attempting to use any of the following commands on Red Hat or SuSe Linux could result in the error: `vradmin syncvol` `vradmin -verify syncvol` `vradmin syncrvg` `vradmin -verify syncrvg` `vradmin verifydata` The fix for this issue will be available in the upcoming VERITAS Volume Replicator (tm) (VVR) 5.1 release. http://support.veritas.com/docs/329145

Describe the issue below. You may enter up to 5000 characters.
Platform:
Release:
Describe the issue:	*
Email address:
* Required

Describe your solution below.
Platform:
Release:
Describe your solution:	*
* Required