On Sun, 13 Feb 2005, Denis Lagno wrote:

>>> So, the reason why /flam and /flam/volatile remain mounted and
>>> /flam/stuffy doesn't is clear.
>>
>> Really? If you remove flam:/stuffy, and recreate it, nfs will not be able
>> to retain that mount. You're basically very lost. You'll have do umount,
>> and mount it again. Doing a mount -u is not the same thing.
>
> Do not understand your "Really?".  I wrote that I recalled
> that directory /stuffy was removed and recreated.  And I wrote about
> reason why flam:/volatile remains mounted and flam:/stuffy
> appears lost.  And I wrote this reason is clear.

Ah, sorry. I misread your sentence. I thought you meant that it wasn't 
clear. My fault.

>>> But anyway it seems not very beatiful that client can not umount
>>> this filesystem.
>>
>> You shouldn't have any problems doing an umount. Did you have /flam/stuffy
>> in your fstab? Otherwise I'm not sure you can do the umount the way you're
>> trying. Perhaps try "umount flam:/stuffy"
>
> However the problem is that I really cannot umount it.
> It is in fstab, but actually it does not matter because
> it was always possible to umount either by device or by mount_point.
>
> # mount
> /dev/wd0a on / type ffs (noatime, nodevmtime, NFS exported, local)
> /dev/cgd1e on /volatile_sekuritat type ffs (noatime, soft dependencies, local)
> /dev/cgd1f on /sekuritat type ffs (noatime, soft dependencies, local)
> procfs on /proc type procfs (read-only, local)
> kernfs on /kern type kernfs (read-only, local)
> mfs:341 on /tmp type mfs (synchronous, local)
> /dev/cgd3f on /volatile type ffs (noatime, soft dependencies, local)
> /dev/cgd3g on /usr/local type ffs (nodev, noatime, local)
> /dev/cgd3e on /home type ffs (nosuid, nodev, noatime, soft dependencies, local)
> /dev/cgd3h on /stuffz type ffs (read-only, noexec, nosuid, nodev, noatime, local)
> flam:/ on /flam type nfs (read-only)
> flam:/volatile on /flam/volatile type nfs
> flam:/stuffy on /flam/stuffy type nfs (read-only, nosuid, nodev)
>
> # umount flam:/stuffy
> umount: /flam/stuffy: Invalid argument
>
> I just cannot umount it.  And if I mount it again, then
> this filesystem appears in df twice.
>
> So this is a bug, probably I should send-pr it..

Hmmm. The "invalid argument" message makes it sound like it just isn't 
parsing the line correctly. Which made me think that it wasn't passed on 
to umount_nfs.

How about "umount -t nfs /flam/stuffy" (or flam:/stuffy) ?
I'm sortof guessing here, but the error message sortof indicates that it 
don't even try to unmount, since it cannot correctly parse what you want.

But yes, you're right. umount can take either information, and extracts 
the other stuff from the fstab. Hmmm. What happens if you do
"umount flam:/stuffy /flam/stuffy" ?

 	Johnny

Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: bqt@update.uu.se           ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol