Date: Sun, 18 Nov 2001 12:37:43 -0700 From: "Kenneth D. Merry" <ken@kdm.org> To: Len Conrad <LConrad@Go2France.com> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: b_bcount 36 is not on a sector boundary Message-ID: <20011118123743.A4903@panzer.kdm.org> In-Reply-To: <5.1.0.14.0.20011118114657.028455f8@mail.Go2France.com>; from LConrad@Go2France.com on Sun, Nov 18, 2001 at 11:47:03AM %2B0000 References: <5.1.0.14.0.20011118114657.028455f8@mail.Go2France.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 18, 2001 at 11:47:03 +0000, Len Conrad wrote: > FreeBSD 4.4 Release, dmesg is showing: > > ahc0: <Adaptec aic7899 Ultra160 SCSI adapter> port 0xdc00-0xdcff mem > 0xfeaff000-0xfeafffff irq 5 at device 5.0 on pci2 > aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs > ahc1: <Adaptec aic7899 Ultra160 SCSI adapter> port 0xd800-0xd8ff mem > 0xfeafe000-0xfeafefff irq 3 at device 5.1 on pci2 > aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/255 SCBs > pcib3: <ServerWorks host to PCI bridge> on motherboard > ... > da0: <SEAGATE ST318305LC 2202> Fixed Direct Access SCSI-3 device > da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing > Enabled > da0: 17366MB (35566478 512 byte sectors: 255H 63S/T 2213C) > Mounting root from ufs:/dev/da0s1a > dscheck(#da/2): b_bcount 36 is not on a sector boundary (ssize 512) > dscheck(#da/2): b_bcount 36 is not on a sector boundary (ssize 512) > dscheck(#da/2): b_bcount 36 is not on a sector boundary (ssize 512) > dscheck(#da/2): b_bcount 36 is not on a sector boundary (ssize 512) > dscheck(#da/2): b_bcount 36 is not on a sector boundary (ssize 512) > dscheck(#da/2): b_bcount 36 is not on a sector boundary (ssize 512) > > Is this hardware, driver ? > > This is a dedicated FreeBSD + postfix + Kaspersky + avcheck anti-virus mail > relay box. We can send 100's of msgs through it and no errors. We send > one msg with a virus attached, and the above error occurs. > > Form what I can find on google, this error seems related to SCSI driver, > but that was for FreeBSD 4.0, not 4.4. > > I'd appreciate some feedback. The client is on the verge of deciding > FreeBSD doesn't support his new Dell hardware. Something is attempting to do I/O to da0c that isn't a sector multiple in size. In general, this probably means that something is accessing the raw device, since the filesystem code shouldn't be doing I/O that isn't a sector multiple. Do you have some application that is doing raw I/O to the drive? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011118123743.A4903>