similar to: CentOS 6 Partitioning Map/Schema

*Re-sending as it appears my original e-mail did not go through*. Good Evening All, I have a question regarding CentOS 6 server partitioning. Now I know there are a lot of different ways to partition the system and different opinions depending on the use of the server. I currently have a quad core intel system running 8GB of RAM with 1 TB hard drive (single). In the past as a FreeBSD user, I

CentOS Community, It is to my understanding that the /boot partition should never be placed on LVM and should be a physical partition on the hard drives (or on top of a RAID array). Is this an accurate statement? Also please advise if the SWAP filesystem is safe to be placed under LVM, or if this should be a hard partition / hard limit as well. I am unsure if boot issues or any filesystem issues

Hi list, I'm new with UEFI and GPT. For several years I've used MBR partition table. I've installed my system on software raid1 (mdadm) using md0(sda1,sdb1) for swap, md1(sda2, sdb2) for /, md2 (sda3,sdb3) for /home. From several how-to concerning raid1 installation, I must put each partition on a different md devices. I've asked times ago if it's more correct create the

On Thu, August 4, 2016 7:13 pm, Paul Heinlein wrote: > On Thu, 4 Aug 2016, Valeri Galtsev wrote: > >> Dear Experts, >> >> Could somebody point to kicstart HOWTO specific for CentOS 7? >> >> On CentOS 7 I somehow am always given human intervention questions >> about drive which defeats unattended ks install. >> >> At least one snag I hit

All machines kickstarted here consistently have a swap partition with the wrong size. According to the RHEL5 manual: | To determine the size of the swap partition automatically, use the | --recommended option: | | swap --recommended | | The recommended maximum swap size for machines with less than 2GB of RAM is | twice the amount of RAM. For machines with 2GB or more, this recommendation |

Suppose I start building nodes with (say) 24 drives each in them. Would the standard/recommended approach be to make each drive its own filesystem, and export 24 separate bricks, server1:/data1 .. server1:/data24 ? Making a distributed replicated volume between this and another server would then have to list all 48 drives individually. At the other extreme, I could put all 24 drives into some

Everyone, I am putting together a new mail server for our firm using a SuperMicro with Centos 7.0. When performed the install of the os, I put 16 gigs of memory in the wrong slots on the mother board which caused the SuperMicro to recognize 8 gigs instead of 16 gigs. When I installed Centos 7.0, this error made the swap file 8070 megs instead of what I would have expected to be a over 16000

Is there a recommended partitioning for dom0? Here''s what I have planned. /swap 2GB /boot 100MB (ext3) / 5GB (ext3) xenmachines LVM volume group for the remaining diskspace dom0 will install in 5GB / and each domU will have a swap and root logical volume in "xenmachines" Thank you, _______________________________________________ Xen-users mailing list

Dear All, I'm trying to create a kickstart installer. I specified an option --byes-per-inode to 'logvol' command, but I got a message "No such option: --bytes-per-inode" during installation. Does anybody know a solution? The following is the lines for disk partitioning definition specified in my kickstart file. ------------------------- ## ## Disk partitioning information

Let me see if I can, um, reboot this thread.... I made a RAID 1 of two raw disks, /dev/sda and /dev/sdb, *not* /dev/sdax /dev/sdbx. Then I installed CentOS 7 on the RAID, with /boot, /, and swap being partitions on the RAID. My problem is that grub2-install absolutely and resolutely refuses to install on /dev/sda or /dev/sdb. I've currently got it up in a half-assed rescue mode, and have

Hi, I'm trying to set up an iscsi 12.5 TB storage for some data backup. Doing so, I had some difficulties to find the right tool, maybe it's also a question of the system settings... The server is a 32Bit CentOS 5.3 with the recent updates. Ths iscsi connection can be establised. fdisk and parted fail to create any information on the device or fail completely. using the lvm tools

On Thu, 2016-08-04 at 22:21 -0400, Jonathan Billings wrote: > Is it a BIOS boot, or are you using the UEFI firmware for booting? > Either way, you might need a small boot partition (not /boot) at the > beginning of the disk. /boot/efi formatted FAT16, circa 150 MB -- Regards, Paul. England, EU. England's place is in the European Union.

In the past I basically used 3 partitions for hard drives. partition 1: was all centos (typically 20G) partition 2: was swap (typically 2*RAM - 2G) partition 3: was everything else I wanted, needed or carded about, database files etc... Now with really big drives coming along 750G and 1T partition 3 is getting big. Except for time to format is there a problem with that??? I'm not really

Dear Experts, Could somebody point to kicstart HOWTO specific for CentOS 7? On CentOS 7 I somehow am always given human intervention questions about drive which defeats unattended ks install. <rant ??> I'm doing kickstart installations for quite some time, normally I was just installing system when new release comes, and am basing kickstart file on anaconda-ks.cfg - with some

I am testing some kickstarts on ESXi virtual machine with pair of 16GB disks. Partitioning is lvm over raid. If i am using "logvol --grow i get "ValueError: not enough free space in volume group" Only workaround i can find is to add --maxsize=XXX where XXX is at least 640MB less than available. (10 extents or 320Mb per created logical volume) Following snippet is failing with

On 06/13/2015 07:51 AM, Jonathan Billings wrote: > On Fri, Jun 12, 2015 at 09:00:52PM -0600, jd1008 wrote: >> But I would still like to get up to 7, >> but as I indicated in another post, I cannot use the 7's >> iso because it crashes immediately during boot. >> Problem with bringing up X. >> As I also stated in another post, centos 6.4 had no problems >>

Guys, I was thrown a cheap OEM-server with a 120 GB SSD and 10 x 4 TB SATA-disks for the data-backup to build a backup server. It's built around an Asus Z87-A that seems to have problems with anything Linux unfortunately. Anyway, BackupPC is my preferred backup-solution, so I went ahead to install another favourite, CentOS 6.4 - and failed. The raid controller is a Highpoint RocketRAID

Le 10/02/2015 02:01, Chris Murphy a ?crit : > It's useful to know what layout you want. The installer will neither > create, nor let you use, what it thinks are ill-advised layouts. The > main reason I can think of for pre-creating md devices is to use a > non-default chunk/strip size. I'd like to be able to create either a simple RAID 1 layout with two disks, with a separate

I plan to upgrade an existing C7 computer which currently has one 256 GB SSD to use mdadmin software RAID1 after adding two 4 TB M2. SSDs, the rest of the system remaining the same. The system also has one additional internal and one external harddisk but these should not be touched. The system will continue to run C7. If I remember correctly, the existing SSD does not use a M2. slot so they

I was learning about the different FS exists. I was working on systems that ReiserFS was the star but since there is no longer support from the creator there are other consolidations to be done. I want to ask about couple FS options. EXT4 which is amazing for one node but for more it's another story. I have heard about GFS2 and GlusterFS and read the docs and official materials from RH on