Date: Sat, 20 Nov 2010 12:28:03 -0600 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Softupdates And Samba Message-ID: <4CE81333.8020804@tundraware.com>
next in thread | raw e-mail | index | archive | help
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<READY,DSC,ERROR> 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<READY,DSC,ERROR> 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CE81333.8020804>