From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: Reallocating sd device Date: Mon, 09 Jun 2008 22:56:12 -0500 Message-ID: <1213070172.3508.102.camel@localhost.localdomain> References: <484D8935.70905@sauce.co.nz> <1213041283.3508.66.camel@localhost.localdomain> <484D8FD1.60000@sauce.co.nz> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from accolon.hansenpartnership.com ([76.243.235.52]:37122 "EHLO accolon.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753501AbYFJD4Q (ORCPT ); Mon, 9 Jun 2008 23:56:16 -0400 In-Reply-To: <484D8FD1.60000@sauce.co.nz> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Richard Scobie Cc: linux-scsi@vger.kernel.org On Tue, 2008-06-10 at 08:17 +1200, Richard Scobie wrote: > James Bottomley wrote: > > > Not really ... relying on a specific sdX name has been deprecated for a > > while. To ensure absolute ordering, you should be using the device by > > id or by label. > > > > James > > Thanks. I was trying to avoid the extra work of modifying smartd.conf > files after drives are replaced, which seem to only be able to use > /dev/sdX, or am I missing something? Depends how you're doing it. I'm pretty sure smartmon is perfectly capable of using /dev/disk/by-id/X; some of the maintainers are on this list, so they can comment further. However, the auto generator for it (if that's what you're using) always emits /dev/sdX, so I agree you have a problem with autogenerated files. James