A good article about users point of view for Slackware distribution.

As I was dirnking my morning cup of coffee and reading GNU/Linux releated news sites I found an pretty good article about the user’s point of view of Slackware Linux distribution (Slackware was my distribution before I migrated to Debian GNU/Linux). In the article the autor who is experienced GNU/Linux user explain the impression he gets with the lastes Slackware release wich is 10.2.

NFS hell

With all my respect I will say that the implentation of NFS (Network File System) in to gnome-vfs and Gnome 2.10 at all is horrible. I spend my day trying to run NFS server for my local network, because there is not enought space left on my workstation. All other 4 PC’s on wich I run Gnome 2.8 working with the server as they should but my workstation can’t. When I mount nfs share and log in to gnome the network just don’t stop running here is some output of tcpdump -vv | grep nfs

root@workstation(1):/home/xpman>tcpdump -vv | grep nfs
(19:29:47) paskov: 19:28:55.907742 IP (tos 0x0, ttl 64, id 125, offset 0, flags [DF], proto: UDP (17), length: 152) workstation.my.flat.3536657554 > server.my.flat.nfs: 124 fsstat [|nfs]
19:28:55.908007 IP (tos 0x0, ttl 64, id 126, offset 0, flags [DF], proto: UDP (17), length: 112) server.my.flat.nfs > workstation.my.flat.3536657554: reply ok 84 fsstat POST: [|nfs]
19:28:56.408677 IP (tos 0x0, ttl 64, id 126, offset 0, flags [DF], proto: UDP (17), length: 152) workstation.my.flat.3553434770 > server.my.flat.nfs: 124 fsstat [|nfs]
19:28:56.908587 IP (tos 0x0, ttl 64, id 127, offset 0, flags [DF], proto: UDP (17), length: 152) workstation.my.flat.3570211986 > server.my.flat.nfs: 124 fsstat [|nfs]
19:28:56.908845 IP (tos 0x0, ttl 64, id 128, offset 0, flags [DF], proto: UDP (17), length: 112) server.my.flat.nfs > workstation.my.flat.3570211986: reply ok 84 fsstat POST: [|nfs]
19:28:57.408553 IP (tos 0x0, ttl 64, id 128, offset 0, flags [DF], proto: UDP (17), length: 152) workstation.my.flat.3586989202 > server.my.flat.nfs: 124 fsstat [|nfs]
19:28:57.408812 IP (tos 0x0, ttl 64, id 129, offset 0, flags [DF], proto: UDP (17), length: 112) server.my.flat.nfs > workstation.my.flat.3586989202: reply ok 84 fsstat POST: [|nfs]
19:28:57.908502 IP (tos 0x0, ttl 64, id 129, offset 0, flags [DF], proto: UDP (17), length: 152) workstation.my.flat.3603766418 > server.my.flat.nfs: 124 fsstat [|nfs]
19:28:57.908762 IP (tos 0x0, ttl 64, id 130, offset 0, flags [DF], proto: UDP (17), length: 112) server.my.flat.nfs > workstation.my.flat.3603766418: reply ok 84 fsstat POST: [|nfs]
19:28:58.410379 IP (tos 0x0, ttl 64, id 130, offset 0, flags [DF], proto: UDP (17), length: 152) workstation.my.flat.3620543634 > server.my.flat.nfs: 124 fsstat [|nfs]
19:28:58.410637 IP (tos 0x0, ttl 64, id 131, offset 0, flags [DF], proto: UDP (17), length: 112) server.my.flat.nfs > workstation.my.flat.3620543634: reply ok 84 fsstat POST: [|nfs]
19:28:58.910346 IP (tos 0x0, ttl 64, id 131, offset 0, flags [DF], proto: UDP (17), length: 152) workstation.my.flat.3637320850 > server.my.flat.nfs: 124 fsstat [|nfs]
19:28:58.910602 IP (tos 0x0, ttl 64, id 132, offset 0, flags [DF], proto: UDP (17), length: 112) server.my.flat.nfs > workstation.my.flat.3637320850: reply ok 84 fsstat POST: [|nfs]
80 packets captured
160 packets received by filter
0 packets dropped by kernel

The network just don’t stop sending packets between my server and workstation. Wich is aint normall… My /etc/exports file is created as apropriate and my /etc/fstab on workstation too. See them below:

My /etc/fstab file on workstation

# /etc/fstab: static file system information.
#
# [file system] [mount point] [type] [options] [dump] [pass]
proc /proc proc defaults 0 0
/dev/hda2 / ext3 defaults,errors=remount-ro 0 1
/dev/hda1 /boot ext3 defaults 0 2
/dev/hdb1 /home ext3 defaults 0 2
/dev/hda5 none swap sw 0 0
/dev/hda6 none swap sw 0 0
/dev/hdc /media/cdrom0 iso9660 ro,user,noauto 0 0
/dev/hdd /media/cdrom1 udf,iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

#NFS mount points
#[file system] [mount point] [type] [options] [dump pass]
server:/home/xpman/nfs_export /mnt/nfs_server nfs rw,user,auto 0 0

I tyed changing server with my server IP address but the result was the same. In two words: unresonable network load.

My /etc/exports on server

# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).

/home/xpman/nfs_export workstation.my.flat(rw,sync) mobile.my.flat(rw,sync)

I tried again changing workstation.my.flat and mobile.my.flat with the machines IP addresses but the result was the same. In case of someone ask a stupid question like this: Are you restart the nfs daemon after? The answer is YES.

What’s bring me to the Gnome 2.10 point? Since all other PC’s on the network work and comunicate well with the nfs server and I run Gnome 2.8 on them withought a problem there is something wrong with the new version of gnome-vfs and it’s implentation in Gnome 2.10. I tryed googling for this but all i found was complains about the buggy administration tools and specialy shared folders. I think it’s early at this time to report a bug in gnome-vfs and Gnome 2.10 at all. Tomorow I will do some more testing and then I will see what should I do….