Timeline for What are inodes good for?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2020 at 0:05 | comment | added | G-Man Says 'Reinstate Monica' | (Cont’d) … Things got better when they changed the filesystem code to do disk writes in a more intelligent order — e.g., remove a block from the free list before allocating it to an inode; allocate and write an inode before writing a directory entry that points to it — and made incremental changes to the filesystem structure — e.g., storing multiple copies of the superblock. Maybe the FAT filesystem was just coded sloppily, and had more subtle design flaws. | |
| Apr 12, 2020 at 0:05 | comment | added | G-Man Says 'Reinstate Monica' | Not per se, but the early Unix systems (e.g., version 6, in the mid-late 1970s) were notorious for suffering filesystem damage whenever the system crashed (whether because of an internal error (panic) or losing power without being shut down), and yet the Unix v6 filesystem was fundamentally similar to later versions — specifically, it had directories that were just lists of filenames and inode numbers, and inodes that were separate from data blocks. … (Cont’d) | |
| Apr 11, 2020 at 22:11 | comment | added | user732 | @G-ManSays'ReinstateMonica' - You've got a good point. But the original FAT filesystem was prone to getting trashed. Got a better explanation? | |
| Apr 10, 2020 at 20:23 | comment | added | G-Man Says 'Reinstate Monica' | I’m not sure your penultimate paragraph really makes much sense. If a sector in the i-list goes bad, you’ve lost several files. Sure, you might know the names of the files that have been lost; how helpful is that? | |
| Apr 10, 2020 at 20:23 | history | edited | G-Man Says 'Reinstate Monica' | CC BY-SA 4.0 | Fixed spelling; formatted quote as a quote; added links. |
| Aug 13, 2012 at 23:08 | history | answered | user732 | CC BY-SA 3.0 |