GParted - Queued actions fail as some background process seems to intervene by automatically re-mounting
Examples of failure
The normal way (which works on other Linuxes)
1) GParted > Unmount a certain partition
2) Programs works, and refreshes the device view, device shown as unmounted.
## Remark: Switching to Thunar still shows the volume mounted!
3) Format your certain partition, Apply. Fails with message:
mke2fs 1.41.12 (17-May-2010)
<your drive and partition path> is mounted; will not make a filesystem here!
Failing Workaround:
1) GParted runs
2) Thunar > Right click on volume > Unmount
Error message:
Unable to unmount "<drive label>":
The enclosing drive for the volume is locked
## Remark: Probably locked by GParted
Working workaround:
1) Close all apps
2) Thunar > Right click on volume > Unmount
3) Start GParted and do your stuff there.
## Remark: The problem is that this only works for single partition drives. As soon as you queue multiple actions in GParted, and then apply them, the first action is performed, and then the further actions fail. Why? The first action is performed, then the unknown background mechanism already mounts a created volume, and further commands such as change partition label, or create fruther partitions fail, because the first partition was already mounted, hence the drive locked fro further modifications.