From: Ewan G. <ewa...@gm...> - 2005-08-12 16:21:09
|
I have been slowly gaining confidence in running my coLinux-based RAID array. Transferring large files. Yes, verily. Playing back videos without skipping or pauses. You bet. Writing to an array at the same time I'm playing from it and still holding up. Sure thing. So last night I decided to try the ACID test of any hard drive on my system - capturing a DV from the camcorder direct to an array. I should point out that when I was running native Linux on a somewhat slower machine, this would ONLY work with a RAID array. You're feeding in 13 gigs of data an hour, and you will notice drop outs and such. In any event, I tried a couple different programs, and even went to the trouble of disk caching the drives under windows, and still kept having a problem where right at 2GB, I'd get a "Delayed Write Error" from Windows, and then that would be it. Since the cobd files are on NTFS partitions, I don't understand why that would be a problem. Since I copied much larger files back and forth when I was first setting up, I am particularly puzzled. However, since this exercises different channels, there could be something about how Windows deals with Samba that could be causing the problem. So, am wondering if anyone here has any ideas about what might be "magic" about 2GB, and if there's anything I can do short of a strategic retreat? TIA, Ewan |
From: Daniel S. <dan...@ya...> - 2005-08-12 16:40:00
|
You mentioned Samba. Are you using the latest version? I seem to vaguely remember that earlier versions of Samba had trouble with files larger than 2GB. Dan > -----Original Message----- > From: col...@li... [mailto:colinux-users- > ad...@li...] On Behalf Of Ewan Grantham > Sent: Friday, August 12, 2005 12:21 PM > To: col...@li... > Subject: [coLinux-users] Anything special about 2 Gigs via DV? > > I have been slowly gaining confidence in running my coLinux-based RAID > array. Transferring large files. Yes, verily. Playing back videos > without skipping or pauses. You bet. Writing to an array at the same > time I'm playing from it and still holding up. Sure thing. > > So last night I decided to try the ACID test of any hard drive on my > system - capturing a DV from the camcorder direct to an array. I > should point out that when I was running native Linux on a somewhat > slower machine, this would ONLY work with a RAID array. You're feeding > in 13 gigs of data an hour, and you will notice drop outs and such. > > In any event, I tried a couple different programs, and even went to > the trouble of disk caching the drives under windows, and still kept > having a problem where right at 2GB, I'd get a "Delayed Write Error" > from Windows, and then that would be it. Since the cobd files are on > NTFS partitions, I don't understand why that would be a problem. Since > I copied much larger files back and forth when I was first setting up, > I am particularly puzzled. However, since this exercises different > channels, there could be something about how Windows deals with Samba > that could be causing the problem. > > So, am wondering if anyone here has any ideas about what might be > "magic" about 2GB, and if there's anything I can do short of a > strategic retreat? > > TIA, > Ewan > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Ewan G. <ewa...@gm...> - 2005-08-12 18:02:40
|
Version 3.0.14a-3. I gather there's a slightly newer version, but the changelog for it doesn't say anything one way or the other about this. I suppose I can try to upgrade to that version and see what happens... Though I get a bit nervous about doing that considering what it would take to roll back if I ran into other issues. On 8/12/05, Daniel Slater <dan...@ya...> wrote: > You mentioned Samba. Are you using the latest version? I seem to vaguely > remember that earlier versions of Samba had trouble with files larger tha= n > 2GB. >=20 > Dan >=20 > > -----Original Message----- > > From: col...@li... [mailto:colinux-users- > > ad...@li...] On Behalf Of Ewan Grantham > > Sent: Friday, August 12, 2005 12:21 PM > > To: col...@li... > > Subject: [coLinux-users] Anything special about 2 Gigs via DV? > > > > I have been slowly gaining confidence in running my coLinux-based RAID > > array. Transferring large files. Yes, verily. Playing back videos > > without skipping or pauses. You bet. Writing to an array at the same > > time I'm playing from it and still holding up. Sure thing. > > > > So last night I decided to try the ACID test of any hard drive on my > > system - capturing a DV from the camcorder direct to an array. I > > should point out that when I was running native Linux on a somewhat > > slower machine, this would ONLY work with a RAID array. You're feeding > > in 13 gigs of data an hour, and you will notice drop outs and such. > > > > In any event, I tried a couple different programs, and even went to > > the trouble of disk caching the drives under windows, and still kept > > having a problem where right at 2GB, I'd get a "Delayed Write Error" > > from Windows, and then that would be it. Since the cobd files are on > > NTFS partitions, I don't understand why that would be a problem. Since > > I copied much larger files back and forth when I was first setting up, > > I am particularly puzzled. However, since this exercises different > > channels, there could be something about how Windows deals with Samba > > that could be causing the problem. > > > > So, am wondering if anyone here has any ideas about what might be > > "magic" about 2GB, and if there's anything I can do short of a > > strategic retreat? > > > > TIA, > > Ewan > > > > > > ------------------------------------------------------- > > SF.Net email is Sponsored by the Better Software Conference & EXPO > > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > > Practices > > Agile & Plan-Driven Development * Managing Projects & Teams * Testing &= QA > > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5= sf > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users >=20 > |
From: Ewan G. <ewa...@gm...> - 2005-08-12 18:28:54
|
Upon further investigation, it looks like the problem might be that the kernel that gets built using the usual coLinux diff doesn't include the CIFS file system. I'm not entirely certain if just adding that will take care of the problem, or if there's more magic I need to use, but it looks like that will certainly be part of it. Anyone else who had implemented this who has some advice? On 8/12/05, Ewan Grantham <ewa...@gm...> wrote: > Version 3.0.14a-3. I gather there's a slightly newer version, but the > changelog for it doesn't say anything one way or the other about this. > I suppose I can try to upgrade to that version and see what happens... > Though I get a bit nervous about doing that considering what it would > take to roll back if I ran into other issues. |
From: Ewan G. <ewa...@gm...> - 2005-08-12 22:43:53
|
Well, I rebuilt my kernel with CIFS built in, rebooted and did the remove and install driver, and started trying again. Same problem. Any idea if there's something i need to do to get Samba to use CIFS rather than SMBFS? Assuming that's even the problem? TIA, Ewan On 8/12/05, Ewan Grantham <ewa...@gm...> wrote: > Upon further investigation, it looks like the problem might be that > the kernel that gets built using the usual coLinux diff doesn't > include the CIFS file system. I'm not entirely certain if just adding > that will take care of the problem, or if there's more magic I need to > use, but it looks like that will certainly be part of it. >=20 > Anyone else who had implemented this who has some advice? >=20 > On 8/12/05, Ewan Grantham <ewa...@gm...> wrote: > > Version 3.0.14a-3. I gather there's a slightly newer version, but the > > changelog for it doesn't say anything one way or the other about this. > > I suppose I can try to upgrade to that version and see what happens... > > Though I get a bit nervous about doing that considering what it would > > take to roll back if I ran into other issues. > |
From: Holger K. <hol...@gm...> - 2005-08-12 23:26:24
|
> So, am wondering if anyone here has any ideas about what might be > "magic" about 2GB, and if there's anything I can do short of a > strategic retreat? Maybe Samba tries to use sendfile and it breaks? Some samba version had use sendfile as default. Try use sendfile = no in smb.conf. |
From: Ewan G. <ewa...@gm...> - 2005-08-15 13:00:08
|
Before I totally give up on this, is there any chance that the problem is not in Samba, but is rather an issue with COBD files? IOW, is there anything in the COBD mechanism that would need to be changed/tuned to get it to accept a capture greater than 2 gigs? TIA, Ewan |
From: Holger K. <hol...@gm...> - 2005-08-15 13:27:14
|
Ewan Grantham schrieb: > Before I totally give up on this, is there any chance that the problem > is not in Samba, but is rather an issue with COBD files? IOW, is there > anything in the COBD mechanism that would need to be changed/tuned to > get it to accept a capture greater than 2 gigs? I'm not sure. But to my understanding the COBD layer knows nothing about files. It transfers data blocks. If the 2 Gig problem persists with different transport mechanisms (ftp, webdav, nfs, netcat ) i would assume COBD to be broken. But i believe it is more likely a samba problem. Another configuration that can make 2 or 4 gig barriers is the parameter fstype. Should be fstype = ntfs. Post your smb.conf |
From: Ewan G. <ewa...@gm...> - 2005-08-15 13:42:42
|
Again, am running version 3.0.14a of Samba. My smb.conf is below: # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options most of which=20 # are not shown in this example # # Any line which starts with a ; (semi-colon) or a # (hash)=20 # is a comment and is ignored. In this example we will use a # # for commentary and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command # "testparm" to check that you have not many any basic syntactic=20 # errors.=20 # #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Glob= al Settings =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D [global] ## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part o= f workgroup =3D FAMLAN # server string is the equivalent of the NT Description field server string =3D %h server (Samba %v) # Windows Internet Name Serving Support Section: # WINS Support - Tells the NMBD component of Samba to enable its WINS Serve= r ; wins support =3D 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 =3D w.x.y.z # If we receive WINS server info from DHCP, override the options above.=20 include =3D /etc/samba/dhcp.conf # This will prevent nmbd to search for NetBIOS names through DNS. dns proxy =3D no # What naming service and in what order should we use to resolve host names # to IP addresses ; name resolve order =3D lmhosts host wins bcast #### Debugging/Accounting #### # This tells Samba to use a separate log file for each machine # that connects log file =3D /var/log/samba/log.%m # Put a capping on the size of the log files (in Kb). max log size =3D 1000 # If you want Samba to only log through syslog then set the following # parameter to 'yes'. ; syslog only =3D no # We want Samba to log a minimum amount of information to syslog. Everythin= g # 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 =3D 0 # Do something sensible when Samba crashes: mail the admin a backtrace panic action =3D /usr/share/samba/panic-action %d ####### Authentication ####### # "security =3D user" is always a good idea. This will require a Unix accou= nt # in this server for every user accessing the server. See # /usr/share/doc/samba-doc/htmldocs/ServerType.html in the samba-doc # package for details. security =3D share # You may wish to use password encryption. See the section on # 'encrypt passwords' in the smb.conf(5) manpage before enabling. encrypt passwords =3D true # If you are using encrypted passwords, Samba will need to know what # password database type you are using. =20 passdb backend =3D tdbsam guest obey pam restrictions =3D yes ; guest account =3D nobody ; invalid users =3D root # 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 =3D no # For Unix password sync to work on a Debian GNU/Linux system, the followin= g # parameters must be set (thanks to Augustin Luton <al...@hy...> = for # sending the correct chat script for the passwd program in Debian Potato). passwd program =3D /usr/bin/passwd %u passwd chat =3D *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n . # 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 =3D no ######## File sharing ######## # Name mangling options ; preserve case =3D yes ; short preserve case =3D yes ############ 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 =3D /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/speed.html # for details # You may want to add the following on a Linux system: SO_RCVBUF=3D8192 SO_SNDBUF=3D8192 socket options =3D 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 =3D /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 =3D auto # Some defaults for winbind (make sure you're not using the ranges # for something else.) ; idmap uid =3D 10000-20000 ; idmap gid =3D 10000-20000 ; template shell =3D /bin/bash #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Shar= e Definitions =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D [homes] comment =3D Home Directories browseable =3D no # By default, the home directories are exported read-only. Change next # parameter to 'yes' if you want to be able to write to them. writable =3D no # File creation mask is set to 0700 for security reasons. If you want to # create files with group=3Drw permissions, set next parameter to 0775. create mask =3D 0700 # Directory creation mask is set to 0700 for security reasons. If you want = to # create dirs. with group=3Drw permissions, set next parameter to 0775. directory mask =3D 0700 # Un-comment the following and create the netlogon directory for Domain Log= ons # (you need to configure Samba to act as a domain controller too.) ;[netlogon] ; comment =3D Network Logon Service ; path =3D /home/samba/netlogon ; guest ok =3D yes ; writable =3D no ; share modes =3D no [printers] comment =3D All Printers browseable =3D no path =3D /tmp printable =3D yes public =3D no writable =3D no create mode =3D 0700 # Windows clients look for this share name as a source of downloadable # printer drivers [print$] comment =3D Printer Drivers path =3D /var/lib/samba/printers browseable =3D yes read only =3D yes guest ok =3D no # Uncomment to allow remote administration of Windows print drivers. # Replace 'ntadmin' with the name of the group your admin users are # members of. ; write list =3D root, @ntadmin # A sample share for sharing your CD-ROM with others. ;[cdrom] ; comment =3D Samba server's CD-ROM ; writable =3D no ; locking =3D no ; path =3D /cdrom ; public =3D yes [usr_src] path =3D /usr/src public =3D yes writable =3D yes browsable =3D yes create mode =3D 0777 directory mode =3D 0777 guest ok =3D yes [md0] path =3D /mnt/md0 public =3D yes writable =3D yes browsable =3D yes create mode =3D 0777 directory mode =3D 0777 guest ok =3D yes [md1] path =3D /mnt/md1 public =3D yes writable =3D yes browsable =3D yes create mode =3D 0777 directory mode =3D 0777 guest ok =3D yes On 8/15/05, Holger Krull <hol...@gm...> wrote: > Ewan Grantham schrieb: >=20 > > Before I totally give up on this, is there any chance that the problem > > is not in Samba, but is rather an issue with COBD files? IOW, is there > > anything in the COBD mechanism that would need to be changed/tuned to > > get it to accept a capture greater than 2 gigs? >=20 > I'm not sure. > But to my understanding the COBD layer knows nothing about files. It tran= sfers data blocks. If the 2 Gig problem persists with different transport m= echanisms (ftp, webdav, nfs, netcat ) i would assume COBD to be broken. But= i believe it is more likely a samba problem. >=20 > Another configuration that can make 2 or 4 gig barriers is the parameter = fstype. > Should be fstype =3D ntfs. > Post your smb.conf >=20 > |
From: Holger K. <hol...@gm...> - 2005-08-15 13:56:52
|
Nothing unusual with this conf. Did you try use sendfile = no? Post testparm -v please > workgroup = FAMLAN > server string = %h server (Samba %v) > include = /etc/samba/dhcp.conf > log file = /var/log/samba/log.%m > max log size = 1000 > syslog = 0 > panic action = /usr/share/samba/panic-action %d > security = share > encrypt passwords = true > passdb backend = tdbsam guest > obey pam restrictions = yes > passwd program = /usr/bin/passwd %u > passwd chat = *Enter\snew\sUNIX\spassword:* %n\n > *Retype\snew\sUNIX\spassword:* %n\n . > > SO_RCVBUF=8192 SO_SNDBUF=8192 > socket options = TCP_NODELAY > > [homes] > comment = Home Directories > browseable = no > writable = no > create mask = 0700 > directory mask = 0700 > > [printers] > comment = All Printers > browseable = no > path = /tmp > printable = yes > public = no > writable = no > create mode = 0700 > > [print$] > comment = Printer Drivers > path = /var/lib/samba/printers > browseable = yes > read only = yes > guest ok = no > [usr_src] > path = /usr/src > public = yes > writable = yes > browsable = yes > create mode = 0777 > directory mode = 0777 > guest ok = yes > > [md0] > path = /mnt/md0 > public = yes > writable = yes > browsable = yes > create mode = 0777 > directory mode = 0777 > guest ok = yes > > [md1] > path = /mnt/md1 > public = yes > writable = yes > browsable = yes > create mode = 0777 > directory mode = 0777 > guest ok = yes |
From: Ewan G. <ewa...@gm...> - 2005-08-15 14:40:11
|
On 8/15/05, Holger Krull <hol...@gm...> wrote: > Nothing unusual with this conf. > Did you try use sendfile =3D no? Yes, in the globals section. Just for completeness sake, the error message I get from the capture progra= m is: Cannot write to file : \\Colinux\md1\Home_Video\Capture.DV Reason: The specified network name is no longer available. At the same time I get a yellow exclamation triangle in my task tay with the message: Windows - Delayed Write Failed. Even though all drives are set with Delayed Write turned off (since it didn't seem to help anyway). > Post testparm -v please Below: # Global parameters [global] =09dos charset =3D CP850 =09unix charset =3D UTF-8 =09display charset =3D LOCALE =09workgroup =3D FAMLAN =09realm =3D=20 =09netbios name =3D COLINUX =09netbios aliases =3D=20 =09netbios scope =3D=20 =09server string =3D %h server (Samba %v) =09interfaces =3D=20 =09bind interfaces only =3D No =09security =3D SHARE =09auth methods =3D=20 =09encrypt passwords =3D Yes =09update encrypted =3D No =09client schannel =3D Auto =09server schannel =3D Auto =09allow trusted domains =3D Yes =09hosts equiv =3D=20 =09min password length =3D 5 =09map to guest =3D Never =09null passwords =3D No =09obey pam restrictions =3D Yes =09password server =3D * =09smb passwd file =3D /etc/samba/smbpasswd =09private dir =3D /etc/samba =09passdb backend =3D tdbsam, guest =09algorithmic rid base =3D 1000 =09root directory =3D=20 =09guest account =3D nobody =09enable privileges =3D No =09pam password change =3D No =09passwd program =3D /usr/bin/passwd %u =09passwd chat =3D *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n . =09passwd chat debug =3D No =09passwd chat timeout =3D 2 =09check password script =3D=20 =09username map =3D=20 =09password level =3D 0 =09username level =3D 0 =09unix password sync =3D No =09restrict anonymous =3D 0 =09lanman auth =3D Yes =09ntlm auth =3D Yes =09client NTLMv2 auth =3D No =09client lanman auth =3D Yes =09client plaintext auth =3D Yes =09preload modules =3D=20 =09use kerberos keytab =3D No =09log level =3D 0 =09syslog =3D 0 =09syslog only =3D No =09log file =3D /var/log/samba/log.%m =09max log size =3D 1000 =09debug timestamp =3D Yes =09debug hires timestamp =3D No =09debug pid =3D No =09debug uid =3D No =09smb ports =3D 445 139 =09large readwrite =3D Yes =09max protocol =3D NT1 =09min protocol =3D CORE =09read bmpx =3D No =09read raw =3D Yes =09write raw =3D Yes =09disable netbios =3D No =09acl compatibility =3D=20 =09defer sharing violations =3D Yes =09nt pipe support =3D Yes =09nt status support =3D Yes =09announce version =3D 4.9 =09announce as =3D NT =09max mux =3D 50 =09max xmit =3D 16644 =09name resolve order =3D lmhosts wins host bcast =09max ttl =3D 259200 =09max wins ttl =3D 518400 =09min wins ttl =3D 21600 =09time server =3D No =09unix extensions =3D Yes =09use spnego =3D Yes =09client signing =3D auto =09server signing =3D No =09client use spnego =3D Yes =09change notify timeout =3D 60 =09deadtime =3D 0 =09getwd cache =3D Yes =09keepalive =3D 300 =09kernel change notify =3D Yes =09lpq cache time =3D 30 =09max smbd processes =3D 0 =09paranoid server security =3D Yes =09max disk size =3D 0 =09max open files =3D 10000 =09socket options =3D TCP_NODELAY =09use mmap =3D Yes =09hostname lookups =3D No =09name cache timeout =3D 660 =09load printers =3D Yes =09printcap cache time =3D 0 =09printcap name =3D=20 =09cups server =3D=20 =09disable spoolss =3D No =09enumports command =3D=20 =09addprinter command =3D=20 =09deleteprinter command =3D=20 =09show add printer wizard =3D Yes =09os2 driver map =3D=20 =09mangling method =3D hash2 =09mangle prefix =3D 1 =09stat cache =3D Yes =09machine password timeout =3D 604800 =09add user script =3D=20 =09delete user script =3D=20 =09add group script =3D=20 =09delete group script =3D=20 =09add user to group script =3D=20 =09delete user from group script =3D=20 =09set primary group script =3D=20 =09add machine script =3D=20 =09shutdown script =3D=20 =09abort shutdown script =3D=20 =09logon script =3D=20 =09logon path =3D \\%N\%U\profile =09logon drive =3D=20 =09logon home =3D \\%N\%U =09domain logons =3D No =09os level =3D 20 =09lm announce =3D Auto =09lm interval =3D 60 =09preferred master =3D Auto =09local master =3D Yes =09domain master =3D Auto =09browse list =3D Yes =09enhanced browsing =3D Yes =09dns proxy =3D No =09wins proxy =3D No =09wins server =3D=20 =09wins support =3D No =09wins hook =3D=20 =09wins partners =3D=20 =09kernel oplocks =3D Yes =09lock spin count =3D 3 =09lock spin time =3D 10 =09oplock break wait time =3D 0 =09ldap admin dn =3D=20 =09ldap delete dn =3D No =09ldap filter =3D (uid=3D%u) =09ldap group suffix =3D=20 =09ldap idmap suffix =3D=20 =09ldap machine suffix =3D=20 =09ldap passwd sync =3D no =09ldap replication sleep =3D 1000 =09ldap suffix =3D=20 =09ldap ssl =3D=20 =09ldap timeout =3D 15 =09ldap user suffix =3D=20 =09add share command =3D=20 =09change share command =3D=20 =09delete share command =3D=20 =09config file =3D=20 =09preload =3D=20 =09lock directory =3D=20 =09pid directory =3D /var/run/samba =09utmp directory =3D=20 =09wtmp directory =3D=20 =09utmp =3D No =09default service =3D=20 =09message command =3D=20 =09dfree command =3D=20 =09get quota command =3D=20 =09set quota command =3D=20 =09remote announce =3D=20 =09remote browse sync =3D=20 =09socket address =3D 0.0.0.0 =09homedir map =3D auto.home =09afs username map =3D=20 =09afs token lifetime =3D 604800 =09log nt token command =3D=20 =09time offset =3D 0 =09NIS homedir =3D No =09panic action =3D /usr/share/samba/panic-action %d =09host msdfs =3D No =09enable rid algorithm =3D Yes =09idmap backend =3D=20 =09idmap uid =3D=20 =09idmap gid =3D=20 =09template primary group =3D nobody =09template homedir =3D /home/%D/%U =09template shell =3D /bin/false =09winbind separator =3D \ =09winbind cache time =3D 300 =09winbind enable local accounts =3D No =09winbind enum users =3D Yes =09winbind enum groups =3D Yes =09winbind use default domain =3D No =09winbind trusted domains only =3D No =09winbind nested groups =3D No =09comment =3D=20 =09path =3D=20 =09username =3D=20 =09invalid users =3D=20 =09valid users =3D=20 =09admin users =3D=20 =09read list =3D=20 =09write list =3D=20 =09printer admin =3D=20 =09force user =3D=20 =09force group =3D=20 =09read only =3D Yes =09create mask =3D 0744 =09force create mode =3D 00 =09security mask =3D 0777 =09force security mode =3D 00 =09directory mask =3D 0755 =09force directory mode =3D 00 =09directory security mask =3D 0777 =09force directory security mode =3D 00 =09force unknown acl user =3D No =09inherit permissions =3D No =09inherit acls =3D No =09guest only =3D No =09guest ok =3D No =09only user =3D No =09hosts allow =3D=20 =09hosts deny =3D=20 =09allocation roundup size =3D 1048576 =09ea support =3D No =09nt acl support =3D Yes =09profile acls =3D No =09map acl inherit =3D No =09afs share =3D No =09block size =3D 1024 =09max connections =3D 0 =09min print space =3D 0 =09strict allocate =3D No =09strict sync =3D No =09sync always =3D No =09use sendfile =3D No =09write cache size =3D 0 =09max reported print jobs =3D 0 =09max print jobs =3D 1000 =09printable =3D No =09printing =3D bsd =09cups options =3D=20 =09print command =3D lpr -r -P'%p' %s =09lpq command =3D lpq -P'%p' =09lprm command =3D lprm -P'%p' %j =09lppause command =3D=20 =09lpresume command =3D=20 =09queuepause command =3D=20 =09queueresume command =3D=20 =09printer name =3D=20 =09use client driver =3D No =09default devmode =3D No =09force printername =3D No =09default case =3D lower =09case sensitive =3D Auto =09preserve case =3D Yes =09short preserve case =3D Yes =09mangling char =3D ~ =09hide dot files =3D Yes =09hide special files =3D No =09hide unreadable =3D No =09hide unwriteable files =3D No =09delete veto files =3D No =09veto files =3D=20 =09hide files =3D=20 =09veto oplock files =3D=20 =09map system =3D No =09map hidden =3D No =09map archive =3D Yes =09mangled names =3D Yes =09mangled map =3D=20 =09store dos attributes =3D No =09browseable =3D Yes =09blocking locks =3D Yes =09csc policy =3D manual =09fake oplocks =3D No =09locking =3D Yes =09oplocks =3D Yes =09level2 oplocks =3D Yes =09oplock contention limit =3D 2 =09posix locking =3D Yes =09strict locking =3D Yes =09share modes =3D Yes =09copy =3D=20 =09include =3D /etc/samba/dhcp.conf =09preexec =3D=20 =09preexec close =3D No =09postexec =3D=20 =09root preexec =3D=20 =09root preexec close =3D No =09root postexec =3D=20 =09available =3D Yes =09volume =3D=20 =09fstype =3D NTFS =09set directory =3D No =09wide links =3D Yes =09follow symlinks =3D Yes =09dont descend =3D=20 =09magic script =3D=20 =09magic output =3D=20 =09delete readonly =3D No =09dos filemode =3D No =09dos filetimes =3D Yes =09dos filetime resolution =3D No =09fake directory create times =3D No =09vfs objects =3D=20 =09msdfs root =3D No =09msdfs proxy =3D=20 [homes] =09comment =3D Home Directories =09create mask =3D 0700 =09directory mask =3D 0700 =09browseable =3D No [printers] =09comment =3D All Printers =09path =3D /tmp =09create mask =3D 0700 =09printable =3D Yes =09browseable =3D No [print$] =09comment =3D Printer Drivers =09path =3D /var/lib/samba/printers [usr_src] =09path =3D /usr/src =09read only =3D No =09create mask =3D 0777 =09directory mask =3D 0777 =09guest ok =3D Yes [md0] =09path =3D /mnt/md0 =09read only =3D No =09create mask =3D 0777 =09directory mask =3D 0777 =09guest ok =3D Yes [md1] =09path =3D /mnt/md1 =09read only =3D No =09create mask =3D 0777 =09directory mask =3D 0777 =09guest ok =3D Yes |
From: Nuno L. <ml-...@xp...> - 2005-08-15 15:29:21
|
[15-08-2005 15:40, Ewan Grantham escreveu] > On 8/15/05, Holger Krull <hol...@gm...> wrote: > >>Nothing unusual with this conf. >>Did you try use sendfile = no? > > > Yes, in the globals section. > > Just for completeness sake, the error message I get from the capture program is: > > Cannot write to file : \\Colinux\md1\Home_Video\Capture.DV > > Reason: The specified network name is no longer available. > > At the same time I get a yellow exclamation triangle in my task tay > with the message: > > Windows - Delayed Write Failed. > > Even though all drives are set with Delayed Write turned off (since it > didn't seem to help anyway). I never tried anything like this but it seems to me you're just reaching the maximum throughput you can have with your current colinux version. You seem to be doing something that even a native linux machine (on samba) could have troubles if not equipped with good hardware (like cheap network cards and hard disks). My guess is just that you are filling the buffer too quick and it is just saying is had to discard writes because the buffer is already full with previous writes. Probably the "stress" is causing other problems, like apparent temporary network disconnections This would not happen with normal disk writes (it would just block until the buffer empties), but my guess is that the software is using some type of "direct write" to speed things up (so it doesn't loose frames). Try to do the same by copying a very large file to a colinux samba folder and see for yourself the time taken, the cpu usage, etc. Best regards, ~Nuno Lucas |
From: Ewan G. <ewa...@gm...> - 2005-08-15 18:37:46
|
On 8/15/05, Nuno Lucas <ml-...@xp...> wrote: > I never tried anything like this but it seems to me you're just reaching > the maximum throughput you can have with your current colinux version. Well, that's kind of what I was wondering. > You seem to be doing something that even a native linux machine (on samba= ) > could have troubles if not equipped with good hardware (like cheap networ= k > cards and hard disks). >=20 > My guess is just that you are filling the buffer too quick and it is just > saying is had to discard writes because the buffer is already full with > previous writes. Probably the "stress" is causing other problems, like > apparent temporary network disconnections >=20 > This would not happen with normal disk writes (it would just block until > the buffer empties), but my guess is that the software is using some type > of "direct write" to speed things up (so it doesn't loose frames). >=20 > Try to do the same by copying a very large file to a colinux samba > folder and see for yourself the time taken, the cpu usage, etc. In other words, is what I should expect. I'm asking too much of the various layers of translation. As far as CPU usage for just a normal file copy, even a large one, I generally don't see it go much past about 70%. But I can imagine a capture or streaming copy adds just that much more overhead to the equation. Since Samba is the only way to access the cobd "partition" from Windows (right?), then this is something that just isn't going to work. And I should plan accordingly. No point in my banging my head against the concrete if the wall isn't going to budge, eh? :-) |
From: mike c. <mik...@co...> - 2005-08-15 19:54:17
|
Ewan Grantham wrote: >On 8/15/05, Nuno Lucas <ml-...@xp...> wrote: > > >>I never tried anything like this but it seems to me you're just reaching >>the maximum throughput you can have with your current colinux version. >> >> > >Well, that's kind of what I was wondering. > > > >>You seem to be doing something that even a native linux machine (on samba) >>could have troubles if not equipped with good hardware (like cheap network >>cards and hard disks). >> >>My guess is just that you are filling the buffer too quick and it is just >>saying is had to discard writes because the buffer is already full with >>previous writes. Probably the "stress" is causing other problems, like >>apparent temporary network disconnections >> >>This would not happen with normal disk writes (it would just block until >>the buffer empties), but my guess is that the software is using some type >>of "direct write" to speed things up (so it doesn't loose frames). >> >>Try to do the same by copying a very large file to a colinux samba >>folder and see for yourself the time taken, the cpu usage, etc. >> >> > >In other words, is what I should expect. I'm asking too much of the >various layers of translation. > >As far as CPU usage for just a normal file copy, even a large one, I >generally don't see it go much past about 70%. But I can imagine a >capture or streaming copy adds just that much more overhead to the >equation. > >Since Samba is the only way to access the cobd "partition" from >Windows (right?), then this is something that just isn't going to >work. And I should plan accordingly. No point in my banging my head >against the concrete if the wall isn't going to budge, eh? :-) > > It has been observerved that there are more "Wear throughs" than "break throughs" I haven't seen any anwers, and not many suggested tests of theories. Have you tried running Samba native to see what sort of limit, if any, you hit? A dual boot or even cd boot system might give you a data point. You might also grep the source for the error message and have a look at the logic that got you to that point. Sorry to have no theory to test myself. My last suggestion would be lurking or even cross posting in the Samba groups. Regards, Mike > >------------------------------------------------------- >SF.Net email is Sponsored by the Better Software Conference & EXPO >September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices >Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA >Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf >_______________________________________________ >coLinux-users mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-users > > > |
From: David N. <nau...@um...> - 2005-08-18 18:52:15
|
On 2005-04-07 07:58 Arthur Lin wrote: > Using TAP, and Windows bridge for my networking. Bost the host > windows and the colinux/gentoo works fine every other sense. > > The only issue is that from host windows (192.168.56.172), it cannot > reach colinux/gentoo (192.168.56.173). > > The problem goes away, after I issue PING 192.168.56.172 from > colinux/gentoo. Both systems can talk to each other without problem. > > It looks like the ARP discovery problem in the windows bridge software > (or maybe the TAP driver in windows?) > > Temporary solution could be to a cron job in colinux that ping the > winows host regularly so that the MAC address for colinux remains in > the windows arp cache. I'm experiencing the same problem that Arthur describes. Has anyone found a better solution than Arthur's temporary solution? I'm trying to help a co-worker (Roman, whom I've copied on this message), upgrade from 0.6.1 to 0.6.2. We didn't have this problem with 0.6.1, only with 0.6.2. We are running WinXP, ICS with TAP, and Debian. We can provide more info if that would be helpful. Thanks! David Naughton |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-08-18 19:06:17
|
David Naughton wrote: > On 2005-04-07 07:58 Arthur Lin wrote: > >>[...] >>Temporary solution could be to a cron job in colinux that ping the >>winows host regularly so that the MAC address for colinux remains in >>the windows arp cache. > > > I'm experiencing the same problem that Arthur describes. Has anyone > found a better solution than Arthur's temporary solution? I have this problem only, if I change from one to other version or booting diferent images without reboot the host (XP home). Perhaps you can set a fix MAC address in XML configuration for the eth0? Have no bridged in use. Only a single TAP device. -- Henry Nestler |
From: Johannes B. <jb...@fr...> - 2005-08-18 19:57:31
|
on 18.08.2005 00:18 David Naughton wrote: > On 2005-04-07 07:58 Arthur Lin wrote: > >>Using TAP, and Windows bridge for my networking. Bost the host >>windows and the colinux/gentoo works fine every other sense. >> >>The only issue is that from host windows (192.168.56.172), it cannot >>reach colinux/gentoo (192.168.56.173). >> >>The problem goes away, after I issue PING 192.168.56.172 from >>colinux/gentoo. Both systems can talk to each other without problem. >> >>It looks like the ARP discovery problem in the windows bridge software >>(or maybe the TAP driver in windows?) >> >>Temporary solution could be to a cron job in colinux that ping the >>winows host regularly so that the MAC address for colinux remains in >>the windows arp cache. > > > I'm experiencing the same problem that Arthur describes. Has anyone > found a better solution than Arthur's temporary solution? > > I'm trying to help a co-worker (Roman, whom I've copied on this > message), upgrade from 0.6.1 to 0.6.2. We didn't have this problem with > 0.6.1, only with 0.6.2. We are running WinXP, ICS with TAP, and Debian. > We can provide more info if that would be helpful. > > Thanks! > David Naughton > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > Got the same problem using colinux/debian with wincap/tap. Switched to native XP bridging. Created two TAP interfaces and configured them like that: <network index="0" type="tap" name="coLAN" mac="<staticmac>" /> <network index="1" type="tap" name="coLinux" mac="<staticmac>" /> Under Debian my /etc/network/interfaces looks this way: ------------------------- auto lo eth0 eth1 iface lo inet loopback iface eth0 inet dhcp iface eth1 inet static address 192.168.10.10 netmask 255.255.255.0 ------------------------- The eth0 is responsible for dhcp bridging on my home/office-lan. The eth1 provides me an stable connection directly on the box. Therefore the "coLinux" interface has the address "192.168.10.1" and netmask "255.255.255.0". Hope this helps someone -- Johannes Becker mail jb...@fr... visit www.fragp.com |
From: Andrew K. <ak...@ya...> - 2005-08-20 21:17:43
|
On Monday 15 August 2005 23:42, Ewan Grantham wrote: > Again, am running version 3.0.14a of Samba. My smb.conf is belo I know sweetFA about Samba or co-linux but I was wondering if this comment I came across might offer you a clue; > > Actually, according to the samba team, the 2Gb limit is actually if you > > use > > mount -t smbfs command which is not within the scope of samba. they > > recommend using smbclient. Even if you dont specifically use the mount -t smbfs command this suggests that the 2Gb limit only applies to using shares which would be the default way that I Imagine you have set up Samba but that using smbclient which treats it similiar to an ftp file transfer would get around the problem. andrew |
From: Holger K. <hol...@gm...> - 2005-08-15 15:13:54
|
> Just for completeness sake, the error message I get from the capture program is: > Cannot write to file : \\Colinux\md1\Home_Video\Capture.DV > Reason: The specified network name is no longer available. And if you do a dir \\Colinux\md1\Home_Video\ is the share really gone? > At the same time I get a yellow exclamation triangle in my task tay > with the message: > > Windows - Delayed Write Failed. > > Even though all drives are set with Delayed Write turned off (since it > didn't seem to help anyway). That is not the delayed write of the drives here, maybe turn that on again. This is the delayed update of file information or client side caching. Delayed Write failures could be a locking issue or EA access that fails. Maybe set oplocks = no for a try. |
From: Ewan G. <ewa...@gm...> - 2005-08-15 15:31:35
|
On 8/15/05, Holger Krull <hol...@gm...> wrote: > > Just for completeness sake, the error message I get from the capture pr= ogram is: > > Cannot write to file : \\Colinux\md1\Home_Video\Capture.DV > > Reason: The specified network name is no longer available. > > And if you do a dir \\Colinux\md1\Home_Video\ is the share really gone? Nope. Just that access to the file has been terminated. Samba seems to be just fine, it's as if either Samba closed access to the file, or COBD terminated Samba's access to the file. That's why I'm suspicious of Samba being the culprit. If it was, I "should" lose access to the share and have to re-establish it - or so I would think. > > At the same time I get a yellow exclamation triangle in my task tay > > with the message: > > > > Windows - Delayed Write Failed. > > > > Even though all drives are set with Delayed Write turned off (since it > > didn't seem to help anyway). > > That is not the delayed write of the drives here, maybe turn that on agai= n. Have tried it both ways, no difference. > This is the delayed update of file information or client side caching. > > Delayed Write failures could be a locking issue or EA access that fails. > Maybe set oplocks =3D no for a try. There seem to be several places where oplocks is specified (Kernel, Fake, etc.) Are you suggesting all of them be set to No? Just for my own edification, has anyone else even tried this? Capturing to a Samba share using the 7/20/2005 snapshot? Just wondering if it's really me, or just I'm the only one crazy enough to try this :-) Thanks, Ewan |
From: Ewan G. <ewa...@gm...> - 2005-08-15 18:32:29
|
On 8/15/05, Holger Krull <hol...@gm...> wrote: > > Ewan Grantham schrieb: > > > > Just for my own edification, has anyone else even tried this? > > Capturing to a Samba share using the 7/20/2005 snapshot? Just > > wondering if it's really me, or just I'm the only one crazy enough to > > try this :-) >=20 > Probably just you. Assuming this is correct, could someone who is doing similar things (ripping DVDs or capturing DVD files or other "streaming" to >2GB files) please show me their smb.conf so I can see what I am doing differently that may be causing the problem? I hate to keep filling the email list with my logs and such if I'm the only one having problems doing this. Thanks, Ewan |