Dear Robert, Thank you. I think that the problem was caused by anti virus GravityZone. After stopping GravityZone demon, reboot makes normal file systems. I'll ask to GravityZone support about this problem. Tadao 2016-04-15 22:09 GMT+09:00 Robert Nichols <rnicholsNOSPAM at comcast.net>: > On 04/15/2016 01:05 AM, 望月忠雄 wrote: > >> Dear Robert, >> >> Before sending 'grep -r /home /etc' data, I want tell you what happned >> this >> morning. >> >> In order to solve the /home/home problem, 'umount /home' had been done, >> system had been running in a normal file system. >> But suddenly /home has been lost. >> >> >> Key information of that time is as in the **** lines. >> And I found in the //// lines messages log. >> How do you think the reason of trouble. >> > > Since you had two different things mounted on /home, it is unclear how > the system would interpret "umount /home". That is why I did not suggest > doing that. > > From the error, it seems that some checks got bypassed and a busy > filesystem was disconnected. It is likely that there is now some > filesystem corruption on /dev/vdb, and you should reboot with a forced > fsck to clean it up. You really should track down the cause of the > extra mount of /dev/vdb on /home first, or the system will just come > up wrong again. > > > -- > Bob Nichols "NOSPAM" is really part of my email address. > Do NOT delete it. > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >