Very Computer

> s_aiocb64.aio_whence = SEEK_SET;
> s_aiocb64.aio_offset = ul_offset;
> s_aiocb64.aio_buf = char_buffer;
> s_aiocb64.aio_nbytes = ul_nbytes;

> if(aio_write64(fid, &s_aiocb64) < 0)
> {
>    fprintf(stderr,"aio_write64 errno:%d\n",errno);
>    perror("aio_write64");
>    return(1);
> }

> but the aio_write64 always returns EINVAL: Indicates that the
> aio_whence field does not have a valid value or that the resulting
> pointer is not valid.

> but the same code works well with block device, eg. /dev/testlv and
> jfs file.

> can anyone tell me how to use aio_write64 with raw device? many
> thanks.

>> I want to use aio_write64 on raw device , eg. /dev/rtestlv. the code
>> likes:

>> s_aiocb64.aio_whence = SEEK_SET;
>> s_aiocb64.aio_offset = ul_offset;
>> s_aiocb64.aio_buf = char_buffer;
>> s_aiocb64.aio_nbytes = ul_nbytes;

>> if(aio_write64(fid, &s_aiocb64) < 0)
>> {
>>     fprintf(stderr,"aio_write64 errno:%d\n",errno);
>>     perror("aio_write64");
>>     return(1);
>> }

>> but the aio_write64 always returns EINVAL: Indicates that the
>> aio_whence field does not have a valid value or that the resulting
>> pointer is not valid.

> >> I want to use aio_write64 on raw device , eg. /dev/rtestlv. the code
> >> likes:

> >> s_aiocb64.aio_whence = SEEK_SET;
> >> s_aiocb64.aio_offset = ul_offset;
> >> s_aiocb64.aio_buf = char_buffer;
> >> s_aiocb64.aio_nbytes = ul_nbytes;

> >> if(aio_write64(fid, &s_aiocb64) < 0)
> >> {
> >>     fprintf(stderr,"aio_write64 errno:%d\n",errno);
> >>     perror("aio_write64");
> >>     return(1);
> >> }

> >> but the aio_write64 always returns EINVAL: Indicates that the
> >> aio_whence field does not have a valid value or that the resulting
> >> pointer is not valid.

> Wait a sec..  The man page I'm looking at says:

> EINVAL - The file offset value implied by aio_offset is invalid,
> aio_reqprio is an invalid value, or aio_nbytes is an invalid value.

> The semantics you describe for EINVAL/whence is the asynchronous
> operation error code.

> >> >> I want to use aio_write64 on raw device , eg. /dev/rtestlv. the code
> >> >> likes:

> >> >> s_aiocb64.aio_whence = SEEK_SET;
> >> >> s_aiocb64.aio_offset = ul_offset;
> >> >> s_aiocb64.aio_buf = char_buffer;
> >> >> s_aiocb64.aio_nbytes = ul_nbytes;

> >> >> if(aio_write64(fid, &s_aiocb64) < 0)
> >> >> {
> >> >>     fprintf(stderr,"aio_write64 errno:%d\n",errno);
> >> >>     perror("aio_write64");
> >> >>     return(1);
> >> >> }

> >> >> but the aio_write64 always returns EINVAL: Indicates that the
> >> >> aio_whence field does not have a valid value or that the resulting
> >> >> pointer is not valid.

> >> Wait a sec..  The man page I'm looking at says:

> >> EINVAL - The file offset value implied by aio_offset is invalid,
> >> aio_reqprio is an invalid value, or aio_nbytes is an invalid value.

> >> The semantics you describe for EINVAL/whence is the asynchronous
> >> operation error code.

> r> I've bzero the s_aiocb64, and the aio.h in AIX4.3.3 MIL10 says:
> r> aio_reqprio no used, my question is the same code works well with
> r> block device , eg. /dev/testlv and JFS file, why can not work with raw
> r> device? any special consideration?

> It's my understanding that accesses to raw devices must be aligned
> on boundaries of the block size of the device itself.  What's the
> value of aio_offset in this case?

> Regards,

> Nicholas