Confirmed as well, thanks! What's really odd is I didn't see *anything* having a lock on /home, nada, zilch. We have a work-around in place for this but I was beating my head against the wall trying to figure it out.
On Fri, Dec 16, 2016 at 11:29 AM, Jonathan Billings billings@negate.org wrote:
On Fri, Dec 16, 2016 at 10:17:21AM -0800, Glenn E. Bailey III wrote:
This is a base install. If you deploy an instance in ec2 or GCE (ec2 you can do the free tier) it's easily repeatable. Even on a RHEL 7.3 instance. Note you'll need to allow root and password logins via SSH before attempting.
I can confirm this.
The culprit? NetworkManager has /home open. I can't figure out *WHY*.
# systemctl start NetworkManager.service # rmdir /home rmdir: failed to remove ‘/home’: Device or resource busy # systemctl stop NetworkManager.service # rmdir /home rmdir: failed to remove ‘/home’: Device or resource busy # systemctl stop NetworkManager.service # rmdir /home rmdir: failed to remove ‘/home’: Device or resource busy # systemctl kill NetworkManager.service # rmdir /home rmdir: failed to remove ‘/home’: Device or resource busy # rmdir /home
So it takes some time for all the parts of NetworkManager to die, but eventually, they do and you can remove /home.
Unfortunately, I don't see any reason why /home would be in use by NM. Very odd.
-- Jonathan Billings billings@negate.org _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos