From: Sir Civit <sircivit@yahoo.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: btrfs-convert destroyed my system
Date: Fri, 17 Jan 2014 19:30:49 -0800 (PST) [thread overview]
Message-ID: <1390015849.15401.YahooMailNeo@web122606.mail.ne1.yahoo.com> (raw)
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.
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.
next reply other threads:[~2014-01-18 3:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 3:30 Sir Civit [this message]
2014-01-19 1:13 ` btrfs-convert destroyed my system Marc MERLIN
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=1390015849.15401.YahooMailNeo@web122606.mail.ne1.yahoo.com \
--to=sircivit@yahoo.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