[Techtalk] Slow booting since installing NFS daemons

Anne Wainwright anotheranne at fables.co.za
Sun Jan 4 13:10:00 UTC 2009

Meryll, hello,

thanks for your input, 2 emails, comment below

On Thu, 1 Jan 2009 12:53:08 -0800
Meryll wrote:

|> Hi Anne,
|> "Block error" or "Superblock error" is a common error when one file system
|> cannot read another, such as when one tries to mount a floppy that hasn't
|> been formatted yet or if the "mount" command is used with a filetype switch
|> that doesn't match the formatted file system.
|> That is why I think the problem might be using 2 different file systems with
|> NFS.  I looked up the reference material that I had on NFS and I haven't
|> found a configuration setting for file system type, which is what makes me
|> think NFS assumes that the mount and mounted file types are the same and
|> might have trouble when they are different.

When making an entry in fstab for an to mount an nfs share you set the file type as 'nfs', as you showed in your Friday email. When issuing a mount command at the root prompt, this is not necessary - ie works ok

Bear in mind that this is a boot up problem, there may be nothing else connected at that stage. Once the dilatory desktop is booted up there is no problem accessing the laptop share from the desktop. Laptop NFS server and shares, access from desktop, no problem.

We are talking about my also having installed NFS daemons on the desktop (as well as the laptop) so that I can potentially access a share on that from the laptop - and the resultant boot delay that occurred after installing the daemons.

[but when I try mount the desktop share from the laptop I get an error message on the laptop

mount: RPC: Program not registered

.... but that is another problem for me to check out.]

I naively assume that you could have it working both ways if you want, whether one way at a time or both ways.


|> Of course, I could be wrong....
|> Meryll
|> -----Original Message-----
|> From: Anne Wainwright [mailto:anotheranne at fables.co.za] 
|> Sent: Thursday, January 01, 2009 2:36 AM
|> To: Meryll Larkin
|> Subject: Re: [Techtalk] Slow booting since installing NFS daemons
|> Hi, Meryll,
|> I think the other posts have answered the reason why, which is because it is
|> a linux to linux connection and I thought it would be easier than samba.
|> Although samba is enabled on the ubuntu box it also has a conspicuous [fail]
|> listed against it which I have not had time to analyse.
|> Daneel suggested i look at /etc/hosts but this is fine. Exactly the same
|> entries on both machines. 
|> I wondered about hosts.allow and have made a generic sort of entry for
|> portmap in there, but no change.
|> I think this is something to do with the failure to start 'NFS common
|> utilities' and will investigate further when I have time. Since I have it
|> running the one way as I wanted, I am going to forget about the ubuntu
|> problems for the moment
|> best for the new year
|> Anne
|> On Sun, 28 Dec 2008 15:01:51 -0800
|> Meryll wrote:
|> |> I need to first confess that I am no expert and it seems to me that in
|> |> general, you have a better handle on what is going on than I do but....
|> |> 
|> |> I was wondering why you chose NFS for your mount instead of SAMBA?  I
|> think
|> |> you were right in your original assessement that the difficulty may be
|> due
|> |> to the fact that Debian and Ubuntu run different file systems.  Unless
|> you
|> |> REALLY have a bad superblock (an fsck would find that) on your laptop, I
|> |> think the problem is that reiser is having a hard time mounting to an
|> ext3
|> |> directory.  Hmmm, I wonder if the lost+found dir could be a problem....
|> |> 
|> |> I think of NFS as being the right tool for mounting like-file systems on
|> |> machines that rarely get rebooted (maybe once per month for updates).  I
|> |> think of Samba as the right tool for mounting different file systems
|> and/or
|> |> where one of them gets rebooted or unattached on a regular basis.
|> |> 
|> |> 
|> |> Meryll
|> |> 

so much to do, so little time :(

More information about the Techtalk mailing list