From owner-freebsd-stable@FreeBSD.ORG Fri Aug 26 10:58:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 157B816A41F for ; Fri, 26 Aug 2005 10:58:22 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (84-245-169-223.ipool.celox.de [84.245.169.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DC4443D46 for ; Fri, 26 Aug 2005 10:58:17 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from [192.168.16.3] (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 66B205DE9 for ; Fri, 26 Aug 2005 12:53:00 +0200 (CEST) Message-ID: <430EF48B.6010405@vwsoft.com> Date: Fri, 26 Aug 2005 12:52:59 +0200 From: Volker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Thunderbird/1.0.2 Mnenhy/0.6.0.101 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com Subject: releng_6 sysinstall creating labels X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Aug 2005 10:58:22 -0000 Hi! I guess I found a (new?) issue with RELENG_6 (as of 2005-08-23). When creating slices and labels by using /stand/sysinstall, the label editor is miscalculating the partition sizes. While having a (SCSI) disk outage yesterday night, I've been forced to put in a new hdu. After labeling it by using sysinstall, sysinstall aborted at creating the partitions and the filesystems. Error message has been 'unable to write to da5'. After that I found that sysinstall created a partition which exceeded past the end of the slice. As far as I remember it has been 16 bytes past the end of the slice, but my memories might be wrong. Because I've been unable to backup my data to tape (another issue with scsi cam, but I have to check that first before posting), I installed another 18G hd, created a slice and a partition by using sysinstall covering the whole disk and even that failed by a partition exceeding the end of the slice. Manual corrections by using bsdlabel -e and manually newfs'ing went ok. This must be an issue with sysinstall and should be fixed before -RELEASE or someone might not be able to install from CDROM because not being able to create filesystems (don't you consider that being a show stopper?). I'm unable to check if this is a SCSI only issue but I guess it should be re-creatable on ata systems. Sorry, but I don't have any other examples for that issue or any dumps, screenshots etc. I had that hd-crash last night and tried to solve that first. I might try to recreate that problem on a testing machine at the weekend and give exact information. Bye, Volker -- GPG/PGP fingerprint: FF93 13A1 2477 B631 E953 06DF 4C49 ADD9 E4BF 79B1