Leonard den Ottolander
2016-Dec-15 18:48 UTC
[CentOS] Can't delete or move /home on 7.3 install
Hello Glen, On Thu, 2016-12-15 at 10:10 -0800, Glenn E. Bailey III wrote:> I was most def root.There's a difference whether you logged in as root or su-ed to root. In the latter case /home is still in use by the user you su-ed from. Even though it is not strictly necessary to init 1 you must make sure not a single user that uses /home for their home directory is logged in and no system user accesses files there (f.e. apache configured with home dirs) when attempting to move /home. Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research
Glenn E. Bailey III
2016-Dec-15 19:51 UTC
[CentOS] Can't delete or move /home on 7.3 install
Doing a lsof showed no open files against /home. Something else is locking it, not a user process. Also disabled SELinux, did a init 1, and only way to remove it was via single user by passing init=/sysinit/bin/sh On Thu, Dec 15, 2016 at 10:48 AM, Leonard den Ottolander <leonard at den.ottolander.nl> wrote:> Hello Glen, > > On Thu, 2016-12-15 at 10:10 -0800, Glenn E. Bailey III wrote: >> I was most def root. > > There's a difference whether you logged in as root or su-ed to root. In > the latter case /home is still in use by the user you su-ed from. > > Even though it is not strictly necessary to init 1 you must make sure > not a single user that uses /home for their home directory is logged in > and no system user accesses files there (f.e. apache configured with > home dirs) when attempting to move /home. > > Regards, > Leonard. > > -- > mount -t life -o ro /dev/dna /genetic/research > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos-- "replicants are like any other machine. They're either a benefit or a hazard. If they're a benefit, it's not my problem."
Jonathan Billings
2016-Dec-16 13:47 UTC
[CentOS] Can't delete or move /home on 7.3 install
On Thu, Dec 15, 2016 at 11:51:28AM -0800, Glenn E. Bailey III wrote:> Doing a lsof showed no open files against /home. Something else is > locking it, not a user process. Also disabled SELinux, did a init 1, > and only way to remove it was via single user by passing > init=/sysinit/bin/shIt sounds like /home is being managed by something in the kernel, then. Are you exporting /home via NFS or SMB? AutoFS? I'm trying to think what would start at runlevel 1, although if this is c7 that might not be a valid description anymore, perhaps services are being started at 'rescue.target'. -- Jonathan Billings <billings at negate.org>