Re: [CentOS] CIFS Issue When Copying Large/Many Files From CentOS To Remote Windows 2003 Server Share
Kemp, Larry wrote:
I automount the remote share via /etc/fstab and have the /mnt/remotewinservershare built. Everything is setup and seems to work properly but during the large file transfer (at intermittent times) the Linux Kernel seems to panic and the CIFS connection seems to fail as a
If the antivirus trick doesn't work I'd suggest trying to do the file transfers through smbclient and not through the cifs kernel module, and see if you get similar types of issues.
nate
Mucho thanks guys...
1) We have disabled the antivirus for the entire drive (which is a RAID5 diskarray). I will try to have Bacula send it job to this mounted system now and see if CENT OS comes back with any CIFS errors.
2) I did try originally editing the /etc/fstab to mount the remote share as SMB in as many different ways that I could find online. But none seemed to work for me. It seemed to be a little bit different across Linux distros and versions, as well as SMB versions. And in the end, I simply got CIFS to work and had just not yet figured out the exact verbiage for SMB to work in /etc/fstab to mount /mnt/remotewinserver automagically at boot. I did read up on SMB as well to see if I was missing something small. If you have a combination that has worked for you Nate, please do share sir, I would be most gracious on my end...believe me. The remote sharer is a Windows 2003 Server running 2 64bit processors, but the OS was installed as 32bit for whatever reason.
3) Unfortunately Windows claimed the big fat HP Storage server before CENT OS could (sorry for this starting to sound like a Windows whinefest too). Having said that, Win2k3 Server runs the array already backing up all Windows servers using Backup Exec. I am ofcourse trying use CENT OS and Bacula but needed large diskspace. Had we had another array/server I could use CENT OS would have no problem running I am certain. So as a second method I am creating a VM running CENT OS and Bacula on the large S:\drive of the Windows server that has an expandable VMDK drive (VMWare). This way my CENT OS/Bacula VM can grow as big as it needs to and to CENT OS and Bacula the storage device is just natively /storage-array. At least that is one plan anyway.
We are also "talking about" just buying the Symantec Linux client for backups. But the original goal was to use CENT OS for this since our production systems are CENT OS.
Okay that's everything I think. Thanks for the help thus far.
LK larry.kemp@usmetrotel.com
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of nate Sent: Thursday, June 18, 2009 10:59 AM To: centos@centos.org Subject: Re: [CentOS] CIFS Issue When Copying Large/Many Files From CentOS To Remote Windows 2003 Server Share
Kemp, Larry wrote:
I automount the remote share via /etc/fstab and have the /mnt/remotewinservershare built. Everything is setup and seems to work properly but during the large file transfer (at intermittent times) the Linux Kernel seems to panic and the CIFS connection seems to fail as a
If the antivirus trick doesn't work I'd suggest trying to do the file transfers through smbclient and not through the cifs kernel module, and see if you get similar types of issues.
nate
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2009-06-18 at 11:46 -0400, Kemp, Larry wrote:
Mucho thanks guys...
We have disabled the antivirus for the entire drive (which is a RAID5 diskarray). I will try to have Bacula send it job to this mounted system now and see if CENT OS comes back with any CIFS errors.
I did try originally editing the /etc/fstab to mount the remote share as SMB in as many different ways that I could find online. But none seemed to work for me. It seemed to be a little bit different across Linux distros and versions, as well as SMB versions. And in the end, I simply got CIFS to work and had just not yet figured out the exact verbiage for SMB to work in /etc/fstab to mount /mnt/remotewinserver automagically at boot. I did read up on SMB as well to see if I was missing something small. If you have a combination that has worked for you Nate, please do share sir, I would be most gracious on my end...believe me. The remote sharer is a Windows 2003 Server running 2 64bit processors, but the OS was installed as 32bit for whatever reason.
Unfortunately Windows claimed the big fat HP Storage server before CENT OS could (sorry for this starting to sound like a Windows whinefest too). Having said that, Win2k3 Server runs the array already backing up all Windows servers using Backup Exec. I am ofcourse trying use CENT OS and Bacula but needed large diskspace. Had we had another array/server I could use CENT OS would have no problem running I am certain. So as a second method I am creating a VM running CENT OS and Bacula on the large S:\drive of the Windows server that has an expandable VMDK drive (VMWare). This way my CENT OS/Bacula VM can grow as big as it needs to and to CENT OS and Bacula the storage device is just natively /storage-array. At least that is one plan anyway.
We are also "talking about" just buying the Symantec Linux client for backups. But the original goal was to use CENT OS for this since our production systems are CENT OS.
Okay that's everything I think. Thanks for the help thus far.
---- What it comes down to is you don not have enough A** in your hardware to do scanning in real time. I had the problem with Samba and the clamav module for samba untill I upgraded the hardware. Very CPU Intensive and memory. The right hardware you can saturate a GigE conection. That is logging all transfers file open and close.
John
Kemp, Larry wrote:
Mucho thanks guys...
We have disabled the antivirus for the entire drive (which is a RAID5 diskarray). I will try to have Bacula send it job to this mounted system now and see if CENT OS comes back with any CIFS errors.
I did try originally editing the /etc/fstab to mount the remote share as SMB in as many different ways that I could find online. But none seemed to work for me. It seemed to be a little bit different across Linux distros and versions, as well as SMB versions. And in the end, I simply got CIFS to work and had just not yet figured out the exact verbiage for SMB to work in /etc/fstab to mount /mnt/remotewinserver automagically at boot. I did read up on SMB as well to see if I was missing something small. If you have a combination that has worked for you Nate, please do share sir, I would be most gracious on my end...believe me. The remote sharer is a Windows 2003 Server running 2 64bit processors, but the OS was installed as 32bit for whatever reason.
Unfortunately Windows claimed the big fat HP Storage server before CENT OS could (sorry for this starting to sound like a Windows whinefest too). Having said that, Win2k3 Server runs the array already backing up all Windows servers using Backup Exec. I am ofcourse trying use CENT OS and Bacula but needed large diskspace. Had we had another array/server I could use CENT OS would have no problem running I am certain. So as a second method I am creating a VM running CENT OS and Bacula on the large S:\drive of the Windows server that has an expandable VMDK drive (VMWare). This way my CENT OS/Bacula VM can grow as big as it needs to and to CENT OS and Bacula the storage device is just natively /storage-array. At least that is one plan anyway.
We are also "talking about" just buying the Symantec Linux client for backups. But the original goal was to use CENT OS for this since our production systems are CENT OS.
Okay that's everything I think. Thanks for the help thus far.
How about getting getting them to carve out a chunk of the storage server through iscsi for dedicated Centos use. Would bypass most of that Windows share crappola.
Kemp, Larry wrote:
Mucho thanks guys...
We have disabled the antivirus for the entire drive (which is a RAID5 diskarray). I will try to have Bacula send it job to this mounted system now and see if CENT OS comes back with any CIFS errors.
I did try originally editing the /etc/fstab to mount the remote share as SMB in as many different ways that I could find online. But none seemed to work for me. It seemed to be a little bit different across Linux distros and versions, as well as SMB versions. And in the end, I simply got CIFS to work and had just not yet figured out the exact verbiage for SMB to work in /etc/fstab to mount /mnt/remotewinserver automagically at boot. I did read up on SMB as well to see if I was missing something small. If you have a combination that has worked for you Nate, please do share sir, I would be most gracious on my end...believe me. The remote sharer is a Windows 2003 Server running 2 64bit processors, but the OS was installed as 32bit for whatever reason.
Unfortunately Windows claimed the big fat HP Storage server before CENT OS could (sorry for this starting to sound like a Windows whinefest too). Having said that, Win2k3 Server runs the array already backing up all Windows servers using Backup Exec. I am ofcourse trying use CENT OS and Bacula but needed large diskspace. Had we had another array/server I could use CENT OS would have no problem running I am certain. So as a second method I am creating a VM running CENT OS and Bacula on the large S:\drive of the Windows server that has an expandable VMDK drive (VMWare). This way my CENT OS/Bacula VM can grow as big as it needs to and to CENT OS and Bacula the storage device is just natively /storage-array. At least that is one plan anyway.
We are also "talking about" just buying the Symantec Linux client for backups. But the original goal was to use CENT OS for this since our production systems are CENT OS.
Okay that's everything I think. Thanks for the help thus far.
If your backups are mostly online, have you looked at backuppc as an alternative to bacula? It's file pooling scheme will usually let you keep a much longer history on line. It can use smbclient or rsync to back up windows targets (and tar or rsync over ssh for linux) and some people have glued VSS support into cygwin rsync to deal with open files on windows. You'll still lose windows acl's, though....
-
JohnS -
Kemp, Larry -
Les Mikesell -
nate -
Toby Bluhm