Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is a long shot, but I'm not sure where else to look. I'm hoping that someone here might have noticed this before.
I've been doing system backups of one of my servers weekly for about a year now using tar and gunzip. The file is then saved off onto an NFS share which is on a SAN. The problem that I just noticed is that about 40% of backup jobs are corrupt. When I try to un-gzip them it says that they are not recognized as gzip files.
I'm sure that it's something to do with NFS because I never once get this problem if I FTP the file to the NAS or if I save the file to a partition on a physical drive. Something in the NFS transfer changes the file because if I make a copy of the good gzip file then copy it to the SAN on the NFS mount I can do a 'diff' and it says that the file is different.
Moloko, thanks for your response. What I have in my fstab file for that mount is
"192.168.1.2:/backup /mnt/backup nfs rw 0 0"
I'm not near that machine today, but I'm excited to use your options. Do you think that the
reason that I'm having the trouble is because of the way I had it set up?
I'm using a switch to connect the computers to the SAN. They are SMC 1000g switches.
I don't think it is because the data that is being moved is coming from about 44 other nodes of which all have the same problem. As far as the SAN that is exporting the NFS we don't see this problem on anything else. We're starting to think it might be an issue with the SAN client software, but not sure yet. Thanks for the continuted input!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.