Re: [Balloon] Mount oddity

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Nick Bane
Date:  
To: Colin Tuckley
CC: balloon
Subject: Re: [Balloon] Mount oddity
Colin Tuckley wrote:
> Nick Bane wrote:
>
>
>>For some reason I think you need the "-o nolock" switch.
>
>
> I tried that and it doesn't make any difference.
>
>
>>I also find that nfs synchronisation can take an age when a lot of data
>>is moved. Not really sure why.
>
>
> It's only the mount that takes any time, data transfers and umount both work
> as expected.
>

Sounds like a dns lookup timeout maybe? Are you mounting using an ip
address or what?

>
>>Thats unexpected. Is it actually installed? If it is then ipkg install
>>portmapper -force-depends should work.
>
>
> I tried this, it didn't fix the mount problem and when I removed it it's
> upset sshd so that I can't ssh into the balloon any more (fortunately I have
> a serial cable for it).
>
> Now that I'm trying things from the console I've noticed several odd things
> happening during the boot phase, some of which I'm sure were not there
> before I tried installing portmap.
>
> So I think it might be best to try installing a new root file system and
> start again from there.
>
> Which means I need to hassle Wookey (or someone) for which files I need to grab.
>
> regards,
>
> Colin
>