From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 7 17:52:05 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C2121065674 for ; Thu, 7 Apr 2011 17:52:05 +0000 (UTC) (envelope-from cronfy@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1B9268FC14 for ; Thu, 7 Apr 2011 17:52:04 +0000 (UTC) Received: by gxk28 with SMTP id 28so1289811gxk.13 for ; Thu, 07 Apr 2011 10:52:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=glMhzIbYrV3cMlIMudsheGWpHFWFSeVNGWnXXGIoA78=; b=MV8mrIzDwl//VPYgL4VWefp7tP+96c23ZFo5ltkEwrqoBCx/qJ5Qpq7cIqaRwU4YOX g24RhUlGSitCgXv+I9QDAS4CsURL9MfzNcLZ7pvIN9JD1My9hLYK5PskxlMtgdJl3aJL MGuetub52hzfbhBTXdFGJQT3dZQiD/737bH0o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=lUTUtueiYdk+HVMP5qd4KyNGAA/zQlTCkvVdPzjuEQxlpvMZ3JyzbYHjLtT3/DSucG Hg3Q7hFxqqeSV0D0JB8tPo/wkLgRkt1Bf9JNolQ6K5QJg0qDtJ5SbQbNunerF33Xs8u+ fMVyq2gfXp2q8cbB6s0EnOekToz0eJzqY5oxA= Received: by 10.91.126.14 with SMTP id d14mr1048144agn.58.1302197208073; Thu, 07 Apr 2011 10:26:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.90.67.6 with HTTP; Thu, 7 Apr 2011 10:26:18 -0700 (PDT) From: cronfy Date: Thu, 7 Apr 2011 21:26:18 +0400 Message-ID: To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: call boot(0) from DDB to avoid filesystem corruption X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2011 17:52:05 -0000 Hello! I am trying to find a way to avoid filesystem corruption after system crashes. I am using FreeBSD 7.3 with DDB enabled. Sometimes system freezes and only DDB (via CTRL-ALT-ESC) is available. Documentation says there is 'call boot(0)' function that performs graceful shutdown from DDB. To test it, I set up fresh install of FreeBSD 7.3 on a new server. Then I started background 'tar -zxf ports.tar.gz' on all partitions: /home, /usr, /var, /tmp and finally /. Waited ~30 seconds and pressed CTRL-ALT-ESC -> call boot(0) -> Enter. Unfortunately, DDB freezed on syncing bufdaemon. I had been waiting for ~5 minutes, but system freezed completely: I could not drop to DDB anymore and keyboard was not working. I had to restart by reset. What can be the reason of this last system freeze? I am using Adaptec controller 3405 with FreeBSD's driver, can it be the cause? I do not know indeed how to ask a good question about this situation because I have no more ideas. Any help would be appreciated! -- cronfy