From owner-freebsd-questions@FreeBSD.ORG Sat Aug 18 02:44:19 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C9B57106566B for ; Sat, 18 Aug 2012 02:44:19 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) by mx1.freebsd.org (Postfix) with ESMTP id 70FB78FC0A for ; Sat, 18 Aug 2012 02:44:19 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id q7I2iC4d004498; Fri, 17 Aug 2012 20:44:12 -0600 (MDT) (envelope-from freebsd@dreamchaser.org) Message-ID: <502F017A.7030001@dreamchaser.org> Date: Fri, 17 Aug 2012 20:44:10 -0600 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120609 Thunderbird/13.0 MIME-Version: 1.0 To: Polytropon References: <502EA73B.6000008@dreamchaser.org> <20120818030537.4d5bf55b.freebsd@edvax.de> In-Reply-To: <20120818030537.4d5bf55b.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Fri, 17 Aug 2012 20:44:12 -0600 (MDT) Cc: FreeBSD Mailing List Subject: Re: fsck recoveries, configuration X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@dreamchaser.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2012 02:44:19 -0000 On 08/17/12 19:05, Polytropon wrote: >> 2. When my machine hung (could not rlogin or ping), I powered >> off and rebooted. > > Does the machine have a "soft power button" and it is configured > to issue a "shutdown -p now" (which is quite common)? When you > have access to the machine, try that. Even if the machine does > not accept network logins, this mechanism might still work. Hmmm. It has a "soft" power button; have to hold it down 5 sec or so to power off. Those things can be configured to issue a command that will actually get executed without a login? I assume you're talking about a bios option? How does that work? sounds like magic of some sort... Or is this a whole login sequence with the shutdown at the end? >> Reboot did a deferred fsck. > > Is this intended? Personally, I'd rather wait some time to boot > in a fully checked file system environment then dealing with the > uncertain situation of snapshots and background FS check activity. > In worst case, I want to be prompted by fsck if a major defect has > been found that requires administrator attention. > > Put > > background_fsck="NO" > > into /etc/rc.conf to get this behaviour. Yeah, I came to that conclusion... Thanks. >> After it booted I logged in, and also logged in on another system. >> On the remote system I could do a ping but rlogin returned >> "connection reset by peer", even though I could log in locally. > > Does rlogin work when you "give the system some time to recover"? yes, if it's not hung -- i.e. done with fsck, I think. I verified that by monitoring the delayed fsck process and as soon as it was done the rlogin worked. >> I then attempted to switch consoles using >> fn >> but could not. > > That would imply you're still stuck in SUM. A strange constellation > given that it appears that you have fsck running in background. > It seems to me this is always the case -- delayed fsck waits 60 seconds by default to start. During that time the system has come up multi-user, so it's trivial to be logged in under multi-user mode with fsck running.