From owner-freebsd-fs@FreeBSD.ORG Sun Mar 29 09:14:30 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3744B1065670; Sun, 29 Mar 2009 09:14:30 +0000 (UTC) (envelope-from kib@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0D2658FC0A; Sun, 29 Mar 2009 09:14:30 +0000 (UTC) (envelope-from kib@FreeBSD.org) Received: from freefall.freebsd.org (kib@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2T9EToW019368; Sun, 29 Mar 2009 09:14:29 GMT (envelope-from kib@freefall.freebsd.org) Received: (from kib@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2T9ETCc019364; Sun, 29 Mar 2009 09:14:29 GMT (envelope-from kib) Date: Sun, 29 Mar 2009 09:14:29 GMT Message-Id: <200903290914.n2T9ETCc019364@freefall.freebsd.org> To: peter@holm.cc, kib@FreeBSD.org, freebsd-fs@FreeBSD.org From: kib@FreeBSD.org Cc: Subject: Re: kern/72424: panic: ffs_blkfree: freeing free block in ffs/ffs_alloc.c:1750 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: Sun, 29 Mar 2009 09:14:30 -0000 Synopsis: panic: ffs_blkfree: freeing free block in ffs/ffs_alloc.c:1750 State-Changed-From-To: open->closed State-Changed-By: kib State-Changed-When: Sun Mar 29 09:13:11 UTC 2009 State-Changed-Why: Several bugs that could cause this issue were fixed since 6.0-CURRENT. Peter' stress2 suite does not reproduce "freeing free blocks" now, at least not that I know about this. http://www.freebsd.org/cgi/query-pr.cgi?pr=72424 From owner-freebsd-fs@FreeBSD.ORG Sun Mar 29 09:20:13 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B31D71065670; Sun, 29 Mar 2009 09:20:13 +0000 (UTC) (envelope-from kib@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 88B9A8FC0A; Sun, 29 Mar 2009 09:20:13 +0000 (UTC) (envelope-from kib@FreeBSD.org) Received: from freefall.freebsd.org (kib@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2T9KD0W020746; Sun, 29 Mar 2009 09:20:13 GMT (envelope-from kib@freefall.freebsd.org) Received: (from kib@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2T9KD3a020712; Sun, 29 Mar 2009 09:20:13 GMT (envelope-from kib) Date: Sun, 29 Mar 2009 09:20:13 GMT Message-Id: <200903290920.n2T9KD3a020712@freefall.freebsd.org> To: sebastian.ssmoller@gmx.net, kib@FreeBSD.org, freebsd-fs@FreeBSD.org From: kib@FreeBSD.org Cc: Subject: Re: kern/62824: [panic] softdep_setup_inomapdep: found inode [5.2-CURRENT] 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: Sun, 29 Mar 2009 09:20:14 -0000 Synopsis: [panic] softdep_setup_inomapdep: found inode [5.2-CURRENT] State-Changed-From-To: open->closed State-Changed-By: kib State-Changed-When: Sun Mar 29 09:19:17 UTC 2009 State-Changed-Why: I believe one known reason for this panic was fixed. Other then that, the problem was not reported at all recently (as in 2-3 years at least). http://www.freebsd.org/cgi/query-pr.cgi?pr=62824 From owner-freebsd-fs@FreeBSD.ORG Sun Mar 29 23:52:09 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF373106566B for ; Sun, 29 Mar 2009 23:52:09 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from mail.jrv.org (adsl-70-243-84-9.dsl.austtx.swbell.net [70.243.84.9]) by mx1.freebsd.org (Postfix) with ESMTP id 81FFD8FC15 for ; Sun, 29 Mar 2009 23:52:09 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.3/8.14.3) with ESMTP id n2TNptQg006073 for ; Sun, 29 Mar 2009 18:51:55 -0500 (CDT) (envelope-from james-freebsd-fs2@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-fs2@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: content-type:content-transfer-encoding; b=j/Jb2dGIfNYvD7lZkvkKiVVuZ6Uu/OqRiTYzhwC82smhzg3qqdI8eWbWc+ZZpEfVf kvN1H36dk/idoOxeOkod9U6WfjmF2ClgYbRI4ZuKF+KQgDUvNVzLegIGWY1RjBW3Ygd m8yFmxBSCzPqEYAiEAlFDwPhyzeK/Nkc6fz0BDE= Message-ID: <49D0099B.2040807@jrv.org> Date: Sun, 29 Mar 2009 18:51:55 -0500 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: ZFS & USB disks? 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: Sun, 29 Mar 2009 23:52:10 -0000 uname -a: FreeBSD bigtex.housenet.jrv 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r189099: Fri Feb 27 07:09:47 CST 2009 james@bigtex.housenet.jrv:/usr/obj/usr/src/sys/GENERIC amd64 This build is from before the recent USB changes. Is it safe to use ZFS with USB disk drives? The kernel output suggests "SYNCHRONIZE_CACHE" isn't supported. Does this cause a write-ordering problem for ZFS? Upon attaching a drive with a pool created on a Mac: kernel: vdev_geom_attach:112[1]: Attaching to da4. kernel: vdev_geom_attach:153[1]: Created consumer for da4. kernel: (da4:umass-sim0:0:0:1): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 kernel: (da4:umass-sim0:0:0:1): CAM Status: SCSI Status Error kernel: (da4:umass-sim0:0:0:1): SCSI Status: Check Condition kernel: (da4:umass-sim0:0:0:1): ILLEGAL REQUEST asc:20,0 kernel: (da4:umass-sim0:0:0:1): Invalid command operation code kernel: (da4:umass-sim0:0:0:1): (da4:umass-sim0:0:0:1): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 kernel: (da4:umass-sim0:0:0:1): ILLEGAL REQUEST asc:20,0 kernel: (da4:umass-sim0:0:0:1): Invalid command operation code kernel: Unretryable error kernel: (da4:umass-sim0:0:0:1): error 22 kernel: (da4:umass-sim0:0:0:1): Unretryable Error From owner-freebsd-fs@FreeBSD.ORG Mon Mar 30 00:12:05 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72022106564A; Mon, 30 Mar 2009 00:12:05 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 471808FC08; Mon, 30 Mar 2009 00:12:05 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2U0C4xU037976; Mon, 30 Mar 2009 00:12:04 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2U0C4Cu037972; Mon, 30 Mar 2009 00:12:04 GMT (envelope-from linimon) Date: Mon, 30 Mar 2009 00:12:04 GMT Message-Id: <200903300012.n2U0C4Cu037972@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/133174: [patch] msdosfs must support utf-encoded international characters in filr names 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: Mon, 30 Mar 2009 00:12:05 -0000 Old Synopsis: msdosfs must support utf-encoded international characters in filr names New Synopsis: [patch] msdosfs must support utf-encoded international characters in filr names Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 30 00:11:27 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). Apparently there is a patch at the supplied URL. http://www.freebsd.org/cgi/query-pr.cgi?pr=133174 From owner-freebsd-fs@FreeBSD.ORG Mon Mar 30 00:51:46 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 953C9106566B; Mon, 30 Mar 2009 00:51:46 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6B14B8FC0A; Mon, 30 Mar 2009 00:51:46 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2U0pkSh092222; Mon, 30 Mar 2009 00:51:46 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2U0pk0t092212; Mon, 30 Mar 2009 00:51:46 GMT (envelope-from linimon) Date: Mon, 30 Mar 2009 00:51:46 GMT Message-Id: <200903300051.n2U0pk0t092212@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/133150: [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while writing data 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: Mon, 30 Mar 2009 00:51:47 -0000 Old Synopsis: Page fault with ZFS on 7.1-RELEASE/amd64 while writing data New Synopsis: [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while writing data Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 30 00:51:20 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=133150 From owner-freebsd-fs@FreeBSD.ORG Mon Mar 30 11:06:52 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15E031065679 for ; Mon, 30 Mar 2009 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 01D738FC32 for ; Mon, 30 Mar 2009 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2UB6pDf054725 for ; Mon, 30 Mar 2009 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2UB6p8k054721 for freebsd-fs@FreeBSD.org; Mon, 30 Mar 2009 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Mar 2009 11:06:51 GMT Message-Id: <200903301106.n2UB6p8k054721@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org 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: Mon, 30 Mar 2009 11:06:53 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int o kern/133150 fs [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while w o kern/133134 fs [zfs] Missing ZFS zpool labels o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132597 fs [tmpfs] [panic] tmpfs-related panic while interrupting o kern/132551 fs [zfs] ZFS locks up on extattr_list_link syscall o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132337 fs [zfs] [panic] kernel panic in zfs_fuid_create_cred o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132145 fs [panic] File System Hard Crashes f kern/132068 fs [zfs] page fault when using ZFS over NFS on 7.1-RELEAS o kern/131995 fs [nfs] Failure to mount NFSv4 server o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/131086 fs [ext2fs] mkfs.ext2 creates rotten partition o kern/131084 fs [xfs] xfs destroys itself after copying data o kern/131081 fs [zfs] User cannot delete a file when a ZFS dataset is o kern/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o bin/130105 fs [zfs] zfs send -R dumps core o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129174 fs [nfs] [zfs] [panic] NFS v3 Panic when under high load o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs] [panic] changing into .zfs dir from nfs client c f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o bin/118249 fs mv(1): moving a directory changes its mtime o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94480 fs [libufs] [patch] bread(3) & bwrite(3) can crash under o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/89991 fs [ufs] softupdates with mount -ur causes fs UNREFS o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc 57 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Mar 30 14:04:22 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 130ED1065670 for ; Mon, 30 Mar 2009 14:04:22 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.9]) by mx1.freebsd.org (Postfix) with ESMTP id BC2D48FC30 for ; Mon, 30 Mar 2009 14:04:21 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail01.m-online.net (mail.m-online.net [192.168.3.149]) by mail-out.m-online.net (Postfix) with ESMTP id B551A1C14E7C; Mon, 30 Mar 2009 15:51:53 +0200 (CEST) Received: from localhost (dynscan2.mnet-online.de [192.168.1.215]) by mail.m-online.net (Postfix) with ESMTP id E2AD19002E; Mon, 30 Mar 2009 15:48:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at mnet-online.de Received: from mail.mnet-online.de ([192.168.3.149]) by localhost (dynscan2.mnet-online.de [192.168.1.215]) (amavisd-new, port 10024) with ESMTP id r4iaNfGN9FQp; Mon, 30 Mar 2009 15:48:57 +0200 (CEST) Received: from mail.reifenberger.com (ppp-93-104-38-175.dynamic.mnet-online.de [93.104.38.175]) by mail.mnet-online.de (Postfix) with ESMTP; Mon, 30 Mar 2009 15:48:57 +0200 (CEST) Received: by mail.reifenberger.com (Postfix, from userid 1001) id 6049932BFC; Mon, 30 Mar 2009 15:48:57 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.reifenberger.com (Postfix) with ESMTP id 57D7F32BF9; Mon, 30 Mar 2009 15:48:57 +0200 (CEST) Date: Mon, 30 Mar 2009 15:48:57 +0200 (CEST) From: Michael Reifenberger To: pjd@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: freebsd-fs@freebsd.org Subject: PR kern/133020 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: Mon, 30 Mar 2009 14:04:23 -0000 Hi, your patch from the PR helped me. Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com From owner-freebsd-fs@FreeBSD.ORG Tue Mar 31 13:00:06 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1647106567E for ; Tue, 31 Mar 2009 13:00:05 +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 D45F28FC08 for ; Tue, 31 Mar 2009 13:00:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2VD056I094650 for ; Tue, 31 Mar 2009 13:00:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2VD05gj094642; Tue, 31 Mar 2009 13:00:05 GMT (envelope-from gnats) Date: Tue, 31 Mar 2009 13:00:05 GMT Message-Id: <200903311300.n2VD05gj094642@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Ivan Voras Cc: Subject: Re: kern/133150: [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while writing data X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ivan Voras List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 13:00:07 -0000 The following reply was made to PR kern/133150; it has been noted by GNATS. From: Ivan Voras To: bug-followup@freebsd.org, jeffb.misc@gmail.com Cc: Subject: Re: kern/133150: [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while writing data Date: Tue, 31 Mar 2009 14:36:57 +0200 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD3FE5A75095A05DBB713766A Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Can you try to repeat the error on 8-CURRENT? --------------enigD3FE5A75095A05DBB713766A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ0g5qldnAQVacBcgRAmiAAJsE1J8Vl1LKC1UztG+9/makz+jgjQCdE4eQ ZjnZc+qdI23Q7vdqKdfSedI= =DM3u -----END PGP SIGNATURE----- --------------enigD3FE5A75095A05DBB713766A-- From owner-freebsd-fs@FreeBSD.ORG Tue Mar 31 20:16:26 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60DC31065688 for ; Tue, 31 Mar 2009 20:16:26 +0000 (UTC) (envelope-from brampton@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mx1.freebsd.org (Postfix) with ESMTP id E906B8FC13 for ; Tue, 31 Mar 2009 20:16:25 +0000 (UTC) (envelope-from brampton@gmail.com) Received: by ey-out-2122.google.com with SMTP id 4so544310eyf.7 for ; Tue, 31 Mar 2009 13:16:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=95I9zcWU/k3xhKV22CxREYtR+19AFe8WbxmhQZT5x2k=; b=RH90yM3QfTQetFapTzgtVKESCIv/RG85yx7LNPwckyFIiHg51cu/zoPqIM5VKm0w6j NFk4CAtmoWf91R1C3YQZEcs8ExEsEYXJROoN36A5RVWZqWE//dhu676YH8IjC0pbbwEJ FVMWISG2GFq0DtzopWscnvEZlmlVEgL3YQrR0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=AMf+LTpnAhffQstl6huyunCLA408aVYvNFZxyEOr9PvHRPknkARgngkrtzVRA0rEyw B3EH31PZJUU3cdU7h4T91+IhWcAZ3WWp4G6b+LkTRi2jT2XTR3kbKXaQ1Lz5g3P6plPf El39t0H7OTShJPkhuAi2y6A3JI/N0+ZaugHQw= MIME-Version: 1.0 Sender: brampton@gmail.com Received: by 10.210.38.5 with SMTP id l5mr5314209ebl.2.1238529340268; Tue, 31 Mar 2009 12:55:40 -0700 (PDT) Date: Tue, 31 Mar 2009 20:55:40 +0100 X-Google-Sender-Auth: 8193f6498a5adf0c Message-ID: From: Andrew Brampton To: freebsd-fs Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Auto mount and ignore errors 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: Tue, 31 Mar 2009 20:16:27 -0000 Hi, Recently my server hung on a reboot because it was unable to fsck a ext2 file system. This was because I didn't have the ext2 fsck tool installed (I do now). The partition in question was however not important, yet I listed it as "auto" in fstab. I would have preferred if my server noticed the problem, failed to mount it and just continue booting as normal. I tried the "late" option in the fstab but that just seem to hang the server later in the boot. So my question is, is there a fstab option which will ignore a failed mount, and if possible continue to boot? I've read the man page, and did a bit of googling, but didn't find anything. Would there be any objection to a patch which implemented a "ignerror" flag? thanks Andrew From owner-freebsd-fs@FreeBSD.ORG Tue Mar 31 22:32:23 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DFE010656C6; Tue, 31 Mar 2009 22:32:23 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D72428FC15; Tue, 31 Mar 2009 22:32:22 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2VMWMFd074737; Tue, 31 Mar 2009 22:32:22 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2VMWMOC074733; Tue, 31 Mar 2009 22:32:22 GMT (envelope-from linimon) Date: Tue, 31 Mar 2009 22:32:22 GMT Message-Id: <200903312232.n2VMWMOC074733@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/133251: [xfs] xfs write Input/output error crash kernel: xfs_iunpin: REC RECABLE ip 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: Tue, 31 Mar 2009 22:32:23 -0000 Synopsis: [xfs] xfs write Input/output error crash kernel: xfs_iunpin: REC RECABLE ip Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Mar 31 22:32:12 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=133251 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 31 23:15:50 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C86981065672; Tue, 31 Mar 2009 23:15:50 +0000 (UTC) (envelope-from kan@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9DDBF8FC20; Tue, 31 Mar 2009 23:15:50 +0000 (UTC) (envelope-from kan@FreeBSD.org) Received: from freefall.freebsd.org (kan@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2VNFo5K028222; Tue, 31 Mar 2009 23:15:50 GMT (envelope-from kan@freefall.freebsd.org) Received: (from kan@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2VNFoq0028218; Tue, 31 Mar 2009 23:15:50 GMT (envelope-from kan) Date: Tue, 31 Mar 2009 23:15:50 GMT Message-Id: <200903312315.n2VNFoq0028218@freefall.freebsd.org> To: thiemel@centrum.cz, kan@FreeBSD.org, freebsd-fs@FreeBSD.org From: kan@FreeBSD.org Cc: Subject: Re: kern/133251: [xfs] xfs write Input/output error crash kernel: xfs_iunpin: REC RECABLE ip 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: Tue, 31 Mar 2009 23:15:51 -0000 Synopsis: [xfs] xfs write Input/output error crash kernel: xfs_iunpin: REC RECABLE ip State-Changed-From-To: open->closed State-Changed-By: kan State-Changed-When: Tue Mar 31 23:14:29 UTC 2009 State-Changed-Why: XFS write support was never released or supported and you should not be trying to use it. http://www.freebsd.org/cgi/query-pr.cgi?pr=133251 From owner-freebsd-fs@FreeBSD.ORG Wed Apr 1 05:24:49 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BE3410658DF for ; Wed, 1 Apr 2009 05:24:49 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from sorbesgroup.com (mail.sorbesgroup.com [217.159.241.118]) by mx1.freebsd.org (Postfix) with ESMTP id C02278FC0A for ; Wed, 1 Apr 2009 05:24:48 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from localhost (localhost.localdomain [127.0.0.1]) by sorbesgroup.com (Postfix) with ESMTP id 228283C52021 for ; Wed, 1 Apr 2009 07:26:28 +0300 (EEST) Received: from sorbesgroup.com ([127.0.0.1]) by localhost (sorbesgroup.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21904-09 for ; Wed, 1 Apr 2009 07:26:25 +0300 (EEST) Received: from [192.168.0.80] (andrei [192.168.0.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sorbesgroup.com (Postfix) with ESMTP id 4F2FB3C5202D for ; Wed, 1 Apr 2009 07:26:25 +0300 (EEST) Message-ID: <49D2F2DE.1090807@bsd.ee> Date: Wed, 01 Apr 2009 07:51:42 +0300 From: Andrei Kolu User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at localhost Subject: Re: Auto mount and ignore errors 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: Wed, 01 Apr 2009 05:24:53 -0000 Andrew Brampton wrote: > So my question is, is there a fstab option which will ignore a failed > mount, and if possible continue to boot? I've read the man page, and > did a bit of googling, but didn't find anything. Would there be any > objection to a patch which implemented a "ignerror" flag? > > Mount from /etc/rc.local? From owner-freebsd-fs@FreeBSD.ORG Wed Apr 1 14:32:44 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1BFB1065670 for ; Wed, 1 Apr 2009 14:32:44 +0000 (UTC) (envelope-from brampton@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id 73BF28FC19 for ; Wed, 1 Apr 2009 14:32:44 +0000 (UTC) (envelope-from brampton@gmail.com) Received: by ey-out-2122.google.com with SMTP id 4so14521eyf.7 for ; Wed, 01 Apr 2009 07:32:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=KRC+4mNM+pke4CPDbePk6PKPgzP51LvflMer+J/d0xo=; b=wM8OE+QhMV+GxnRR5t6G/+LFAOtVWzgOF4qYCf6PeprBXdKHY0JzaNRdP+ooiqJccq +VsByTuqgjrKF+Po9fY0u/f/rvYJxtE7ybV5CNP88I+wdh/01/2PGzX+5vqwO98wNIJR qSWSWqp2u24zbXTPxF3A4cZSy55u03TMbJQGY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=aKe2H+E27HiMpCfJlzYxRMuS8a3nL+YoIVnrO1Mj3HtdtQa0ZQrF2J/r6ysG12jmaa d66QoKcWAeqAWw7uqdg/psPQOKZjFFRn5LfV4XxELFc9D/jNSGvvwRtD/R561kSz4Xg4 PjrGZ6XWgRRt5othNk12b6ygov/1VfVWmGCNk= MIME-Version: 1.0 Sender: brampton@gmail.com Received: by 10.210.67.4 with SMTP id p4mr6032885eba.18.1238596363559; Wed, 01 Apr 2009 07:32:43 -0700 (PDT) In-Reply-To: <49D2F2DE.1090807@bsd.ee> References: <49D2F2DE.1090807@bsd.ee> Date: Wed, 1 Apr 2009 15:32:42 +0100 X-Google-Sender-Auth: b76a6ba38c1fe948 Message-ID: From: Andrew Brampton To: Andrei Kolu Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Auto mount and ignore errors 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: Wed, 01 Apr 2009 14:32:45 -0000 2009/4/1 Andrei Kolu : > Andrew Brampton wrote: >> >> So my question is, is there a fstab option which will ignore a failed >> mount, and if possible continue to boot? I've read the man page, and >> did a bit of googling, but didn't find anything. Would there be any >> objection to a patch which implemented a "ignerror" flag? >> >> > > Mount from /etc/rc.local? > You mean create my own script for the mounting? Sure that would work but I don't see that as "clean" as placing it in fstab. Andrew From owner-freebsd-fs@FreeBSD.ORG Wed Apr 1 17:43:30 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94469106566B for ; Wed, 1 Apr 2009 17:43:30 +0000 (UTC) (envelope-from aaron@goflexitllc.com) Received: from mail.goflexitllc.com (mail.goflexitllc.com [70.38.81.12]) by mx1.freebsd.org (Postfix) with ESMTP id 33EAB8FC22 for ; Wed, 1 Apr 2009 17:43:29 +0000 (UTC) (envelope-from aaron@goflexitllc.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=goflexitllc.com; h=message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type; s=gamma; bh=mV6pkE9v9A5av12Ydg3TrEQB0 1w=; b=NS/qaVw5+v3utNLcy7ijE6575jhNXGslb7+qeogz7ckqAKWYdtiAc9n7S JyZl01hourIo71uBtfALpCNx0+fhd0TV24yVAtFplrxOs5OItoVuTvyZt4PuEj+A xx7+6AI DomainKey-Signature: a=rsa-sha1; c=nofws; d=goflexitllc.com; h=message-id :date:from:mime-version:to:subject:references:in-reply-to: content-type; q=dns; s=gamma; b=CIeFY0iE8nkU3lecJOYfgwORY/LPD8HY RlbOYn/ZA15tFoqoiSfR+sBaJUK0k/e5vDyggWadIr/04+Cl9/CuDfKi4/ZNNrx+ Dh0glVwSL9rhMw/0fAVH76sJ3tSq0YKi Received: (qmail 5602 invoked by uid 89); 1 Apr 2009 17:16:49 -0000 Received: (simscan 1.4.1 ppid 5578 pid 5584 t 0.2887s) (scanners: regex: 1.4.1 attach: 1.4.1 clamav: 0.94.2/m:); 01 Apr 0109 17:16:48 -0000 DomainKey-Status: no signature X-Originating-IP: 75.105.141.21 Received: from 75-105-141-21.cust.wildblue.net (HELO ?172.16.1.128?) (aaron@goflexitllc.com@75.105.141.21) by mail.goflexitllc.com with ESMTPA; 1 Apr 2009 17:16:46 -0000 Message-ID: <49D3A177.2040106@goflexitllc.com> Date: Wed, 01 Apr 2009 12:16:39 -0500 From: Aaron Hurt User-Agent: Thunderbird 2.0.0.21 (X11/20090319) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <49D2F2DE.1090807@bsd.ee> In-Reply-To: Content-Type: multipart/mixed; boundary="------------060305080907040308050306" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Auto mount and ignore errors 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: Wed, 01 Apr 2009 17:43:31 -0000 This is a multi-part message in MIME format. --------------060305080907040308050306 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Andrew Brampton wrote: > 2009/4/1 Andrei Kolu : > >> Andrew Brampton wrote: >> >>> So my question is, is there a fstab option which will ignore a failed >>> mount, and if possible continue to boot? I've read the man page, and >>> did a bit of googling, but didn't find anything. Would there be any >>> objection to a patch which implemented a "ignerror" flag? >>> >>> >>> >> Mount from /etc/rc.local? >> >> > > You mean create my own script for the mounting? Sure that would work > but I don't see that as "clean" as placing it in fstab. > > Andrew > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > !DSPAM:2,49d37b5b210281774033920! > > I think "clean" here is a bit misplaced. It's not ever "clean" to ignore a file system mount error. If you're file system in question is prone to mount failures it's probably not a good idea to mount it from fstab at all. Aaron Hurt Managing Partner Flex I.T., LLC 611 Commerce Street Suite 3117 Nashville, TN 37203 Phone: 615.438.7101 E-mail: aaron@goflexitllc.com --------------060305080907040308050306-- From owner-freebsd-fs@FreeBSD.ORG Wed Apr 1 19:44:17 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3353D106566C for ; Wed, 1 Apr 2009 19:44:17 +0000 (UTC) (envelope-from fb-fs@psconsult.nl) Received: from mx1.psconsult.nl (psc11.adsl.iaf.nl [80.89.238.138]) by mx1.freebsd.org (Postfix) with ESMTP id B65BD8FC08 for ; Wed, 1 Apr 2009 19:44:16 +0000 (UTC) (envelope-from fb-fs@psconsult.nl) Received: from mx1.psconsult.nl (localhost [80.89.238.138]) by mx1.psconsult.nl (8.14.2/8.14.2) with ESMTP id n31JWr69087846 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 1 Apr 2009 21:32:58 +0200 (CEST) (envelope-from fb-fs@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.2/8.14.2/Submit) id n31JWrSU087845 for freebsd-fs@freebsd.org; Wed, 1 Apr 2009 21:32:53 +0200 (CEST) (envelope-from fb-fs@psconsult.nl) Date: Wed, 1 Apr 2009 21:32:53 +0200 From: Paul Schenkeveld To: freebsd-fs@freebsd.org Message-ID: <20090401193253.GA87622@psconsult.nl> Mail-Followup-To: freebsd-fs@freebsd.org References: <49D2F2DE.1090807@bsd.ee> <49D3A177.2040106@goflexitllc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49D3A177.2040106@goflexitllc.com> User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: Auto mount and ignore errors 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: Wed, 01 Apr 2009 19:44:17 -0000 On Wed, Apr 01, 2009 at 12:16:39PM -0500, Aaron Hurt wrote: > Andrew Brampton wrote: >> 2009/4/1 Andrei Kolu : >> >>> Andrew Brampton wrote: >>> >>>> So my question is, is there a fstab option which will ignore a failed >>>> mount, and if possible continue to boot? I've read the man page, and >>>> did a bit of googling, but didn't find anything. Would there be any >>>> objection to a patch which implemented a "ignerror" flag? >>>> >>> Mount from /etc/rc.local? >> >> You mean create my own script for the mounting? Sure that would work >> but I don't see that as "clean" as placing it in fstab. >> >> Andrew >> > I think "clean" here is a bit misplaced. It's not ever "clean" to ignore a > file system mount error. If you're file system in question is prone to > mount failures it's probably not a good idea to mount it from fstab at all. I use my notebook both in my home office and when visiting customers. When in my office I like to mount some nfs filesystems that are not available when I'm out. Before 7.1 /etc/rc worked just the way I wanted mounting these nfs filesystems when in my office and skipping them with an error telling me that the name of the nfs server cannot be resolved when visiting customers. That old behaviour was clearly wrong as it would also continue booting when really important filesystems cannot be mounted, e.g. due to network problems. However I'd like to argue that there are perfectly legal cases for having filesystems in /etc/fstab that only get mounted when available. So I agree with OP that there should be a clean way of marking some filesystems 'optional' or 'ignerror' in fstab. My 2 cents. Paul Schenkeveld From owner-freebsd-fs@FreeBSD.ORG Thu Apr 2 05:56:41 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13E26106564A for ; Thu, 2 Apr 2009 05:56:41 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from sorbesgroup.com (mail.sorbesgroup.com [217.159.241.118]) by mx1.freebsd.org (Postfix) with ESMTP id 91A578FC22 for ; Thu, 2 Apr 2009 05:56:40 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from localhost (localhost.localdomain [127.0.0.1]) by sorbesgroup.com (Postfix) with ESMTP id 345C93C520BA for ; Thu, 2 Apr 2009 08:31:17 +0300 (EEST) Received: from sorbesgroup.com ([127.0.0.1]) by localhost (sorbesgroup.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13441-08 for ; Thu, 2 Apr 2009 08:31:15 +0300 (EEST) Received: from [192.168.0.80] (andrei [192.168.0.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sorbesgroup.com (Postfix) with ESMTP id D16F33C5207B for ; Thu, 2 Apr 2009 08:31:15 +0300 (EEST) Message-ID: <49D4539A.3080506@bsd.ee> Date: Thu, 02 Apr 2009 08:56:42 +0300 From: Andrei Kolu User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <49D2F2DE.1090807@bsd.ee> <49D3A177.2040106@goflexitllc.com> <20090401193253.GA87622@psconsult.nl> In-Reply-To: <20090401193253.GA87622@psconsult.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at localhost Subject: Re: Auto mount and ignore errors 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: Thu, 02 Apr 2009 05:56:41 -0000 Paul Schenkeveld wrote: > On Wed, Apr 01, 2009 at 12:16:39PM -0500, Aaron Hurt wrote: > >> Andrew Brampton wrote: >> >>> 2009/4/1 Andrei Kolu : >>> >>> >>>> Andrew Brampton wrote: >>>> >>>> >>>>> So my question is, is there a fstab option which will ignore a failed >>>>> mount, and if possible continue to boot? I've read the man page, and >>>>> did a bit of googling, but didn't find anything. Would there be any >>>>> objection to a patch which implemented a "ignerror" flag? >>>>> >>>>> >>>> Mount from /etc/rc.local? >>>> >>> You mean create my own script for the mounting? Sure that would work >>> but I don't see that as "clean" as placing it in fstab. >>> >>> Andrew >>> >>> >> I think "clean" here is a bit misplaced. It's not ever "clean" to ignore a >> file system mount error. If you're file system in question is prone to >> mount failures it's probably not a good idea to mount it from fstab at all. >> > > I use my notebook both in my home office and when visiting customers. > When in my office I like to mount some nfs filesystems that are not > available when I'm out. Before 7.1 /etc/rc worked just the way I wanted > mounting these nfs filesystems when in my office and skipping them with > an error telling me that the name of the nfs server cannot be resolved > when visiting customers. > > For NFS I use automounter: /etc/rc.conf # NFS automount amd_enable="YES" In case my NFS backup server is down or there is problem with network then I can start fileserver without manually interacting with fstab to start up operating system. Now my backup script can mount filesystems as needed with this script: #!/bin/sh # This script does personal backups to a rsync backup server. You will end up # with a 7 day rotating incremental backup. The incrementals will go # into subdirectories named after the day of the week, and the current # full backup goes into a directory called "current" # tridge@linuxcare.com # directory to backup BDIR=/data/samba ######################################################################## cd /host/192.168.0.249/ BACKUPDIR=`date +%A` OPTS="--progress --force --ignore-errors --delete-excluded --exclude-from=$EXCLUDES --delete --backup --backup-dir=/data/backup/$BACKUPDIR -a" export PATH=$PATH:/bin:/usr/bin:/usr/local/bin # the following line clears the last weeks incremental directory [ -d $BDIR/emptydir ] || mkdir $BDIR/emptydir rsync --delete -a $BDIR/emptydir/ /data/backup/$BACKUPDIR/ rmdir $BDIR/emptydir # now the actual transfer rsync $OPTS $BDIR /data/backup/current From owner-freebsd-fs@FreeBSD.ORG Thu Apr 2 16:20:04 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F0B9106564A for ; Thu, 2 Apr 2009 16:20:04 +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 32EDD8FC24 for ; Thu, 2 Apr 2009 16:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n32GK4hj047472 for ; Thu, 2 Apr 2009 16:20:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n32GK4AZ047471; Thu, 2 Apr 2009 16:20:04 GMT (envelope-from gnats) Date: Thu, 2 Apr 2009 16:20:04 GMT Message-Id: <200904021620.n32GK4AZ047471@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Peter Holm Cc: Subject: kern/94769: [ufs] Multiple file deletions on multi-snapshotted filesystems causes hang X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Peter Holm List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2009 16:20:04 -0000 The following reply was made to PR kern/94769; it has been noted by GNATS. From: Peter Holm To: bug-followup@FreeBSD.org Cc: Subject: kern/94769: [ufs] Multiple file deletions on multi-snapshotted filesystems causes hang Date: Thu, 2 Apr 2009 17:51:48 +0200 With the described test scenario I was able to reproduce a deadlock consistently on HEAD. The time of deadlock however seems to be a bit different from that described in the pr. On HEAD the deadlock occur during deletion of the snapshot files. http://people.freebsd.org/~pho/stress/log/pr-94769.txt - Peter From owner-freebsd-fs@FreeBSD.ORG Thu Apr 2 17:19:44 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F0971065678; Thu, 2 Apr 2009 17:19:44 +0000 (UTC) (envelope-from delphij@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 634A98FC23; Thu, 2 Apr 2009 17:19:44 +0000 (UTC) (envelope-from delphij@FreeBSD.org) Received: from freefall.freebsd.org (delphij@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n32HJil9027894; Thu, 2 Apr 2009 17:19:44 GMT (envelope-from delphij@freefall.freebsd.org) Received: (from delphij@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n32HJhsN027890; Thu, 2 Apr 2009 17:19:43 GMT (envelope-from delphij) Date: Thu, 2 Apr 2009 17:19:43 GMT Message-Id: <200904021719.n32HJhsN027890@freefall.freebsd.org> To: m.pelt@xs4all.nl, delphij@FreeBSD.org, freebsd-fs@FreeBSD.org, delphij@FreeBSD.org From: delphij@FreeBSD.org Cc: Subject: Re: kern/94480: [libufs] [patch] bread(3) & bwrite(3) can crash under low memory conditions 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: Thu, 02 Apr 2009 17:19:44 -0000 Synopsis: [libufs] [patch] bread(3) & bwrite(3) can crash under low memory conditions State-Changed-From-To: open->patched State-Changed-By: delphij State-Changed-When: Thu Apr 2 17:19:12 UTC 2009 State-Changed-Why: A fix has been applied against -HEAD, MFC reminder. Responsible-Changed-From-To: freebsd-fs->delphij Responsible-Changed-By: delphij Responsible-Changed-When: Thu Apr 2 17:19:12 UTC 2009 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=94480 From owner-freebsd-fs@FreeBSD.ORG Thu Apr 2 21:55:19 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EB92106564A for ; Thu, 2 Apr 2009 21:55:19 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from acadia.cs.uoguelph.ca (acadia.cs.uoguelph.ca [131.104.94.221]) by mx1.freebsd.org (Postfix) with ESMTP id B8DC38FC14 for ; Thu, 2 Apr 2009 21:55:18 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by acadia.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id n32LtHcG028353 for ; Thu, 2 Apr 2009 17:55:17 -0400 Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n32M1Hc28888 for ; Thu, 2 Apr 2009 18:01:17 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Thu, 2 Apr 2009 18:01:17 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: freebsd-fs@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.63 on 131.104.94.221 Subject: nfsv4 sharing nfssvc() with the regular nfsd 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: Thu, 02 Apr 2009 21:55:19 -0000 For nfsv4 to live side-by-side with the regular nfsd, they must either share the nfssvc() system call or a new one must be allocated for nfsv4. As such, I've cobbled some code to-gether to allow the nfssvc() syscall to be shared. It basically consists of a small module called nfssvc with only the nfssvc() syscall function in it, where nfsserver and nfsv4 "register" with it by setting the appropriate function pointer non-null. These functions are then called, based on the NFSSVC_xxx flag value. (I've coalesced the NFSSVC_xxx flags into a separate .h file, to avoid confusion.) I also deleted the following, since I believe that it is just cruft. (sysproto.h is included in all of these files.) #ifndef _SYS_SYSPROTO_H_ struct nfssvc_args { int flag; caddr_t argp; }; #endif Is there a reason for the above? I've attached the "diff -u" in case anyone would be willing to review it, rick. diff -u -r -N nfsserver/nfs.h nfsserver.new/nfs.h --- nfsserver/nfs.h 2009-04-02 03:55:57.000000000 -0400 +++ nfsserver.new/nfs.h 2009-04-02 05:34:17.000000000 -0400 @@ -40,6 +40,8 @@ #include "opt_nfs.h" #endif +#include + /* * Tunable constants for nfs */ @@ -116,13 +118,6 @@ #endif /* - * Flags for nfssvc() system call. - */ -#define NFSSVC_OLDNFSD 0x004 -#define NFSSVC_ADDSOCK 0x008 -#define NFSSVC_NFSD 0x010 - -/* * vfs.nfsrv sysctl(3) identifiers */ #define NFS_NFSRVSTATS 1 /* struct: struct nfsrvstats */ @@ -447,6 +442,13 @@ struct mbuf **mrq); int nfsrv_write(struct nfsrv_descript *nfsd, struct nfssvc_sock *slp, struct mbuf **mrq); +/* + * #ifdef _SYS_SYSPROTO_H_ so that it is only defined when sysproto.h + * has been included, so that "struct nfssvc_args" is defined. + */ +#ifdef _SYS_SYSPROTO_H_ +int nfssvc_nfsserver(struct thread *, struct nfssvc_args *); +#endif #endif /* _KERNEL */ #endif diff -u -r -N nfsserver/nfs_srvkrpc.c nfsserver.new/nfs_srvkrpc.c --- nfsserver/nfs_srvkrpc.c 2009-04-02 03:55:57.000000000 -0400 +++ nfsserver.new/nfs_srvkrpc.c 2009-04-02 05:34:17.000000000 -0400 @@ -151,6 +151,9 @@ /* * NFS server system calls */ +/* + * This is now called from nfssvc() in nfs/nfs_nfssvc.c. + */ /* * Nfs server psuedo system call for the nfsd's @@ -163,25 +166,14 @@ * - sockaddr with no IPv4-mapped addresses * - mask for both INET and INET6 families if there is IPv4-mapped overlap */ -#ifndef _SYS_SYSPROTO_H_ -struct nfssvc_args { - int flag; - caddr_t argp; -}; -#endif int -nfssvc(struct thread *td, struct nfssvc_args *uap) +nfssvc_nfsserver(struct thread *td, struct nfssvc_args *uap) { struct file *fp; struct nfsd_addsock_args addsockarg; struct nfsd_nfsd_args nfsdarg; int error; - KASSERT(!mtx_owned(&Giant), ("nfssvc(): called with Giant")); - - error = priv_check(td, PRIV_NFS_DAEMON); - if (error) - return (error); if (uap->flag & NFSSVC_ADDSOCK) { error = copyin(uap->argp, (caddr_t)&addsockarg, sizeof(addsockarg)); @@ -208,8 +200,6 @@ } else { error = ENXIO; } - if (error == EINTR || error == ERESTART) - error = 0; return (error); } diff -u -r -N nfsserver/nfs_srvsubs.c nfsserver.new/nfs_srvsubs.c --- nfsserver/nfs_srvsubs.c 2009-04-02 03:55:57.000000000 -0400 +++ nfsserver.new/nfs_srvsubs.c 2009-04-02 05:34:17.000000000 -0400 @@ -100,10 +100,6 @@ int nfsd_head_flag; #endif -static int nfssvc_offset = SYS_nfssvc; -static struct sysent nfssvc_prev_sysent; -MAKE_SYSENT(nfssvc); - struct mtx nfsd_mtx; /* @@ -519,13 +515,14 @@ nfsv3err_commit, }; +extern int (*call_nfsserver)(struct thread *, struct nfssvc_args *); + /* * Called once to initialize data structures... */ static int nfsrv_modevent(module_t mod, int type, void *data) { - static int registered; int error = 0; switch (type) { @@ -560,11 +557,7 @@ NFSD_UNLOCK(); #endif - error = syscall_register(&nfssvc_offset, &nfssvc_sysent, - &nfssvc_prev_sysent); - if (error) - break; - registered = 1; + call_nfsserver = nfssvc_nfsserver; break; case MOD_UNLOAD: @@ -573,8 +566,7 @@ break; } - if (registered) - syscall_deregister(&nfssvc_offset, &nfssvc_prev_sysent); + call_nfsserver = NULL; callout_drain(&nfsrv_callout); #ifdef NFS_LEGACYRPC nfsrv_destroycache(); /* Free the server request cache */ @@ -596,6 +588,7 @@ /* So that loader and kldload(2) can find us, wherever we are.. */ MODULE_VERSION(nfsserver, 1); +MODULE_DEPEND(nfsserver, nfssvc, 1, 1, 1); #ifndef NFS_LEGACYRPC MODULE_DEPEND(nfsserver, krpc, 1, 1, 1); #endif diff -u -r -N nfsserver/nfs_syscalls.c nfsserver.new/nfs_syscalls.c --- nfsserver/nfs_syscalls.c 2009-04-02 03:55:57.000000000 -0400 +++ nfsserver.new/nfs_syscalls.c 2009-04-02 05:34:17.000000000 -0400 @@ -113,6 +113,9 @@ */ /* + * This is now called from nfssvc() in nfs/nfs_nfssvc.c. + */ +/* * Nfs server psuedo system call for the nfsd's * Based on the flag value it either: * - adds a socket to the selection list @@ -123,27 +126,14 @@ * - sockaddr with no IPv4-mapped addresses * - mask for both INET and INET6 families if there is IPv4-mapped overlap */ -#ifndef _SYS_SYSPROTO_H_ -struct nfssvc_args { - int flag; - caddr_t argp; -}; -#endif int -nfssvc(struct thread *td, struct nfssvc_args *uap) +nfssvc_nfsserver(struct thread *td, struct nfssvc_args *uap) { struct file *fp; struct sockaddr *nam; struct nfsd_addsock_args nfsdarg; int error; - KASSERT(!mtx_owned(&Giant), ("nfssvc(): called with Giant")); - - AUDIT_ARG(cmd, uap->flag); - - error = priv_check(td, PRIV_NFS_DAEMON); - if (error) - return (error); NFSD_LOCK(); while (nfssvc_sockhead_flag & SLP_INIT) { nfssvc_sockhead_flag |= SLP_WANTINIT; @@ -181,8 +171,6 @@ } else { error = ENXIO; } - if (error == EINTR || error == ERESTART) - error = 0; return (error); } diff -u -r -N nfs/nfs_nfssvc.c nfs.new/nfs_nfssvc.c --- nfs/nfs_nfssvc.c 1969-12-31 19:00:00.000000000 -0500 +++ nfs.new/nfs_nfssvc.c 2009-04-02 05:34:47.000000000 -0400 @@ -0,0 +1,152 @@ +/*- + * Copyright (c) 1989, 1993 + * The Regents of the University of California. All rights reserved. + * + * This code is derived from software contributed to Berkeley by + * Rick Macklem at The University of Guelph. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 4. Neither the name of the University nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + */ + +#include + +#include "opt_nfs.h" + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#include + +#include + +static int nfssvc_offset = SYS_nfssvc; +static struct sysent nfssvc_prev_sysent; +MAKE_SYSENT(nfssvc); + +/* + * This tiny module simply handles the nfssvc() system call. The other + * nfs modules that use the system call register themselves by setting + * the call_xxx function pointers non-NULL. + */ + +int (*call_nfsserver)(struct thread *, struct nfssvc_args *) = NULL; +int (*call_nfsv4)(struct thread *, struct nfssvc_args *) = NULL; +int (*call_nfsv4client)(struct thread *, struct nfssvc_args *) = NULL; +int (*call_nfsv4server)(struct thread *, struct nfssvc_args *) = NULL; + +/* + * Nfs server psuedo system call for the nfsd's + */ +int +nfssvc(struct thread *td, struct nfssvc_args *uap) +{ + int error; + + KASSERT(!mtx_owned(&Giant), ("nfssvc(): called with Giant")); + + AUDIT_ARG(cmd, uap->flag); + + error = priv_check(td, PRIV_NFS_DAEMON); + if (error) + return (error); + error = EINVAL; + if ((uap->flag & (NFSSVC_ADDSOCK | NFSSVC_OLDNFSD | NFSSVC_NFSD)) && + call_nfsserver != NULL) + error = (*call_nfsserver)(td, uap); + else if ((uap->flag & (NFSSVC_CBADDSOCK | NFSSVC_NFSCBD)) && + call_nfsv4client != NULL) + error = (*call_nfsv4client)(td, uap); + else if ((uap->flag & (NFSSVC_IDNAME | NFSSVC_GETSTATS | + NFSSVC_GSSDADDPORT | NFSSVC_GSSDADDFIRST | NFSSVC_GSSDDELETEALL | + NFSSVC_NFSUSERDPORT | NFSSVC_NFSUSERDDELPORT)) && + call_nfsv4 != NULL) + error = (*call_nfsv4)(td, uap); + else if ((uap->flag & (NFSSVC_NFSDNFSD | NFSSVC_NFSDADDSOCK | + NFSSVC_PUBLICFH | NFSSVC_V4ROOTEXPORT | NFSSVC_NOPUBLICFH | + NFSSVC_STABLERESTART | NFSSVC_ADMINREVOKE | + NFSSVC_DUMPCLIENTS | NFSSVC_DUMPLOCKS)) && + call_nfsv4server != NULL) + error = (*call_nfsv4server)(td, uap); + if (error == EINTR || error == ERESTART) + error = 0; + return (error); +} + +/* + * Called once to initialize data structures... + */ +static int +nfssvc_modevent(module_t mod, int type, void *data) +{ + static int registered; + int error = 0; + + switch (type) { + case MOD_LOAD: + error = syscall_register(&nfssvc_offset, &nfssvc_sysent, + &nfssvc_prev_sysent); + if (error) + break; + registered = 1; + break; + + case MOD_UNLOAD: + if (call_nfsserver != NULL || call_nfsv4 != NULL || + call_nfsv4client != NULL || call_nfsv4server != NULL) { + error = EBUSY; + break; + } + if (registered) + syscall_deregister(&nfssvc_offset, &nfssvc_prev_sysent); + registered = 0; + break; + default: + error = EOPNOTSUPP; + break; + } + return error; +} +static moduledata_t nfssvc_mod = { + "nfssvc", + nfssvc_modevent, + NULL, +}; +DECLARE_MODULE(nfssvc, nfssvc_mod, SI_SUB_VFS, SI_ORDER_ANY); + +/* So that loader and kldload(2) can find us, wherever we are.. */ +MODULE_VERSION(nfssvc, 1); + diff -u -r -N nfs/nfssvc.h nfs.new/nfssvc.h --- nfs/nfssvc.h 1969-12-31 19:00:00.000000000 -0500 +++ nfs.new/nfssvc.h 2009-04-02 05:34:47.000000000 -0400 @@ -0,0 +1,66 @@ +/* + * Copyright (c) 1989, 1993 + * The Regents of the University of California. All rights reserved. + * + * This code is derived from software contributed to Berkeley by + * Rick Macklem at The University of Guelph. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 4. Neither the name of the University nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + */ + +#ifndef _NFS_NFSSVC_H_ +#define _NFS_NFSSVC_H_ + +/* + * Flags for nfssvc() system call. + */ +#define NFSSVC_OLDNFSD 0x004 +#define NFSSVC_ADDSOCK 0x008 +#define NFSSVC_NFSD 0x010 + +/* + * and ones for nfsv4. + */ +#define NFSSVC_NOPUBLICFH 0x00000020 +#define NFSSVC_STABLERESTART 0x00000040 +#define NFSSVC_NFSDNFSD 0x00000080 +#define NFSSVC_NFSDADDSOCK 0x00000100 +#define NFSSVC_IDNAME 0x00000200 +#define NFSSVC_GSSDDELETEALL 0x00000400 +#define NFSSVC_GSSDADDPORT 0x00000800 +#define NFSSVC_NFSUSERDPORT 0x00001000 +#define NFSSVC_NFSUSERDDELPORT 0x00002000 +#define NFSSVC_V4ROOTEXPORT 0x00004000 +#define NFSSVC_ADMINREVOKE 0x00008000 +#define NFSSVC_DUMPCLIENTS 0x00010000 +#define NFSSVC_DUMPLOCKS 0x00020000 +#define NFSSVC_GSSDADDFIRST 0x00040000 +#define NFSSVC_PUBLICFH 0x00080000 +#define NFSSVC_NFSCBD 0x00100000 +#define NFSSVC_CBADDSOCK 0x00200000 +#define NFSSVC_GETSTATS 0x00400000 + +#endif /* _NFS_NFSSVC_H */