From owner-freebsd-fs@FreeBSD.ORG Sun Jan 29 22:24:55 2012 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 6CEDE106564A for ; Sun, 29 Jan 2012 22:24:55 +0000 (UTC) (envelope-from uffe@uffe.org) Received: from mail.starion.dk (mx0.starion.dk [93.162.70.34]) by mx1.freebsd.org (Postfix) with SMTP id A0B9E8FC0A for ; Sun, 29 Jan 2012 22:24:54 +0000 (UTC) Received: (qmail 2690 invoked by uid 1004); 29 Jan 2012 22:25:15 -0000 Message-ID: <4F25C710.6000806@uffe.org> Date: Sun, 29 Jan 2012 23:24:16 +0100 From: Uffe Jakobsen X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; DSN=0; uuencode=0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111229 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <201201272310.q0RNABvZ065758@freefall.freebsd.org> <20120128004755.GA89980@icarus.home.lan> <4F246CA9.30803@uffe.org> <4F248B44.1090304@uffe.org> <20120129042647.GJ2726@deviant.kiev.zoral.com.ua> In-Reply-To: <20120129042647.GJ2726@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: kern/164516: [ext2fs] unable to mount EXT2 filesystem 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 Jan 2012 22:24:55 -0000 On 2012-01-29 05:26, Kostik Belousov wrote: > On Sun, Jan 29, 2012 at 12:56:52AM +0100, Uffe Jakobsen wrote: >>> Question is if there exists a scenario >>> where the requested filesystem type would/could not be found by >>> getvfsbyname() ? >>>> >> Anyway - would you accept a patch that checked the fstype using >> getvfsbyname() before calling nmount() ? > > Kernel tries to load the named module if it is not registered in the > list of know VFSes. Your proposal would break this functionality. Thanks that was exactly the info I asked for - I had a feeling that there was some sort of catch. I was not aware of that functionality in nmount - it is not mentioned in the manpage and I admit that i did not look deep into its source. Well that settles the question - it is a no go - thx for your answer. /Uffe