All of lore.kernel.org
 help / color / mirror / Atom feed
* Newer kernels do not oops if log cannot be re-read at mount
@ 2013-09-04 18:15 Marc MERLIN
  0 siblings, 0 replies; only message in thread
From: Marc MERLIN @ 2013-09-04 18:15 UTC (permalink / raw)
  To: linux-btrfs

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/  

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2013-09-04 18:15 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-04 18:15 Newer kernels do not oops if log cannot be re-read at mount Marc MERLIN

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.