From nobody@www.freebsd.org  Sun May 26 12:44:07 2002
Return-Path: <nobody@www.freebsd.org>
Received: from nwww.freebsd.org (www.FreeBSD.org [216.136.204.117])
	by hub.freebsd.org (Postfix) with ESMTP id 5A55F37B42F
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 26 May 2002 12:44:01 -0700 (PDT)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by nwww.freebsd.org (8.12.2/8.12.2) with ESMTP id g4QJi0hG007757
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 26 May 2002 12:44:00 -0700 (PDT)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.2/8.12.2/Submit) id g4QJi0pd007756;
	Sun, 26 May 2002 12:44:00 -0700 (PDT)
Message-Id: <200205261944.g4QJi0pd007756@www.freebsd.org>
Date: Sun, 26 May 2002 12:44:00 -0700 (PDT)
From: Neil Ludban <nludban@columbus.rr.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: sysinstall sets newfs flag after changing mount point
X-Send-Pr-Version: www-1.0

>Number:         38582
>Category:       bin
>Synopsis:       [sysinstall] sysinstall sets newfs flag after changing mount point
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun May 26 12:50:01 PDT 2002
>Closed-Date:    Sun Jun 10 06:19:11 GMT 2007
>Last-Modified:  Sun Jun 10 06:19:11 GMT 2007
>Originator:     Neil Ludban
>Release:        4.5-RELEASE
>Organization:
>Environment:
i386 sysinstall, booted from 4.5-RELEASE install CD
>Description:
Doing an "upgrade" on an existing system, sysinstall partition editor
screen is used to allow user to specify mount points.  The first mount
point (per partition) entered is accepted OK, but when a change is made
after that (eg, to correct a spelling mistake) the newfs flag is set
to "Y" -- not a good thing to do when upgrading.
>How-To-Repeat:
See description.  I set mount points for all my partitions (/, /tmp,
/var, /home, /usr), double checked and noticed /home and /usr were
reversed.  Tried changing /home to /usr, which complained (/usr already
exists).  Set /home to /foo, /usr to /home, and /foo to /usr.  Checked
again and saw that /home and /usr had newfs flag set.  Toggled newfs
off for each, then changed /var to /foo and saw that newfs flag was
set again.
>Fix:
      
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-qa 
Responsible-Changed-By: johan 
Responsible-Changed-When: Tue Jun 4 17:51:46 PDT 2002 
Responsible-Changed-Why:  
Over to maintainer list 

http://www.freebsd.org/cgi/query-pr.cgi?pr=38582 

From: Craig Carey <snowfall@gmx.co.uk>
To: freebsd-gnats-submit@FreeBSD.org
Cc: nludban@columbus.rr.com, ob@www.partner.de
Subject: Re: misc/38582: sysinstall sets newfs flag after changing
  mount point
Date: Wed, 13 Aug 2003 02:05:27 +1200

 I note that these two problem reports appear to be reporting the same
 problem:
 
   misc/38582:
     "sysinstall sets newfs flag after changing mount point" [26 May 2002]
      http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/38582
 
 
   bin/31837: "sysinstall change mountpoint" [7 Nov 2001]
     "... then ... change the mount point in the disk labeling, the newfs
     flag switch from no format to newfs !.
     http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/31837
 
 PS. Sysinstall has 2 bugs that could result in loss of over xxxxGB per
  user:
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/47384 [22 Jan 2003]
    "Machine has two disks, ad0 (existing 5.0 system) and da0 (scratch
    disk).  Selecting da0 as the target for 'partition' and then
    following that by the sequence 'label/distribution/commit'
    results in a wiped ad0."
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/29375
     "the disk editor used by /stand/sysinstall gets confused by
      slices that are not labelled in order and writes the
      partition table incorrectly."
 
     --  C Carey
 
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Sun Jun 10 06:18:40 UTC 2007 
State-Changed-Why:  
Duplicate of bin/31837, was fixed in 2003 (label.c 1.123) 

http://www.freebsd.org/cgi/query-pr.cgi?pr=38582 
>Unformatted:
