Bug 107049 - nfs mount of SnapServer partition produces I/O errors
nfs mount of SnapServer partition produces I/O errors
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Steve Dickson
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-10-14 12:00 EDT by John Rivlin
Modified: 2007-04-18 12:58 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-15 20:40:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Rivlin 2003-10-14 12:00:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 
1.0.3705; .NET CLR 1.1.4322)

Description of problem:
I have an nfs mounted a partition on a SnapAppliance SnapServer 4100 (I think 
its FreeBSD under the covers). I get I/O errors when copying files from the 
SnapServer to the Linx 9 installation. I also sometimes get data corruption. 
Repeating the same copy multiple times will work sometimes and fail others. In 
addition, a Thiz Linuz 7.0 installation I have works just fine with the same 
SnapAppliance SnapServer.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. mount snap server partition (mount /snap1)
2. cp -r from to

Actual Results:  Get I/O error on some copied files. Also some files are 
corrupted on the destination machine.

Expected Results:  Expect not to get errors

Additional info:

Copying the same file twice does not produce the same output.
Comment 1 Steve Dickson 2003-10-15 09:59:06 EDT
What transport are you using UDP or TCP?
Are you using Soft mounts?
Comment 2 John Rivlin 2003-10-15 11:23:33 EDT
I'm using UDP. I've tried both soft and hard mounts. I tried TCP as well but 
got "mount: RPC: program not registered" from the mount command.
Comment 3 Steve Dickson 2003-10-18 21:28:00 EDT
Would it be possible to get a ethereal trace of the problem?
Comment 4 John Rivlin 2003-10-18 21:56:38 EDT
Not really. I decided to try installing Red Had Enterprise ES and just 
discovered that that resolved the problem.
Comment 5 Dan Baxter 2004-01-03 16:55:06 EST
I had a similar problem with 2.4.20-27.7 and 2.4.20-24.7 but not
2.4.18-3smp (different machine), all RH7.3, connected to a SnapServer
1100.  After I added the mount option -o nfsvers=2, the problem seems
to have disappeared.
Comment 6 Steve Dickson 2004-01-04 18:58:21 EST
The only way to decisively tell why nfsv3 breaks a SnapServer is to
have get a network trace. I need to see which NFS op is failing

Note You need to log in before you can comment on or make changes to this bug.