Date: Tue, 26 Jun 2012 22:31:54 -0400 From: Robert Simmons <rsimmons0@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: Freeze when running freebsd-update Message-ID: <CA%2BQLa9B8o9Y81P%2BGFzAfBG2d8q7dNoJLravooZowcJcT%2B=QdRw@mail.gmail.com> In-Reply-To: <20120627005428.298430@gmx.com> References: <20120627005428.298430@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 26, 2012 at 8:54 PM, Dieter BSD <dieterbsd@engineer.com> wrote: > Robert writes: >> 3) the box is responsive to hitting enter at the console (it produces >> another login: prompt) > > Getty is in memory and can run. > >> 5) if I try to login to the console, it lets me enter a username then >> locks up totally, it does not present me with a password: prompt. > > Login(1) is not in memory, and the kernel cannot read it from disk > for some reason. > > I can get this symptom by writing a large file to a disk on a > controller that FreeBSD doesn't support NCQ on. I assume there > is a logjam in the buffer cache. Something trivial like reading > login in from disk that would normally happen in well under a > second can take many minutes. > > Perhaps geli is causing a similar logjam? Does it hang forever or > is it just obscenely slow? If it truely hangs forever it is > probably something else. Is there disk activity after it hangs? > Can you try it without geli? systat -vmstat might provide a clue. Well, it is geli. I'm unable to reproduce the freeze on the same exact system with everything else the same except for no geli. I'm going to move this thread over to geom, and continue it there. Thanks for your help!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BQLa9B8o9Y81P%2BGFzAfBG2d8q7dNoJLravooZowcJcT%2B=QdRw>