From owner-freebsd-fs@FreeBSD.ORG Sat May 19 05:58:30 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D580816A400 for ; Sat, 19 May 2007 05:58:30 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: from web63006.mail.re1.yahoo.com (web63006.mail.re1.yahoo.com [69.147.96.217]) by mx1.freebsd.org (Postfix) with SMTP id 72A6813C45A for ; Sat, 19 May 2007 05:58:30 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: (qmail 3524 invoked by uid 60001); 19 May 2007 05:58:26 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=PxSofQCRNEvHqWzEuWzS8kxSfUvKOQ1q3cWoehBCj7mUioiK58CARdKMc+1at9KLQRypZyYvgc+ZhBMd3lDHzfOD1i9QWVeK0OhzipnzX2iAdiNTI1GntqEibcCjlUzZEx4TR/gQHjOUK0ZbdMSV07ZcSPMbRQMvQv4K06rMjTA=; X-YMail-OSG: MBiqt6IVM1nw.DJuirLG6UbCc4SLkw584UH9pasnDnV1mAenUUY1Qp_Bfi8vefWZRb.mUQLwbPIZg4YPL1o6xkyMKZXmWeBXuRR0U.IevGI0yx9.RPIkokZzZ7lwUjwt Received: from [24.118.228.153] by web63006.mail.re1.yahoo.com via HTTP; Fri, 18 May 2007 22:58:26 PDT Date: Fri, 18 May 2007 22:58:26 -0700 (PDT) From: Gore Jarold To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <550589.3257.qm@web63006.mail.re1.yahoo.com> Subject: dangers of delaying an fsck on busy fileserver ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2007 05:58:30 -0000 I have a busy fileserver - 5-20 sftp/rsync processes running on it at all times. For unknown reasons, this server crashes in the middle of the night sometimes. When it does, I comment out my four big arrays in /etc/fstab, reboot, and fsck them manually (without a snapshot and BG fsck). Easy. The problem is, I need to sit around and wait for an fsck in the middle of the night and then re-edit fstab and reboot. So I am curious ... what happens if I instruct the NOC tech to just press the reset switch instead of calling me ? If he does this, the system will boot, the arrays will come online, and since I have a very very long time set until bg_fsck starts, I can then reboot the machine and foreground fsck it during sunlight hours. But it does mean that users will continue to operate on those dirty disks for 4-8 hours until I do that. Is this a dangerous strategy ? Does this put me at some increased risk of finding myself with disks that cannot be fsck'd ? (I've never seen it, but I have heard horror stories...) Will I lose a lot of the data that has been transacted during the hours that the disks were used in a dirty state ? Any comments ? ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367