From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Newer kernels do not oops if log cannot be re-read at mount
Date: Wed, 4 Sep 2013 11:15:12 -0700 [thread overview]
Message-ID: <20130904181512.GU5342@merlins.org> (raw)
I just wanted to confirm that the crash on unexpected log read during mount
is indeed fixed for me, I now just get a log read failed message.
I've filed a bug with debian to encourage them to add btrfs-zero-log as a
tool in the initrd so that one can have the choice of running this on a non
mounting root filesystem.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721857
Thanks for having fixed this.
In case someone is wondering why I'm still sticking with my SSD :) I'm holding
off just a bit longer for the next generation of SSDs coming out now so that
I can switch away from that questionable line of OCZ Vertex 4 (I tried 4,
they all have this problem of not writing everything correctly when they
hang, which fortunately is rarely).
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/
reply other threads:[~2013-09-04 18:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130904181512.GU5342@merlins.org \
--to=marc@merlins.org \
--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).