From owner-freebsd-fs@FreeBSD.ORG Tue Feb 7 23:10:13 2012 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 87F691065696 for ; Tue, 7 Feb 2012 23:10:13 +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 773DC8FC0C for ; Tue, 7 Feb 2012 23:10:13 +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 q17NAD31052231 for ; Tue, 7 Feb 2012 23:10:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q17NAD0h052230; Tue, 7 Feb 2012 23:10:13 GMT (envelope-from gnats) Date: Tue, 7 Feb 2012 23:10:13 GMT Message-Id: <201202072310.q17NAD0h052230@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Yar Tikhiy Cc: Subject: Re: bin/145309: bsdlabel: Editing disk label invalidates the whole device X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Yar Tikhiy List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2012 23:10:13 -0000 The following reply was made to PR bin/145309; it has been noted by GNATS. From: Yar Tikhiy To: "Andrey V. Elsukov" Cc: Pawel Jakub Dawidek , bug-followup@freebsd.org Subject: Re: bin/145309: bsdlabel: Editing disk label invalidates the whole device Date: Wed, 8 Feb 2012 10:08:54 +1100 Hi Andrey, 2012/2/6 Andrey V. Elsukov : > On 04.02.2012 7:50, Yar Tikhiy wrote: >> >> =A0Sorry but FreeBSD 9.0-RELEASE still appears to have this issue. =A0Wh= en >> =A0installed using BSD label partitioning scheme, a modification to >> =A0ada0's label seems to nuke the kernel's view of the disk -- I can't >> =A0think of a better way to explain it. =A0The disk itself is OK and the >> =A0change makes it OK to the disk but the kernel can no more use the roo= t >> =A0partition until rebooted, returning weird errnos such as EIO or EXIO. >> =A0No idea here if the bug is limited to BSD label scheme. > > When you are in single user mode your root filesystem is mounted read-onl= y. > When you run bsdlabel it opens geom provider for writing and this trigger= s spoiling for it. > When bsdlabel closes provider GEOM_PART destroys it and creates again. > But VFS code seems loses it. Sorry but do you think it's intended behavior or not? It doesn't look so to me and, IMMSMR, it wasn't there before. Please correct me if I'm wrong. Thanks, Yar