linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Chris Mason <clm@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: URGENT: my laptop's boot ssd btrfs crashed, what do you need off it?
Date: Wed, 7 May 2014 17:43:44 -0700	[thread overview]
Message-ID: <20140508004344.GE11401@merlins.org> (raw)
In-Reply-To: <536AD20E.70004@fb.com>

On Wed, May 07, 2014 at 08:38:38PM -0400, Chris Mason wrote:
> Looks like you're on 3.14, did this have the fixes from my git tree
> that went into 3.15-rc?
 
You're correct, it's running 3.14.0. Considering that it's my main laptop
that I kind of need to work, I avoid rc kernels if possible :)
But if I had known that 3.14 had corruption problems, I'd have
re-thought that :)
(besides my report, were there other ones I missed? Is 3.14.0 something
to avoid for now?)
(yes, I know 3.14.3 is out now, I should upgrade)

> For now I'd say that if you can make a dd image of the FS, please do
> so.  Otherwise, I don't want to suck down your time right before the
> trip.

A full dd image is not practical, it's 1TB and I have nowhere to put it.
I could do an image if you'd like, and upload it when I have proper
internet (I'm thinking it's likely going to be a 1GB upload)

(by the way, I'm already in the trip, and I have 1h before my next
plane and a bit of time tonight (in 10H my time that is) to upload stuff
or more logs if that helps.

But more importantly, I have my main file server at home running 3.14.0
too. Is there a risk of known corruption, or nothing known yet?

Of if you'd like output of fsck in dry-run mode, I can do that too.

Thanks,
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/                         | PGP 1024R/763BE901

  reply	other threads:[~2014-05-08  0:43 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 [this message]
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 ` URGENT: my laptop's boot ssd btrfs crashed, what do you need off it? Tom Kuther
2014-05-10 11:42   ` 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=20140508004344.GE11401@merlins.org \
    --to=marc@merlins.org \
    --cc=clm@fb.com \
    --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).