Behind the death of antipasto

0
34

By Calder Phillips-Grafflin

antipasto.union.edu is dead, killed by the power surge at approximately 5 a.m. on Saturday, April 16.

For years, the computer science department’s antipasto server has provided services for students of Division 4 ranging from Mechanical Engineering to Neuroscience, but this has come to a sudden end. In its place, eagle.union.edu (shown here) has taken its place.

What killed antipasto? While we may never know completely, it appears that antipasto died because of hard drive corruption. When the power abruptly failed, several critical parts of the boot directories were corrupted.

Because antipasto is an older RHEL 4 (Red Hat Enterprise Linux) system, the older EXT3 file system failed to handle to the corruption properly and simply deleted the corrupt files.

Normally, this wouldn’t be a problem, but since the corrupted files were necessary for antipasto to boot, this caused a critical failure when Lance tried to start it back up.

The good news, however, about this sort of failure is that none of your data was damaged. In fact, the reason that all your files are intact on eagle is because all the data on antipasto could be manually transferred from antipasto to eagle.

However, if you had a website hosted on antipasto, you’ve probably already talked to Lance about it, since the links and fancy domain names don’t work anymore.

For everyone else, the only potential problem caused by moving your antipasto accounts to eagle is that your files are no longer at

/home/<your_name>/

but are instead at

/export/students/<your_name>/

This should only pose a problem if you’re using a script that requires precise directory paths, since everything else is handled automatically by the server.

NO COMMENTS

Leave a Reply