mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
39bdf601f6
I often get complains that container removal failed and users got following error message. "Driver devicemapper failed to remove root filesystem 18a69ba82aaf7a039ce7d44156215012d703001643079775190ac7dd6c6acf56:Device is Busy" This error message talks about container id but does not give any info about which particular device id is busy. Most likely device is mounted in some other mount namespace and if one knows the device id, they can try to do some debugging figuring which process and which mount namespace is keeping the device busy and how did we reach that stage. Without that information, it becomes almost impossible to debug the problem. So to improve the debuggability, when device removal fails, also return device id in error message. Now new message looks as follows. "Driver devicemapper failed to remove root filesystem 18a69ba82aaf7a039ce7d44156215012d703001643079775190ac7dd6c6acf56: Failed to remove device dbc15bdf9994a17c613d8ef9e924f3cffbf67f91e4f709295c901ad628377991:Device is Busy" Signed-off-by: Vivek Goyal <vgoyal@redhat.com> |
||
|---|---|---|
| .. | ||
| aufs | ||
| btrfs | ||
| devmapper | ||
| graphtest | ||
| overlay | ||
| overlay2 | ||
| overlayutils | ||
| quota | ||
| register | ||
| vfs | ||
| windows | ||
| zfs | ||
| counter.go | ||
| driver.go | ||
| driver_freebsd.go | ||
| driver_linux.go | ||
| driver_solaris.go | ||
| driver_unsupported.go | ||
| driver_windows.go | ||
| fsdiff.go | ||
| plugin.go | ||
| proxy.go | ||