Re: umount -a -f -t nfs doesn't work when a file has been written and "-l" option is needed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



El sáb, 12-09-2009 a las 16:01 +0100, Al Viro escribió:
> > > Seems that I need to run "umount -l" for being able to unmount it, even
> > > when I expected that "-f" should be enough.
> > Hopefully you will be rebooting soon since kernel structures (ala the
> > super block) are not cleaned up with 'umount -l'. Which could make the
> > system somewhat unstable. 
> 
> Um...  Not really.  The damn thing is detached from the namespace and
> left alone until it's not busy anymore.  At that point it's hit with the
> rest of umount() (i.e. with filesystem driver being told to shut it down).
> 
> So it won't go away in that case, but you shouldn't get any instability from
> that - from the VFS POV nothing nasty has happened, from the NFS client
> code POV... well, it's not being unmounted yet, as far as NFS code cares.
> Just a mounted fs from a stuck server...

OK :-)

Anyway, I am running this just before halting system , to prevent
suffering the hang when powering off my computer ;-)

Thanks!

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux