Lost and found
So, today we had a 3ware card spectacularly fail. More on that on another post tomorrow.
In the course of trying to recover from it, there was a long fsck that ended up having to put lots of stuff in lost+found. That’s fine, I really can’t expect that it would do more than that when it doesn’t have the information.
However, who the hell decided that the files should not only be named after their inodes, but that there should be a # in front of the inode number in the filename? I think naming them after the inode is fine, but anyone who is savvy enough to be poking around in lost+found after a major filesystem breakdown KNOWS that they’re inode numbers, and when you’re already in a frustrating enough situation (and, in a lot of circumstances like this you’re going to be at the console, perhaps in a loud datacenter, rather than in a comfy chair with your laptop), why do you want to have metacharacters in every freaking filename?
You have to remember to escape the # in every single freaking file, so that you don’t do something like
cd #0774339
and end up in /root/
It seems like needless complexity in an already complicated situation.
