From: Rich Freeman <r-btrfs@thefreemanclan.net>
To: Anand Jain <Anand.Jain@oracle.com>
Cc: "G. Richard Bellamy" <rbellamy@pteradigm.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Upgrade to 3.19.2 Kernel fails to boot
Date: Mon, 23 Mar 2015 09:22:36 -0400 [thread overview]
Message-ID: <CAGfcS_miW0=6A7a5PAQZcseCbS1KDpTPM7woKTosMjnAB3C3Cw@mail.gmail.com> (raw)
In-Reply-To: <550FCD9C.1000706@oracle.com>
On Mon, Mar 23, 2015 at 4:23 AM, Anand Jain <Anand.Jain@oracle.com> wrote:
>
> Do you still have the problem ? Can you pls confirm on the latest btrfs ?
> Since I am fixing the devices part of the btrfs, I am bit nervous.
I'm having a similar problem. I'm getting some kind of btrfs
corruption that causes a panic/reboot, and then the initramfs won't
mount root for 3.18.9, but it will mount it for 3.18.8.
Running on 3.18.8 eventually caused the panic to repeat, so I'm not
sure that 3.18.9 is necessarily breaking things - it might just be
fussier about not mounting a dirty fs.
I did run a btrfs check --repair and it ended up moving some chromium
preferences from the user profile folder to lost+found. That got the
system to run for about 8 hours, but it still paniced the next
morning. I'm now running on 3.18.7 to see what happens.
Unfortunately I haven't been doing a good job about capturing logs.
I'll try to capture more the next time this happens. I've been
running fine on 3.18 for a while now, so I'm not sure where all of
this is coming from.
--
Rich
next prev parent reply other threads:[~2015-03-23 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 23:06 Upgrade to 3.19.2 Kernel fails to boot G. Richard Bellamy
2015-03-19 23:19 ` Chris Murphy
2015-03-22 21:15 ` Ochi
2015-03-22 21:25 ` Roman Mamedov
2015-03-23 8:23 ` Anand Jain
2015-03-23 13:22 ` Rich Freeman [this message]
2015-03-23 16:37 ` Rich Freeman
2015-03-24 6:31 ` Anand Jain
2015-03-24 10:40 ` Rich Freeman
2015-04-01 6:50 ` Anand Jain
2015-04-01 19:48 ` Rich Freeman
2015-03-31 21:24 ` Benjamin Hodgetts
2015-03-31 22:23 ` Chris Murphy
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='CAGfcS_miW0=6A7a5PAQZcseCbS1KDpTPM7woKTosMjnAB3C3Cw@mail.gmail.com' \
--to=r-btrfs@thefreemanclan.net \
--cc=Anand.Jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rbellamy@pteradigm.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).