To prove or disprove that the file is good or bad, you could cut / paste 
into an email the output of

hexdump -C /etc/fstab

Should be short enough with just a few text lines for email posting.

Chris (a different one than before)

Genie Jhang wrote:
> Thanks Chris.
>
> I used vi for the editor.
>
> I'm wondering too.
>
> It's odd.
>
> 2010/2/17 Chris Tooley <[log in to unmask] <mailto:[log in to unmask]>>
>
>     On 10-02-16 9:49 AM, Genie Jhang wrote:
>
>         I solved it with little cheat.
>
>         It looks like skipping the first line of nfs mount part of
>         fstab file.
>
>         I simply added two same lines as
>
>         192.168.0.109:/data     /data                   nfs
>         tcp,soft,bg,intr,ro 0 0
>         192.168.0.109:/data     /data                   nfs
>         tcp,soft,bg,intr,ro 0 0
>         192.168.0.109:/home     /home                   nfs
>         tcp,soft,bg,intr,rw 0 0
>
>         so that if it skips one line, it should do the the same line
>         next. haha
>
>         Thanks for all!!
>
>         Have a nice day or night all around the world.
>
>
>     In what editor are you editing the fstab? Perhaps it's adding an
>     invisible character to the beginning of the file which could
>     invalidate the first line...?
>
>     Is that the exact fstab you're using (i.e. the first line is the
>     first line? Are there comments before that? I find it really
>     strange that one line would work and the other wouldn't - there
>     must be something strange with the file itself.
>
>     -Chris
>
>