[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 980507: bad netCDF 3.4 problems on winterpark address@hidden

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 980507: bad netCDF 3.4 problems on winterpark address@hidden
  • Date: Thu, 7 May 1998 19:36:24 -0600
> >From: Charlie Zender <address@hidden>
> >Keywords: 199805072123.PAA08776
>
> I'm not an OS expert, so I don't know the answers to most of your ?s
> about the filesystem stuff. Ed Arnold can help you there. It's
> definitely IRIX64 though. And, Ed, FYI, the bug has shown itself whether
> the source file is on /fs/cgd/data0 or /usr/tmp, but it seems to occur
> more frequently on /fs/cgd/data0. I havn't tried it on /fs/cgd/home0
> because my disk quota is too close to its limit.
>
> Here's the output from the few commands I do know how to run:
>
> /fs/cgd/data0/zender/tmp: uname -a
> IRIX64 winterpark 6.2 03131016 IP25
>
> /fs/cgd/data0/zender/tmp: showprods | grep patch | grep nfs
> I  patchSG0002147.nfs_sw  03/15/98  NFS Software
> I  patchSG0002147.nfs_sw.nfs  03/15/98  NFS Support
> I  patchSG0002611.nfs_man  03/15/98  NFS Documentation
> I  patchSG0002611.nfs_man.nfs  03/15/98  NFS Support Manual Pages
> I  patchSG0002611.nfs_sw  03/15/98  NFS Software
> I  patchSG0002611.nfs_sw.nis  03/15/98  NIS (formerly Yellow Pages) Support
> I  patchSG0002654.nfs3_sw  03/15/98  NFS Version 3 Software
> I  patchSG0002654.nfs3_sw.nfs3  03/15/98  NFS Version 3 Support
> I  patchSG0002654.nfs_sw  03/15/98  NFS Software
> I  patchSG0002654.nfs_sw.nfs  03/15/98  NFS Support

One would presume that /usr/tmp is a local file system.
If so, that would rule out NFS as being the problem area.

In general terms, what is your program doing?
Does it create a new output file or perform an redefintion?

As as experiment which may further isolate the problem,
add a command line option which adds the NC_SHARE flags
to the open or create. If the problem goes away or persists
with this flag on will focus our attention.

-glenn