On Sat, Jan 24, 2004 at 12:14:20AM +0300, Andrew B. Panphiloff wrote:... skpd[EMAIL PROTECTED] /]ls -l /home/ | grep alucard drwx------ 2 alucard alucard 4096 Dec 12 14:23 alucard [EMAIL PROTECTED] /]id alucard uid=509(alucard) gid=510(alucard) groups=510(alucard) [EMAIL PROTECTED] /]chown -R alucard:alucard /home/alucard [EMAIL PROTECTED] /]chmod -R u+rwx /home/alucard/ [EMAIL PROTECTED] /]ls -l /home/ | grep alucard drwx------ 2 alucard alucard 4096 Dec 12 14:23 alucard [EMAIL PROTECTED] /]su - alucard su: warning: cannot change directory to /home/alucard: Permission denied -bash: /home/alucard/.bash_profile: Permission denied -bash-2.05b$ only cp solve my problem, but I can't copy all my disk!Are you using NFS by any chance? Or some other network-mounted file system for home directories (run 'mount' with no options to find out).
Good idea! If you don't deem it sensitive, it might be a good idea to post it here too. I for one have had trouble with mounted volumes before, both local and remote ones.
If it's not an nfs-mount, what filesystem are you using on the volume hosting /home? ext2, ext3, reiser or something else maybe?
If it is indeed a network mount, you need to make sure you have necessary permissions on the server as it may not honor your local 'root' privileges. Also, in this case you need to double check if your 'cp ' commands above didn't screw things up i.e. you didn't end up with local copies of that stuff instead of the network mounted directories (could happen if you are running an automount).
Automount seems to take control over the mount even to the extent that root is denied access in some cases, if youre running autofs, check your configs thoroughly, I've seen some cases where it (autofs) starts up with no errors, just to refuse all access later...
The only other thing that comes to mind is a corrupt filesystem, in which case you can try 'shutdown -r -F 0' , where '-F' should force 'fsck' on reboot (even for journalized filesystems).
