Discuss December 2007

discuss@lists.centos.org

279 participants
374 discussions

unstable kernel after update to CentOS 4.5
by Kai Schaetzl 11 Dec '07

11 Dec '07

On Saturday I finally upgraded a machine from CentOS 4.3 (I think) to 4.5 via yum. Seemed to went fine. However, during the following night /home got mounted read-only because of an EXT3-fs error. The next night happened the same. Also, today, I saw the first-ever kernel crash on this machine. The machine is about three years old or so, went into production two years ago with CentOS 4.1 or so and has been rock stable since then. The fs errors, no kernel crashes, no other "weird" occurences. As the problems are now happening right after upgrading to a new kernel I rather suspect a bug in the kernel (or some module) than a hardware problem. No RAID, no LVM, a few partitions on an IDE disk. I didn't file it as a bug yet. I want to first gather some more information or get some help. Here are some details. Kernel was updated from 2.6.9-34.0.2.EL to 2.6.9-55.0.12.EL. There is not a single package update missing now. Dec 9 04:30:35 nx10 kernel: EXT3-fs error (device hda3): htree_dirblock_to_tree: bad entry in directory #1330023: rec_len % 4 != 0 - offset=10264, inode=808542775, rec_len=13621, name_len=100 Dec 9 04:30:35 nx10 kernel: Aborting journal on device hda3. Dec 9 04:30:35 nx10 kernel: ext3_abort called. Dec 9 04:30:35 nx10 kernel: EXT3-fs error (device hda3): ext3_journal_start_sb: Detected aborted journal Dec 9 04:30:35 nx10 kernel: Remounting filesystem read-only The second error tonight happened about 5 minutes earlier. With exactly the same directory inode. http://www.google.de/search?as_q=centos+rec_len+4+0&hl=de&num=30&btnG=Googl… tory&as_oq=&as_eq=&lr=&cr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=&as_rights=&saf e=images shows this error is very scarce (I also tried it with fedora and got a few more). It seems to be related to heavy disk i/o, but only under certain (hardware?) circumstances and may be a bug introduced in some Fedora kernel and this krept into RHEL/CentOS 4.4/4.5. Once this happens that filesystem (in my case /home) is read-only and the machine just hangs when one tries to shutdown (probably when unmounting) or remount ro (for a file check). After a hard reset the automatic fschk in dmesg lists only an few orphan inode cleanups. Also, I found that dmesg delivers me an output of the iptables logging (which is on kern.=debug) before the problem is fixed with a reset. Can I use fsdebug safely on that system while mounted? I'm not familiar with it and just stumbled over a mention of it. I tried it on a machine here on a mounted device and there was no problem. That other machine is in a remote data center, so options are a bit limited. The kernel crash from today starts like this: Dec 10 10:30:01 nx10 kernel: Unable to handle kernel paging request at virtual address 8f38df23 Dec 10 10:30:01 nx10 kernel: printing eip: Dec 10 10:30:01 nx10 kernel: c019190b Dec 10 10:30:01 nx10 kernel: *pde = 00000000 Dec 10 10:30:01 nx10 kernel: Oops: 0000 [#1] Dec 10 10:30:01 nx10 kernel: Modules linked in: ipt_REJECT ipt_limit ipt_state ipt_LOG iptable_filter ip_tables ip_conntrack_ftp ip_conntrack md5 ipv6 autofs4 i2c_dev i2c_core sunrpc dm_mirror dm_mod button battery ac 8139too mii ext3 jbd ata_piix libata sd_mod scsi_mod Dec 10 10:30:01 nx10 kernel: CPU: 0 Dec 10 10:30:01 nx10 kernel: EIP: 0060:[<c019190b>] Not tainted VLI Dec 10 10:30:01 nx10 kernel: EFLAGS: 00010282 (2.6.9-55.0.12.EL) Dec 10 10:30:01 nx10 kernel: EIP is at seq_escape+0x21/0xaa Dec 10 10:30:01 nx10 kernel: eax: 8f38df23 ebx: c0370260 ecx: d35a9151 edx: d35aa000 Dec 10 10:30:01 nx10 kernel: esi: c518c200 edi: c518c200 ebp: c032f9d9 esp: c63d9f28 Dec 10 10:30:01 nx10 kernel: ds: 007b es: 007b ss: 0068 Dec 10 10:30:01 nx10 kernel: Process mv (pid: 16585, threadinfo=c63d9000 task=cee5a1b0) Dec 10 10:30:01 nx10 kernel: Stack: d35aa000 8f38df23 c0370260 c518c200 dfe08982 00000000 c018e0e3 c03702c0 Dec 10 10:30:01 nx10 kernel: c518c200 00000000 dfe08982 c019157f 00000151 00000000 00000400 b7fd5000 Dec 10 10:30:01 nx10 kernel: 0000000c 00000000 0000000b 00000000 c0371300 cea00b80 00000400 c63d9fac Dec 10 10:30:01 nx10 kernel: Call Trace: Dec 10 10:30:01 nx10 kernel: [<c018e0e3>] show_vfsmnt+0x28/0xf5 Dec 10 10:30:01 nx10 kernel: [<c019157f>] seq_read+0x1c3/0x2bd Dec 10 10:30:01 nx10 kernel: [<c016c91b>] vfs_read+0xb6/0xe2 Dec 10 10:30:01 nx10 kernel: [<c016cb30>] sys_read+0x3c/0x62 Dec 10 10:30:01 nx10 kernel: [<c031b777>] syscall_call+0x7/0xb I wonder if I can go back to 2.6.9-34.0.2.EL. Should I expect problems with other updated packages? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

4 8

watchdog on gigabyte motherboard
by Jerry Geis 11 Dec '07

11 Dec '07

All, I have an GigaByte motherboard GA-M61P-S3 and I was wondering if any kernel watchdog processes will work with that? Jerry ----------------------------- /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/softdog.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/ibmasr.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/pcwd_usb.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/pcwd_pci.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/alim7101_wdt.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/wdt_pci.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/w83877f_wdt.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/alim1535_wdt.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/w83627hf_wdt.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/i8xx_tco.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/machzwd.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/w83977f_wdt.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/i6300esb.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/ipmi/ipmi_watchdog.ko

1 0

Re: [CentOS] building a Xen guest image on straight LVM partitions?
by Ross S. W. Walker 11 Dec '07

11 Dec '07

Amos, The quickest way to deploy a Xen VM requires a little more prep work... Use the regular (long) method as discussed. Most use an HVM to do the install but config it as a domU afterward as most installers only work reliably in a fully virtualized environment. Create an LVM based guest for each distribution/OS you plan to use. Then for each Xen guest you want to create take an LVM snapshot of the distribution/OS of choice and use that for the guest. This way guest deployment is very quick and disk space is conserved wisely. You can start with 1 or 2 GB snapshot and as space gets tight in the snapshot add more storage. -Ross -----Original Message----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Sent: Tue Dec 11 01:50:01 2007 Subject: Re: [CentOS] building a Xen guest image on straight LVM partitions? On 11/12/2007, Ross S. W. Walker <rwalker(a)medallion.com> wrote: > Here is a good link: http://wiki.rpath.com/wiki/Xen_DomU_Guide Ah and forgot to say "thank you" for the link. Looks useful. Cheers, --Amos _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

1 0

Re: Samba Upgrade on Centos 3 Resolved
by Ben Mohilef 11 Dec '07

11 Dec '07

>> bugzilla.redhat.com and provide us with the bug number there? >> >> Thanks, >> >> Ralph >> > >Red Hat Bug 389021 opened on 11-17-07. RedHat released updates for samba late last week: samba-2.2.12-1.21as.8.2 samba-3.0.9-1.3E.14.3 samba-3.0.25b-1.el4_6.4 samba-3.0.25b-1.el5_1.4 They fixed the linux-linux directory panic issue with this update as well as a couple of new security issues. regards, benm

2 1

CentOS-announce Digest, Vol 34, Issue 8
by centos-announce-request＠centos.org 11 Dec '07

11 Dec '07

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2007:1114 Critical CentOS 3 ia64 samba - security update (Pasi Pirhonen) 2. CESA-2007:1076 Moderate CentOS 3 ia64 python - security update (Pasi Pirhonen) 3. CESA-2007:1114 Critical CentOS 4 ia64 samba - security update (Pasi Pirhonen) 4. CESA-2007:1076 Moderate CentOS 4 ia64 python - security update (Pasi Pirhonen) 5. CESA-2007:1114 Critical CentOS 3 i386 samba - security and bug fix update (Tru Huynh) 6. CESA-2007:1114 Critical CentOS 3 x86_64 samba - security and bug fix update (Tru Huynh) 7. CESA-2007:1076 Moderate CentOS 3 i386 python - security update (Tru Huynh) 8. CESA-2007:1076 Moderate CentOS 3 x86_64 python - security update (Tru Huynh) 9. CESA-2007:1114 Critical CentOS 3 s390(x) samba - security update (Pasi Pirhonen) 10. CESA-2007:1114 Critical CentOS 4 s390(x) samba - security update (Pasi Pirhonen) 11. CESA-2007:1077-01: Moderate CentOS 2 i386 python security update (John Newbigin) 12. CESA-2007:1114-01: Critical CentOS 2 i386 samba security and bug fix update (John Newbigin) 13. CESA-2007:1132-03: Low CentOS 2 i386 tzdata enhancement update (John Newbigin) 14. CESA-2007:1114 Critical CentOS 5 x86_64 samba Update (Karanbir Singh) 15. CESA-2007:1114 Critical CentOS 5 i386 samba Update (Karanbir Singh) 16. CESA-2007:1076 Moderate CentOS 3 s390(x) python - security update (Pasi Pirhonen) 17. CESA-2007:1076 Moderate CentOS 4 s390(x) python - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Mon, 10 Dec 2007 21:26:24 +0200 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2007:1114 Critical CentOS 3 ia64 samba - security update To: centos-announce(a)centos.org Message-ID: <20071210192624.GI16424(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2007:1114 https://rhn.redhat.com/errata/RHSA-2007-1114.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/samba-3.0.9-1.3E.14.3.ia64.rpm updates/ia64/RPMS/samba-client-3.0.9-1.3E.14.3.ia64.rpm updates/ia64/RPMS/samba-common-3.0.9-1.3E.14.3.ia64.rpm updates/ia64/RPMS/samba-swat-3.0.9-1.3E.14.3.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

re-installing a package without removing it?
by Amos Shapira 11 Dec '07

11 Dec '07

Hello, I've just noticed that the file /etc/ha.d/resource.d/drbddisk, which belongs to package drbd-8.0.6-1.el5.centos, is missing from one of my test machines: # rpm --verify drbd S.5....T c /etc/drbd.conf missing /etc/ha.d/resource.d/drbddisk I'm looking at this as an opporunity to learn something about RPM which bugged me for a while - in Debian, aptitude and apt-get provide options to re-install existing package without removing it. If I understand this correctly, then "rpm -i --force drbd-8.0.6-1.el5.centos.rpm" would re-install the package. Is this correct? The rpm solution would require me to find and manually download the rpm file. Is there a way to do this through yum? Thanks, --Amos

3 2

Yum FTP concurrency
by Tom Lanyon 11 Dec '07

11 Dec '07

Greetings, My chosen CentOS mirror has a limit of 5 max FTP connections per IP. A simple 'yum update' is hitting this limit and causing the whole update procedure to fail. Are there any settings to limit yum's FTP concurrency? Regards, Tom

2 1

building a Xen guest image on straight LVM partitions?
by Amos Shapira 11 Dec '07

11 Dec '07

Hello, When I needed to build Xen guests under Debian I could follow more or less the instructions in http://preview.tinyurl.com/2oc48r and the advantage of this approach is that it allows me to setup the Xen guest directly on the LVM partition without making it consider the LVM partition as an entire disk with a partition table. The advantages of this approach are: 1. I can add more LVM's later, or share LVM's at the host level among multiple Xen guests. 2. I can easily grow/shrink the Xen guest's disks. 3. I can access the Xen guest's filesystem much more easily 5. Probably less overhead in having LVM->parition->LVM. But I didn't find a way to achieve this with CentOS 5's automatic tools. Is this supported by CentOS as a Xen host or do I have to find my own way? Thanks, --Amos

4 9

Repository for debuginfo (CentOS 5.1)
by MHR 11 Dec '07

11 Dec '07

It has been suggested (elsewhere) that, to track down the nautilus problem I reported a while back, I need to install the nautilus debuginfo rpm. However, my yum can't find it. The only repositories I have set up on my machine are these: CentOS-Base.repo CentOS-Media.repo kbs-CentOS-Extras.repo mirrors-rpmforge rpmforge.repo Do I need another one for debuginfo rpms? Thanks. mhr

2 1

OT: Rsync question
by Steven Vishoot 11 Dec '07

11 Dec '07

Hello All, I have an off topic question about rsync and was wondering if i can get some kind person help with it. I have two servers with each server have three same directories on them /dir1/ /dir2/ /dir3/ . How would i achieve this by using rsync? I have tried rsync -avrt --delete server_ip:/dir1/ /dir2/ /dir3/ /dir1/ /dir2/ /dir3/ this does not do anything except give errors. Someone on IRC suggested i do a loop something like this, for i in "/dir1/ /dir2/ /dir3/"; do rsync -av $i root@server:${i};done but when i do it i do not get what i was expecting and also receive errors about not able to transfer files. I am not able to post the exact errors since it has been a while since i have attempted this and do not wish to screw stuff up right at the moment, but in general both say rsync cannot transfer files. So in general is there a way i can do multiple directories in one command or am i left with doing them each individual as in rsync -av server:/dir1/ /dir1/ and repeat for the rest of directories. or does someone know of a better way. my final goal is to have a cronjob do this. thanks steven

9 12

← Newer
1
...
18
19
20
21
22
23
24
...
38
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss December 2007