[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.01.0906121450530.3237@localhost.localdomain>
Date: Fri, 12 Jun 2009 14:55:33 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Chris Mason <chris.mason@...cle.com>
cc: linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 2.6.31-rc
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists