this post was submitted on 02 Apr 2025
5 points (100.0% liked)
Hacker News
1148 readers
497 users here now
Posts from the RSS Feed of HackerNews.
The feed sometimes contains ads and posts that have been removed by the mod team at HN.
founded 6 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You are bringing up good approaches and you would have been hired if you could explain how you would start to troubleshoot some of those issues.
The answer to the problem that this team ran into was that you can actually run out of inodes in a filesystem if you have a very large number of relatively small files, and that might show up as failed writes that can make a program like a DBMS say "the disk is full".
Regarding getting hired though, I have no idea about the market and pay nowadays especially wherever you are. I hope it's good for you, it was certainly good for me in the 2010s in Eastern Europe, but I've heard it's shit everywhere these days.
Thank you! One more question: "explain" has always tripped me up. How much detail is necessary, vs too much, for a technical interview? Because in my mind "fsck" is self-explanatory, as would be "check the inode count". Should I cover everything like I'm explaining it to a new user, or is there a baseline skill level I'm expected to address?