From owner-freebsd-bugs@FreeBSD.ORG Wed Dec 28 13:40:11 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 158491065673 for ; Wed, 28 Dec 2011 13:40:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C8AFA8FC12 for ; Wed, 28 Dec 2011 13:40:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBSDeAwC000468 for ; Wed, 28 Dec 2011 13:40:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBSDeAA5000467; Wed, 28 Dec 2011 13:40:10 GMT (envelope-from gnats) Resent-Date: Wed, 28 Dec 2011 13:40:10 GMT Resent-Message-Id: <201112281340.pBSDeAA5000467@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Oleg Baranov Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70F3D1065670 for ; Wed, 28 Dec 2011 13:35:20 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 603258FC19 for ; Wed, 28 Dec 2011 13:35:20 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id pBSDZJq7000664 for ; Wed, 28 Dec 2011 13:35:19 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id pBSDZJTM000663; Wed, 28 Dec 2011 13:35:19 GMT (envelope-from nobody) Message-Id: <201112281335.pBSDZJTM000663@red.freebsd.org> Date: Wed, 28 Dec 2011 13:35:19 GMT From: Oleg Baranov To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: conf/163668: fstab 'failok' option has no effect on missing hard drive X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 13:40:11 -0000 >Number: 163668 >Category: conf >Synopsis: fstab 'failok' option has no effect on missing hard drive >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 28 13:40:10 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Oleg Baranov >Release: 8.2-STABLE, 9-STABLE >Organization: MARIS AS >Environment: FreeBSD 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #1: Wed Dec 28 16:59:09 MSK 2011 root@bsd-gw:/usr/obj/usr/src/sys/GENERIC amd64 >Description: System drops to Single mode on boot in case special device is missing even corresponding filesystem is marked as 'failok' in /etc/fstab. Thus server cannot boot becomes remotely unaccessible even if some unimportant drive is missing (or got corrupted and undetectable). fstab(5) documentation mentions: "If the option ``failok'' is specified, the system will ignore any error which happens during the mount of that filesystem, which would otherwise cause the system to drop into single user mode. " I fill this behavior as a bug suggesting a server must withstand minor failures as long as it can and definitely should not get rendered totally useles in case of some secondary (non-root in general) drive/filesystem fault. It should be up to server admin to define those 'secondary' filesystems. 'failok' option has been designed for this particular purpose as far as I understand. Part of boot log from a faulty system: ----------------------------- Starting file system checks: /dev/ada0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ada0p2: clean, 50085826 free (6626 frags, 6259900 blocks, 0.0% fragmentatio n) Mounting local file systems:mount: /dev/ufs/botva : No such file or directory >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: