Date: Tue, 7 Feb 2012 23:10:13 GMT From: Yar Tikhiy <yar@freebsd.org> To: freebsd-fs@FreeBSD.org Subject: Re: bin/145309: bsdlabel: Editing disk label invalidates the whole device Message-ID: <201202072310.q17NAD0h052230@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/145309; it has been noted by GNATS. From: Yar Tikhiy <yar@freebsd.org> To: "Andrey V. Elsukov" <ae@freebsd.org> Cc: Pawel Jakub Dawidek <pjd@freebsd.org>, 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 <ae@freebsd.org>: > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202072310.q17NAD0h052230>