Red Hat Bugzilla – Bug 1021882
GlusterFS mount succeeded and exists although the create storage domain failed
Last modified: 2016-02-10 13:50:01 EST
Created attachment 814915 [details]
Description of problem:
GlusterFS mount succeeded and exists although the create storage doamin failed becuase we use path which was in use previously and includes data
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create glusterFS storage domain using path that was in use previously and includes data
create new glusterSD fails (good) but as we already mount to check the mount remains in the host and we can't clean data and recreate the SD without manually umount.
in case create glusterFS SD fails we need to umount it from host.
[root@camel-vdsb /]# date
Tue Oct 22 12:17:31 IDT 2013
[root@camel-vdsb /]# mount
/dev/mapper/vg0-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
10.35.161.249:/acanan01 on /rhev/data-center/mnt/glusterSD/10.35.161.249:_acanan01 type fuse.glusterfs (rw,default_permissions,allow_other,max_read=131072)
How is the SD created?
GUI? REST? doesn't matter?
probably a dup of bug 1020812.
Daniel - please take a look?
verified using is23
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
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.