Discuss

discuss@lists.centos.org

34753 discussions

NFS mount auto remount in case of problems.
by Rafał Radecki 24 Feb '13

24 Feb '13

Hi All. I have a setup in which I have two servers serving nfs share. The nfs service is made highly available with pacemaker. When the primary server goes down the secondary starts nfs service. Service IP is floating between servers but they have NO "shared" storage/filesystem so NFS state/connection information in case of failover is lost. I have two clients. When the failover from primary to secondary occurs the mount is stale and I need to manually remount the share. Is there a way in linux/CentOS to automatically remount nfs share in such case? Or should I just write a script which (for example) check /proc/mounts and execute it from crontab? I am curious if it can be done with "standard" linux services (automounter?) ;) Best regards, Rafal Radecki.

3 3

centos 5 with xfs root?
by Eero Volotinen 24 Feb '13

24 Feb '13

Hi List, Is it possible to install centos 5 with xfs root and how to do it? -- Eero

4 9

Re: [CentOS] Warning: Your BIOS is broken
by Robert Moskowitz 24 Feb '13

24 Feb '13

On 02/22/2013 03:04 PM, Reindl Harald wrote: > > Am 22.02.2013 20:58, schrieb Robert Moskowitz: >> Kernel param. I really should have caught that. >> >> So I was all ready to edit grub.conf and then slapped my hand. >> You TEST it out first, adding the command at boot time. ARGH! > one option > >> Once before (5+ years back) I had to add a kernel param and did it wrong and >> it was a big recovery challenge > what is the challenge? > there is no difference add or remove a param at boot If you get the option wrong and the system will now not boot? Then you have to boot from a recovery CD, mount your harddrve /boot and edit out the change from grub.conf and try again. All the time you SHOULD have been working on something else. > >> But as I read up on this option, it does not sound like something I want >> to globally turn off just to stop a supposedly annoying >> message (if they have indeed worked around it, and my new DNS server is running with this OK) > and you looked at the other options? > "intel_iommu=igfx_off" maybe a good idea > > intel_iommu= [DMAR] Intel IOMMU driver (DMAR) option > on > Enable intel iommu driver. > off > Disable intel iommu driver. > igfx_off [Default Off] > By default, gfx is mapped as normal device. If a gfx > device has a dedicated DMAR unit, the DMAR unit is > bypassed by not enabling DMAR with this option. In > this case, gfx device will use physical address for > DMA. > forcedac [x86_64] > With this option iommu will not optimize to look > for io virtual address below 32 bit forcing dual > address cycle on pci bus for cards supporting greater > than 32 bit addressing. The default is to look > for translation below 32 bit and if not available > then look in the higher range. > strict [Default Off] > With this option on every unmap_single operation will > result in a hardware IOTLB flush operation as opposed > to batching them for performance. > sp_off [Default Off] > By default, super page will be supported if Intel IOMMU > has the capability. With this option, super page will > not be supported. > I will look at these closely and figure out what course to test. The sabbath is almost here, so got a hard stop time.

2 2

About CentOS & RH References
by Bassem Sossan 23 Feb '13

23 Feb '13

Hello Since CentOS is a clone of RedHat, can I ask about the depeandable references guides of RedHat that are produced by RedHat itself, such as RH033 and so on... I need to know which is the latest copyright of this suit ( RH033, RH133 and RH253 ) Thanks in advaned

2 1

Firefox 17.0.3 New Tab
by Mark LaPierre 23 Feb '13

23 Feb '13

Hey Y'll, Where might I enter a complaint about the new tabs showing a tile of recent web sites visited. I don't like that. I would like to change that setting but I don't see anything in the preferences to adjust. -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

3 3

How to re-enable Adobe Flash in Firefox
by David McGuffey 23 Feb '13

23 Feb '13

Mozilla seems to have disabled Adobe Flash in a recent update. I have one 6.3 Desktop load that I need flash. when directed to the Adobe site and download the latest version, yum tells me I have the latest version for x86_64 already installed. I must keep the wife happy with Facebook and YouTube--and if the wife isn't happy, no one in the house is happy. How do I re-enable flash? DaveM

2 1

problem building partitionable RAID-1 on Centos-6
by Fred 23 Feb '13

23 Feb '13

Trying to install Centos6 on my system (it's been running C5 for years). I've got a pair of drives, so I'm trying to use RAID-1. Previously I used a procedure where each partition was part of a separate RAID device, but this time I'm trying the HOWTO from the Centos WIKI on making a partitionable RAID pair. I've been having a lot of problems, but have also been working thru them. but t his latest one has me stumped, I'd appreciate some advice. Booting encounters a panic when trying to mount the RAID subsystem. you can see an image of it at users.rcn.com/fredricksmith/panic.JPG. Looks as if it's trying to boot from md127. there ain't no such critter, where'd it get the idea it could boot from there? or more importantly, how can I solve it? thanks! I may have to revert to the other method, but I figured this one was worth a try. Fred

3 3

Centos 6.3 and dovecot with an abrt problem
by Gregory P. Ennis 23 Feb '13

23 Feb '13

Everyone, I have a mail server running CentOS release 6.3 (Final) with 2.6.32-279.22.1.el6.i686 kernel that is reporting errors to me pertaining dovecot. I have appended the error message to this note. There is only one user that appears to generate this message, and it is generated to me by way of e-mail without a perceptible problem to the user which is not me. This particular user had an inbox greater than 2 gigs in size, so I asked him to move or delete unwanted files, which reduced the size of the inbox to 400 megs. Unfortunately, the abrt messages have continued. I did a google search on : "usr/libexec/dovecot/imap was killed by signal 6", but did not find much that I could use to help me debug this. Can any of you point me in the right direction. ' Thanks much!!! Greg From: user(a)domain.com To: root(a)domain.com Subject: [abrt] full crash report Date: Fri, 22 Feb 2013 17:57:29 -0600 abrt_version: 2.0.8 cmdline: dovecot/imap environ: '\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab\xab \xab\xab' executable: /usr/libexec/dovecot/imap kernel: 2.6.32-279.22.1.el6.i686 pid: 12871 pwd: /home/user reason: Process /usr/libexec/dovecot/imap was killed by signal 6 (SIGABRT) time: Fri 22 Feb 2013 05:56:56 PM CST uid: 507 username: user sosreport.tar.xz: Binary file, 2236756 bytes limits: :Limit Soft Limit Hard Limit Units :Max cpu time unlimited unlimited seconds :Max file size unlimited unlimited bytes :Max data size unlimited unlimited bytes :Max stack size 10485760 unlimited bytes :Max core file size 0 unlimited bytes :Max resident set unlimited unlimited bytes :Max processes 1024 19090 processes :Max open files 1024 4096 files :Max locked memory 65536 65536 bytes :Max address space unlimited unlimited bytes :Max file locks unlimited unlimited locks :Max pending signals 19090 19090 signals :Max msgqueue size 819200 819200 bytes :Max nice priority 0 0 :Max realtime priority 0 0 :Max realtime timeout unlimited unlimited us maps: :001ec000-001f8000 r-xp 00000000 08:07 2108047 /lib/libnss_files-2.12.so :001f8000-001f9000 r--p 0000b000 08:07 2108047 /lib/libnss_files-2.12.so :001f9000-001fa000 rw-p 0000c000 08:07 2108047 /lib/libnss_files-2.12.so :00595000-00596000 r-xp 00000000 00:00 0 [vdso] :0069b000-006b9000 r-xp 00000000 08:07 2109054 /lib/ld-2.12.so :006b9000-006ba000 r--p 0001d000 08:07 2109054 /lib/ld-2.12.so :006ba000-006bb000 rw-p 0001e000 08:07 2109054 /lib/ld-2.12.so :006bd000-0084d000 r-xp 00000000 08:07 2109055 /lib/libc-2.12.so :0084d000-0084f000 r--p 0018f000 08:07 2109055 /lib/libc-2.12.so :0084f000-00850000 rw-p 00191000 08:07 2109055 /lib/libc-2.12.so :00850000-00853000 rw-p 00000000 00:00 0 :00881000-00884000 r-xp 00000000 08:07 2109061 /lib/libdl-2.12.so :00884000-00885000 r--p 00002000 08:07 2109061 /lib/libdl-2.12.so :00885000-00886000 rw-p 00003000 08:07 2109061 /lib/libdl-2.12.so :00888000-0089f000 r-xp 00000000 08:07 2109060 /lib/libpthread-2.12.so :0089f000-008a0000 r--p 00016000 08:07 2109060 /lib/libpthread-2.12.so :008a0000-008a1000 rw-p 00017000 08:07 2109060 /lib/libpthread-2.12.so :008a1000-008a3000 rw-p 00000000 00:00 0 :008bb000-008c2000 r-xp 00000000 08:07 2109063 /lib/librt-2.12.so :008c2000-008c3000 r--p 00006000 08:07 2109063 /lib/librt-2.12.so :008c3000-008c4000 rw-p 00007000 08:07 2109063 /lib/librt-2.12.so :008c6000-00946000 r-xp 00000000 08:07 1071940 /usr/lib/dovecot/libdovecot.so.0.0.0 :00946000-00948000 rw-p 0007f000 08:07 1071940 /usr/lib/dovecot/libdovecot.so.0.0.0 :00948000-00949000 rw-p 00000000 00:00 0 :0094b000-00a21000 r-xp 00000000 08:07 1079292 /usr/lib/dovecot/libdovecot-storage.so.0.0.0 :00a21000-00a25000 rw-p 000d6000 08:07 1079292 /usr/lib/dovecot/libdovecot-storage.so.0.0.0 :00d59000-00d76000 r-xp 00000000 08:07 2109059 /lib/libgcc_s-4.4.6-20120305.so.1 :00d76000-00d77000 rw-p 0001d000 08:07 2109059 /lib/libgcc_s-4.4.6-20120305.so.1 :08048000-08066000 r-xp 00000000 08:07 1187972 /usr/libexec/dovecot/imap :08066000-08069000 rw-p 0001e000 08:07 1187972 /usr/libexec/dovecot/imap :09722000-0976c000 rw-p 00000000 00:00 0 [heap] :b7619000-b769a000 rw-p 00000000 00:00 0 :b7703000-b7705000 rw-p 00000000 00:00 0 :b771c000-b771f000 r--s 00000000 08:06 5373984 /home/user/mail/.imap/INBOX/dovecot.index.log :b771f000-b7720000 rw-p 00000000 00:00 0 :bf9d8000-bf9ed000 rw-p 00000000 00:00 0 [stack] open_fds: :0:/dev/null :pos: 0 :flags: 0100001 :1:/dev/null :pos: 0 :flags: 0100001 :2:pipe:[12459322] :pos: 0 :flags: 01 :3:pipe:[12459236] :pos: 0 :flags: 01 :4:pipe:[16684763] :pos: 0 :flags: 04000 :5:pipe:[12459338] :pos: 0 :flags: 04001 :6:pipe:[12459231] :pos: 0 :flags: 01 :7:socket:[12459252] :pos: 0 :flags: 04002 :8:pipe:[16684763] :pos: 0 :flags: 04001 :9:anon_inode:[eventpoll] :pos: 0 :flags: 02 :10:/home/user/mail/.imap/Draft/dovecot.index.log :pos: 0 :flags: 0100002 :11:socket:[16684731] :pos: 0 :flags: 04002 :12:/home/user/mail/.imap/Draft/dovecot.index :pos: 0 :flags: 0100002 :13:/home/user/mail/.imap/INBOX/dovecot.index.log :pos: 0 :flags: 0100002 :14:/home/user/mail/.imap/INBOX/dovecot.index :pos: 0 :flags: 0100002 :15:/home/user/mail/.imap/Sent/dovecot.index.log :pos: 0 :flags: 0100002 :16:/home/user/mail/.imap/Sent/dovecot.index :pos: 0 :flags: 0100002

1 0

Re: [CentOS] Warning: Your BIOS is broken
by Robert Moskowitz 22 Feb '13

22 Feb '13

On 02/22/2013 02:32 PM, Reindl Harald wrote: > > Am 22.02.2013 20:28, schrieb Robert Moskowitz: >>> on a similar/identical bug with Fedora FC17, someone suggested booting >>> with iommu=off to work around this. >> Where do I add this? > like every other kernel param in /boot/grub/grub.conf at > the end of the kernel line Kernel param. I really should have caught that. So I was all ready to edit grub.conf and then slapped my hand. You TEST it out first, adding the command at boot time. ARGH! Once before (5+ years back) I had to add a kernel param and did it wrong and it was a big recovery challenge. No test and verify before making permanent. Whew. So I googled the param to get its format right, and it is iommu=off. Without that dash in front. But as I read up on this option, it does not sound like something I want to globally turn off just to stop a supposedly annoying message (if they have indeed worked around it, and my new DNS server is running with this OK). So I will test from booting and typing the option in without actually altering grub.conf. But if there is a way to just stop getting this message, that would be good too. thank you all for your help. > > https://www.google.com/search?q=linux+add+kernel+params > http://www.kernel.org/doc/Documentation/kernel-parameters.txt >

1 0

Warning: Your BIOS is broken
by Robert Moskowitz 22 Feb '13

22 Feb '13

I am getting the following on my 'new box' for my DNS server: Date: Wed, 20 Feb 2013 13:58:04 -0500 From: To: Subject: [abrt] full crash report User-Agent: Heirloom mailx 12.4 7/29/08 abrt_version: 2.0.8 cmdline: ro root=/dev/mapper/vg_onlo3-root_01 rd_NO_LUKS rd_LVM_LV=vg_onlo3/root_01 LANG=en_US.UTF-8 +rd_NO_MD SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=128M rhgb quiet rd_NO_DM rhgb +quiet kernel: 2.6.32-279.22.1.el6.i686 not-reportable: Your BIOS is broken reason: WARNING: at drivers/pci/dmar.c:594 warn_invalid_dmar+0x7f/0xa0() (Not tainted) time: Wed 20 Feb 2013 01:57:36 PM EST sosreport.tar.xz: Binary file, 460076 bytes backtrace: :WARNING: at drivers/pci/dmar.c:594 warn_invalid_dmar+0x7f/0xa0() (Not tainted) :Hardware name: HP Compaq dc7800 Small Form Factor :[Firmware Warn]: Your BIOS is broken; DMAR reported at address fed90000 returns all ones! :BIOS vendor: Hewlett-Packard; Ver: 786F1 v01.04; Product Version: :Modules linked in: :Pid: 0, comm: swapper Not tainted 2.6.32-279.22.1.el6.i686 #1 :Call Trace: :[<c0455141>] ? warn_slowpath_common+0x81/0xc0 :[<c06217ff>] ? warn_invalid_dmar+0x7f/0xa0 :[<c06217ff>] ? warn_invalid_dmar+0x7f/0xa0 :[<c04551d3>] ? warn_slowpath_fmt_taint+0x33/0x40 :[<c06217ff>] ? warn_invalid_dmar+0x7f/0xa0 :[<c0abdeb8>] ? check_zero_address+0xfb/0x132 :[<c06608b7>] ? acpi_tb_verify_table+0x1d/0x46 :[<c0abdefd>] ? detect_intel_iommu+0xe/0x57 :[<c0aae15b>] ? mem_init+0x10/0x2ab :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c082ee00>] ? die_nmi+0x80/0xf0 :[<c082ee00>] ? die_nmi+0x80/0xf0 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0a9781d>] ? start_kernel+0x1d1/0x3b5 :[<c0a9748a>] ? unknown_bootoption+0x0/0x190 Should I worry?

4 8

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss