Mageia forum

Upgrading from Mageia 1 to Mageia 2 went smoothly. Yes, but...

When I start dolphin it does not show anything like files or folders. Just an empty space. I added _netdev for my NFS mounts in fstab, but this did not change anything. Any ideas?

Are you saying that Dolphin starts with a blank page, but you can navigate to folders, or are you saying dolphin is blank no matter what you do?

magfan wrote:When I start dolphin it does not show anything like files or folders. Just an empty space. I added _netdev for my NFS mounts in fstab, but this did not change anything.

The _netdev thing was for a totally different issue. And are you talking about accessing your NFS mounts, or where exactly does dolphin show nothing?
Does the problem also persist when trying with a freshly created user?

The only time dolphin shows something is when I right-click on the desktop an select "open with dolphin". Only in this single case dolphin shows the icons from the desktop. But I cannot navigate to different folders. That is why I thought this behavior has something to do with the file systems and I mounted two NFS directories with this additional option. But it did not help. In the meantime I discovered that also the file open dialog of kwrite (or any other KDE program) does not let me navigate and does not show anything.

Is konqueror installed?

Yes, konqueror is installed and has the same problem.

I just called kdf and realized that the same NFS directories (/data1, /data2) seem to be mounted twice: once unsuccessful (NFS) and once successful (NFS4). Maybe that causes problems? Anyway, I do not know how to set it to only one NFS version.

Another thing is that all partitions appear as "removable devices".

Please show the output of

Code: Select all

showmount -e

and also the contents of /etc/exports from the NFS server and the contents of /etc/fstab from the client you're having this problem with.

Upgrade info:
cortex (client) - Mandriva 2010.2 -> Mageia 1 -> Mageia 2
amygdala (server) - Mandriva 2010.2 -> Mageia 1


showmount on cortex (client):

Code: Select all

[root@cortex opt]# showmount -e
Export list for cortex:
/imagepool amygdala_nfs
[root@cortex opt]#


/etc/fstab on cortex (client):

Code: Select all

#/dev/sda5 swap swap defaults 0 0
# Entry for /dev/sda6 :
UUID=0419fb8a-cabe-4dd9-9722-4f3644f2effc / ext4 acl,relatime 1 1
# Entry for /dev/sda1 :
UUID=b5aa7f55-a7c9-4b38-ad33-723ae94fa267 /boot ext3 acl,relatime 1 2
#/dev/sda9 /data ext4 acl,relatime 1 2
UUID=19136443-b9af-4283-97c6-49357ae78226 /data ext4 acl,relatime 1 2
#
amygdala_nfs:/data1 /data1 nfs rsize=8192,wsize=8192,nosuid,soft 0 0
amygdala_nfs:/data2 /data2 nfs rsize=8192,wsize=8192,nosuid,soft 0 0
#/dev/sda7 /tmp ext4 acl,relatime 1 2
# Entry for /dev/sda8 :
UUID=f1b73a0f-ba7a-4e6e-ba8d-cb1ab6e10950 /home ext4 acl,relatime 1 2
# Entry for /dev/sdd1 :
UUID=db2da449-a7af-40f4-bf8f-2d5cf6a466d9 /imagepool ext4 defaults,acl 1 2
#/dev/DICOM/1 /imagepool ext4 defaults,acl 1 2
/dev/sr1 /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0
none /proc proc defaults 0 0
#/dev/sda6 / ext4 acl,relatime 1 1
# Entry for /dev/sda7 :
UUID=a0e5f589-1cfc-453b-a937-1d3700406e8a /tmp ext4 acl,relatime 1 2
#/dev/sda1 /boot ext3 acl,relatime 1 2
# Entry for /dev/sda5 :
UUID=8556eaea-6ea5-43e7-81bf-9d4ee7c604cd swap swap defaults 0 0


/etx/exports on amygdala (server):

Code: Select all

# generated by drakhosts.pl
/data1 cortex_nfs(no_root_squash,async,secure,no_subtree_check,rw)
/data2 cortex_nfs(no_root_squash,async,secure,no_subtree_check,rw)


Can this be related to the following bug?

https://bugs.archlinux.org/task/27851

I could solve the problem be editing /etc/fstab (adding a slash at the end of the mounted directory). Instead of just "/data1" and "/data2" I had to mount "/data1/" and "/data2/" like in /etc/mtab:

Code: Select all

cat /etc/fstab | grep amygdala_nfs
amygdala_nfs:/data1/ /data1 nfs rsize=8192,wsize=8192,nosuid,soft 0 0
amygdala_nfs:/data2/ /data2 nfs rsize=8192,wsize=8192,nosuid,soft 0 0

cat /etc/mtab | grep amygdala_nfs
amygdala_nfs:/data1/ /data1 nfs4 rw,nosuid,relatime,vers=4,rsize=8192,wsize=8192,namlen=255,soft,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.4.1,minorversion=0,local_lock=none,addr=192.168.4.2 0 0
amygdala_nfs:/data2/ /data2 nfs4 rw,nosuid,relatime,vers=4,rsize=8192,wsize=8192,namlen=255,soft,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.4.1,minorversion=0,local_lock=none,addr=192.168.4.2 0 0


Could the missing slash be automatically added by mcc? That would be nice.

How did you setup those NFS mounts on the client?

And yes, it could be related to the bug you mentioned, but i'm not sure.

doktor5000 wrote:How did you setup those NFS mounts on the client?

I used mcc to create /etc/fstab. Later I added the trailing slashes manually when I saw that the system itself uses them in /etc/mtab. Unmounting and mounting again solved the problem.

I thought the problem was solved, but it is not! Dolphin works very well as long as you never try to access a NFS mounted directory via dolphin. It turns out to be very closely related to bug https://bugs.archlinux.org/task/27851. Is there any chance to "downgrade" the filesystem package?

Dolphin works very well as long as you never try to access a NFS mounted directory via dolphin.

I do not have the same problem with Dolphin and NFS mounts.
You never answered when asked if a new user has the same problem?

Can you navigate the NFS file system using Midnight Commander ( mc ) on the command line? (as your user)

Yes, any user on this system. I deleted my own account including $HOME and created a new account again. But it did not help. Doing so I could solve another problem (viewtopic.php?f=7&t=2632) but the NFS problem remains.

There is no problem to navigate the NFS file system using konsole or mc.

Just as an experiment.
What do you get if you put the URL into Dolphin or Konqueror

Code: Select all

nfs://amygdala_nfs:/data2

djennings wrote:Just as an experiment.
What do you get if you put the URL into Dolphin or Konqueror

Code: Select all

nfs://amygdala_nfs:/data2

An error like "authentication failed. amygdala_nfs not supported"

I'm experiencing the same problems. Not only in dolphin, but also on the Desktop, see https://forums.mageia.org/de/viewtopic.php?f=8&t=724.

My /home is mounted via NFS, too.

This problem is related to https://forums.mageia.org/en/viewtopic.php?f=7&t=2685.