From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Random file system corruption in 3.17 (not BTRFS related...?)
Date: Tue, 14 Oct 2014 22:35:14 +0000 (UTC) [thread overview]
Message-ID: <pan$ce890$598bb3af$d0bcd705$e79f1b9b@cox.net> (raw)
In-Reply-To: 543D555B.50708@pobox.com
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
next prev parent reply other threads:[~2014-10-14 22:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 16:54 Random file system corruption in 3.17 (not BTRFS related...?) Robert White
2014-10-14 17:22 ` David Arendt
2014-10-14 20:06 ` Robert White
2014-10-14 22:35 ` Duncan [this message]
2014-10-15 7:08 ` Juan Orti Alcaine
2014-10-15 8:53 ` Duncan
2014-10-15 13:46 ` Josef Bacik
2014-10-15 14:05 ` Juan Orti Alcaine
2014-10-15 14:30 ` Josef Bacik
2014-10-15 14:34 ` Juan Orti Alcaine
2014-10-15 19:30 ` Rich Freeman
2014-10-15 20:20 ` Josef Bacik
2014-10-17 16:26 ` Filipe David Manana
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$ce890$598bb3af$d0bcd705$e79f1b9b@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).