Bug 3762 - fstype parameter in smb.conf
fstype parameter in smb.conf
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: File Services
3.0.14a
x86 FreeBSD
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-06 07:15 UTC by Vladimir
Modified: 2007-06-28 15:41 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir 2006-05-06 07:15:10 UTC
Very sorry for my bad english.
I have got a problem with Samba3.
I have installed Samba3.0.14a on FreeBSD 6.0 from ports with defaults parameters 
but without Active directory and CUPS support. All my data that would be shared 
is stored on FAT32 volume on second HDD, that's why I've decided to change 
parameter in "smb.conf" fstype = FAT32. When I start to test the server, I've 
found a problem: every file that is bigger than 32 kbytes that was copied on 
server from a LAN has been filled with garbage from 32768th byte (you can see 
it by comparing goodfile.doc & badfile.doc). I was trying to copy file from 
different computers with Win98, WinXP, Win2003, - the problems persists. 
Later I've deinstalled samba & install Samba3.0.22,1 from new port, - 
the problem persists. Then I changed fstype to default (NTFS) and problem 
has been solved.

May be I did something wrong (it is my first experience with Samba) ?


---smb.conf---
# Samba config file created using SWAT
# from 200.201.204.214 (200.201.204.214)
# Date: 2006/05/06 15:35:57

[global]
        dos charset = CP866
        unix charset = KOI8-R
        workgroup = ASU
        server string = Samba Server
        map to guest = Bad Password
        null passwords = Yes
        passwd program = /usr/bin/passwd %u
        unix password sync = Yes
        log file = /var/log/samba/log.%m
        max log size = 128
        max open files = 8192
        load printers = No
        disable spoolss = Yes
        show add printer wizard = No
        ldap ssl = no
        passdb expand explicit = No
        admin users = admin
        read list = admin
        write list = admin
        map readonly = no

[public]
        comment = Public file space
        path = /public/public
        read list = @nobody
        write list = @nobody
        read only = No
        guest ok = Yes
        fstype = FAT

[archive]
        comment = Archives
        path = /public/archive
        admin users =
        read list = @nobody
        write list = @staff
        read only = No
        guest ok = Yes
        fstype = FAT


Regards,
Vladimir Osipov

vlamios@yandex.ru
Comment 1 Timur Bakeyev 2007-06-03 08:22:19 UTC
(In reply to comment #0)
> Later I've deinstalled samba & install Samba3.0.22,1 from new port, - 
> the problem persists. Then I changed fstype to default (NTFS) and problem 
> has been solved.
> 
> May be I did something wrong (it is my first experience with Samba) ?

It's hard to believe, that fstype did actually change anything in the processing, unless Windows uses different set of command sto deall with remote NTFS and FAT systems.

From other side there were numerous reports that Samba3 has issues with FAT32, upto the crash of the FreeBSD box itself. Still have to be investigated.

With regards,
Timur