From owner-freebsd-bugs@FreeBSD.ORG Sun May 11 12:50:05 2008 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 1CB62106566B for ; Sun, 11 May 2008 12:50: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 0914B8FC1B for ; Sun, 11 May 2008 12:50: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.2/8.14.2) with ESMTP id m4BCo4mI012913 for ; Sun, 11 May 2008 12:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4BCo4Em012912; Sun, 11 May 2008 12:50:04 GMT (envelope-from gnats) Date: Sun, 11 May 2008 12:50:04 GMT Message-Id: <200805111250.m4BCo4Em012912@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?iso-8859-1?q?Ga=EBl_Roualland?= Cc: Subject: Re: kern/122833: [snapshots] [patch] mountd fails on nmount() after UFS snapshot creation with mount X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?iso-8859-1?q?Ga=EBl_Roualland?= List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 12:50:05 -0000 The following reply was made to PR kern/122833; it has been noted by GNATS. From: =?iso-8859-1?q?Ga=EBl_Roualland?= To: bug-followup@freebsd.org, leon.kos@lecad.fs.uni-lj.si Cc: Subject: Re: kern/122833: [snapshots] [patch] mountd fails on nmount() after UFS snapshot creation with mount Date: Sun, 11 May 2008 13:14:27 +0200 Same problem here. After looking a bit in mount and mksnap_ffs, this seems due to a difference in the way the snapshot is created : mount calls nmount(2), while mksnap_ffs only calls mount(2). There might also be differences in the options passed to the syscalls, that needs investigating. Note that mount sends a HUP signal to mountd after each successful mount (including snapshots), while mksnap_ffs does not, however manually restarting mountd after a mksnap_ffs does not exhibit the bug.