Bug 379021
Summary: | GFS2: xdoio with jdata and directio fails | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Robert Peterson <rpeterso> |
Component: | kernel | Assignee: | Steve Whitehouse <swhiteho> |
Status: | CLOSED NOTABUG | QA Contact: | GFS Bugs <gfs-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.1 | CC: | cluster-maint, djansa, rpeterso |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-11-13 08:37:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Robert Peterson
2007-11-12 23:03:11 UTC
I should mention that this same test works just fine if I don't do the chattr to turn on the jdata attribute. This problem still occurs in the -4 version, but does NOT occur in the SRPM version of gfs2 in the -54 kernel. jdata and directio is a meaningless combination, it should always have been disallowed and even though it appeared to work before, it wasn't actually doing jdata at all. We had previously agreed that we'd disable this combination and hence the new behaviour. But the puzzle here is that none of GFS2 code path exactly disables this combination. Does it ? Why would the open fail ? The error is returned due to the (intentional) NULL pointer in the directIO slot of the address space operations for jdata files. |