Boot fails due to file check. Inode "long_number" has EXTENTS_FL flag set on filesystem without extents support.
I was configuring desktop settings and suddenly ubuntu was going terribly slow and windows turned grey.
So I restart (by normal means and with a lot oof patience) and it runs a "routine" filescan. It stops at 25% and this is the problem: "Inode "long_number" has EXTENTS_FL flag set on filesystem without extents support."
And it sais it's in read only mode and it can't fix the problem. But I can manually fix it:)
so I type: sudo fsck
and it works:-D.
I asks me if I want to fix this problem (Y), "clear Inode "bla bla bla"?"(Y).
So why ask a question? Well I'm pretty new to ubuntu(1week and a few days) and I wonder if I'm doing the rght thing. Because the Inodes without extents support keep coming and do I have to keep clearing them? Because I'm just doing what seems right. I have no Idea if it's right.
So far I cleared about 10 Inodes, do I continue?
Or should I reboot?
Or something else?
Many thanks in advance,
Thomas.
ps: If it's possible, can someone explain what Inodes are and what my problem is?
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Vanostaajen
- Solved:
- Last query:
- Last reply: