Date: 01 Feb 2006 09:53:28 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Frank Staals <frankstaals@gmx.net> Cc: questions@FreeBSD.org Subject: Re: Weird behaviour 'umount' on NFS disk Message-ID: <448xsvjfkn.fsf@be-well.ilk.org> In-Reply-To: <43DF8392.7000204@gmx.net> References: <43DF8392.7000204@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Frank Staals <frankstaals@gmx.net> writes: > Hey, > > Usually I work at my laptop, if I'm at home I can mount some > directories from my server so I can also access those files and I > don't have to ftp them. For the mounting I use this script : > > frank@Riza$ cat /usr/local/bin/nfsmount > #!/bin/sh > > srv="192.168.2.1" > > if [ "$1" = "-wlan" ]; then > srv="192.168.5.1" > fi > > echo "Mounting home/net/var->/mnt/var , home->/mnt/server and > home/net/server->/mnt/series from $srv" > mount $srv:/home/net/var/ /mnt/var/ > mount $srv:/home/ /mnt/server/ > mount $srv:/home/net/series/ /mnt/series/ > frank@Riza$ > > The IP adres of my server is 192.168.2.1 when using LAN and it is > accessable at 192.168.5.1 using WLAN. It is set up allowing mounts > from my laptop using LAN as well as WLAN. This works perfectly. > > For unmounting the three NFS-mounts I use an other script which is > just three times an 'umount' : > > #!/bin/sh > > umount /mnt/server > umount /mnt/series > umount /mnt/var > > df -m > echo "/mnt/server , /mnt/series and /mnt/var unmounted" > > > frank@Riza$ > > Up until a week ago this worked fine. I could mount and unmount the > directories without any problems. But then a weird error occured. When > I tried unmounting them. The umount command hangs when trying to > unmount a disk but when I cancel the umount ( with Ctrl + c ) df > shows that the disk is unmounted. It just won't give me a prompt > again. The same thing happens when I try to unmount them manually. I > can unmount a disk, but it just stops. To clear things up: > > root@Riza# df Filesystem 1K-blocks Used > Avail Capacity Mounted on > /dev/ad0s1a 4058062 3450302 283116 92% / > devfs 1 1 0 100% /dev > /dev/ad0s1d 33524236 23047782 7794516 75% /home > 192.168.2.1:/home/net/var 75685352 57816262 11814262 83% /mnt/var > 192.168.2.1:/home 52195402 29726280 18293490 62% > /mnt/server > 192.168.2.1:/home/net/series 151368706 128022780 11236430 92% > /mnt/series > root@Riza# umount /mnt/server/ > ^C > root@Riza# df > Filesystem 1K-blocks Used Avail Capacity > Mounted on > /dev/ad0s1a 4058062 3450302 283116 92% / > devfs 1 1 0 100% /dev > /dev/ad0s1d 33524236 23047782 7794516 75% /home > 192.168.2.1:/home/net/var 75685352 57816262 11814262 83% /mnt/var > 192.168.2.1:/home/net/series 151368706 128022780 11236430 92% > /mnt/series > root@Riza# > > This is quite annoying since I can't use my script to unmount the > disks anymore. I didnt' change anything to my mounts ( /etc/fstab ) > and unmounting a DVD doesn't give any problems. The only thing I can > see has changed is that at boot the system hangs at: > > Mounting NFS file systems: > NFS access cache time=2 > > and I have to ctrl + c it to continue booting, this only happend > before when I hadn't any network connection. But mounting the > nfs-disks using my script did work. > > Anyone an Idea what I can do to fix this ? Running FreeBSD 7.0-Current > by the way. Well, try "umount -f" and trace the process to see where it's hanging. But this sounds kind of familiar from the -CURRENT list; you really should keep track of that list if you're going to run -CURRENT.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448xsvjfkn.fsf>