Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New filesize limit for svn inputdata that restricts our larger ctsm5.3.0 files being rimported #2751

Open
1 of 3 tasks
ekluzek opened this issue Sep 10, 2024 · 3 comments
Open
1 of 3 tasks
Labels
bug something is working incorrectly enhancement new capability or improved behavior of existing capability

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Sep 10, 2024

Currently the svn server in CGD for inputdata has a file size limit for importing new files that is around 23GBytes. When we rimported ctsm5.2.0 files we put in files up to 114GB and did NOT see this problem.

This came up in ctsm5.3.0 work in #2500 as referenced below.

In our CSEG meeting we decided we need to transition to a new inputdata storage solution anyway. So we plan to leave these files OUT of svn inputdata until later.

          @ekluzek I have started the last ./rimport but these landuse files returned an error, which makes me think that all that f09 landuse files (and possibly others) are too big:
svn: E175002: Unexpected HTTP status 413 'Request Entity Too Large' on '/!svn/txr/68458-1k6x/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_0.9x1.25_hist_1700-2023_78pfts_c240908.nc'
svn: E175002: Unexpected HTTP status 413 'Request Entity Too Large' on '/!svn/txr/68458-1k6y/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_0.9x1.25_SSP1-1.9_1850-2100_78pfts_c240908.nc'
svn: E175002: Unexpected HTTP status 413 'Request Entity Too Large' on '/!svn/txr/68458-1k6z/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_0.9x1.25_SSP1-2.6_1850-2100_78pfts_c240908.nc'

UPDATE: Some give a more vague error such as this:
svn: E175002: PUT request on '/!svn/txr/68459-1k71/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_0.9x1.25_SSP2-4.5_1850-2100_78pfts_c240908.nc' failed

Some non-f09 files that failed with the same errors:

svn: E175002: PUT request on '/!svn/txr/68462-1k79/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_360x720cru_SSP2-4.5_1850-2100_78pfts_c240908.nc' failed
svn: E175002: PUT request on '/!svn/txr/68463-1k7b/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_C96_SSP2-4.5_1850-2100_78pfts_c240908.nc' failed
svn: E175002: Unexpected HTTP status 413 'Request Entity Too Large' on '/!svn/txr/68463-1k7c/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_mpasa120_SSP2-4.5_1850-2100_78pfts_c240908.nc'
svn: E175002: PUT request on '/!svn/txr/68465-1k7f/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_ne0np4CONUS.ne30x8_SSP2-4.5_1979-2026_78pfts_c240908.nc' failed
svn: E175002: Unexpected HTTP status 413 'Request Entity Too Large' on '/!svn/txr/68468-1k7j/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_ne30np4.pg3_SSP2-4.5_1850-2100_78pfts_c240908.nc'
svn: E175002: Unexpected HTTP status 413 'Request Entity Too Large' on '/!svn/txr/68468-1k7k/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/landuse.timeseries_ne30np4_SSP2-4.5_1850-2100_78pfts_c240908.nc'
svn: E175002: PUT request on '/!svn/txr/68496-1k8d/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/surfdata_mpasa15_hist_2000_16pfts_c240908.nc' failed
svn: E175002: PUT request on '/!svn/txr/68496-1k8e/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/surfdata_mpasa3p75_hist_2000_16pfts_c240908.nc' failed
svn: E175002: Unexpected HTTP status 413 'Request Entity Too Large' on '/!svn/txr/68507-1k8q/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/surfdata_ne120np4.pg3_hist_1850_78pfts_c240908.nc'
svn: E175002: PUT request on '/!svn/txr/68507-1k8r/trunk/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0/surfdata_ne120np4.pg3_hist_2000_78pfts_c240908.nc' failed

Originally posted by @slevis-lmwg in #2500 (comment)

Definition of done:

  • Have a backup copy of these files on Izumi
  • This list of files is imported into the new system
  • Remove the extra copy on Izumi
@ekluzek
Copy link
Collaborator Author

ekluzek commented Sep 10, 2024

Also see:

#2500 (comment)

#2500 (comment)

@ekluzek ekluzek added this to the ctsm6.0.0 (code freeze) milestone Sep 10, 2024
@ekluzek ekluzek added enhancement new capability or improved behavior of existing capability bug something is working incorrectly next this should get some attention in the next week or two. Normally each Thursday SE meeting. labels Sep 10, 2024
@ekluzek
Copy link
Collaborator Author

ekluzek commented Sep 10, 2024

Pinging @briandobbins and @wwieder

@samsrabin samsrabin removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Sep 12, 2024
@ekluzek
Copy link
Collaborator Author

ekluzek commented Sep 16, 2024

After 5.3.0 is done, we'll need to handle these files and make sure they are in the new system once it's available.

@slevis-lmwg @briandobbins

@ekluzek ekluzek added next this should get some attention in the next week or two. Normally each Thursday SE meeting. labels Sep 16, 2024
@ekluzek ekluzek removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something is working incorrectly enhancement new capability or improved behavior of existing capability
Projects
None yet
Development

No branches or pull requests

2 participants