Bruce Dubbs wrote:
> About Filesystems, LVM, and RAID
> 
> 
>     Filesystems
> 
>       Compare Ext2/3/4, Reiser4, JFS, XFS (Add jfsutils to the book)
> 
>       Mention FAT/NTFS, BTRFS, ISO9660, and UDF
> 
>     LVM
>       fdisk type 8e

Note that this is absolutely not required.  I'm using partition type 83
on my PV with no problems at all.  You just need to ensure vgchange can
find the PV(s) when you run it at boot time; it doesn't use the info in
the partition table to do that.  :-)

(Though I don't know how vgchange finds the PVs.  I think it scans
through /proc somehow, looking for all block devices, and looks for the
PV header on each, then finds the VG name(s) from those headers.)

Anyway, it's a somewhat useful convention, but I think as long as we
make that clear (that it's not required, it's only convention), that's
fine.

>       pvcreate
>       vgcreate
>       lvcreate
>       mkfs
>       mount / fstab
> 
>     RAID
> 
>       Type 0, 1, 5, others
>       fdisk type fd

Only for Linux md-raid kernel autoassembly, I think?  Otherwise (if you
manually assemble the device in an initramfs), you should be able to
specify the --homehost field to mdadm, and it'll find all current RAID
members with that same field value in their metadata.

>       Using mdadm (needs to be added to the book)
>         mdadm --create
>       LVM and RAID
>       Mention HW RAID

One thing that a lot of "hardware RAID" guides get wrong is that most
consumer hardware RAID isn't, actually.  If it was, it wouldn't need
assembly by Linux; it'd auto-assemble itself and expose just a single
block device to userspace.  Most real hardware RAID cards are SCSI these
days.  :-)

However, winmodem-style RAID is a reasonable fit for an initramfs, too,
so hey whatever.  Used to be this was handled via device-mapper and the
dmraid userland tool, but development seems to have stopped on that, and
I don't know how more recent winmodem-style RAID "cards" are driven from
Linux these days.

> -------------
> 
> GRUB and initramfs
> 
>    Using dracut to create an initramfs (add dracut to the book)

Does dracut try to reuse the same /dev in the initramfs and in the real
rootfs?  (Is *not* doing that an option?)  Because there are all kinds
of issues with not losing uevents when moving udev from the initramfs
onto the real rootfs (after it gets mounted) that are easier to sidestep
I think.

(Plus trying to set it up will require bootscript changes, which won't
work with a non-initramfs setup.)

>    Grub2 Configuration for advanced partition layouts
>      Other considerations

Looks good.  Thanks!

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to