Firefox made a weird CACHE problem.

Asked by heatblazer

Just an hour ago, I was browsing with FF3 then a weird error appeared when I tried to download a small file. It said that my download dir is only READ and I don`t have a permission to write there and to select a different one. A seconds after that my aMule closed and refused to open because the ./amule/TEMP is read only then Azureus gave the same error. I opened HOME and right-click to create a new file/folder - it was disabled due to root restricitons... That was weird, I rebooted and a FCSK was performed. At the very begining it stopped giving me an error and required a PASS and a manual usage. I did so. After a confirmed a few "Y"-ses I saw the check disk: there was an error in Mozilla Firefox Cache in ??? fix? [Y] for yes.... Now everything is fine. But that error gave me the creeps....

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu firefox Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #326797.

Revision history for this message
C. Cooke (ccooke) said :
#1

Hi,

In Ubuntu, the filesystems are mounted with an option that tells the kernel to automatically make them read-only when there's an error detected. This is to prevent any (further) damage to your files. Such an error could be a sign of hardware failure, a random bit error (random bit errors are rare, but unavoidable; statistically, with many of the large drives on sale today, you would expect to get one random bit error if you ever read the entire disk). It may even be a kernel filesystem bug, although that's less likely.

I'm going to mark this bug as incomplete for now; if you get more errors, we can try to determine if it's hardware or software. If there's nothing new, I'll mark it as invalid after a week or so.

Revision history for this message
heatblazer (heatblazer-gmail) said :
#2

Thanx, I`ll report if there is something fishy.

Revision history for this message
heatblazer (heatblazer-gmail) said :
#3

In Ubuntu, the filesystems are mounted with an option that tells the kernel to automatically make them read-only when there's an error detected. This is to prevent any (further) damage to your files. Such an error could be a sign of hardware failure, a random bit error (random bit errors are rare, but unavoidable; statistically, with many of the large drives on sale today, you would expect to get one random bit error if you ever read the entire disk). It may even be a kernel filesystem bug, although that's less likely.

Now that I recall, looking at you comment, I am sure that it`s not the preventer of the mounting. I`ve had such issues on windows drives when win crashes then you boot in linux the win drive is unmountable. No probs here. The problem was that even though nothing crashed, the check disk could not initiate it wanted Ctrl + D to reboot or master pass to manually conf. Then it found:
Error on mozilla cache in 156666 (something like that) found ??? Fix it? [y] for yes

So that was weird. Not the safe mounting...

Revision history for this message
C. Cooke (ccooke) said :
#4

That's just fsck playing safe; when it finds an error that needs more than very trivial fixing, it requires the root password to continue. This ensures that the fsck only runs when the computer's administrator is ready for it.

Revision history for this message
xteejx (xteejx-deactivatedaccount) said :
#5

This is not a bug, but rather how it is meant to be. If Windows crashes or shuts down uncleanly, linux will not mount it to save data loss. If this happens, boot into Windows and run chkdsk /r to repair any problems, and reboot twice.
This bug report is being converted to a question.
In future, you can find answers to many problems on the Answers section of Launchpad or on IRC at the #ubuntu channel at irc.freenode.net
Thank you.

Revision history for this message
xteejx (xteejx-deactivatedaccount) said :
#6

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs#When%20not%20to%20file%20a%20bug.

Revision history for this message
Launchpad Janitor (janitor) said :
#7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.