NFSGW File corruption

hgov...@banctec.ca

unread,

Sep 24, 2003, 1:08:11 PM9/24/03

to

Hi,
We upgraded a NW4.2 server with NFS 2.x to NW 5.1(SP6) and NFS 3 (SP5)
this past weekend. Since the upgrade, an application that has been working
fine for years is writing a corrupt output file to a Nfsgw volume.

The file starts out being built correctly and then for some reason in the
middle of the file, data is missing and an append to the file was started.

I have increased the cache in both the BTI and gateway config files with
no better results.

The output file is usually only about 150 K but the file remains open for
about 5 minutes during it's creation. (Slow process of writing a record
and then moving the image...repeated).

We have tried redirecting the output to another non NFS drive (which
works) although this then requires a manual move of the file which is not
acceptable. (We should be able to create this file as we did before the
upgrade)

Does anyone have any suggestions as how I can resolve this issue?

Thanks in advance,

Henry

Brad Doster

unread,

Sep 26, 2003, 9:23:43 AM9/26/03

to

Also check that you have the latest NSS patches applied -- I believe
there are some beyond what SP6 has.

bd
NSC Volunteer SysOp
www.InsightNetSolutions.net

hgov...@banctec.ca

unread,

Sep 26, 2003, 9:46:06 AM9/26/03

to

I was under the impression that the NFS service pack level was supposed to
be 1 revision below the Netware service pack level. It seems as if the
volume is dismounted and then remounted the problem will disappear for
about 30 minutes. Perhaps the shadow file (over 11 MB) is corrupt. I will
try stopping NFS, deleting this one shadow file and restarting the
services.

Copies of any file size work fine but the building of a file over time (5
Minutes) seems to cause a problem. Could it be a lockd issue?

Thanks,

Henry

hgov...@banctec.ca

unread,

Oct 10, 2003, 1:08:21 PM10/10/03

to

> In article <yqXcb.461$g11...@prv-forum3.provo.novell.com>, wrote:
> > I was under the impression that the NFS service pack level was
supposed to
> > be 1 revision below the Netware service pack level.
> >

> I doubt there's a rule like that, although it may coincidentally be the
case
> at this moment in time. In any event, I was referring to NSS patches,
not
> NFS service packs.

>
> > Could it be a lockd issue?
> >

> Mmmm... maybe... lockd and NSS don't get along well at all, from what
I've
> read here.
>
> Let us know how rebuilding the shadow file goes.

>
> bd
> NSC Volunteer SysOp
> www.InsightNetSolutions.net
>

Hi,

Sorry it took so long but it is a production system.
We stopped the GW and removed the shadow file and restarted.
The shadow file is considerably smaller (will grow with access) but the
issue remains. Opening a new file and building it (appends) for anymore
than about 15 seconds causes the file to become corrupt. Looking at the
file, it is like the connection is lost and then reconnected. There are
just missing records.
If I run the same program & build the file on a non NFSGW volume, the file
is built correctly.

Anyone have more idea's.

Thanks in Advance,

HG

Brad Doster

unread,

Oct 10, 2003, 9:28:00 PM10/10/03

to

Like you suggested earlier, I suspect you're stuck with a lockd vs. NSS
issue. Again, updating the *NSS* patches may help, but I can't
guarantee it.

Brad Doster

unread,

Oct 16, 2003, 9:41:45 AM10/16/03

to

In article <o_wjb.3920$S13....@prv-forum3.provo.novell.com>, wrote:
> Any other suggestions?
>
Mmm... call Novell tech support? If needed they'll dial into your
network to look directly at your system.