Viewing a single comment thread. View all comments

ItsMeOnly3 t1_ja7002q wrote

Technically it didn't crash per see, it rebooted due to disk failure and stopped because automatic recovery might make things worse (crosslinked i-nodes - two files occupying the same space).

67

d4nowar t1_ja9bifw wrote

Probably opens and closes files as part of its app and crashed originally due to hitting an inode limit?

3

ItsMeOnly3 t1_ja9tedi wrote

Or streamed large files (movies), hit disk full (bet there's a rather small and thus inexpensive SD card present), aborted bringing down X and forcing system reboot where upon next boot fsck hit duplicated blocks

3

TechnicalParrot t1_ja9hi91 wrote

Every time I think I've understood the Linux boot error someone understands it better - I only got as far as drive corruption though seeing fsck

1