Robert White posted on Tue, 14 Oct 2014 09:54:51 -0700 as excerpted: > On the BTRFS system much of my browser settings for firefox were > trashed, particularly the cookies and saved conifigurations for add-ons > (like which sites had scripts enabled/disabled in no-script) etc.
FWIW, this reply is more toward the firefox corruption than the why-particulars of the crash. The prefs.js file in the profile dir holds addon settings and seems to be particularly sensitive to corruption. At least here, firefox has created several backups, prefs-1.js thru prefs-7.js, I suppose at upgrade. The first time I lost settings I restored prefs-7.js (the newest/largest of the backups) as prefs.js, and only lost a few settings that I had changed since the last upgrade, which had changed the firefox interface so I had to change my settings accordingly. The time or two since then that I hard-crashed and lost my addons, I was able to replace the prefs.js file from a recent /home backup. Anyway, it's the prefs.js file that you want to restore. Whether it's from the last prefs-N.js backup that firefox did, or from your own backup, prefs.js is it. As for cookies, history, etc. I didn't notice them going corrupt. I do run raid1 btrfs and after a crash, do a scrub, which may recover some files. And I run tight enough security that most cookies are session- only (and no third-party), so that file won't be written to much, which probably saves it. I don't know about history. Maybe it was corrupted and I simply didn't notice it, as I don't use history that often. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
