Red Hat Bugzilla – Bug 450276
GFS2: cannot use fifo nodes (named pipes)
Last modified: 2010-10-22 21:44:25 EDT
GFS2 in RHEL5.x is currently unable to use named pipes, refer to:
This has been resolved in the upstream kernel (see links below).
Please backport this capability in to RHEL5.x.
The above shows:
[linux/kernel/git/torvalds/linux-2.6.git] / fs / gfs2 / inode.c
2008-05-12 Bob Peterson [GFS2] filesystem consistency error from do_strip
2008-04-10 Josef Bacik [GFS2] fix GFP_KERNEL misuses
2008-03-31 Cyrill Gorcunov [GFS2] possible null pointer dereference fixup
2008-03-31 Denis Cheng [GFS2] re-support special inode
2008-03-31 Denis Cheng [GFS2] remove gfs2_dev_iops
Bumping the priority, we should have this for 5.3
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Created attachment 310297 [details]
Patches merged and ported from upstream
You can download this test kernel from http://people.redhat.com/dzickus/el5
Partners, this bug should be fixed in the latest RHEL 5.3 Snapshot. We believe that you have some interest in its correct functionality, so we're making a friendly request to send us some testing feedback.
If you have a chance to test it, please share with us your findings. If you have successfully VERIFIED the fix, please add PartnerVerified to the Bugzilla keywords, along with a description of the results. Thanks!
~~ Snapshot 6 is out ~~ Partners, please test and let us know if this bug has been fixed. Add PartnerVerified keyword if everything works as expected. For any new issues encountered, CLONE this bug and report the issues in the new bug.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.