Ignore ebusy when deleting a directory
#11066
Conversation
There was a problem hiding this comment.
@lukebakken unlike with enoent, should ebusy lead to a (limited) number retries with sleeps in between?
Which would require a slightly larger change.
|
According to So looks like we must retry up to N times with a delay in between (of, say, 5ms?) |
|
A retry won't fix the issue with |
lukebakken
force-pushed
the
rabbitmq-server-11047-ignore-ebusy
branch
from
6ddd380
to
f45a262
Compare
lukebakken
force-pushed
the
rabbitmq-server-11047-ignore-ebusy
branch
from
f45a262
to
ab909c3
Compare
Reported in #11047 This error manifests when the quorum directory is its own mount point
A folder can be a mount point and the kernel won't allow deleting a mount point - it will return ebusy We don't need to check for ebusy when deleting a file
msg_stores is a potential mount point and therefore might exist
michaelklishin
force-pushed
the
rabbitmq-server-11047-ignore-ebusy
branch
from
ab909c3
to
c9fcc4d
Compare
|
The force-push was a rebase. |
|
An additional investigation suggests that when there are two overlapping directories on two different Linux mounts (at least with EBS volumes), for instance
then the node won't be able to delete |
|
@Mergifyio backport v3.13.x |
✅ Backports have been created
|
Ignore `ebusy` when deleting a directory (backport #11066)
Reported in #11047
This error manifests when the quorum directory is its own mount point.