Public bug reported:
I was upgrading a small 16.04 hpc cluster to 20.04 and noticed the
following. An nfs v3 mount causes netcdf4 file reads to fail. Nfs v4
mounts from the nfs server running 20.04 works fine. Netcdf3 files work
fine with both nfs v3 and v4 mounts. I checked a 16.04 setup and 18.0
** Package changed: ubuntu => nfs-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903974
Title:
issue reading netcdf4 files with nfs v3 on ubuntu 20.04
To manage notifications about t
The test is done with a netcdf4 file from here -
http://rain.ucis.dal.ca/ctm/GEOS_0.5x0.625_NA.d/MERRA2/1980/01/MERRA2.19800101.A1.05x0625.NA.nc4
>From 20.04 nfs server
v3 mount test - mount -t nfs -o vers=3 192.168.1.225:/nfs /tmp/test/
ncdump -h -s MERRA2.19800101.A1.05x0625.NA.nc4|tail -
Thanks Rafael! Disabling hdf5 file locking solved it.
export HDF5_USE_FILE_LOCKING=FALSE
I didn't have to do this for v3 mounts before. The only time I remember of
users having to use this is when using xarray and dask to open the netcdf file
in parallel. Anyhow I am happy that it works now.
