Date: Sun, 28 Jun 2009 10:55:23 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Daniel O'Connor <doconnor@gsoft.com.au> Cc: scottl@freebsd.org, freebsd-current@freebsd.org, Kamigishi Rei <spambox@haruhiism.net> Subject: Re: RFC: ATA to CAM integration patch Message-ID: <4A4721EB.9060404@FreeBSD.org> In-Reply-To: <200906280847.59316.doconnor@gsoft.com.au> References: <4A4517BE.9040504@FreeBSD.org> <20090627141412.GN31709@acme.spoerlein.net> <4A462A7A.20005@haruhiism.net> <200906280847.59316.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel O'Connor wrote: > On Sat, 27 Jun 2009, Kamigishi Rei wrote: >> This poses the question of daXX enumeration order. I've already had >> some 'fun' with an IBM server which has an LVD/320 SCSI controller. >> While the controller's bus was enumerated properly, somehow if you >> attach an USB mass storage device before the system boot that said >> mass storage could suddenly appear earlier than one of the SCSI disks >> (that was on 7.0-RELEASE) thus breaking the boot process sometimes >> (when it appeared as da0). > > 7.2 has UFSID in GENERIC so you can mount your disks that way which is > non-ambiguous. > > Unfortunately you can't specify swap this way because it has no ID, I > don't know how hard it would be to add such a thing (which would > require a mkswap or somesuch, and modification to the dump & swap > code..) Yes. I've hit this problem. I haven't tried yet, but probably marking the whole disk with glabel could be an option now. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A4721EB.9060404>