From owner-freebsd-current@freebsd.org Mon Aug 1 19:37:59 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 228F9BAB431 for ; Mon, 1 Aug 2016 19:37:59 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 07AC317A6 for ; Mon, 1 Aug 2016 19:37:58 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 77e5f87f-581f-11e6-8929-8ded99d5e9d7 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Mon, 1 Aug 2016 19:38:05 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u71JaoEs034534; Mon, 1 Aug 2016 13:36:50 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1470080210.1283.36.camel@freebsd.org> Subject: Re: CURRENT: [USB] : GEOM_PART: da4 was automatically resized. From: Ian Lepore To: Matthew Grooms , freebsd-current@freebsd.org Date: Mon, 01 Aug 2016 13:36:50 -0600 In-Reply-To: <0b4f142a-7c44-832d-5fe2-c2a6264383cc@shrew.net> References: <20160801110554.289d040d@freyja.zeit4.iv.bundesimmobilien.de> <20160801174035.GI74453@gmail.com> <0b4f142a-7c44-832d-5fe2-c2a6264383cc@shrew.net> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2016 19:37:59 -0000 On Mon, 2016-08-01 at 13:55 -0500, Matthew Grooms wrote: > On 8/1/2016 12:40 PM, Randy Westlund wrote: > > On Mon, Aug 01, 2016 at 11:05:54AM +0200, O. Hartmann wrote: > > > On every(!) USB drive which worked well with 11-CURRENT up to 11 > > > -BETA, I fail > > > to access with 12-CURRENT (12.0-CURRENT FreeBSD 12.0-CURRENT #14 > > > r303475: Fri > > > Jul 29 11:59:11 CEST 2016) with the error shown below. > > > > > > On USB flash drives I created myself, the suggested gpart command > > > solved the > > > problem, but I can not do this with drives I was given by a > > > vendor or supplier. > > > > > > What is wrong? > > > > > > Kind regards and thank you very much in advance, > > > > > > O. Hartmann > > > > > > > > > On console, I get the report: > > > > > > [...] > > > GEOM_PART: da4 was automatically resized. > > > Use `gpart commit da4` to save changes or `gpart undo da4` to > > > revert them. > > > > I noticed something similar when I was trying to dd a more recent > > memstick installer to a USB drive on 12-CURRENT. When I plugged in > > the > > flash drive I couldn't dd to it until I noticed that message in > > syslog > > and ran 'gpart undo da0'. Looks like something is unhelpfully > > auto-resizing partitions. > > > > Do you have growfs_enable in your rc.conf file? I think this is added > to > certain flash images by default so it will automatically grow to your > device capacity. See ... > > /etc/rc.d/growfs > > ... and ... > > https://lists.freebsd.org/pipermail/freebsd-rc/2014-May/003497.html > > -Matthew I think rather than being related to growfs, this is fallout from r303019 [*] which automatically resizes the device geom based on what the device reports. I suspect the intent was to make gpt backup partition data appear at the right place on the device even when the original image is created on a device of a different size. Unfortunately, leaving an uncommited geom change lurking in the system is going to lead to a fair amount of confusion, since it makes other attempts to work with the device fail, usually with no clue about why it's failing. Uncommitted geom changes are a bit like an invisible time bomb in your system; it wouldn't be so bad if they weren't so invisible, and weren't so hard to figure out how to properly get out of the situation. Something like a "gpart undo -r " to recursively undo all uncommitted changes would go a long way towards fixing the "what to do" part. I'm not sure how to make pending changes more visible. Maybe it would work to have gpart show flag uncommitted changes somehow. * https://svnweb.freebsd.org/base/head/sys/geom/geom_disk.c?view=log -- Ian