Date: Wed, 10 Aug 2011 17:43:09 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: "Ian Downes" <ian@ndwns.net> Cc: freebsd-jail@freebsd.org Subject: Re: umounting md backed jail filesystems - busy Message-ID: <629ADCE73AB740D1A24CF9327449234C@multiplay.co.uk> References: <20110810021750.GA83262@weta.stanford.edu> <CAPd55qAZ70OORvqe7RrKGKMaKworgoZsEa38-d=OwVbnvgC9zA@mail.gmail.com> <20110810160047.GA74133@weta.stanford.edu> <EF80C7EA91CE45D3B3EDE9DDB5CB9EB5@multiplay.co.uk> <20110810163600.GA77840@weta.stanford.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----
From: "Ian Downes" <ian@ndwns.net>
> Thanks, indeed jls -d does show the jail as in the process of dying. I
> watched jls -d and (unscientifically) as soon as jls -d reported the jail was
> completely dead I was able to umount and destroy the filesystem.
>
> I hadn't expected it to take a minute or more for a jail to die. Is this usual?
> Can anyone suggest what may be causing this? Perhaps a network related timeout?
Yes its very likely a network timeout. You can either track down the app which
is not closing properly or you could try reducing the tcp timeout via the sysctl:-
net.inet.tcp.msl
Be aware that changing this does technically break the RFC.
Regards
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?629ADCE73AB740D1A24CF9327449234C>