From owner-freebsd-questions@FreeBSD.ORG Sat Nov 20 18:28:30 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C1531065674 for ; Sat, 20 Nov 2010 18:28:30 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 3ADE08FC08 for ; Sat, 20 Nov 2010 18:28:29 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.4/8.14.4) with ESMTP id oAKIS676006260 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Sat, 20 Nov 2010 12:28:11 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <4CE81333.8020804@tundraware.com> Date: Sat, 20 Nov 2010 12:28:03 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: FreeBSD Mailing List X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (ozzie.tundraware.com [75.145.138.73]); Sat, 20 Nov 2010 12:28:12 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: oAKIS676006260 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Softupdates And Samba X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 18:28:30 -0000 I installed another SATA drive on a FreeBSD 8.1-STABLE box here last night. After the disk prep, I mounted it and then shared the whole drive via Samba. This morning when I came in, the machine had horked all over itself and I saw this in the log after the reboot: Nov 20 01:06:59 ozzie kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=34066054 3 Nov 20 01:06:59 ozzie kernel: ad6: FAILURE - WRITE_DMA48 status=51 error=10< NID_NOT_FOUND> LBA=340660543 Nov 20 01:06:59 ozzie kernel: g_vfs_done():ad6s1d[WRITE(offset=174418165760, length=131072)]e rror = 5 Nov 20 02:15:07 ozzie kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=14580695 35 Nov 20 02:15:07 ozzie kernel: ad6: FAILURE - WRITE_DMA48 status=51 error=10< NID_NOT_FOUND> LBA=1458069535 Nov 20 02:15:07 ozzie kernel: g_vfs_done():ad6s1d[WRITE(offset=746531569664, length=131072)]e rror = 5 I reformatted and remounted the drive and accidentally forgot to enable softupdates. It seems to now be working fine. Is there a known interaction with softupdates and Samba such that I should not use them in this case, or could this just have been a loose cable or something? The drive is pretty new (< 6mo) and it's never been a problem when I used it on an NTFS system previously. TIA, -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/