Vendor meetings and time… Caffeine: The Double Edged Sword
Mar 27

Today I learned a valuable lesson about the /tmp directory. Now in the afternoon halfdime asked me if I could create a vol on one of our filers of about 100GB, and I’m like sure no problem. So I go abouts creating the slice, adding it to the exports file, and creating the fstab entry (which I slightly screwed up), but honestly that wasn’t the problem. I for some reason known to only myself and god (if you swing that way) decided to test whether I could mount the dir on the /tmp directory. Now I usually know better than to do something like that, though I know we all make noobish mistakes, that was pretty high on the list of n00bish mistakes I have made. It was funny watching my linux system die a slow death of not being able to write anything to the /tmp directory (this is where my screwing up the fstab comes into play), so I wonder if I had set the permissions correctly would my data meant for /tmp have been written to the filer? (I am going to guess yes, but there is still a lot of magic I don’t understand about some of the underpinnings of the *nix OS). So my advice the newb, noob, and n00b systems administrators out there, don’t mount remote filesystems on the /tmp dir.

Ok, so here’s the caveat, we all know and understand the being a system administrator is an interrupt driven job, and I was going to mount then umount the dir on the tmp (I still don’t know why I choose tmp and not mnt, but whatever), but I got distracted.

written by meh. \\ tags: , , , , , , , , , , , , ,

Leave a Reply