PDA

View Full Version : [ubuntu] 10.04 - Samba - Error: There is not enough free disk space



squiggie
April 22nd, 2010, 04:48 PM
I have recently upgraded to 10.04 alpha2. I have an external ntfs hard drive that I use for media storage. In Jaunty, I had this drive mounted with ntfs-3g and could read and write to it from my Windows laptop.

Now, I have mounted this drive in 10.04 and have rw access to it from within the machine itself i.e. I can move files around from the console etc... but when I try to write something to the share from my windows laptop, I get the following error:

Cannot copy [filename]: There is not enough free disk space. Delete one or more files to free disk space and then try again.

Here is df showing I have enough disk space. Also, I can copy the same file to my home directory which is also shared and them mv it through the console to the storage ntfs drive with no problem.

/dev/sdc1 488384000 416883568 71500432 86% /media/storage


Here is a copy of my smb.conf file.

[global]

## Browsing/Identification ###

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

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# 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.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d


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

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# 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).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

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

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# 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

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

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

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
[homes]
comment = Home Directories
browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
read only = no

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = yes
path = /var/spool/samba
printable = yes
guest ok = yes
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = yes
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin

#Storage
[storage]
comment = Storage
read only = no
locking = no
path = /media/storage
guest ok = no
If i look at samba and syslog at the time of the error there is nothing in these logs to speak of. I'm at a loss as what to check next. Any help would be appreciated.

squiggie
April 24th, 2010, 04:07 PM
Bump for suggestions

Morbius1
April 24th, 2010, 05:28 PM
Consider this a bump because I don't see any errors in your smb.conf.

That Windows error:

Cannot copy [filename]: There is not enough free disk space. Delete one or more files to free disk space and then try again.is exactly the error you would receive if you tried to save a file > 4GB to a FAT32 partition. Very strange.

If it were a linux file permissions problem on /media/Storage you'd get a different error.

plus2plus
April 24th, 2010, 05:33 PM
Consider this a bump because I don't see any errors in your smb.conf.

I too agree with him. No error found. :P

djchandler
April 24th, 2010, 06:29 PM
It's possibly a permissions conflict in the smb.conf file. Under Authentication you have:

map to guest = bad userThen under Misc you have:

usershare allow guests = yesAnd finally under Storage you have:

guest ok = noIn Misc try putting a semicolon or # in front of

usershare allow guests = yesand restart samba and see if your problem goes away.

Samba is confused by the conflicting permissions and giving you a bogus error message, probably due to improper error trapping.

I use system-config-samba to create my smb.conf files now. I haven't had a problem since I started doing that instead of editing by hand. Those little semicolons are easy to miss, or in this case, not miss.

I have recently upgraded to 10.04 alpha2.BTW, the 10.04 release candidate is available now, and beta 2 for 2 weeks before that. What do you mean by "recently?";)

Morbius1
April 24th, 2010, 07:06 PM
You need map to guest = bad user ( despite it's ominous name :wink:)or else you'll never be able to convert an non-authenticated remote user to a "guest"

usershare allow guests = yes enables nautilus-share ( Nautilus > Right Click > Sharing Options ) to allow setting "guest access" to a share. He's not using Nautilus-share he's using Classic-share but that specific parameter has no influence on that share definition in smb.conf.

These are not conflicting parameters and both parametes are the default settings.

squiggie
May 5th, 2010, 09:32 PM
I've tried a few additional things with no results. I've tried enabling guests by changing guest ok = yes in the storage section but that didn't help.

I'm soon going to be getting a new hdd and will be formatting it to ext which will more than likely resolve the issue, but I will also need to still be able to write to this drive and I don't want to have to format is to ext since it is an external usb drive that I will likely be moving from linux to windows systems occasionally. Any more suggestions?

toker_tok
August 11th, 2010, 01:51 AM
I ran into this problem, and my problem was i could not write from the windows computers to the samba share hosted on the server. The share was located on a mounted ntfs volume on the server. It turns out the volume was on an extended partition. I have another ntfs partition on the server which is primary, and it worked with that. So after some reformatting, I made the ntfs volume on the extended partition a primary partition and it works...don't know why this is the case, but i thought i will share my solution.

squiggie
August 11th, 2010, 02:39 PM
Thanks for the reply. I did end up formatting this drive to ext3 which allowed unix permissions which resolved the problem. I guess since it was an ntfs partition, ubuntu, or the ntfs driver rather, had a hard time writing to it and getting permissions correct. After I formatted, everything worked fine.