From: Marc MERLIN <marc@merlins.org>
To: Sir Civit <sircivit@yahoo.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-convert destroyed my system
Date: Sat, 18 Jan 2014 17:13:11 -0800 [thread overview]
Message-ID: <20140119011311.GC20097@merlins.org> (raw)
In-Reply-To: <1390015849.15401.YahooMailNeo@web122606.mail.ne1.yahoo.com>
On Fri, Jan 17, 2014 at 07:30:49PM -0800, Sir Civit wrote:
>
>
> To start off, I have an encrypted LVM setup with a root logical volume and a home
> logical volume. Today decided to upgrade my home LV to btrfs for
> compression. I installed btrfs-progs, unmounted /home, and ran
> btrfs-convert /dev/MyVolumeGroup/home
> and it completed with no errors reported. I rebooted my system, and I got a "Welcome to emergency mode!" message. I rebooted into a live CD and
> found that all of my logical volumes were showing up, but almost all of
> them showed status "NOT available". I ran vgck and lvck, both of which
> found no
> errors. I ran lvscan and still /dev/MyVolumeGroup/ (and
> /dev/mapper/MyVolumeGroup-*) contains only one of the LVs.
What's the kernel verion?
What's the version of btrfs-tools?
For what it's worth I also tried a btrfs convert on ubuntu precise with
their stock kernel and old btrfs-tools and it mostly destroyed the
filesystem too, but at the same time I figured I got what I deserved for
running tools and a kernel that old on that machine (not mine, hence the
issue).
Marc
> It seems that btrfs-convert possibly overwrote the LVM metadata somehow, but I have no idea how
> since the argument was a logical volume. Even if I had accidentally
> typed /dev/MyVolumeGroup, I would think that btrfs-convert should have
> realized that it was not an ext2/3/4 filesystem.
>
> I tried mounting one of the "available" LVs, and got
> mount: /dev/MyVolumeGroup/root is write-protected, mounting read only.
> mount: special device /dev/MyVolumeGroup/root does not exist.
>
> I've already
> started a fresh installation due to time constraints, but I'd like to
> find out why this happened and let everyone know about a potential bug.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
"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
next prev parent reply other threads:[~2014-01-19 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 3:30 btrfs-convert destroyed my system Sir Civit
2014-01-19 1:13 ` Marc MERLIN [this message]
2014-01-20 3:46 ` Roger Binns
2014-01-19 18:51 ` Martin Steigerwald
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=20140119011311.GC20097@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=sircivit@yahoo.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 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.