From: Linus Torvalds <torvalds@linux-foundation.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 2.6.31-rc
Date: Fri, 12 Jun 2009 14:55:33 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906121450530.3237@localhost.localdomain> (raw)
In-Reply-To: <20090611204456.GA3834@think>
On Thu, 11 Jun 2009, Chris Mason wrote:
>
> Existing filesystems will be upgraded to the new format on the first
> mount. All of your old data will still be there and still work
> properly, but I strongly recommend a full backup before going to the new
> code.
Auugh.
This is horrible. I just screwed up my system by booting a kernel on this:
it worked beatifully, but due to other reasons I then wanted to bisect a
totally unrelated issue. While having _totally_ forgotten about this
issue, even if I was technically aware of it.
.. so I installed a new kernel, and now it won't boot due to "couldn't
mount because of unsupported optional features (1)". In fact, I have no
kernel available on that system that will boot, since my normal "safe"
fall-back kernels are all distro kernels that can't boot this either.
Ok, so I'll end up booting from a USB stick, and it will all work out in
the end, but this does essentially make it entirely impossible to do any
bisection on any btrfs system.
Double-plus-ungood.
Linus
next prev parent reply other threads:[~2009-06-12 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 20:44 [GIT PULL] Btrfs updates for 2.6.31-rc Chris Mason
2009-06-12 21:55 ` Linus Torvalds [this message]
2009-06-12 23:19 ` Theodore Tso
2009-06-13 0:18 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2009-07-02 19:10 Chris Mason
2009-07-02 19:46 ` Chris Mason
2009-07-30 17:56 Chris Mason
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=alpine.LFD.2.01.0906121450530.3237@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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