Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJaroslav Kortus
2013-10-29 19:53:30 UTC
Description of problem:
Currently tmpfs is recognized as a supported filesystem of fs.sh resource.
This filesystem cannot work in current implementation ("none" device is not supported and later it requires fsck).
As probably no one has ever run it, we could drop it from the agent.
Version-Release number of selected component (if applicable):
resource-agents-3.9.2-40.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. add <fs device="/dev/loop0" fstype="tmpfs" mountpoint="/tmp/fstest" name="filesystem"/> to your cluster service
2.
3.
Actual results:
tmpfs cannot be mounted via rgmanager
Expected results:
message that tmpfs is not supported
Additional info:
Comment 5Oyvind Albrigtsen
2015-11-02 10:39:17 UTC
Comment 6Oyvind Albrigtsen
2015-11-02 10:40:31 UTC
Tested patch. Had to change the return code from OCF_ERR_ARGS as utils/fs-lib.sh thought that means success.
Comment 7Oyvind Albrigtsen
2015-11-09 12:44:22 UTC
Created attachment 1091728[details]
Updated working patch
Improved the patch and tested that it's working without any issues.
Comment 8Oyvind Albrigtsen
2015-12-21 12:26:05 UTC
Before:
- Error about none-device not being supported, or error when running fsck if device is set to e.g. /dev/loop0.
After:
- Message that tmpfs is not supported.
Comment 9Oyvind Albrigtsen
2015-12-24 13:09:41 UTC
Setup:
Add the following service to /etc/cluster/cluster.conf:
<service autostart="0" domain="fodom" name="tmpfs">
<fs device="/dev/loop0" fstype="tmpfs" mountpoint="/tmp/fstest" name="filesystem"/>
</service>
Before:
# rpm -q resource-agents
resource-agents-3.9.5-24.el6_7.1.x86_64
# clusvcadm -e tmpfs
# tail -f /var/log/cluster/rgmanager.log
Dec 24 14:05:57 rgmanager Starting disabled service service:tmpfs
Dec 24 14:05:57 rgmanager [fs] start_filesystem: Creating mount point /tmp/fstest for device /dev/loop0
Dec 24 14:05:57 rgmanager [fs] Unknown file system type 'tmpfs' for device /dev/loop0. Assuming fsck is required.
Dec 24 14:05:57 rgmanager [fs] Running fsck on /dev/loop0
Dec 24 14:05:57 rgmanager [fs] 'fsck -p /dev/loop0' failed, error=8; check /var/log/cluster/loop0.fsck.log for errors
Dec 24 14:05:57 rgmanager [fs] Invalidating buffers for /dev/loop0
After:
# rpm -q resource-agents
resource-agents-3.9.5-28.el6.x86_64
# clusvcadm -e tmpfs
# tail -f /var/log/cluster/rgmanager.log
Dec 24 14:06:57 rgmanager Starting disabled service service:tmpfs
Dec 24 14:06:57 rgmanager [fs] File system type tmpfs not supported
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-0735.html
Description of problem: Currently tmpfs is recognized as a supported filesystem of fs.sh resource. This filesystem cannot work in current implementation ("none" device is not supported and later it requires fsck). As probably no one has ever run it, we could drop it from the agent. Version-Release number of selected component (if applicable): resource-agents-3.9.2-40.el6.x86_64 How reproducible: always Steps to Reproduce: 1. add <fs device="/dev/loop0" fstype="tmpfs" mountpoint="/tmp/fstest" name="filesystem"/> to your cluster service 2. 3. Actual results: tmpfs cannot be mounted via rgmanager Expected results: message that tmpfs is not supported Additional info: