On 04/29/2011 05:46 PM, Michael Sullivan wrote:
OK. I recently switched my three computers (carter, camille, and
catherine) to the new gcc profile: i686-pc-linux-gnu-4.4.5 from
i686-pc-linux-gnu-4.3.4. As recommended, I performed emerge -e system
and then emerge -e world on all of them. Carter finished his emerge -e
world a couple of days ago (he's faster than the others). Camille and
catherine were a few hundred packages from the end of their emerge -e
world when the power went out. Carter supplies daily
updated /usr/portage to camille and catherine via nfs, but when I
restarted the computers when the power came back on, I get this:
camille ~ # mount carter:/usr/portage /usr/portage/
mount.nfs: an incorrect mount option was specified
Am I not constructing my command correctly?
I have tried mount -t nfs and it still doesn't work. I can ping carter
fine, and carter says nfs is running. How do I get nfs back?
I use nfs about twice/year to transfer large files between machines -- so
I'm quite an expert at praying to the computer gods to "please let this nfs
mount work just this one last time and I'll never bother you again, I promise!"
I'm lying, of course, because I intend to do it again six months from now.
Every time, the computer gods make me suffer through multiple attempts to
guess the correct magic prayer before the remote nfs filesystem finally
appears for its biannual visit on /mnt/nfs.
Yes, I may well be paranoid, but it seems to me that the magic prayer for
nfs mounts changes every time I need it.
Sometimes I succeed using mount.nfs4, sometimes using mount -t nfs -o
nfsvers=4, or sometimes just mount -t nfs.
I have NFI what the real secret is, so I ask you nfs wonks to have mercy
and fill us in...
