3 ms·
You'd never need to know anything about it as a user. I don't know how anyone could seriously make the argument otherwise. In fact the only reason I know anyth
by pram 5y ago
You'd never need to know anything about it as a user. I don't know how anyone could seriously make the argument otherwise.
In fact the only reason I know anything about inode and dentry specifics is because they are 'very clever' interviewer favorites! I've been a professional UNIX admin for 15 years and I've dealt with inode issues literally once in my life lol
- kevstev 5y agoThanks. Its comments like the GPs that makes me wonder how I have avoided learning some very commonplace issue and its these types of comments that foment imposter syndrome. I have even read books on linux architecture and remember discussions about filesystems and inodes and remember the general structure and form, but a detail around what is and what is not stored in the actual inode... seems like an absurd detail to memorize. The only way I could see this being commonplace is if I somehow missed out on a widespread bug that somehow caused inodes to be corrupted and requiring manual intervention/surgery to prevent data loss.
- pram 5y agoIt's easy to remember that inode = the stuff that shows up in 'ls -l'