On Thu, May 16, 2019 at 8:38 PM Darrell Budic <budic@onholyground.com> wrote:
I tried adding a new storage domain on my hyper converged test cluster running Ovirt 4.3.3.7 and gluster 6.1. I was able to create the new gluster volume fine, but it’s not able to add the gluster storage domain (as either a managed gluster volume or directly entering values). The created gluster volume mounts and looks fine from the CLI. Errors in VDSM log:

... 
2019-05-16 10:25:09,584-0500 ERROR (jsonrpc/5) [storage.fileSD] Underlying file system doesn't supportdirect IO (fileSD:110)
2019-05-16 10:25:09,584-0500 INFO  (jsonrpc/5) [vdsm.api] FINISH createStorageDomain error=Storage Domain target is unsupported: () from=::ffff:10.100.90.5,44732, flow_id=31d993dd, task_id=ecea28f3-60d4-476d-9ba8-b753b7c9940d (api:52)

The direct I/O check has failed.

This is the code doing the check:

 98 def validateFileSystemFeatures(sdUUID, mountDir):
 99     try:
100         # Don't unlink this file, we don't have the cluster lock yet as it
101         # requires direct IO which is what we are trying to test for. This
102         # means that unlinking the file might cause a race. Since we don't
103         # care what the content of the file is, just that we managed to
104         # open it O_DIRECT.
105         testFilePath = os.path.join(mountDir, "__DIRECT_IO_TEST__")
106         oop.getProcessPool(sdUUID).directTouch(testFilePath)                                                                                                             
107     except OSError as e:
108         if e.errno == errno.EINVAL:
109             log = logging.getLogger("storage.fileSD")
110             log.error("Underlying file system doesn't support"
111                       "direct IO")
112             raise se.StorageDomainTargetUnsupported()
113 
114         raise

The actual check is done in ioprocess, using:

319     fd = open(path->str, allFlags, mode);                                                                                                                                
320     if (fd == -1) {
321         rv = fd;
322         goto clean;
323     }
324 
325     rv = futimens(fd, NULL);
326     if (rv < 0) {
327         goto clean;
328     }
With:

allFlags = O_WRONLY | O_CREAT | O_DIRECT

See:

According to the error message:
Underlying file system doesn't support direct IO

We got EINVAL, which is possible only from open(), and is likely an issue opening
the file with O_DIRECT.

So something is wrong in the files system.

To confirm, you can try to do:

dd if=/dev/zero of=/path/to/mountoint/test bs=4096 count=1 oflag=direct

This will probably fail with:
dd: failed to open '/path/to/mountoint/test': Invalid argument

If it succeeds, but oVirt fail to connect to this domain, file a bug and we will investigate.

Nir



On May 16, 2019, at 11:55 AM, Nir Soffer <nsoffer@redhat.com> wrote:

On Thu, May 16, 2019 at 7:42 PM Strahil <hunter86_bg@yahoo.com> wrote:

Hi Sandro,

Thanks for the update.

I have just upgraded to RC1 (using gluster v6 here)  and the issue  I detected in 4.3.3.7 - where gluster Storage domain fails creation - is still present.


What is is this issue? can you provide a link to the bug/mail about it?

Can you check if the 'dd' command executed during creation has been recently modified ?

I've received update from Darrell  (also gluster v6) , but haven't received an update from anyone who is using gluster v5 -> thus I haven't opened a bug yet.

Best Regards,
Strahil Nikolov

On May 16, 2019 11:21, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
The oVirt Project is pleased to announce the availability of the oVirt 4.3.4 First Release Candidate, as of May 16th, 2019.

This update is a release candidate of the fourth in a series of stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used inproduction.

This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
* oVirt Node 4.3 (available for x86_64 only)

Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included.

See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node is already available[2]

Additional Resources:
* Read more about the oVirt 4.3.4 release highlights:http://www.ovirt.org/release/4.3.4/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:http://www.ovirt.org/blog/


--
Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/REDV54BH7CIIDRCRUPCUYN4TX5Z3SL6R/
_______________________________________________
Announce mailing list -- announce@ovirt.org
To unsubscribe send an email to announce-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/announce@ovirt.org/message/ABFECS5ES4MVL3UZC34GLIDN5PNDTNOR/

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RO6PQQ4XQ6KZXRUOHKMM2J2HFN2LTEGB/