Re: [CentOS] fsck.ext4 Failed to optimize directory
Joakim Ziegler joakim@... writes: ... Failed to optimize directory ... EXT2 directory corrupted ... Disable dir_index (tune2fs(8)): # tune2fs -O ^dir_index /dev/??? and run (e2fsck(8)): # e2fsck -fD Some more, perhaps unrelated hints: http://lists.lustre.org/pipermail/lustre-discuss/2010-October/014397.html jb ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Looking for a tutorial or manpage describing sysctl params
Hi, I'm looking for a toturial or manpage describing all the thing that you can set with sysctl on RHEL 6 or CentOS 6. It apperas the the default /etc/sysctl.conf coming with the distribution gives a couple of errors on bridgen. Any hints??? Adrian -- Adri P. van Bloois Antonlaan 104 email: adr...@pa0rda.nl 3701 VG Zeist voice: +31-(0)-30-6912741 The Netherlands fax:NONE 52 05'15.77N 5 4'44.56E QTH-locater JO 22 OC The whole point of cooking is to get as much flavour out of the ingredients as possible. -- Delia Smith ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Is X79 Motherboard supported by latest Centos 5.9 version?
Hi Guys, In a bit of a pickle.. Is anyone running the latest Centos 5.9 or earlier version with an Intel X79 based motherboard. I have a server which needs the motherboard replacing asap and I have a spare Sabertooth X79. I have a machine with a Sabertooth X79 motherboard to test on which boots up fine on on Centos 5.9 i386 image from the troubled server. However the output from lspci (see below) seems far less descriptive than you normally see in Centos 5 or Centos 6. I am just a bit worried that this might imply lack of support. I do not need audio/firewire.. but need the essential to work memory, sata etc. Also I thought i386 installs could not see more than 3 and a bit Gigs of ram? The test machine has 32G and meminfo shows MemTotal: 3574676 kB MemFree: 3146556 kB I would really appreciate any advice. Regards Steve e.g. The output from Sabertooth X79 and Centos 5.9 gives 00:00.0 Host bridge: Intel Corporation Device 3c00 (rev 06) 00:01.0 PCI bridge: Intel Corporation Device 3c02 (rev 06) 00:02.0 PCI bridge: Intel Corporation Device 3c04 (rev 06) 00:03.0 PCI bridge: Intel Corporation Device 3c08 (rev 06) 00:05.0 System peripheral: Intel Corporation Device 3c28 (rev 06) 00:05.2 System peripheral: Intel Corporation Device 3c2a (rev 06) 00:05.4 PIC: Intel Corporation Device 3c2c (rev 06) 00:11.0 PCI bridge: Intel Corporation Device 1d3e (rev 05) 00:16.0 Communication controller: Intel Corporation Device 1d3a (rev 05) 00:19.0 Ethernet controller: Intel Corporation Device 1503 (rev 05) 00:1a.0 USB Controller: Intel Corporation Device 1d2d (rev 05) 00:1b.0 Audio device: Intel Corporation Device 1d20 (rev 05) 00:1c.0 PCI bridge: Intel Corporation Device 1d10 (rev b5) 00:1c.1 PCI bridge: Intel Corporation Device 1d12 (rev b5) 00:1c.2 PCI bridge: Intel Corporation Device 1d14 (rev b5) 00:1c.3 PCI bridge: Intel Corporation Device 1d16 (rev b5) 00:1c.4 PCI bridge: Intel Corporation Device 1d18 (rev b5) 00:1c.5 PCI bridge: Intel Corporation Device 1d1a (rev b5) 00:1c.7 PCI bridge: Intel Corporation Device 1d1e (rev b5) 00:1d.0 USB Controller: Intel Corporation Device 1d26 (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation Device 1d41 (rev 05) 00:1f.2 SATA controller: Intel Corporation Device 1d02 (rev 05) 00:1f.3 SMBus: Intel Corporation Device 1d22 (rev 05) 01:00.0 VGA compatible controller: nVidia Corporation Device 104a (rev a1) 01:00.1 Audio device: nVidia Corporation Device 0e08 (rev a1) 06:00.0 USB Controller: Device 1b21:1042 07:00.0 USB Controller: Device 1b21:1042 08:00.0 USB Controller: Device 1b21:1042 09:00.0 SATA controller: Device 1b21:0612 (rev 01) 0a:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. Device 3403 (rev 01) 0b:00.0 SATA controller: Device 1b4b:9130 (rev 11) ff:08.0 System peripheral: Intel Corporation Device 3c80 (rev 06) ff:08.3 System peripheral: Intel Corporation Device 3c83 (rev 06) ff:08.4 System peripheral: Intel Corporation Device 3c84 (rev 06) ff:09.0 System peripheral: Intel Corporation Device 3c90 (rev 06) ff:09.3 System peripheral: Intel Corporation Device 3c93 (rev 06) ff:09.4 System peripheral: Intel Corporation Device 3c94 (rev 06) ff:0a.0 System peripheral: Intel Corporation Device 3cc0 (rev 06) ff:0a.1 System peripheral: Intel Corporation Device 3cc1 (rev 06) ff:0a.2 System peripheral: Intel Corporation Device 3cc2 (rev 06) ff:0a.3 System peripheral: Intel Corporation Device 3cd0 (rev 06) ff:0b.0 System peripheral: Intel Corporation Device 3ce0 (rev 06) ff:0b.3 System peripheral: Intel Corporation Device 3ce3 (rev 06) ff:0c.0 System peripheral: Intel Corporation Device 3ce8 (rev 06) ff:0c.1 System peripheral: Intel Corporation Device 3ce8 (rev 06) ff:0c.2 System peripheral: Intel Corporation Device 3ce8 (rev 06) ff:0c.6 System peripheral: Intel Corporation Device 3cf4 (rev 06) ff:0c.7 System peripheral: Intel Corporation Device 3cf6 (rev 06) ff:0d.0 System peripheral: Intel Corporation Device 3ce8 (rev 06) ff:0d.1 System peripheral: Intel Corporation Device 3ce8 (rev 06) ff:0d.2 System peripheral: Intel Corporation Device 3ce8 (rev 06) ff:0d.6 System peripheral: Intel Corporation Device 3cf5 (rev 06) ff:0e.0 System peripheral: Intel Corporation Device 3ca0 (rev 06) ff:0e.1 Performance counters: Intel Corporation Device 3c46 (rev 06) ff:0f.0 System peripheral: Intel Corporation Device 3ca8 (rev 06) ff:0f.1 System peripheral: Intel Corporation Device 3c71 (rev 06) ff:0f.2 System peripheral: Intel Corporation Device 3caa (rev 06) ff:0f.3 System peripheral: Intel Corporation Device 3cab (rev 06) ff:0f.4 System peripheral: Intel Corporation Device 3cac (rev 06) ff:0f.5 System peripheral: Intel Corporation Device 3cad (rev 06) ff:0f.6 System peripheral: Intel Corporation Device 3cae (rev 06) ff:10.0 System peripheral: Intel Corporation Device 3cb0 (rev 06) ff:10.1 System peripheral: Intel Corporation Device 3cb1 (rev 06) ff:10.2 System peripheral: Intel Corporation Device 3cb2 (rev 06)
Re: [CentOS] Looking for a tutorial or manpage describing sysctl params
adr...@pa0rda.nl wrote: Hi, I'm looking for a toturial or manpage describing all the thing that you can set with sysctl on RHEL 6 or CentOS 6. It apperas the the default /etc/sysctl.conf coming with the distribution gives a couple of errors on bridgen. Any hints??? Sure. Hint 1. Find what rpm package installed the file. rpm -qf /etc/sysctl.conf Hint 2. Find out what documentation came with that package. rpm -qd initscripts Hint 3. See if you can find anything in those files. (I didn't). Hint 4. Search for linux sysctl howto (Reading a few pages let me know that it won't be a simple webpage with all the answers.) Hint 5. Search for linux sysctl parameters (One hit looks pretty good. Read it for advice.) http://archive09.linux.com/feature/146599 Hint 6. Search for linux sysctl bridgen Have fun! c 0 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Looking for a tutorial or manpage describing sysctl params
On 24.Aug.2013, at 11:57, adr...@pa0rda.nl wrote: Hi, I'm looking for a toturial or manpage describing all the thing that you can set with sysctl on RHEL 6 or CentOS 6. It apperas the the default /etc/sysctl.conf coming with the distribution gives a couple of errors on bridgen. $ sysctl -a gives you a list of all things you can set Besides google or similar, documentation for these things are in the documentation for the kernel install the kernel-doc package you can get a list of possibly interesting files (although this list may be not comprehensive, I do not know) with $ rpm -ql kernel-doc|grep sysctl -- Markus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fastest way of removing very large number of files?
In article 20130823104855.ga15...@mercury.spuddy.org, Stephen Harris li...@spuddy.org wrote: On Fri, Aug 23, 2013 at 12:40:51PM +0200, Dennis Jacobfeuerborn wrote: I doubt saving functions calls is going to gain you anything in this case as 99.9% of the time the rm takes is on disk I/O. If you want to reduce the rm time you have to find a way to reduce the disk I/O it requires. Correct. If it's a whole directory (tree) that needs removing then I find mv dir dir.o ; mkdir dir ; chown ##:## dir; chmod ### dir ; rm -r dir.o type stuff works just fine; the rm can chunk along in the background while there's now a nice clean empty directory for the application. You can even dispense with the ## variable parts. And I would get the owner and modes correct before making the new directory appear: mkdir dir.n chown --reference=dir dir.n chmod --reference=dir dir.n \ mv dir dir.o mv dir.n dir echo rm -fr dir.o \; echo dir.o deleted | batch That will do the removal in a batch job without hanging on to the tty, and will email you a quick note (the output from batch) when it's done. Cheers Tony -- Tony Mountifield Work: t...@softins.co.uk - http://www.softins.co.uk Play: t...@mountifield.org - http://tony.mountifield.org ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] ... cdfs?
On 08/21/2013 07:53 AM Joerg Schilling wrote: ken geb...@mousecar.com wrote: Then too of course there'd need to be a way to ascertain if there was any substantial differences in the outputs. There's some code out there since kernel version 2.2 called cdfs which doesn't seem to be on my (v.5.9) system. This allows mounting an audio CD or a disk image of one so that it can be examined and, presumably, manipulated. In fact, maybe this is all I need at the moment... that is, after cloning the CD to a disk image, it might be possible to edit the track data prior to burning. I don't burn CDs that often, so this would be an acceptable solution. This cdfs does not deliver better quality than from using the read audio ioctls from the kernel. Cdda2wav gives much better quylity in case of non-optiimal media and cdda2wav gives you the meta data you need to make a decent copy. You don't get that from cdfs. Jörg CDfs allows mounting a CD with something like: # mount -t cdfs -o ro /dev/cdrom /mnt/cdfs [From http://users.elis.ugent.be/~mronsse/cdfs/.] How would a person mount a CD using the software mentioned above (if that would be possible at all)? Also, I haven't been able to find cdfs in 5.9. Is it to be found in a later version? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Is X79 Motherboard supported by latest Centos 5.9 version?
On Sat, Aug 24, 2013 at 8:08 AM, Steve Brooks ste...@mcs.st-and.ac.ukwrote: Hi Guys, In a bit of a pickle.. Is anyone running the latest Centos 5.9 or earlier version with an Intel X79 based motherboard. I have a server which needs the motherboard replacing asap and I have a spare Sabertooth X79. I have a machine with a Sabertooth X79 motherboard to test on which boots up fine on on Centos 5.9 i386 image from the troubled server. However the output from lspci (see below) seems far less descriptive than you normally see in Centos 5 or Centos 6. I am just a bit worried that this might imply lack of support. I do not need I'm not familiar with the Sabertooth X79, so specifics there are better suited for someone else. Though the lack of detail in the newer board might be more apparent if we had output from both systems to compare. audio/firewire.. but need the essential to work memory, sata etc. Also I thought i386 installs could not see more than 3 and a bit Gigs of ram? The test machine has 32G and meminfo shows MemTotal: 3574676 kB MemFree: 3146556 kB Are you using a PAE kernel? If you want access to the additional memory above ~3.5GB you'll need a PAE kernel. CentOS 5 i386 has both non-PAE and PAE kernels. CentOS 6 i386 only has kernels with PAE support. Take a peek at the output from uname to find out what kernel you're running. I would really appreciate any advice. Regards Steve -- ---~~.~~--- Mike // SilverTip257 // ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
