[Samba] File System Size Limits?
lx
lx at survive-linux.com
Fri Jun 24 18:43:59 GMT 2005
try making an ls -al on /opt/
does the folder data exist?
sometimes it is the permission which fail
i got the same setup -> FC4 SMB
but i got 840 GB Raid 5 with encrypted lvm
should work
Harold Pritchett schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Is there some limit on the size of a file system which can
> be shared via samba? I'm trying to set up a file server
> with a 100GB shared partition and it doesn't want to work.
>
> I'm running Fedora Core 4, and Samba Version 3.0.14a-2.
>
> The output from testparm looks like this:
>
> [root at stitch samba]# testparm
> Load smb config files from /etc/samba/smb.conf
> Processing section "[homes]"
> Processing section "[printers]"
> Processing section "[haldisk]"
> Loaded services file OK.
> Server role: ROLE_STANDALONE
> Press enter to see a dump of your service definitions
>
> # Global parameters
> [global]
> workgroup = HOME
> server string = Stitch
> null passwords = Yes
> log level = 1
> log file = /var/log/samba/%m.log
> max log size = 50
> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
> domain master = Yes
> dns proxy = No
> idmap uid = 16777216-33554431
> idmap gid = 16777216-33554431
> hosts allow = 192.168.1., 127.
> cups options = raw
>
> [homes]
> comment = Home Directories
> read only = No
> browseable = No
>
> [printers]
> comment = All Printers
> path = /var/spool/samba
> printable = Yes
> browseable = No
>
> [haldisk]
> path = /opt/data
> write list = harold
> read only = No
> guest ok = Yes
>
> This works OK. the /opt filesystem is only 5 Gb in size. If I
> simply change the line "path = /opt/data" to "path = /bigdisk/data"
> where the /bigdisk file system is 100GB is size, and restart smb,
> all attempts to connect to the file system give the following
> error on the windows box (smb name is piglet)
>
> "\\stitch\haldisk is not accessable"
> "The Network Name cannot be found"
>
> and the following errors appear in /var/log/samba/piglet.log
> [2005/06/24 10:15:58, 0] lib/util_sock.c:read_socket_data(384)
> read_socket_data: recv failure for 4. Error = Connection reset by
> peer
> [2005/06/24 10:15:58, 0] smbd/service.c:make_connection_snum(615)
> '/bigdisk/data' does not exist or is not a directory, when
> connecting to [haldisk]
> [2005/06/24 10:15:58, 0] smbd/service.c:make_connection_snum(615)
> '/bigdisk/data' does not exist or is not a directory, when
> connecting to [haldisk]
> [2005/06/24 10:15:58, 0] smbd/service.c:make_connection_snum(615)
> '/bigdisk/data' does not exist or is not a directory, when
> connecting to [haldisk]
>
> (log level = 1, anything higher and I get far too many message to
> digest)
>
> The file systems in question look like this:
>
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/hda2 505636 146754 332777 31% /
> /dev/hdc1 505604 14287 465213 3% /boot
> none 517732 0 517732 0% /dev/shm
> /dev/mapper/VG0-LV00 5160576 2205760 2692672 46% /usr
> /dev/mapper/VG0-LV01 1032088 218100 761560 23% /var
> /dev/mapper/VG0-LV02 507748 10555 470979 3% /tmp
> /dev/mapper/VG0-LV04 507748 10572 470962 3% /usr/local
> /dev/mapper/VG0-LV05 5160576 43652 4854780 1% /home
> /dev/mapper/VG0-LV06 5160576 43056 4855376 1% /opt
> /dev/mapper/VG0-LV07 101573920 94280 96236760 1% /bigdisk
>
> Hardware consists of two 200Gb Western Digital drives in a
> software raid1 configuration. The Linux LVM is used to create
> the file systems on the defined raid device.
>
> I have spent the last two days searching the web for anything which
> might explain this. Any ideas why this strange behavior? Anything
> else you need to see?
>
> Thanks for any help you can provide.
>
> Harold
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.1 - not licensed for commercial use: www.pgp.com
>
> iQA/AwUBQrwhHy1Q3vInf5sREQIilgCcCTRadqS2pP6Rt0iqx1jLNW9Il7AAoOUT
> 1Raxiqtx+nvBRFgkRFHw/mE3
> =FcMf
> -----END PGP SIGNATURE-----
>
More information about the samba
mailing list