Opened 14 years ago

Closed 12 years ago

#2445 closed defect (wontfix)

mythtv-HOWTO LVM2: resizing ext2/3 needs updating

Reported by: hugh@… Owned by: Robert Kulagowski
Priority: minor Milestone: 0.21.1
Component: documentation Version: head
Severity: medium Keywords:
Cc: hugh@… Ticket locked: no


mythtv-HOWTO-24.html describes how to use LVM. The described method for adding to a logical volume and extending an ext2/3 partition is not quite correct for Fedora Core 5.

-lvextend is needed (the current wording suggests that it is only needed for the ReiserFS)

-e2fsadm is replaced by resize2fs (perhaps e2fsadm included lvextend)

Change History (6)

comment:1 Changed 14 years ago by Robert Kulagowski

Status: newassigned

comment:2 Changed 13 years ago by danielk

Milestone: unknown0.21
Type: enhancementdefect
Version: 0.20head

comment:3 Changed 13 years ago by stuartm

Now that we have storage groups, do we really need to give advice on LVM, Raid etc in the MythTV documentation? Although I'm sure people will still want to use them instead of storage groups it's no longer a requirement if you need to expand your mythtv system. Having that information in the documentation is just likely to confuse first time users and will need updating regularly to reflect changes in distros.

I'd be inclined to remove information on LVM from the official docs and into the wiki instead.

comment:4 Changed 13 years ago by Bradley Ford <…>

I agree it should be removed from the official docs and put into the Wiki as the current recommended path is Rec Groups

comment:5 Changed 12 years ago by paulh

Component: mythtvdocumentation

Is no one looking after the docs anymore?

comment:6 Changed 12 years ago by Robert Kulagowski

Resolution: wontfix
Status: acceptedclosed

Docs are still being worked on; just catching up.

However, there's a big warning in the LVM section already: <bf>NOTE</bf>: If you are running MythTV 0.21 and you are using LVM to create one large filesystem to store your recordings, it's no longer recommended that you go the LVM route. The preferred solution is to use <ref id="storagegroups" name="Storage Groups">. They're more flexible and less likely to lose all of your recordings if you have a drive failure.

And this is in the source for the LVM section: <!-- XXXXX REMOVE ME FOR 0.22 -->

So closing this ticket.

Note: See TracTickets for help on using tickets.