thanks so much for the reply..... On 12/2/06, andrelst <[EMAIL PROTECTED]> wrote:
Warren, It's a bit late, but here is my take. The samba list did not give you the answer because as you mentioned, it looks like an LVM issue rather than a samba one. No LVM snapshots, no issues. Increasing max. timeouts won't help you much because you are fixing the effect not the cause.
yes, no lvm snapshots no issues. i'm not really sure if this problem points to lvm or samba. I test using fc5 as client and the volume is under snapshot, no problem, file transfer is ok. but if i used winxp pro, then i got a problem. this happens only for large files like 500MB+ to me its the server who is cutting the connections, when the client sees that the other side is no longer there then it will report that the connection is no longer available. but why it will cut the connection? I am also thinking maybe the problem is on NIC, something like the socket buffers are choked up. the client is sending more data than the server can write into the device maybe because of the file system is too busy. To further digg deeper, what LVM version are using? LVM1 or LVM2?
Linux kernel and Linux distro are you using? what does "lvm version" say?
we actually upgraded to newer versions but still we have problems. LVM2 LVM version: 2.02.15 (2006-11-20) Library version: 1.02.13 (2006-11-28) Driver version: 4.10.0 Device mapper Library version: 1.02.13 (2006-11-28) Driver version: 4.10.0 kernel 2.6.19 smp LFS like distro, customize build linux (NAS) Search google and see what happens. In addition, have read in the past
that certain combination of Linux kernel versions amd dmand userland LVM utilities have performance issues and more. Another thing, snapshots on an LVM will slow down writes by 2x to 3x. Reads are fine though. It gets worse if your production LV(logical volume) and LV snapshot are on the same PV (physical Volume)! and that's probably what's happening here.
yes exactly, it will even slow down up to 50%+. There are lots of issues regarding lvm snapshots and performance, one solution is to put the snapshot on different PV. but to me samba or other file sharing protocols does not matter whats the speed of the underlying device. if the server is slow then it should reflect the speed of file transfer but not to the point that it will cut or lose the connection. What you can try to alleviate is add another HD(harddrive), let it be
part of the VG (Volume Group). Let the snapshot LV be on the new HD and the prod LV on the old HDD. But of course, both harddrive should be on the the same PV and VG. This way, writes are going to different HDD. But personally, it probably would not help much (Linux kernel is still managing the I/O.) but you can try.
--
regards, Andre | http://www.varon.ca On 11/29/06, Warren Beldad <[EMAIL PROTECTED]> wrote: > Hello mga kababayan, > > This is the mail that I submitted in the samba mailing list, walang gustong > sumagot.... maybe anyone has an idea how to solve it. > > ---------- > I have a problem when uploading file to samba server when the share's volume > is under lvm snapshot. I always got "The specified network name is no longer > available", this happens when uploading large files like 500MB and the > volume has a lvm snapshot(even 1 snapshot). If there are no snapshots, > everything is ok, I can transfer large files without problem. my client is > windows XP. > samba version 3.0.22 > > What would be the caused of this kind of problem? To me it looks like samba > is closing the connection, is this because of the file system busy because > of snapshot? I can see also in the log that samba connects to the same > service a lot of times until it reaches the max connection option, then I > need again to increase the maximum connections. I have here attached a log > file during user logon then transfer files until the connection problem. > > [global] > workgroup = VM2K-MIXED0 > realm = VM2K-MIXED.NET > server string = NAS > smb passwd file = /etc/sysconfig/sambad/smbpasswd > log level = 2 > log file = /var/log/samba > max log size = 300 > debug timestamp = No > socket options = TCP_NODELAY IPTOS_LOWDELAY > disable spoolss = Yes > os level = 8 > idmap uid = 10000-30000 > idmap gid = 10000-30000 > template homedir = /mnt/NAS/home/%D/%U > template shell = /bin/bash > winbind cache time = 15 > [share1] > comment = <new share description> > path = /mnt/NAS/share1/share1 > valid users = admin, @users > read only = No > security mask = 0760 > force security mode = 0760 > directory security mask = 0770 > force directory security mode = 0770 > max connections = 200 > case sensitive = No > volume = share1-nas > > level 2 log file------------- > > check_ntlm_password: authentication for user [admin] -> > [admin] -> [admin] > succeeded > warrenlt (192.168.100.170) connect to service share1 initially as user admin > (uid=500, gid=500) (pid 18058) > admin opened file 6.1-RELEASE-i386-disc1.iso read=No write=Yes (numopen=2) > netbios connect: name1=NAS164 name2=WARRENLT > netbios connect: local=nas164 remote=warrenlt, name type = 0 > Closing connections > setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all > old resources. > setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all > old resources. > check_ntlm_password: authentication for user [admin] -> > [admin] -> [admin] > succeeded > warrenlt (192.168.100.170) connect to service share1 initially as user admin > (uid=500, gid=500) (pid 18372) > Closing connections > admin closed file 6.1-RELEASE-i386-disc1.iso (numopen=0) > warrenlt (192.168.100.170) closed connection to service share1 > admin opened file 6.1-RELEASE-i386-disc1.iso read=Yes write=No (numopen=1) > admin closed file 6.1-RELEASE-i386-disc1.iso (numopen=0) > admin opened file 6.1-RELEASE-i386-disc1.iso read=No write=No (numopen=1) > admin closed file 6.1-RELEASE-i386-disc1.iso (numopen=0) > warrenlt (192.168.100.170) closed connection to service share1 > > thanks, > warren > > > > > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > [email protected] (#PLUG @ irc.free.net.ph) > Read the Guidelines: http://linux.org.ph/lists > Searchable Archives: http://archives.free.net.ph > > _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
