[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-390
Subject:    Re: FEDORA F20 boot HCPGIR453W CP entered; program interrupt loop
From:       Tom Huegel <tehuegel () gmail ! com>
Date:       2014-04-15 19:48:10
Message-ID: CAJ=UyY5G8CZdssfeaapthjDc2ogjHXrP0nFosHGujQfY0n0Y=Q () mail ! gmail ! com
[Download RAW message or body]

By it worked I meant the HCPGIR453W error went away and I was able to boot
the Linux Kernel.


On Tue, Apr 15, 2014 at 12:21 PM, Rick Troth <rickt@velocitysoftware.com>wrote:

> Don't let the filesystems scare you. (see below)
>
>
> On 04/15/2014 02:04 PM, Tom Huegel wrote:
> > I did the install using btrfs (whatever that is... don't laugh I am a VM
> > guy not too much into LINUX) file system and it worked.
>
> Based on your note some 45 min later, I have to ask: "it worked" means
> what worked?
>
> As Russ reports, kickstart installation (to EXT4 on top of LVM) works.
> Problem is that when one applies service, _and the kernel is updated_,
> reboot fails.
> In VM speak,  new IPL text is stamped on the minidisk, and it goes wrong.
>
> So ... you would do well to use _EXT4+LVM and then defer updating your
> kernel_ until the problem is fixed.
> OR ... if you can install so that _/boot has its own partition_ (or even
> its own disk), that would be safer still.
>
> --- snip ---
>
> Filesystems ... Think CMS "EDF", the stuff you see when you eyeball your
> 191 with DITTO. That's all there is to it. Different ideas, different
> requirements, and other factors have led to many filesystems being
> created over time. Linux supports more filesystem types than any other
> op sys. BTRFS and EXT4 are just two of them.
>
> BTRFS and ZFS do some of what LVM does, so people often dispense with
> LVM when using BTRFS or ZFS.
>
> The most common filesystem used in new Linux installations (I state w/o
> proof) is presently EXT4. Before that it was EXT3. At one point,
> ReiserFS had some traction. (long sordid story - not going there) Going
> back further, EXT2 was common on Linux before journalling was recognized
> as vital.
>
> LVM is the logical volume manager which can host any supported Linux
> filesystem. Think of it as an alternative to partitioning. (But most
> people still render individual disks as one large partition, even when
> it's not strictly required.) Feed disks or partitions into LVM as PVs
> and then mount filesystems on the other side of LVM as LVs. Some links
> which may help ... good bedtime reading ...
>
>   * http://en.wikipedia.org/wiki/List_of_file_systems
>     (sadly, CMS EDF doesn't show up in the list)
>
>   * http://en.wikipedia.org/wiki/Btrfs
>
>   * http://en.wikipedia.org/wiki/Ext4
>      -and-
>   * http://en.wikipedia.org/wiki/Ext2
>
>   * http://en.wikipedia.org/wiki/Logical_Volume_Manager_%28Linux%29
>
>
>
>
> --
>
> Rick Troth
> Senior Software Developer
>
> Velocity Software Inc.
> Mountain View, CA 94041
> Main: (877) 964-8867
> Direct: (614) 594-9768
> rickt@velocitysoftware.com <mailto:rickt@velocitysoftware.com>
>
>
>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to LISTSERV@VM.MARIST.EDU with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.MARIST.EDU with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
[prev in list] [next in list] [prev in thread] [next in thread]