Bug 763921 (GLUSTER-2189)

Summary: ioctl: LOOP_SET_FD: Invalid argument when creating loopback device
Product: [Community] GlusterFS Reporter: Jacob Shucart <jacob>
Component: coreAssignee: Anand Avati <aavati>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 3.1.1CC: chrisw, gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: DP CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Anand Avati 2010-12-03 13:19:26 UTC
what kernel version did you try this in? Can you try mounting glusterfs with -o direct-io-mode=off and see if this losetup works well? This must just be a documentation update in the FAQ section.

Avati

Comment 1 Jacob Shucart 2010-12-03 13:35:41 UTC
Am I doing something wrong?

[root@jacobgfs31-s1 ~]# mount -t glusterfs -o direct-io-mode=off localhost:/test /test
/usr/sbin/glusterfs: unrecognized option `--disable-direct-io-mode'
Try `glusterfs --help' or `glusterfs --usage' for more information.
Mount failed. Please check the log file for more details.


[root@jacobgfs31-s1 ~]# mount -t glusterfs -o direct-io-mode=disable localhost:/test /test
/usr/sbin/glusterfs: unrecognized option `--disable-direct-io-mode'
Try `glusterfs --help' or `glusterfs --usage' for more information.
Mount failed. Please check the log file for more details.

Is there a bug with disabling direct-io-mode in 3.1.1?

Comment 2 Jacob Shucart 2010-12-03 13:36:49 UTC
Kernel version is:

2.6.18-194.17.1.el5.centos.plus


This is CentOS 5.5 64-bit

Comment 3 Anand Avati 2010-12-03 13:52:58 UTC
Try this instead -

sh# glusterfs -s localhost --volfile-id volname --direct-io-mode=off /test

Comment 4 Jacob Shucart 2010-12-03 14:08:07 UTC
That worked.

Comment 5 Anand Avati 2010-12-03 14:10:19 UTC
(In reply to comment #5)
> That worked.

if you have a recent enough kernel (2.6.27+) it would have worked by default

Comment 6 Jacob Shucart 2010-12-03 16:15:28 UTC
IF I run the following command inside a Gluster volume mounted using the Gluster native protocol:

mount -t glusterfs localhost:/volname /test
cd /test
dd if=/dev/zero of=./whatever bs=1024 count=1 seek=$((1*1024*1024))
losetup /dev/loop0 /test/whatever

I get:

ioctl: LOOP_SET_FD: Invalid argument

The same works using NFS.  A user Verio reported this.