Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 113448 - shutdown fails if client has a nfs-mount and server is not available
Summary: shutdown fails if client has a nfs-mount and server is not available
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-24 03:43 UTC by rumzajs
Modified: 2005-11-25 01:01 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rumzajs 2005-11-24 03:43:43 UTC
the client has a nfs share, the server is not more available, the client gone    
hang at shutdown :    
    
* Failed to simply unmount filesystems    
*     Unmounting network filesystems (retry #1) ...   
   
i have wait here 5 min but nothing happend so i try press ESC, ENTER,   
[Ctrl+Alt+ENTF] to force it, no success, i have to cold-reset the box :/   
   
   
Gentoo Base System version 1.12.0_pre10  
Portage 2.0.53_rc7 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r3,  
2.6.14-reiser4-r2 i686)  
=================================================================  
System uname: 2.6.14-reiser4-r2 i686 AMD Athlon(TM) XP 2500+  
ccache version 2.4 [enabled]  
dev-lang/python:     2.4.2  
sys-apps/sandbox:    1.2.13  
sys-devel/autoconf:  2.13, 2.59-r7  
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1  
sys-devel/binutils:  2.16.1  
sys-devel/libtool:   1.5.20-r1  
virtual/os-headers:  2.6.11-r3  
ACCEPT_KEYWORDS="x86 ~x86"  
AUTOCLEAN="yes"  
CBUILD="i686-pc-linux-gnu"  
CFLAGS="-march=athlon-xp -pipe -O2 -fomit-frame-pointer"  
CHOST="i686-pc-linux-gnu"  
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"  
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"  
CXXFLAGS="-march=athlon-xp -pipe -O2 -fomit-frame-pointer"  
DISTDIR="/portage/distfiles"  
FEATURES="autoconfig ccache distlocks sandbox sfperms strict"  
GENTOO_MIRRORS="*cut*"  
LANG="de_DE@euro"  
LINGUAS="de"  
MAKEOPTS="-j2"  
PKGDIR="/usr/portage/packages"  
PORTAGE_TMPDIR="/var/tmp"  
PORTDIR="/portage"  
PORTDIR_OVERLAY="/usr/local/portage"  
SYNC="rsync://rsync.gentoo.org/gentoo-portage"  
USE="x86 3dnow 3dnowext X alsa apm arts audiofile avi berkdb bitmap-fonts bzip2  
cdr crypt cups curl dvd eds emboss encode esd ethereal exif expat fam ffmpeg  
flac foomaticdb fortran gdbm gif glut gphoto2 gpm gstreamer gtk2 hal idn  
imagemagick imap imlib ipv6 java jpeg kde lcms libg++ libwww mad mbox mikmod  
mng motif mp3 mpeg ncurses nls nptl nptlonly ogg oggvorbis opengl oss pam pcre  
pdflib perl png python qt quicktime readline scanner sdl spell ssl svga tcpd  
tiff truetype truetype-fonts type1-fonts udev usb userlocales vorbis xine xml2  
xmms xv xvid zlib linguas_de userland_GNU kernel_linux elibc_glibc"  
Unset:  ASFLAGS, CTARGET, LC_ALL, LDFLAGS
Comment 1 SpanKY gentoo-dev 2005-11-24 12:15:14 UTC
thats probably because of the options you used to mount the nfs file system ...

i dont know how much we should really try to compensate for this ...
Comment 2 rumzajs 2005-11-24 21:45:36 UTC
/etc/fstab   
mbox:/home      /mnt/mbox/home  nfs   noauto    
    
then mounted it with : mount mbox:/home   
   
the source of the procedure at the unmount point :  
   * Failed to simply unmount filesystems      
   *     Unmounting network filesystems (retry #1) ...  
should be checked cause its looks like it was stuck there, (loop hangs same 
where ?) 
maybe ask the user : Ignore and continue without unmouting the nfs (Y/N) ?, and 
count a timer 0:59..., after 'Y' pressed or timer reach 0:00 continue the 
shutdown, to make sure the box gone get pass this point and get 
shutdowned/restared 
Comment 3 SpanKY gentoo-dev 2005-11-24 23:20:26 UTC
it isnt a matter of the init scripts getting hung up, the `umount` call itself
gets hung up in the kernel and with the options you specified to mount the nfs
drive, there isnt anyway to kill it until the nfs server starts responding again

the only thing we could do would be to fork all the calls to `umount` and then
do some sleeps and see if the process exited yet

all in all, kind of ugly
Comment 4 rumzajs 2005-11-25 01:01:09 UTC
ok i have take a look at the avaible nfs mount options and found a solution  
  
option "soft"  
  
This option allows the kernel to time out if the nfs  server  is  
not  responding  for  some  time. The time can be specified with  
timeo=time.  This option might be  useful  if  your  nfs  server  
sometimes doesn't respond or will be rebooted while some process  
tries to get a file from the server.   Usually  it  just  causes  
lots of trouble  
  
thx for point me to the mount options 
 
Solved