io_fsync() calls the syscall io_submit(). When doing IO_CMD_FSYNC and IO_CMD_FDSYNC, Linux kernel will involve the filesystem's aio_fsync and aio_fdsync operations, and if the filesystem doesn't implement these two operations, it will return -EINVAL. In general, this CMD is not implemented in Linux kernel.

io_fsync() calls the syscall io_submit(). When doing IO_CMD_FSYNC and IO_CMD_FDSYNC, Linux kernel will involve the filesystem's aio_fsync and aio_fdsync operations, and if the filesystem doesn't implement these two operations, it will return -EINVAL. In general, this CMD is not implemented in Linux kernel.

io_fsync() calls the syscall io_submit(). When doing IO_CMD_FSYNC and IO_CMD_FDSYNC, Linux kernel will involve the filesystem's aio_fsync and aio_fdsync operations, and if the filesystem doesn't implement these two operations, it will return -EINVAL. In general, this CMD is not implemented in Linux kernel.

io_fsync() calls the syscall io_submit(). When doing IO_CMD_FSYNC and IO_CMD_FDSYNC, Linux kernel will involve the filesystem's aio_fsync and aio_fdsync operations, and if the filesystem doesn't implement these two operations, it will return -EINVAL. In general, this CMD is not implemented in Linux kernel.

io_fsync() calls the syscall io_submit(). When doing IO_CMD_FSYNC and IO_CMD_FDSYNC, Linux kernel will involve the filesystem's aio_fsync and aio_fdsync operations, and if the filesystem doesn't implement these two operations, it will return -EINVAL. In general, this CMD is not implemented in Linux kernel.

1.4.1 RC1 20130612 build

total: 19

LTP cases

status

owner

error msg

lsb

comment

bugzilla

aio02

NAB

n/a

io_fsync write: Invalid argument

n/a

io_fsync() calls the syscall io_submit(). When doing IO_CMD_FSYNC and IO_CMD_FDSYNC, Linux kernel will involve the filesystem's aio_fsync and aio_fdsync operations, and if the filesystem doesn't implement these two operations, it will return -EINVAL. In general, this CMD is not implemented in Linux kernel.

The system doesn't have /proc/pid/io, unable to determine read bytes during test

n/a

aio02

NAB

n/a

io_fsync write: Invalid argument

n/a

io_fsync() calls the syscall io_submit(). When doing IO_CMD_FSYNC and IO_CMD_FDSYNC, Linux kernel will involve the filesystem's aio_fsync and aio_fdsync operations, and if the filesystem doesn't implement these two operations, it will return -EINVAL. In general, this CMD is not implemented in Linux kernel.

1.3.2 20130516 build

total: 18

LTP cases

status

owner

error msg

lsb

comment

bugzilla

aio02

NAB

n/a

io_fsync write: Invalid argument

n/a

io_fsync() calls the syscall io_submit(). When doing IO_CMD_FSYNC and IO_CMD_FDSYNC, Linux kernel will involve the filesystem's aio_fsync and aio_fdsync operations, and if the filesystem doesn't implement these two operations, it will return -EINVAL. In general, this CMD is not implemented in Linux kernel.

1.4 M6 RC2 20130418 build

total: 19

LTP cases

status

owner

error msg

lsb

comment

bugzilla

aio02

NAB

n/a

io_fsync write: Invalid argument

n/a

io_fsync() calls the syscall io_submit(). When doing IO_CMD_FSYNC and IO_CMD_FDSYNC, Linux kernel will involve the filesystem's aio_fsync and aio_fdsync operations, and if the filesystem doesn't implement these two operations, it will return -EINVAL. In general, this CMD is not implemented in Linux kernel.

1.4 M5 RC3 20130403 build

total: 21

LTP cases

status

owner

error msg

lsb

comment

bugzilla

aio02

NAB

n/a

io_fsync write: Invalid argument

n/a

io_fsync() calls the syscall io_submit(). When doing IO_CMD_FSYNC and IO_CMD_FDSYNC, Linux kernel will involve the filesystem's aio_fsync and aio_fdsync operations, and if the filesystem doesn't implement these two operations, it will return -EINVAL. In general, this CMD is not implemented in Linux kernel.

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Could not mount the filesystem quota_remount_test01 1 TFAIL : Quota on Remount Failed

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Could not mount the filesystem quota_remount_test01 1 TFAIL : Quota on Remount Failed

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Could not mount the filesystem quota_remount_test01 1 TFAIL : Quota on Remount Failed

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Could not mount the filesystem quota_remount_test01 1 TFAIL : Quota on Remount Failed

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Could not mount the filesystem quota_remount_test01 1 TFAIL : Quota on Remount Failed

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Could not mount the filesystem quota_remount_test01 1 TFAIL : Quota on Remount Failed

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Could not mount the filesystem quota_remount_test01 1 TFAIL : Quota on Remount Failed

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Could not mount the filesystem quota_remount_test01 1 TFAIL : Quota on Remount Failed

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Could not mount the filesystem quota_remount_test01 1 TFAIL : Quota on Remount Failed

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Could not mount the filesystem quota_remount_test01 1 TFAIL : Quota on Remount Failed