Bug 150481
Summary: | Stopping of filesystem service fails with certain devices | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Derek Anderson <danderso> |
Component: | rgmanager | Assignee: | Lon Hohberger <lhh> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | cluster-maint |
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: | 2005-05-06 20:45:36 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
Derek Anderson
2005-03-07 15:41:56 UTC
Ah, an artifact of 5-year-old mount/umount code ;) Er, why will 'mount' work but not 'umount' ? Fixed in CVS Needs to follow symlinks in status portion so that we can compare multiple possible outputs of mount(1). (Don't forget to watch for symlink loops.) e.g.: fstab has: /dev/vg0/root which is a symlink to: /dev/mapper/vg0-root The latter is what mount(1) reports. Derek noted that we should run down symlinks in the output of mount too. Fixes in CVS. a. Walks symlinks / does findfs / whatever for specifed device b. Figures out if mount output is a symlink and traces it for each "device" output from mount(1). fs.sh should work with symlinks specified, UUID=<foo>, LABEL=<foo>, and directly-specified devices (e.g. /dev/sda1) now, even if the output of mount(1) doesn't directly match what was specified in cluster.conf (as long as the final device matches...). These have been fixed in CVS for some time; closing |