From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 07:25:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3B0B16A417 for ; Sun, 17 Feb 2008 07:25:50 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from webmail26.yandex.ru (webmail26.yandex.ru [213.180.200.91]) by mx1.freebsd.org (Postfix) with ESMTP id 7003E13C447 for ; Sun, 17 Feb 2008 07:25:50 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from YAMAIL (webmail26) by mail.yandex.ru id S1736723AbYBQHZk for ; Sun, 17 Feb 2008 10:25:40 +0300 X-Yandex-Spam: 0 Received: from [77.72.136.70] ([77.72.136.70]) by mail.yandex.ru with HTTP; Sun, 17 Feb 2008 10:25:40 +0300 From: "Andrey V. Elsukov" To: unixmania@gmail.com In-Reply-To: 9060000000163393529 References: <20080216210736.GA17517@eos.sc1.parodius.com> 9060000000163393529 MIME-Version: 1.0 Message-Id: <886021203233140@webmail26.yandex.ru> Date: Sun, 17 Feb 2008 10:25:40 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-stable@freebsd.org Subject: Re: ATA -- erratic behaviour when removing disk 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: Sun, 17 Feb 2008 07:25:50 -0000 17.02.08, 02:08, "Carlos A. M. dos Santos" : > > precautions prior to yanking the disk. Upon reinsertion, the system > > found the disk and I could continue I/O operations on it as if it had > > never been removed. Only reason I'm pointing this out is that it > > confirms the issue isn't hardware or with vendor implementation, but > > rather specific to the OS. > Congratulations to the Linux folks. Or not, since this looks like a > very risky behavior. Who warrants you that the *same* disk was plugged > back? Blindly continuing to write could easily corrupt the contents of > the second drive. There is no risk. Linux's libata detects it when you inserts a different disk. You can read some details here: http://www.mail-archive.com/linux-ide@vger.kernel.org/msg11742.html -- WBR, Andrey V. Elsukov