Why does a filesystem (fs) resource fail to start on RHEL 6?
Issue
- Why does a filesystem (
fs
) resource fail to start on RHEL 6? It produces the following error:
Mar 14 11:31:27 rhel6-1 rgmanager[31844]: Starting disabled service service:ext3
Mar 14 11:31:27 rhel6-1 rgmanager[1673]: [lvm] Starting volume group, vg_shared_2
Mar 14 11:31:27 rhel6-1 rgmanager[1720]: [fs] start_filesystem: Could not match /dev/mapper/vg_shared_2-lvol1 with a real device
Mar 14 11:31:30 rhel6-1 rgmanager[1741]: [fs] start_filesystem: Could not match /dev/mapper/vg_shared_2-lvol1 with a real device
Mar 14 11:31:33 rhel6-1 rgmanager[1763]: [fs] start_filesystem: Could not match /dev/mapper/vg_shared_2-lvol1 with a real device
Mar 14 11:31:36 rhel6-1 rgmanager[31844]: start on fs "ext3lvol2" returned 2 (invalid argument(s))
Mar 14 11:31:36 rhel6-1 rgmanager[31844]: #68: Failed to start service:ext3; return value: 1
Mar 14 11:31:36 rhel6-1 rgmanager[31844]: Stopping service service:ext3
Mar 14 11:31:37 rhel6-1 rgmanager[1805]: [fs] stop: Could not match /dev/mapper/vg_shared_2-lvol1 with a real device
Mar 14 11:31:37 rhel6-1 rgmanager[31844]: stop on fs "ext3lvol2" returned 5 (program not installed)
Mar 14 11:31:37 rhel6-1 rgmanager[31844]: #12: RG service:ext3 failed to stop; intervention required
Mar 14 11:31:37 rhel6-1 rgmanager[31844]: Service service:ext3 is failed
Mar 14 11:31:37 rhel6-1 rgmanager[31844]: #13: Service service:ext3 failed to stop cleanly
Environment
- Red Hat Enterprise Linux Server 6 (with the High Availability Add On)
rgmanager
managing a filesystem (fs
) resource
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.