Hi,
Is there a known issue with FreeBSD 5.2.1 and Samba 3.0.4?
I am getting file corruption when copying to a local FAT32 drive (mounted
under FBSD) from a Windows XP Pro workstation. There doesn't seem to be any
pattern in the corruption. If I mount an UFS drive, everthing is fine. I'd
also like to find out if the corruption would also have affected file
updates, and not just new file copies.
I have posted a more detailed question on the fbsd mailing list, but no
answers yet.
http://groups.google.com/groups?selm=1086168229.00060891.1086156006%4010.7.7
.3
<http://groups.google.com/groups?selm=1086168229.00060891.1086156006%4010.7.
7.3&output=gplain> &output=gplain
I am getting the following error messages, which go away if I set posix
locks = no, but the corruption doesn't go away. I'm not using NFS at
all,
and the drive is local. In fact, NFS is not even compiled in this kernel.
I'm on a 32-bit system.
2004/06/02 00:41:53, 0] locking/posix.c:posix_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.c:posix_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.c:posix_fcntl_lock(659)
on 32 bit NFS mounted file systems.
[2004/06/02 00:41:53, 0] locking/posix.c:posix_fcntl_lock(673)
Count greater than 31 bits - retrying with 31 bit truncated length.
[2004/06/02 00:41:54, 0] locking/posix.c:posix_fcntl_lock(657)
posix_fcntl_lock: WARNING: lock request at offset 0, length 16580 returned
[2004/06/02 00:41:54, 0] locking/posix.c:posix_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.c:posix_fcntl_lock(659)
on 32 bit NFS mounted file systems.
[2004/06/02 00:41:54, 0] locking/posix.c:posix_fcntl_lock(657)
posix_fcntl_lock: WARNING: lock request at offset 16580, length 16580
returne\ D
