[opensuse] Can't list home directory
When I do a "ls -a /home/jan" as a user the console hangs. As a root it works, but I get this error on top: "ls: cannot access /home/jan/.gvfs: Permission denied" "ls -ls /home/jan" as root gets the whole directory listing, which includes this entry: "? d????????? ? ? ? ? ? .gvfs" "rm -rf" won't remove it, I get "Permission denied" as a root! Opening Dolphin results in it hanging also, as it tries to list the home directory. What now? /Jan K. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 05 February 2009 15:48:59 Jan Karjalainen wrote:
When I do a "ls -a /home/jan" as a user the console hangs. As a root it works, but I get this error on top: "ls: cannot access /home/jan/.gvfs: Permission denied"
"ls -ls /home/jan" as root gets the whole directory listing, which includes this entry:
"? d????????? ? ? ? ? ? .gvfs"
"rm -rf" won't remove it, I get "Permission denied" as a root!
Opening Dolphin results in it hanging also, as it tries to list the home directory.
What now?
Don't do it as root. .gvfs is only accessible for the user who owns it It is related to FUSE Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-02-05 at 15:48 +0100, Jan Karjalainen wrote:
When I do a "ls -a /home/jan" as a user the console hangs. As a root it works, but I get this error on top: "ls: cannot access /home/jan/.gvfs: Permission denied"
"ls -ls /home/jan" as root gets the whole directory listing, which includes this entry:
"? d????????? ? ? ? ? ? .gvfs"
"rm -rf" won't remove it, I get "Permission denied" as a root!
Opening Dolphin results in it hanging also, as it tries to list the home directory.
Log out as user, log in as root. Issue the command "mount". Normally you would see an entry like this one: gvfs-fuse-daemon on /home/jan/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=jan) Yours will be different; please post it, I'm curious. Then umount that entry, it has no business with the user logged out. Once umounted, try to log in again. If it doesn't allow root to umount it, then try to log in as user but on the text console (ctrl-alt-f1), not gnome. Or use xfce if you don't like text mode. I think there is/was a bugzilla about this. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmLDcUACgkQtTMYHG2NR9WR1ACdEOx0ItMfs3Jcij+iob20oiGT TmMAn2fixgsxyjryegrTaFuI2fj8MEpZ =YOmX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday February 5 2009, Carlos E. R. wrote:
...
Log out as user, log in as root. Issue the command "mount". Normally you would see an entry like this one:
I don't believe the mount command restricts its output based on privilege, does it? I use the Archive Mount software which uses FUSE and libarchive to provide transparent access to TAR, PkZip and other archive formats and I always see other users' FUSE mounts that were performed via Archive Mount.
gvfs-fuse-daemon on /home/jan/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=jan)
...
-- Cheers, Carlos E. R.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-02-05 at 08:13 -0800, Randall R Schulz wrote:
On Thursday February 5 2009, Carlos E. R. wrote:
...
Log out as user, log in as root. Issue the command "mount". Normally you would see an entry like this one:
I don't believe the mount command restricts its output based on privilege, does it? I use the Archive Mount software which uses FUSE and libarchive to provide transparent access to TAR, PkZip and other archive formats and I always see other users' FUSE mounts that were performed via Archive Mount.
That mount entry is special, root is not allowed to see it: nimrodel:~ # mount | grep fuse fusectl on /sys/fs/fuse/connections type fusectl (rw) gvfs-fuse-daemon on /home/cer/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=cer) nimrodel:~ # ls /home/cer/.gvfs ls: cannot access /home/cer/.gvfs: Permission denied nimrodel:~ # But the reason to log out as user is because it hangs for the OP, so he would not be able to do anything. So he has to try as root or using a different desktop than gnome, which uses that strange filesystem. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmLEg4ACgkQtTMYHG2NR9U7CACgjgVdQwdSPTP4od1psEZdsp3w bYYAn2buVyoJciBj6eDefvD/9m5Q6KyW =KqRS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Feb 5, 2009 at 17:21, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2009-02-05 at 08:13 -0800, Randall R Schulz wrote:
On Thursday February 5 2009, Carlos E. R. wrote:
...
Log out as user, log in as root. Issue the command "mount". Normally you would see an entry like this one:
I don't believe the mount command restricts its output based on privilege, does it? I use the Archive Mount software which uses FUSE and libarchive to provide transparent access to TAR, PkZip and other archive formats and I always see other users' FUSE mounts that were performed via Archive Mount.
That mount entry is special, root is not allowed to see it:
nimrodel:~ # mount | grep fuse fusectl on /sys/fs/fuse/connections type fusectl (rw) gvfs-fuse-daemon on /home/cer/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=cer) nimrodel:~ # ls /home/cer/.gvfs ls: cannot access /home/cer/.gvfs: Permission denied nimrodel:~ #
But the reason to log out as user is because it hangs for the OP, so he would not be able to do anything. So he has to try as root or using a different desktop than gnome, which uses that strange filesystem.
- -- Cheers, Carlos E. R.
When I do Ctrl+Alt+F1, the only thing I see is the startup messages and the last line which says "Blocking file system". F2-F6 won't work at all, just F1 and F7. The same happens when I reboot and put 1 or 3 as an option in Grub menu. "Blocking file system" comes up after a while... It never goes as far as to giving me a console prompt. Is re-installation the only way to go? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday February 5 2009, Jan Karjalainen wrote:
...
When I do Ctrl+Alt+F1, the only thing I see is the startup messages and the last line which says "Blocking file system". F2-F6 won't work at all, just F1 and F7.
The same happens when I reboot and put 1 or 3 as an option in Grub menu. "Blocking file system" comes up after a while... It never goes as far as to giving me a console prompt.
Now there's a classic phrase for a Web search. Google gives many hits (using the quotations that make it search for a literal phrase, not just a document with all those words; add other keywords as necessary to refine or redirect the search on subsequent attempts). The bulk of the first page of Google hits mention VMware. Are you using that?
Is re-installation the only way to go?
Gack! This ain't Windows territory... But to be a bit more serious, this notion of reinstalling as a means of correcting errors is something we need to stamp out. If you don't understand what's happening and / or how / why it happened, then even if a reinstallation appears to solve the problem, how do you know you won't walk right back into it again? Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday February 5 2009, Randall R Schulz wrote:
On Thursday February 5 2009, Jan Karjalainen wrote:
...
When I do Ctrl+Alt+F1, the only thing I see is the startup messages and the last line which says "Blocking file system". F2-F6 won't work at all, just F1 and F7.
The same happens when I reboot and put 1 or 3 as an option in Grub menu. "Blocking file system" comes up after a while... It never goes as far as to giving me a console prompt.
Now there's a classic phrase for a Web search. Google gives many hits (using the quotations that make it search for a literal phrase, not just a document with all those words; add other keywords as necessary to refine or redirect the search on subsequent attempts). The bulk of the first page of Google hits mention VMware. Are you using that?
Check it out (from my own system, where VMware Workstation 6.5 is installed): % egrep -li 'Blocking File System' /etc/init.d/* /etc/init.d/vmware Examining /etc/init.d/vmware, I find that it prints that just before running "vmware_start_vmblock" (during start-up) and again before executing "vmware_stop_vmblock" (during shut-down). Clearly VMware is, if not the culprit itself, involved in this symptom. Thus perusal and search of the VMware forums is a good place to start. There are many knowledgeable users and clearly this has come up before and either the solution of further diagnostic actions can likely be found there. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Feb 5, 2009 at 11:55 AM, Jan Karjalainen <jrock@akkalakkadakka.com> wrote:
The same happens when I reboot and put 1 or 3 as an option in Grub menu. "Blocking file system" comes up after a while... It never goes as far as to giving me a console prompt.
Is re-installation the only way to go? -- Jan,
I've had the same issue for sometime now. After having my console hang while trying to list the home directory, I ran fdisk and found a corrupt segment somewhere. The only way to fix it was to reboot and let fdisk do its thing during startup. It seems to happen randomly and most of the time, my home partition is not umounted when I shut down. Removing fuse seems to have reduced the occurence, but it still pops up every once in a while. Nkoli -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday February 5 2009, Nkoli wrote:
On Thu, Feb 5, 2009 at 11:55 AM, Jan Karjalainen
<jrock@akkalakkadakka.com> wrote:
The same happens when I reboot and put 1 or 3 as an option in Grub menu. "Blocking file system" comes up after a while... It never goes as far as to giving me a console prompt.
Is re-installation the only way to go? --
Jan,
I've had the same issue for sometime now. After having my console hang while trying to list the home directory, I ran fdisk and found a corrupt segment somewhere. The only way to fix it was to reboot and let fdisk do its thing during startup.
Unless the problem is on your root file system, rebooting is not necessary. Simply going to single-user mode, unmounting the file system in question and running fsck on it (and note, fdisk is for establishing, examining and manipulating partitions, not file systems per se). Once it's been repaired by fsck, you can "init 5" to get your GUI back or "init 3" to get multi-user + networking w/o X.
It seems to happen randomly and most of the time, my home partition is not umounted when I shut down. Removing fuse seems to have reduced the occurence, but it still pops up every once in a while.
Nkoli
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Feb 5, 2009 at 12:24 PM, Randall R Schulz <rschulz@sonic.net> wrote:
Unless the problem is on your root file system, rebooting is not necessary. Simply going to single-user mode, unmounting the file system in question and running fsck on it (and note, fdisk is for establishing, examining and manipulating partitions, not file systems per se). Once it's been repaired by fsck, you can "init 5" to get your GUI back or "init 3" to get multi-user + networking w/o X.
Whoops. I meant fsck not fdisk. Side effects of being at work and in a hurry :) I tried manually unmounting the home partition the first time, but it hung forever in the process, so I restarted. Even shutting down doesn't unmount it, but at least truncated segments are cleaned up at boot. I do have vmware workstation installed and don't use nfs. Haven't really had a chance yet to poke around to locate the culprit. Nkoli -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jan Karjalainen wrote:
When I do Ctrl+Alt+F1, the only thing I see is the startup messages and the last line which says "Blocking file system". F2-F6 won't work at all, just F1 and F7.
The same happens when I reboot and put 1 or 3 as an option in Grub menu. "Blocking file system" comes up after a while... It never goes as far as to giving me a console prompt.
Is re-installation the only way to go?
A way to bypass a hang at this point is press Alt+SysRq+e which will terminate the hanging program (along with a few others) and give you a working console where you can log in. Have you fscked your partitions yet and checked the permissions on your home directory? Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jan Karjalainen wrote:
When I do a "ls -a /home/jan" as a user the console hangs. As a root it works, but I get this error on top: "ls: cannot access /home/jan/.gvfs: Permission denied"
"ls -ls /home/jan" as root gets the whole directory listing, which includes this entry:
"? d????????? ? ? ? ? ? .gvfs"
"rm -rf" won't remove it, I get "Permission denied" as a root!
Opening Dolphin results in it hanging also, as it tries to list the home directory.
What now?
/Jan K.
Jan, Here is a repost from the other thread: Looks like /home isn't mounted anymore or the drive with /home on it died. Do a mount to check. I only see ? d????????? stuff when a mounted drive is unavailable and the system thinks it is still mounted. You can try and umount the /home partition and then your permission should go back to normal, then figure out why the mount died. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Feb 5, 2009 at 18:32, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Jan Karjalainen wrote:
When I do a "ls -a /home/jan" as a user the console hangs. As a root it works, but I get this error on top: "ls: cannot access /home/jan/.gvfs: Permission denied"
"ls -ls /home/jan" as root gets the whole directory listing, which includes this entry:
"? d????????? ? ? ? ? ? .gvfs"
"rm -rf" won't remove it, I get "Permission denied" as a root!
Opening Dolphin results in it hanging also, as it tries to list the home directory.
What now?
/Jan K.
Jan,
Here is a repost from the other thread:
Looks like /home isn't mounted anymore or the drive with /home on it died. Do a mount to check. I only see ? d????????? stuff when a mounted drive is unavailable and the system thinks it is still mounted. You can try and umount the /home partition and then your permission should go back to normal, then figure out why the mount died.
I uninstalled VMware Workstation and rebooted. Here's my /var/log/boot.msg: http://pastebin.com/d7bde3ba It seems to hang at the "Starting NFS client services: sm-notify idmapd" line. mount gives this: ------------------------------------------ /dev/sda2 on / type ext3 (rw,acl,user_xattr) /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sda3 on /home type ext3 (rw,acl,user_xattr) /dev/sda4 on /windows/C type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096) fusectl on /sys/fs/fuse/connections type fusectl (rw) securityfs on /sys/kernel/security type securityfs (rw) ------------------------------------------ "ls -a /home/jan" as user "jan" hangs the console still, as root it works fine. I ran fsck on both /dev/sda2 and /dev/sda3 without errors. I now have a machine that won't let me Ctrl+Alt+F1-6 into a console, and it won't mount NFS shares when booting, and it hangs the console when doing ls -a in the /home/jan directory. "rcnfs start" outputs "Starting NFS client services: sm-notify idmapd" and then it hangs. "mount -a -F" gives this: ------------------------------------------- mount -a -F mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. can't lock lock file /etc/mtab~: timed out can't lock lock file /etc/mtab~: timed out ------------------------------------------- Then it hangs. Listing the NFS shares works fine after that though. Seems like there's something wrong with the nfs client service too. Tired of this now... :-( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jan Karjalainen wrote:
On Thu, Feb 5, 2009 at 18:32, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Jan Karjalainen wrote:
When I do a "ls -a /home/jan" as a user the console hangs. As a root it works, but I get this error on top: "ls: cannot access /home/jan/.gvfs: Permission denied"
"ls -ls /home/jan" as root gets the whole directory listing, which includes this entry:
"? d????????? ? ? ? ? ? .gvfs"
"rm -rf" won't remove it, I get "Permission denied" as a root!
Opening Dolphin results in it hanging also, as it tries to list the home directory.
What now?
/Jan K. Jan,
Here is a repost from the other thread:
Looks like /home isn't mounted anymore or the drive with /home on it died. Do a mount to check. I only see ? d????????? stuff when a mounted drive is unavailable and the system thinks it is still mounted. You can try and umount the /home partition and then your permission should go back to normal, then figure out why the mount died.
I uninstalled VMware Workstation and rebooted. Here's my /var/log/boot.msg: http://pastebin.com/d7bde3ba It seems to hang at the "Starting NFS client services: sm-notify idmapd" line. <snip> ------------------------------------------- mount -a -F mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. can't lock lock file /etc/mtab~: timed out can't lock lock file /etc/mtab~: timed out ------------------------------------------- Then it hangs.
Listing the NFS shares works fine after that though. Seems like there's something wrong with the nfs client service too.
Tired of this now... :-(
I feel your pain. The mtab lock problem looks promising. I don't use NFS, so I can't just spit out and answer, but it looks like it is trying to mount something it can't and that is causing a bloody mess. I experience "the exact-same list/hang" symptoms when I have a mounted smb share that goes away while it is mounted (like when I have a share mapped to one of the kids computers and they reboot to get into windows). Trying to get a directory listing in either konsole or konqueror causes a hang for the timeout period (120 secs I think) then the listing completes. If you are trying to mount an NFS share that isn't there or is having problems, that could explain the symptoms, but somebody else smarter than I am will have to give nfs specific help. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-02-05 at 18:59 +0100, Jan Karjalainen wrote:
I uninstalled VMware Workstation and rebooted. Here's my /var/log/boot.msg: http://pastebin.com/d7bde3ba It seems to hang at the "Starting NFS client services: sm-notify idmapd" line.
I would try disabling that service for the moment: if init does not complete, you do not get the text consoles, which is another of your symptoms.
mount gives this: ------------------------------------------ /dev/sda2 on / type ext3 (rw,acl,user_xattr) /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sda3 on /home type ext3 (rw,acl,user_xattr) /dev/sda4 on /windows/C type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096) fusectl on /sys/fs/fuse/connections type fusectl (rw) securityfs on /sys/kernel/security type securityfs (rw) ------------------------------------------
"ls -a /home/jan" as user "jan" hangs the console still, as root it works fine. I ran fsck on both /dev/sda2 and /dev/sda3 without errors.
And there is not that fuse filesystem on home, it seems?
I now have a machine that won't let me Ctrl+Alt+F1-6 into a console, and it won't mount NFS shares when booting, and it hangs the console when doing ls -a in the /home/jan directory. "rcnfs start" outputs "Starting NFS client services: sm-notify idmapd" and then it hangs.
Well, you need to find out why, or disable it.
"mount -a -F" gives this: ------------------------------------------- mount -a -F mount.nfs: rpc.statd is not running but is required for remote locking.
rpc? You may need to start "nfsserver" first, it is there where that daemon is started. Or do what it says below:
mount.nfs: Either use '-o nolock' to keep locks local, or start statd. can't lock lock file /etc/mtab~: timed out can't lock lock file /etc/mtab~: timed out ------------------------------------------- Then it hangs.
Maybe that's the root cause, you need nfsserver first so that rpc.statd is running and you have remote locking enabled.
Listing the NFS shares works fine after that though. Seems like there's something wrong with the nfs client service too.
Yes.
Tired of this now... :-(
Understandable. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmLOi8ACgkQtTMYHG2NR9UYigCfS15r1xsdsFzmSYD3Gvts45Cx kGIAnjwiZtdiivhvuM95R8f1cmPFFFXX =kZw0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Anders Johansson -
Carlos E. R. -
Dave Plater -
David C. Rankin -
Jan Karjalainen -
Nkoli -
Randall R Schulz