Discuss December 2017

discuss@lists.centos.org

82 participants
59 discussions

Re: [CentOS] Good linux software RAID primer advise
by Arun Khan 03 Dec '17

03 Dec '17

On Fri, Dec 1, 2017 at 7:38 AM, Miguel Medalha <medalist(a)sapo.pt> wrote: >>> Could someone recommend good Linux software RAID primer. It would >> be good if it has good coverage of monitoring and dealing with failures. > > https://raid.wiki.kernel.org/index.php/Linux_Raid +1 and practice recovery scenarios using VMs with virtual disks. -- Arun Khan

1 0

Firefox print to file fail silent & side notes of cms4all.
by Andreas Benzler 02 Dec '17

02 Dec '17

Hello everyone, in time when i start to rebuilt my csm4all-media, I tryed to print into file from firefox. The print box close but no pdf is created. With cups-pdf works, but: - You can not name the printout - can not change the directory from userland, only with cups configuration. Where is the hunt? I only wanne tell, that is not my domain. Side note: cms4all-kernel, cms4-all-drivers, cms4all-mesa is in takt, but I will push information when cms4all-gstreamer an cms4all-media closed in my private Project. My aspect "best of" isn't closed yet, still experimental. Will take addional weeks, as i did it 2016 for centos. @Nux, my VLC is still more stable as yours and I don't no why. Yes I'm still there, but private and work takes to much time. I'm still there ... Sincrely Andy

2 1

time foo
by hw 02 Dec '17

02 Dec '17

Hi, isn´t this weird: # time foo real 43m39.841s user 15m31.109s sys 0m44.136s Almost 30 minutes have disappeared, but it actually took about that long, so what happened?

5 8

C7 and docker storage
by m.roth＠5-cent.us 01 Dec '17

01 Dec '17

Was working on docker on a server, and on startup, I see Nov 29 10:58:27 <servername> dockerd-current: time="2017-11-29T10:58:27.612849959-05:00" level=warning msg="devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section." Nov 29 10:58:27 <servername> dockerd-current: time="2017-11-29T10:58:27.655600686-05:00" level=warning msg="devmapper: Base device already exists and has filesystem xfs on it. User specified filesystem will be ignored." The latter would explain the message my user's job gave him when it tried to umount / A bit of googling, and I see something called overlayFS can be used... but I know nothing about that, or how dangerous it is. Anyone got a pointed to something more than the minimal how to configure docker to use it? mark

3 2

Re: [CentOS] C7 and docker storage
by m.roth＠5-cent.us 01 Dec '17

01 Dec '17

Gianluca Cecchi <gianluca.cecchi(a)gmail.com> wrote: > Date: Thu, 30 Nov 2017 09:55:58 +0100 > On Wed, Nov 29, 2017 at 10:23 PM, <m.roth(a)5-cent.us> wrote: > >> The latter would explain the message my user's job gave him when it tried >> to umount / >> >> A bit of googling, and I see something called overlayFS can be used... but >> I know nothing about that, or how dangerous it is. Anyone got a pointed >> to something more than the minimal how to configure docker to use it? >> > You could follow CentOS Atomic SIG > https://wiki.centos.org/SpecialInterestGroup/Atomic > http://www.projectatomic.io/download/ > > and/or read here and adapt in case for your storage needs: > http://www.projectatomic.io/docs/docker-storage-recommendation/ > > See also here for overlayfs addiction in CentOS Atomic Host in September > this year > https://seven.centos.org/2017/09/new-centos-atomic-host-with-overlayfs-stor… > Interesting, but it doesn't help me: I can't rebuild the server, it's in use, and I yum installed docker from the std. repos. What I see from the links tells me how to switch storage, not how to manually configure overlay2 storage, and whether I can do as I said, and point it to an NFS-mounted location. mark

1 1

Re: [CentOS] Good linux software RAID primer advise
by Miguel Medalha 01 Dec '17

01 Dec '17

>> Could someone recommend good Linux software RAID primer. It would >> be good if it has good coverage of monitoring and dealing with failures. https://raid.wiki.kernel.org/index.php/Linux_Raid

1 0

Partition advice
by Kenneth Porter 01 Dec '17

01 Dec '17

I'm setting up a new mail server (dovecot + sendmail + SpamAssassin + ClamAV + MIMEDefang) to replace an aging CentOS 6 box. The new box is a low-end PowerEdge with an SSD, 3 4TB red drives on a PERC RAID controller which I'll probably set up RAID5, and possibly mirrored internal SD cards as a boot device. I'm debating how to partition it and am soliciting advice. My initial instinct is to put /boot and the OS on the SSD and the home directories with their mail store on the RAID array. I might put a rescue partition on the internal SD drive (which is normally intended for a VM host). Does anyone see anything wrong with that? Should I do something different? Anything I should avoid putting on the SSD, such as swap, /tmp, and /var/tmp? I've been running Red Hat as a small office server since 5.2 back in the 90's. I'm trying to create a system that's easy to fix when it breaks. I find that's the real power of Linux over any other OS: It's easy to fix when it breaks. Oh, and backup will be to an external USB drive using BackupPC, with the drive regularly swapped off-site, plus an off-site rsync mirror.

1 0

Good linux software RAID primer advise
by Valeri Galtsev 01 Dec '17

01 Dec '17

Dear Experts, Could someone recommend good Linux software RAID primer. It would be good if it has good coverage of monitoring and dealing with failures. I inherited a couple of boxes with big bunch of software RAIDs each, and I even may have some problems, but I don't want to bother anybody with specifics unless I really hit brick wall, not just my own ignorance. Thanks in advance for all your answers! Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

2 1

Gnome boot problem (again :-) )
by vychytraly . 01 Dec '17

01 Dec '17

Hello friends I was using EL7 on gnome 3 for few months without any problem. Even 2 hours ago I had the computer (Laptop running on Nvidia-Prime) turned on and everything was working without flaw. But when I turned on the computer few minutes ago, I got login screen (which does not usually happen, since I have autologin turned on) and when I entered my login credentials I got black screen and went back to login screen. Everytime I entered my credentials the same thing happened so I was stuck in endless login loop. At first I thought it was caused by gnome-extension I updated to new version today. So I restarted the pc, went to runlevel 3, renamed the folder with extension in /home/user/.local/share/gnome-shell/extensions/"extension_name" to another name as a quick and dirty way to disable it. I restarted the pc and now I can't even get to login screen. I get stuck at text saying: "A start job is running for Wait for Plymouth Boot Screen to quit (25s / no limit)". I can go to another cmdline session and when I try to run exec gnome-session nothing happens, I just get logged off the cmdline session and must log in again. When I try to run startx my screen blinks and I get this output: xauth: file /home/user/serverauth.2372 does not exist. Output from command systemctl status gdm says: Starting gnome display manager Started gnome display manager GLib-GObject: g_object_set_valist: object class "GdmSession" has no property named "display-is-initial", GdmDisplay: display lasted 2.909... Seconds gdm_display_finish: assertion 'GDM_IS_DISPLAY (self)' failed journalctl -r gives me these errors: vgargb: this pci device is not a vga device gdm_display_finish: assertion 'GDM_IS_Display (self)' failed Process 1165 (gnome-shell) of user 42 killed by SIGSEGV - dumping core Process 1194 (gnome-shell) of user 42 killed by SIGSEGV - ignoring (repeated crash) Unrecoverable failure in component org.gnome.Shell.desktop Please could you help me with finding the problem? I am not really sure what could be the issue, since I did not change or update any packages today, nor changed the configuration files. Only change I am aware of was the update of the gnome-extension. Thank you very much and have a nice day O.

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss December 2017