"...Well I dunno but let's see...Filesystem Z(let's say reiserfs)...so this one's pretty good with really large files...its preferred to other ones(say ext2) for both support of larger files and better disk checking...at the time of distro x, version y, filesystem D(that you may be familiar with) hadn't even come out and was probably an improvement over Z, so I'd wager less bytes per block than filesytem D but more than...."
...or so could be a possible response...I hope I am getting my point through, though of course you're the one to have lived through the day and not me and I'm sure your reply was what you felt best, at the time.
"I'd google it" is exactly the right answer, as far as I'm concerned. Unfortunately, it's never the answer interviewers want to hear. Regardless of whether they've asked good questions, it's invariably one of the most common responses interviewees will make when they don't know the answer. Whether or not the interviewer had a justified expectation that you should know the answer, "I'd google it" immediately gets you downranked by association with people who don't know their shit.
I assume this was an intentional approach: find an area of knowledge the candidate should understand at a high level, but probably hasn't committed the details of to memory, and see if they can reason it out.
You learn significantly more about someone when they're a bit out of their element; does their confidence evaporate, or do they work through it and come up with a reasonable solution?
That particular thought did only occur to me sometime later though so could be it certainly.
I'll frame this in what I know, which is programming. I think it's entirely reasonable to ask someone how a hashtable or even a quick sort (or some other O(n log n) sort) works because programmers should be familiar with that even if 99.9% of the time (if not 100% of the time) you're using a HashMap or std::map or dict or whatever.
But number of inodes does seem somewhat esoteric.
I found it pretty ironic actually as that's exactly the kind of thing we have search engines for.
Anyway, isn't block size standard across all OS?
Apologies for sounding a little addled but it's been five years since I have been a systems administrator so it's all melted together in my memory.
-b block-size Specify the size of blocks in bytes. Valid block-size values are 1024, 2048 and 4096 bytes per block. If omitted, block-size is heuristically determined by the filesystem size and the expected usage of the filesystem (see the -T option).
I remember that Red Hat and Fedora used 1024 on my computer.
As for the distribution specific thing, maybe some distribution had their own version of /etc/mke2fs.conf (settings for mkfs, including block size).
echo "a" > a; du -sh a; rm a
2.0K a
dumpe2fs /dev/sda1 | grep -i 'Block size'
Block size: 1024
$ du -sh /tmp/a
4.0K a
$ tune2fs -l /dev/mapper/VolGroup00-LogVol00 | grep "Block size"
Block size: 4096
I get similar behavior on the other partition:
echo "a" > a; du -sh a
8.0K a
dumpe2fs /dev/VolGroup00/LogVol00 | grep "Block size"
Block size: 4096
Though if I 'touch' the files to create them, they are the blocksize. Which seems odd, since on my AIX and HP-UX boxes that gives files of size 0.
And of course there are those who would answer take a best guess stab rather than appear to not know the answer which would be undesirable as well.
What's the default bytes per block in random linux distribution x version y when using filesystem z?
My response;
I'd google it.
Perhaps this is unique to the Australian branch of Google or something but I get the impression that they're much more into the whole meaningless rote memorisation of facts than is often let on.
I had a contact from another Google HR person a couple months back in Estonia, this time for a development position. I can't say I wasn't tempted but this time I turned them down flat.