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@xxxxxxxxxxxxxxxx> 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@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos