https://bugzilla.redhat.com/show_bug.cgi?id=253530
Pavel Raiskup <praiskup(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |NEW
CC| |praiskup(a)redhat.com
Resolution|WONTFIX |---
Keywords| |Reopened
--- Comment #22 from Pavel Raiskup <praiskup(a)redhat.com> ---
I've been bitten by this issue today. Going through strace did not help too
much, lucky googling gave me link to this bug report. Uff.
Is this documented somewhere at least? Or is this so well known issue? It
was like facing some magic :)
mount-a options: rw,context=system_u:object_r:httpd_sys_content_t:s0
mount-b options: rw
Well, I tried to switch mount-b options to 'rw,sync' and it worked
(sometimes?) :), having context= there also worked, having other options did
not work.
I see that there is hard to guess real reason for EBUSY, but it does not seem
to be impossible based on already existing mount points.
Well, I'll never do the same mistake again, but others may do and we should
tell them, somehow. In the worst case, making the warning more verbose
mentioning that it "could be this, see rhbz#253530" could save some painful
hours of debugging ..
Pavel
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=5bv4QfW8Z1&a=cc_unsubscribe