decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
LVM is NOT a filesystem | 246 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
LVM
Authored by: PJ on Sunday, March 03 2013 @ 01:36 AM EST
OK.

[ Reply to This | Parent | # ]

LVM is NOT a filesystem
Authored by: jesse on Sunday, March 03 2013 @ 07:45 AM EST
It is a VOLUME manager. It creates virtual disks, supports software raid,
stitching physical partitions together to create a software implemented disk
that can the be partitioned.

The problem happened to a lot of people upgrading from F15/16 as there has been
a change in how the boot system recognizes partitions - and it can be easily
confused.

I managed to avoid the problem by having enough disk space to allocate
sufficiently large partitions to not need to use LVM.

Unfortunately, the easiest "fix" is to make a full backup, and then do
a clean install.

Everything else seems to revolve around rebuilding the initrd (initialization
system for Fedora) so that it will recognize the LVM.

UNFORTUNATELY, it is not the custom of Fedora to rebuild the install/upgrade
CDs/DVDs originally released. That means that these disks always have the
problem.

One possible way to upgrade uses "preupgrade" to go from F15 to F17.

Then you have to use the "fedup" procedure (the replacement for
"preupgrade" to go from F17 to F18.

Unfortunately, this is not guaranteed to work.

My suggestion (I'm staying on F16 due to the problems both F17 and F18 have -
I'm hoping they are fixed in F19) is to wait a while. The F19 is supposed to be
released in a month or two, and hopefully the fix will be in that.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )