From owner-freebsd-performance@FreeBSD.ORG Fri Jun 1 13:11:36 2007 Return-Path: X-Original-To: freebsd-performance@freebsd.org Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF3E916A400 for ; Fri, 1 Jun 2007 13:11:36 +0000 (UTC) (envelope-from tec@mega.net.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 3D04E13C44C for ; Fri, 1 Jun 2007 13:11:35 +0000 (UTC) (envelope-from tec@mega.net.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l51BuXKu076726 for ; Fri, 1 Jun 2007 08:56:33 -0300 (BRT) (envelope-from tec@mega.net.br) From: NOC Meganet Organization: Prowip Telecom Ltda To: freebsd-performance@freebsd.org Date: Fri, 1 Jun 2007 08:55:59 -0300 User-Agent: KMail/1.9.6 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706010855.59841.tec@mega.net.br> X-Spam-Status: No, score=-100.2 required=5.0 tests=ALL_TRUSTED, AWL, ISO_7BITS, USER_IN_WHITELIST autolearn=unavailable version=3.1.8 X-Spam-Checker-Version: Antispam Datacenter Matik msrv.matik.com.br X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Subject: hd device names X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2007 13:11:36 -0000 Hi all I am not sure if this is exactly the right list but perhaps some could point me to it. I think it is not the best way having different hard disk device names. I think it should be generally hd or something independent of type, driver or controller. Once I had trouble because I needed to change the MB and the new one called the first SATA ad8 and not ad4 Now I was terrible bitten by a ahd controller failure and I had no suitable backup card on site and decided to put an aac card in, so here it was not da anymore it was aacd which caused me a long down time of my cluster because the hardware maintainer was not trained to get the fstab change done. So long story short question, is there any link trick so that I can prepare my servers for something like that otherwise I would like to make such a suggestion to the project people. Meyer -- -- Prowip Telecom Ltda AS 22706 A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br