From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 27 20:56:18 2014 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A75F939 for ; Sat, 27 Sep 2014 20:56:18 +0000 (UTC) Received: from nm6-vm1.access.bullet.mail.gq1.yahoo.com (nm6-vm1.access.bullet.mail.gq1.yahoo.com [216.39.63.4]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6457AFC for ; Sat, 27 Sep 2014 20:56:17 +0000 (UTC) Received: from [216.39.60.165] by nm6.access.bullet.mail.gq1.yahoo.com with NNFMP; 27 Sep 2014 20:53:45 -0000 Received: from [216.39.60.243] by tm1.access.bullet.mail.gq1.yahoo.com with NNFMP; 27 Sep 2014 20:53:45 -0000 Received: from [127.0.0.1] by omp1014.access.mail.gq1.yahoo.com with NNFMP; 27 Sep 2014 20:53:45 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 770708.39495.bm@omp1014.access.mail.gq1.yahoo.com Received: (qmail 10853 invoked by uid 60001); 27 Sep 2014 20:53:45 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1411851225; bh=3LT5EZ0GALkM8fUp5bXb9S3yCdBBMcMTvc9GBeJlwEg=; h=Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=S5NtY3hwJolDX2nmyn5JUyB4BgLs2XGWAtQebS9/AcxUraaGfr0wz+X/ZMSFbiN6RwMGXhbzOWy8U6hN4okTlcKNmXEpjIzfi/K4Rch3y/bmJ+S4AW3egAHa9LzBrYGbmHlOpkMc3QNT9PNmwg0dOgVUCpjHPDdzcpo4zhHz77o= X-YMail-OSG: t2l2jLsVM1nVP2hS1BTHg54MycVu886E8SQzLynI_sOheyz SAkbxFBMGb0GcOa58gkT1kyig.IAYQVcTVYlyRjFhLTkWGiD8skEJexEwf_8 aR.nfTYUCqi9Rjlh0xeiANjJA3ffOf9HWcMG7vdloxYM0WRRhHvhhNqWu5B2 hGFyoVnPUjI17gHVW.ZB7F8ol.RS11SPvrHOcKQOd.Xz9RQT8fKyni2lPkZi GnhTkr4AK3J1yzlwDwLmM4.QuSuIAyXX28FpOiNPQJ8m2oJ6RAIqetNVsQkB lfUkVW60R1mY2kPSR1rWMDWpUm.IioZIULtrqUgiVMcyn_4u9c0xOpc0MtzU VeukVODVPPEJyFhPpaSFnW5p4ZbojEUooqENtC3LLA_qxTU7MnDzxG._Q8mY FcyYaM1F6N9CmzO9U5zt6hKQl3yhMAuFV.cmN9aYdn6FfkSMmK4WEok3_3FN omAx1pIO9UAFD26o0chCip0Y3GyaH0xZM6ZHxqvl5uYhFBfjJjkkKfBs4smw RpCZ9XxLVFgLzjFl8DW1Xb4vh9gEW.SXeUmMsL11sYV.6d1lGBC6YUGBDZh_ .RSOLgA7syQjD05Q- Received: from [162.239.0.170] by web180902.mail.ne1.yahoo.com via HTTP; Sat, 27 Sep 2014 13:53:45 PDT X-Rocket-MIMEInfo: 002.001, SW5zdGFsbGVkIDEwLUJFVEEyIG9uIFNBVEEgcG9ydCA0IChhZDgpIGFuZCB0aGVuIGFkZGVkIGFub3RoZXIgU0FUQSBwb3J0IDMgKGFkNiksIHRoZSBzeXN0ZW0gaGFzIG5vdCBjb3JyZWN0bHkgZW51bWVyYXRlIHRoZSBhZGEgIyBmb3IgdGhlIGJvb3QgZGV2aWNlLgpBcyBvcmlnaW5hbCBib290ICh3aXRob3V0IHRoZSBzZWNvbmQgU0FUQSBkcml2ZSksIHRoZSBhZDggaXMgZW51bWVyYXRlZCBhcyBhZGEwIC0tIHRoZSBib290IGRyaXZlOgoKU2VwIDI0IDIyOjUxOjMwIFIxMC1CMiBrZXJuZWw6IGFkYTAgYXQBMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 Message-ID: <1411851225.9364.YahooMailNeo@web180902.mail.ne1.yahoo.com> Date: Sat, 27 Sep 2014 13:53:45 -0700 From: Jin Guojun Reply-To: Jin Guojun Subject: Inproper ada# assignment in 10-BETA2 To: questions freebsd , "hackers@freebsd.org" MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 27 Sep 2014 23:32:41 +0000 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Sep 2014 20:56:18 -0000 Installed 10-BETA2 on SATA port 4 (ad8) and then added another SATA port 3 (ad6), the system has not correctly enumerate the ada # for the boot device. As original boot (without the second SATA drive), the ad8 is enumerated as ada0 -- the boot drive: Sep 24 22:51:30 R10-B2 kernel: ada0 at ahcich2 bus 0 scbus2 target 0 lun 0 Sep 24 22:51:30 R10-B2 kernel: ada0: ATA-8 SATA 2.x device ... Sep 24 22:51:30 R10-B2 kernel: ada0: Previously was known as ad8 However, after added another SATA drive (ad6), this new drive is assigned to ada0, but ad8 has changed to ada1. This is incorrect dynamic device assignment. FreeBSD has kept using fixed disk ID assignment due to the same problem introduced in around 4-R (or may be slightly later), and after a simple debate, a decision was made to use fixed drive ID to avoid such hassle. If now we want to use dynamic enumeration for drive ID# assignment, this has to be done correctly -- boot drive MUST assigned to 0 or whatever the # as installation assigned to; otherwise, adding a new drive will cause system not bootable, or make other existing drive not mountable due to enumeration # changes. Has this been reported as a known problem for 10-R, or shall I open a bug to track? -Jin