top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Centos 7.0 and mismatched swap file

0 votes

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 megs.

I am using the default xfs file system on the other partitions. Is there a way to expand the swap file? If not, then is this problem sufficiently bad enough for me to start over with a new install. I do not want to start over unless I need to.

posted Feb 15, 2015 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

You can grow xfs or create more swap on filesystem files ("swap in file")

answer Feb 15, 2015 by Honey
Similar Questions
+1 vote

We can permanently set hostname using hostnamectl set-hostname. How can we permanently set domain name in CentOS 7?
I found an article ( ) that recommended setting FQDN using hostnamectl. Is that the right way to set hostname and domainname at the same time using hostnamectl set-hostname command?

Running hostnamectl set-hostname will set the hostname in /etc/hostname but it doesn't change /etc/hosts. What's the proper way of adding hostname and FQDN to /etc/hosts in CentOS 7?

+1 vote

I use "yum list installed" to determine if a package has been installed on centos. In particular, I was interested in the "man" program, installed with the command "yum install man".

In Centos6, if I look at the results, I see that "man" was installed. This is good.
In Centos7, if I look at the results, I see that "man-db" was installed. This is inconsistent.

The result is that the generic algorithm:

if I want package X , check the "yum list installed" output.
If X is not listed, install it, otherwise assume it's already installed.

Is there a reason for this inconsistency? The above algorithm works with most other packages.

+1 vote

It seems that RHEL 7 will only support 64 bit. Is this correct, and what for Centos 7? Also the ARM info I found was the target is ARMv8 which is 64 bit, not the ARMv7 which is 32bit.

Any clarification?

0 votes

I've installed CentOS 7 in a KVM powered VM on my CentOS 6 desktop. I'm not getting any sound.
Google seams to have no clue what to do. How about you?

0 votes

The system log (/var/log/messages) of a CentOS 7.2 system has frequently-repeated message line pairs like:

Jul 18 14:00:01 localhost systemd: Started Session 307 of user root.
Jul 18 14:00:01 localhost systemd: Starting Session 307 of user root.

where the session number increases each time.

Looking around on this, e.g. Red Hat Bugzilla bug 727315, it looks like it's when crond starts a task; it looks like it might be fixed - I would think that would be in CentOS but don't know how to find/compare the Fedora and CentOS systemd versions to know for sure.

I found a post on a workaround - in /etc/systemd/system.conf to change the line:




I did that and rebooted, and it has stopped the messages.

I'm worried though that this may have knocked out something of actual interest from the syslog.

So my question is, is there a better way? A way that info messages could go to some other log, or better yet, a way that those particular "session" messages, and only those, could go to some other log or be filtered out?