I had a temporary RO mount of an external drive on /mnt, and updates of 'filesystem' package failed. I unmounted /mnt and the update proceeded without error. I wasn't able to reproduce it because the update is not idempotent, and I didn't want to risk (?) rolling it back, but if you have trouble reproducing I could be persuaded to try it. In any case, the package should not be messing with /mnt. Reproducible: Always Steps to Reproduce: 1. mount /dev/sde1 /mnt 2. yum update filesystem Actual Results: 100% | 4.0 B/s | 2.0 B | 00m00s [3/4] Upgrading filesystem-0:3.18-47.fc42.x86_64 100% | 857.9 KiB/s | 212.8 KiB | 00m00s >>> [RPM] unpacking of archive failed on file /mnt: cpio: chmod failed - Device or resource busy >>> Unpack error: filesystem-0:3.18-47.fc42.x86_64 Transaction failed: Rpm transaction failed. Expected Results: successful update
I guess what is happening is that rpm tries to adjust the mode of /mnt as described in the package, and there's VFAT mounted on /mnt, and that fails as unsupported. Since /mnt *is* supposed to be used like this, I think it'd make sense to change the entry to be %noverify or %ghost or something like that to make that case work.
I don't think any existing rpm file flag will help there, as long as the directory actually exists. There's no good solution to this ATM, but there's an upstream ticket on this use-case: https://github.com/rpm-software-management/rpm/issues/3400