Hello! Sorry if I repeated. I have next problem with Samba 3.5.8 *Scenario:* - CentOS 5.5 - Mounted disk image with loop device to /mnt/.sharedDisk mount (output) /SharedDiskImage.img on /mnt/.sharedDisk type vfat (rw,noexec,nosuid,nodev,loop=/dev/loop0,uid=99) df -h (output) Filesystem Size Used Avail Use% Mounted on /SharedDiskImage.img 128M 128M 1.5K 100% /mnt/.sharedDisk - Avail 1.5K space - I was test with vfat, ext3, ext4 file system. Samba share /mnt/.sharedDisk folder. On my windows XP pc I map this share as network drive. In drive properties I see, avail only 1.5K free disk space However, I can open existed BMP image (10K size) with MS Paint, resize image and save. Paint alert me disk is full. Now my BMP image size is 54K, and corrupted. Why 54K if only 1.5K avail? Above example with MS Paint. If I use MS Wordpad in same scenario (Save more data than avail) Wordpad alert me in half of the cases. This problem is very important for me. I thinking, this problem with Paint and Wordpad and have been do some alternative test. I create virtual disk on local XP machine, and try same scenario, Paint and Wordpad works well. They alert about disk full and not rewrite early saved file. So, I don't loss saved file. Does it possible to solve this problem? Thanks Dmitry
From: Dmitry Mordovin <d.mordovin at dwide.com> Date: Fri, 01 Apr 2011 18:16:45 +0400> I have next problem with Samba 3.5.8(snip)> On my windows XP pc I map this share as network drive. > In drive properties I see, avail only 1.5K free disk space > > However, I can open existed BMP image (10K size) with MS Paint, resize > image and save. Paint alert me disk is full. > Now my BMP image size is 54K, and corrupted.I cannot reproduce your problem in my Samba 3.5.8 box. Anyway "strict allocate = yes" maybe solve your problem. --- TAKAHASHI Motonobu <monyo at monyo.com>
> I cannot reproduce your problem in my Samba 3.5.8 box. > > Anyway "strict allocate = yes" maybe solve your problem. > > --- > TAKAHASHI Motonobu<monyo at monyo.com>Hello I prepare 50MB disk image. The test.bmp file exists in the root of disk. Step 1: Mount image on same server where samba: Disk image here: http://www.2shared.com/file/WPs5R8Rk/disk_ext4.html mkdir /mnt/test_disk_ext4 mount -o loop disk_ext4.img /mnt/test_disk_ext4 Step 2: My smb.conf: [global] pid directory = /opt/samba/run lock directory = /opt/samba/cache private dir = /opt/samba/cache log file = /opt/samba/smbd.log log level = 0 workgroup = HOME server string = Home storage security = share load printers = no printcap name = /dev/null printing = bsd disable spoolss = yes enable spoolss = no show add printer wizard = no max log size = 102400 dns proxy = no allocation roundup size = 0 strict allocate = yes nt acl support = no bind interfaces only = true interfaces = eth0 smb ports = 139 socket options = SO_REUSEADDR TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE unix extensions = no nt pipe support = no map hidden = yes hide dot files = no [homes] browseable = yes printable = no [test] path = /mnt/test_disk_ext4 comment = "" read only = no guest ok = yes follow symlinks = no Step 3: Map shared "test" as network drive on your PC (Win XP in my case, Vista+ not tested) Step 4: To reproduce problem - just edit test.bmp (Right click, choose Edit), set new bigger image size and save. Paint must alert - disk space not enough / disk full. After all - test.bmp file not readable and file size increased. Thank you. Dmitry
From: Dmitry Mordovin <d.mordovin at dwide.com> Date: Mon, 04 Apr 2011 13:04:40 +0400> > I cannot reproduce your problem in my Samba 3.5.8 box. > > > > Anyway "strict allocate = yes" maybe solve your problem. > > Step 4: To reproduce problem - just edit test.bmp (Right click, choose > Edit), set new bigger image size and save. > Paint must alert - disk space not enough / disk full. > After all - test.bmp file not readable and file size increased.OK, I can reproduce your problem. Step 4 is important. Perhaps this may be a Samba bug. I recommend for you to post to Bugzilla with minimum set to reproduce and level10 log. My smb.conf: ----- [global] [mnt2] path =/mnt2/tmp writeable = yes ----- /mnt2 is an ext3 filesystem of 10MB size. I first create a 9MB file and put a 30KB bmp file. Open a 30KB bmp file, type PrintScreen and Paste the file and try to save. Save is failed as you said at Step 4 and problem occurs. --- TAKAHASHI Motonobu <monyo at samba.gr.jp>