Is there a known problem in 5.2.1 while exporting Fat32 via samba?
Something like kern/39043?

I wrote a long question on freebsd-questions but I had no answers. No luck
with the samba list either. Am I the only one seeing this? I would think a
file corruption issue would at least receive a nod... I'd hate to abandon
freebsd for this project, but I have no other option since I can't juggle
the disk space to convert this drive to UFS (I don't suppose there is an
in-place convert?)

Help?

Here's the message I posted:

----

Hi,

Is there any status on bug kern/39043? I think I'm experiencing the same
problem, but under 5.2.1. The bug was written against 4.6 but it does not
seem to have been closed for 2 years (if I'm reading it correctly.. I'm not
very familiar with the bug database). But I'm asking here as opposed to the
samba mailing list since the bug report seems to be pointing the finger at a
kernel bug.

Symptoms:

I installed FreeBSD 5.2.1 then samba 3.0.4 from source (I was unable to
install the samba 3.0.x from ports, it keeps failing with ec = -1).

By default I was getting the following message in /var/log/messages:

May 30 14:24:21 mbox kernel: kern.maxpipekva exceeded, please see

tuning(7)

so I added:

kern.ipc.maxpipekva=16222976

to the defaults. Don't know what the value should've been, but at least this
fixes the message. I attached an older 80GB drive as /library.

I created 10 files in notepad on windows XP Pro. They are just text files,
with the sequence 0-9 repeated six times per line, then repeated for about
200,000 lines, giving me 10 identical files of about 16 mb. Exported my fat
drive as /fat, and my /tmp drive as /ufs. Ran a copy from windows:

copy testfile* \\computername\fat

and

copy testfile* \\computername\ufs

in my tmp, the ten files were identical. on my fat drive, none of the ten
files were identical to each other. The size was the same, but the data
inside was scrambled, after a few correct blocks at the beginning. Using the
/V flag on xcopy didn't signal any errors, but doing an fc /b after the copy
from the windows machine showed a lot of differences. There were no errors
while copyin to the ufs share, but coping to the fat share I get tons of the
following in the samba.machine log:

[2004/06/02 00:41:53, 0] locking/posix.cosix_fcntl_lock(657)

posix_fcntl_lock: WARNING: lock request at offset 0, length
92233720368547758\

08 returned

[2004/06/02 00:41:53, 0] locking/posix.cosix_fcntl_lock(658)

an Invalid argument error. This can happen when using 64 bit lock offsets

[2004/06/02 00:41:53, 0] locking/posix.cosix_fcntl_lock(659)

on 32 bit NFS mounted file systems.

[2004/06/02 00:41:53, 0] locking/posix.cosix_fcntl_lock(673)

Count greater than 31 bits - retrying with 31 bit truncated length.

[2004/06/02 00:41:54, 0] locking/posix.cosix_fcntl_lock(657)

posix_fcntl_lock: WARNING: lock request at offset 0, length 16580 returned

[2004/06/02 00:41:54, 0] locking/posix.cosix_fcntl_lock(658)

an Invalid argument error. This can happen when using 64 bit lock offsets

[2004/06/02 00:41:54, 0] locking/posix.cosix_fcntl_lock(659)

on 32 bit NFS mounted file systems.

[2004/06/02 00:41:54, 0] locking/posix.cosix_fcntl_lock(657)

posix_fcntl_lock: WARNING: lock request at offset 16580, length 16580
returne\ D

Note that I'm not using NFS at all. This is a 32-bit machine. NFSCLIENt and
NFSSERver is commented out in the kernel config file.

I am also curious to know if this bug would affect updates to files, or just
copies. Some of the files were updated over the share. I'm not sure if I
trust the updates, but I can't visually inspect 60GB of data looking for
anomalies.

TIA...

FWIW, my fstab and dmesg follows. The drive passed rom-based diagnostics.

/etc/fstab:

# Device Mountpoint FStype Options Dump

Pass#

/dev/ad0s1b none swap sw 0 0

/dev/ad0s1a / ufs rw 1 1

/dev/ad0s1d /tmp ufs rw 2 2

/dev/ad0s1f /usr ufs rw 2 2

/dev/ad0s1e /var ufs rw 2 2

/dev/acd0 /cdrom cd9660 ro,noauto 0 0

/dev/ad1s1 /library msdosfs rw,-u=1012,-g=1012

\

2 2



Copyright (c) 1992-2004 The FreeBSD Project.

Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

The Regents of the University of California. All rights reserved.

FreeBSD 5.2.1-RELEASE #0: Sat May 29 09:11:27 CDT 2004

root@testbox:/usr/obj/usr/src/sys/mbox

Preloaded elf kernel "/boot/kernel/kernel" at 0xc0815000.

Timecounter "i8254" frequency 1193182 Hz quality 0

CPU: Intel Pentium III (863.87-MHz 686-class CPU)

Origin = "GenuineIntel" Id = 0x683 Stepping = 3

Features=0x383fbff
CMOV,PAT,PSE36,MMX,FXSR,SSE>

real memory = 267386880 (255 MB)

avail memory = 250081280 (238 MB)

MPTable:

ioapic0: Changing APIC ID to 8

ioapic0: Assuming intbase of 0

ioapic0 irqs 0-23 on motherboard Pentium Pro MTRR support
enabled

npx0: [FAST]

npx0: on motherboard

npx0: INT 16 interface

pcibios: BIOS version 2.10

Using $PIR table, 10 entries at 0xc00e8810

pcib0: at pcibus 0 on motherboard

pci0: on pcib0

pcib0: slot 2 INTA routed to irq 16

pcib0: slot 31 INTC routed to irq 23

pcib0: slot 31 INTB routed to irq 17

agp0: mem
0x40500000-0x4057ffff,0x44000000-0x47ffffff irq 16 at device 2.0 on pci0

pcib1: at device 30.0 on pci0

pci2: on pcib1

pcib1: slot 8 INTA routed to irq 20

pcib1: slot 11 INTA routed to irq 22

fxp0: port 0x1000-0x103f mem
0x40100000-0x40100fff irq 20 at device 8.0 on pci2

fxp0: Ethernet address 00:02:a5:00:b2:ad

miibus0: on fxp0

inphy0: on miibus0

inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

fxp1: port 0x1040-0x107f mem
0x40000000-0x400fffff,0x40200000-0x40200fff irq 22 at device 11.0 on pci2

fxp1: Ethernet address 00:d0:b7:b1:59:ab

miibus1: on fxp1

inphy1: on miibus1

inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

isab0: at device 31.0 on pci0

isa0: on isab0

atapci0: port 0x2460-0x246f at device 31.1
on pci0

ata0: at 0x1f0 irq 14 on atapci0

ata0: [MPSAFE]

ata1: at 0x170 irq 15 on atapci0

ata1: [MPSAFE]

uhci0: port 0x2440-0x245f
irq 23 at device 31.4 on pci0

usb0: on uhci0

usb0: USB revision 1.0

uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1

uhub0: 2 ports with 2 removable, self powered

pcm0: port 0x2400-0x243f,0x2000-0x20ff irq 17 at
device 31.5 on pci0

pcm0:

orm0: