From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Problem with unmountable filesystem.
Date: Thu, 18 Sep 2014 21:25:02 +0000 (UTC) [thread overview]
Message-ID: <pan$ad8f6$a12f1532$9aeffa42$c560f86b@cox.net> (raw)
In-Reply-To: 541B1263.3090804@gmail.com
Austin S Hemmelgarn posted on Thu, 18 Sep 2014 13:12:03 -0400 as
excerpted:
> Secondarily, this almost makes me want to set the ssd option on all
> BTRFS filesystems, just to get the rotating superblock updates, because
> if it weren't for that behavior, I probably wouldn't have been able to
> recovery anything in this particular case.
That's an interesting point. All my btrfs are on ssd ATM and I'm still
using reiserfs on the spinning rust until btrfs further stabilizes, but
at some point I imagine I'll switch everything to btrfs, and I hadn't
thought about this.
Tho I could do with a good explanation of how both ssd and rotational
superblock update handling works and the differences between the two, as
I'm not entirely clear on it myself, at this point.
--
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-09-18 21:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 14:40 Problem with unmountable filesystem Austin S Hemmelgarn
2014-09-16 20:57 ` Chris Murphy
2014-09-17 11:23 ` Austin S Hemmelgarn
2014-09-17 18:57 ` Chris Murphy
2014-09-17 20:07 ` Duncan
2014-09-18 17:12 ` Austin S Hemmelgarn
2014-09-18 21:15 ` Chris Murphy
2014-09-18 21:25 ` Duncan [this message]
2014-09-19 17:07 ` Chris Murphy
2014-09-19 17:42 ` Austin S Hemmelgarn
2014-09-17 20:22 ` Duncan
2014-09-18 17:19 ` Austin S Hemmelgarn
2014-09-19 17:54 ` Chris Murphy
2014-09-19 18:44 ` Austin S Hemmelgarn
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$ad8f6$a12f1532$9aeffa42$c560f86b@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).