| Table of Contents |
|---|
This page details some of the ways that uploading a file might fail, the client errors received, files persisted to disk, etc. as a result. The primary objective is to understand how Fedora fails under different circumstances, and identify any bugs that can be fixed to improve reliability.
...
- Uploads that completed successfully and without error message could all be transferred to another VM and read successfully.
- Filling up the disk or undeploying Fedora result in files being written to the Fedora home directory but not tracked by the repository.
- Filling up the disk and then attempting to update Fedora results in an unresponsive repository.
...
General procedure
- Run Fedora 4 in Tomcat on one VM.
- Upload a large file from a second VM using curl. 4GB files were used so transfer times would be long enough to interrupt the upload process.
- Upload a second file, and interrupting the upload in various ways to simulate application, network or hardware failures.
- Copy the Fedora home directory to the second VM and run a separate Fedora instance to verify that the files could be retrieved
...