This morning the 2025 order archive was attached to the server — it is mounted read-write at /mnt/archive. Accounting asks you to check July. Open orders-07.csv and mark the check with an empty file next to it.
Check the July orders
The archive is mounted at /mnt/archive. Open the July orders, mark the check with an empty checked.txt file next to them and see how the archive is mounted.
First, predict
orders-07.csv did not open. What will touch answer for a new file in the same directory?
Now start the exercise, run the command and compare your prediction with the output.
cat got Bad message, touch got Input/output error, and findmnt shows the archive mounted read-write. What follows from this?
-
Running out of space gives
No space left on device. The archive is a separate filesystem on /dev/loop0;df -h /mnt/archiveshows its space. -
The kernel calls a lack of permissions
Permission denied. The directory is yours:ls -ld /mnt/archive/2025. -
A flock lock does not stop reading the file or creating others next to it. The read and write errors came from the filesystem itself.
The archive filesystem is damaged, and writing to it has been stopped.