Re: How to rebuild the kernel for the network install

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2011/9/29 Craig White <craigwhite@xxxxxxxxxxx>:
> On Wed, 2011-09-28 at 15:03 -0500, Bruno Wolff III wrote:
>> On Wed, Sep 28, 2011 at 11:41:22 -0600,
>>   Pete Travis <me@xxxxxxxxxxxxxx> wrote:
>> > Bash will expand $(inane -r) for you - you can pass it any kernel you have
>> > headers installed for.
>> >
>> > I wanted to jump in to suggest you reconsider motherboard driven fakeraid.
>> > The mainboard becomes a single point of failure, and replacing it or
>> > migrating the array can be problematic, especially with different chipset
>> > revisions or BIOS versions.
>> >
>> > I recommend you set up a mdadm array.  Drivers are in the kernel,
>> > documentation is profuse, and management is fairly simple once you get the
>> > hang of it. The graphical installer can even do it for you.  Use the array
>> > for /home and possibly /etc and /var, and keep your root filesystem separate
>> > from your important data.
>>
>> There is a downside to using mdadm over fake raid and that is that you
>> can hit a bottleneck with the PCI bus as the data needs to be sent to
>> each disk drive that needs a copy of the data (or parity info) instead of
>> just once to the controller. Typically this will be twice as much data.
>>
>> That said, I use mdadm. I have done such things as drop one side of my
>> raid 1 mirrors, repartition that drive, set up new mirrors with encrypted
>> file systems, and copy over file system data, repartion the other disk,
>> add those partitions to the new mirrors.
> ----
> doesn't fake raid do the same thing? If there isn't an intelligent
> controller, the same type of data still has to travel through the exact
> same bus. Neither have write-back cache that would actually improve
> peformance.
>
> Additionally, fakeraid requires proprietary kernel modules, dies with
> the motherboard and typically is slower performance than mdadm.
>
> Craig
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> users mailing list
> users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>

Do I need to set any corn jobs to monitor the raid? This is
recommended in most of the guides I read. If so, any suggestions why
and how to do this?
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux