I was most def root. /home isn't mounted as a separate filesystem. It's not even tmpfs or btrfs. I was able to boot into single user mode to remove it, but this isn't possible in an automated fashion. I may just have to start building my own images. Still curious to know why I can't rename or move it. Anyone else try this on a stock 7.3 build? On Thu, Dec 15, 2016 at 8:42 AM, <m.roth at 5-cent.us> wrote: > Jon LaBadie wrote: >> On Thu, Dec 15, 2016 at 04:10:07AM -0600, geo.inbox.ignored wrote: >>> On 12/15/2016 01:47 AM, Gianluca Cecchi wrote: >>> > On Thu, Dec 15, 2016 at 2:49 AM, Glenn E. Bailey III < >>> > replicant at dallaslamers.org> wrote: >>> > >>> >> Tried this in both AWS and GCE as I though it may be a specific cloud >>> >> vendor issue. SELinux is disabled, lsof | grep home shows nothing, >>> >> lsattr /home shows nothing. Simply get "Device or resource busy." >>> >> >>> >> Works just find on 7.2 so I'm kinda at a loss. Scanned over the RHEL >>> >> release notes and didn't see anything. Anyone else have this issue? >>> We >>> >> move our /home to another mount point and symlink /home to it .. >>> >> >>> >> >>> > Do you have access to the console, so that you can try to do the move >>> while >>> > in single user mode? >>> > >>> }} >>> >>> that is one possibility. >>> >>> even greater is op is a 'user', not 'root'. > <snip> > > Here's a question to OP: how did you log into the system? If as *user*, > rather than as root, the filesystem is busy because you're logged on, and > in it. > > Missed some of the posts overnight - has anyone asked for the o/p of df -h? > > mark > > _______________________________________________ > 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."