You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the import of SVN repositories we used uncompressed dump files. The dump is copied to the system temp folder. The import is started with the copy of the dump.
Bug Report
In case of too less space on the system drive, the copy process is started and then aborts suddenly with internal error.
Describe how to reproduce the bug
Bloat your system drive with rubbish in your temp directory up to a few megabytes left on the drive. Then do an import of a large SVN repository. We used a dump file with 47 GB of size.
Describe your SCM-Manager setup
SCM-Manager 2.39.1
Which operating system, browser and versions do you use?
Windows Server
Proposals
After the dump-file is selected, check the size of the dump and check the free space on the system drive. In case of not enough space do not start the import process.
Do not use the system temp folder but an own temp folder inside of SCM-Manager installation.
Start the import directly with the given file without copy.
The text was updated successfully, but these errors were encountered:
Issue description
For the import of SVN repositories we used uncompressed dump files. The dump is copied to the system temp folder. The import is started with the copy of the dump.
Bug Report
In case of too less space on the system drive, the copy process is started and then aborts suddenly with internal error.
Describe how to reproduce the bug
Bloat your system drive with rubbish in your temp directory up to a few megabytes left on the drive. Then do an import of a large SVN repository. We used a dump file with 47 GB of size.
Describe your SCM-Manager setup
SCM-Manager 2.39.1
Which operating system, browser and versions do you use?
Windows Server
Proposals
The text was updated successfully, but these errors were encountered: