From: Marc MERLIN <marc@merlins.org>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: linux-btrfs@vger.kernel.org, jbacik@fb.com, clm@fb.com,
takeuchi_satoru@jp.fujitsu.com
Subject: Re: btrfs-zero-log fails, can't mount FS
Date: Thu, 14 Aug 2014 10:27:43 -0700 [thread overview]
Message-ID: <20140814172743.GC27531@merlins.org> (raw)
In-Reply-To: <53ECE953.70009@gmail.com>
On Thu, Aug 14, 2014 at 12:52:35PM -0400, Austin S Hemmelgarn wrote:
> I don't think it is likely that the Samsung SSD is to blame, in my
> experience Samsung's SSD's are better than almost every other brand
> except Intel, and I know that they honor write-barriers correctly.
> The likely issue is that the system hung during the process of a commit,
> which is one of the few things that I know of that consistently corrupts
> the filesystem. There isn't really anything I know of to prevent it,
> except for making your system as stable as possible.
> Interestingly, this type of thing is the only issue I've ever had with
> BTRFS that wasn't traceable to hardware problems.
That was my understanding too, thanks for confirming.
Until this bug gets fixed, I'm perplexed as to why btrfs-zero-log isn't
fixing this.
Can't I unroll the last commits until I get to a stable one?
As luck would have it (again), I'm boarding a plane to Chicago tomorrow to
go speak at linuxcon about btrfs.
I would very much like not to have to spend 12H to restore my SSD from
backup :)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2014-08-14 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 16:09 btrfs-zero-log fails, can't mount FS Marc MERLIN
2014-08-14 16:52 ` Austin S Hemmelgarn
2014-08-14 17:27 ` Marc MERLIN [this message]
2014-08-14 19:10 ` Chris Murphy
2014-08-14 19:14 ` Marc MERLIN
2014-08-14 22:03 ` Chris Mason
2014-08-14 22:28 ` Marc MERLIN
2014-08-15 0:17 ` Chris Mason
2014-08-15 4:11 ` Marc MERLIN
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=20140814172743.GC27531@merlins.org \
--to=marc@merlins.org \
--cc=ahferroin7@gmail.com \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=takeuchi_satoru@jp.fujitsu.com \
/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).