From: Tom Kuther <tom@kuther.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: URGENT: my laptop's boot ssd btrfs crashed, what do you need off it?
Date: Sat, 10 May 2014 09:26:22 +0000 (UTC) [thread overview]
Message-ID: <loom.20140510T112209-573@post.gmane.org> (raw)
In-Reply-To: 20140507233959.GB11401@merlins.org
Marc MERLIN <marc <at> merlins.org> writes:
>
> Details:
> My system didn't crash, but the filesystem went read only, and of course
> couldn't syslog the error.
> Thankfully I was saved by remote syslog which did work:
>
> kernel: [545039.443412] ------------[ cut here ]------------
> kernel: [545039.443429] WARNING: CPU: 2 PID: 556 at fs/btrfs/inode.c:4927
btrfs_invalidate_inode
The same thing happened to me just right now. Also on my SSD, also at
"fs/btrfs/inode.c:4927 btrfs_invalidate_inode", also on 3.14.
Is this maybe the (in)famous snapshots bug that got fixed in 3.15?
next prev parent reply other threads:[~2014-05-10 9:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 23:39 URGENT: my laptop's boot ssd btrfs crashed, what do you need off it? Marc MERLIN
2014-05-08 0:38 ` Chris Mason
2014-05-08 0:43 ` Marc MERLIN
2014-05-08 1:34 ` Marc MERLIN
2014-05-08 17:40 ` Justin Maggard
2014-05-08 22:02 ` Marc MERLIN
2014-05-09 10:35 ` Fwd: " Marc MERLIN
2014-05-09 16:19 ` Chris Murphy
2014-05-09 22:36 ` btrfs cleaner failure - fs/btrfs/extent-tree.c:5748 (3.14.0) Marc MERLIN
2014-05-10 0:00 ` Chris Murphy
2014-05-10 0:42 ` Marc MERLIN
2014-05-10 1:05 ` Hugo Mills
2014-05-10 1:54 ` Chris Murphy
2014-05-10 13:51 ` Marc MERLIN
2014-05-10 16:34 ` Chris Murphy
2014-05-10 1:09 ` Hugo Mills
2014-05-10 2:02 ` Duncan
2014-05-10 3:40 ` Marc MERLIN
2014-05-11 2:28 ` Duncan
2014-05-11 12:34 ` Marc MERLIN
2014-05-10 0:13 ` Chris Samuel
2014-05-10 9:26 ` Tom Kuther [this message]
2014-05-10 11:42 ` URGENT: my laptop's boot ssd btrfs crashed, what do you need off it? Chris Samuel
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=loom.20140510T112209-573@post.gmane.org \
--to=tom@kuther.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 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.