From nobody@FreeBSD.org  Thu Oct 18 13:43:35 2001
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id F383837B403
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 18 Oct 2001 13:43:34 -0700 (PDT)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.4/8.11.4) id f9IKhYb77939;
	Thu, 18 Oct 2001 13:43:34 -0700 (PDT)
	(envelope-from nobody)
Message-Id: <200110182043.f9IKhYb77939@freefall.freebsd.org>
Date: Thu, 18 Oct 2001 13:43:34 -0700 (PDT)
From: Dave Walton <dwalton@acm.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: sysinstall "partition editor" silently corrects partition table
X-Send-Pr-Version: www-1.0

>Number:         31363
>Category:       bin
>Synopsis:       sysinstall(8): "partition editor" silently corrects partition table
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-sysinstall
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 18 13:50:01 PDT 2001
>Closed-Date:    
>Last-Modified:  Sun Jan 23 21:12:57 UTC 2011
>Originator:     Dave Walton
>Release:        4.4-RELEASE
>Organization:
>Environment:
>Description:
I recently ran into this problem while installing 4.4-RELEASE into a
pre-existing slice.  It is discussed in -questions with the subject
"Partition table problem".  The exact details are impossible to know due
to data loss, but it appears that I somehow had two slices overlapped
by about 600MB (how this happened is beyond me).  The "partition editor"
appears to have detected this error and zeroed out the partition table
entry it decided was in error, and sysinstall then wrote the change to
the partition table.  I did not actually make any changes in the
"partition editor".  I entered it only long enough to remember that
I had already created the partition at an earlier date, then quickly
exited and went on to the label editor.  Obviously the actual data
loss occurred when the installation overwrote the data in the overlapped
slice, and was not the fault of FreeBSD.  But data loss could have been
avoided if the "partition editor" had popped up an alert about the
invalid slice configuration and requested confirmation to correct it,
rather than doing so silently.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-qa 
Responsible-Changed-By: johan 
Responsible-Changed-When: Wed Aug 21 14:04:16 PDT 2002 
Responsible-Changed-Why:  
Over to sysinstall maintainers. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=31363 
Responsible-Changed-From-To: freebsd-bugs->brucec  
Responsible-Changed-By: brucec 
Responsible-Changed-When: Sat Mar 13 11:29:20 UTC 2010 
Responsible-Changed-Why:  
Take. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=31363 
Responsible-Changed-From-To: brucec->freebsd-sysinstall 
Responsible-Changed-By: brucec 
Responsible-Changed-When: Sun Jan 23 21:12:39 UTC 2011 
Responsible-Changed-Why:  
Back to the pool. 

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