Bug 6972 - not enough disk space when sharing ntfs mounted partitions
not enough disk space when sharing ntfs mounted partitions
Status: NEW
Product: Samba 3.4
Classification: Unclassified
Component: File services
3.4.0
x86 Linux
: P3 normal
: ---
Assigned To: Björn Jacke
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-07 11:50 UTC by Roozbeh Gh
Modified: 2013-02-09 20:56 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 Roozbeh Gh 2009-12-07 11:50:26 UTC
It seems to be a bug related to samba(or maybe ntfs), i just don know exactly.

I try to share my /media/MEDIA mount point (which is a ntfs-3g) to my lan clients.
but they can not copy files into subdirectories of folders.
copying files into root of this partition is ok.
creating directories eveywhere is ok.
copying small files sizes(<1~2KB) is also to eveywhere is ok.
copying bigger files to subdirectories give, not enough disk space error in windows xp.


my host os is ubuntu 9.1(samba installed by default, exact version is 2:3.4.0-3ubuntu5.1) and clients are windows xp sp3.

here is my smb.conf

#======================= Global Settings =======================
[global]
	log file = /var/log/samba/log.%m # logfile
	netbios name = linux-mint 
	server string = linux-mint
	workgroup = WORKGROUP
	os level = 20
	syslog = 0
	max log size = 1000 # logfile max size


## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of

# server string is the equivalent of the NT Description field


#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects

# Put a capping on the size of the log files (in Kb).

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.

# Do something sensible when Samba crashes: mail the admin a backtrace

####### Authentication #######

;	passdb backend = tdbsam


# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).

############ Misc ############

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
;	socket options = tcp_nodelay

#======================= Share Definitions =======================


[DriveD]
	path = /media/MEDIA
        public = yes
	writeable = yes
	locking = no
;	browseable = yes
;	valid users = anybody
	directory mask = 0666
	create mask = 0666
	guest ok = yes
	case sensitive = no
	msdfs = no

[DriveC]
	writeable = yes
	locking = no
	public = yes
	path = /media/WIN98
	directory mask = 0666
	create mask = 0666

-----

here is my fstab
# /etc/fstab: static file system information.
#
#  -- This file has been automaticly generated by ntfs-config -- 
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc /proc proc defaults 0 0
# Entry for /dev/sdb1 :
UUID=afa0c5b6-3b59-41d2-a57e-042a53f6ab43 / ext4 errors=remount-ro 0 1
# Entry for /dev/sdb5 :
UUID=2b5eda05-3ad8-4122-9233-606e34d59a72 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
/dev/sda6 /media/PROGRAMMING ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sda5 /media/MEDIA ntfs-3g defaults,umask=0000,locale=en_US.UTF-8 0 0
/dev/sda1 /media/WIN98 vfat defaults,auto,rw,umask=0000 0 0

thanks
Comment 1 Roozbeh Gh 2009-12-07 12:26:22 UTC
also to make sure it is not ntfs-3g problem i also checked it with ntfs package, and i still get the same error.

i dont know if there are any log messages required to be posted here, if so let me know.
Comment 2 Björn Jacke 2013-02-09 20:54:08 UTC
can u retry with 3.6 or 4.0 and attach a level 10 log if it still fails?