New install issue, need help

[cpanelben]

I recommend grabing a 2.6.7 tarball from kernel.org, then applying your favorite patchset (if you have a favorite). Patch the kernel sources, then copy over Fedora's config from your latest rpm installed kernel. Run "make oldconfig" to rectify the differences in Fedora's config and the new kernel's config, then build and install it. Since you're building a custom kernel anyways, I recommend optimizing the kernel for your processesor. That should give you a nice little performance boost while still providing you with a flexible kernel. Other than that its probably a good idea to keep the kernel as close to Fedora's configuration as possible. Redhat/Fedora may not be perfect, but they are experts on configuring kernels to work reliably with a variety of hardware and architectures.

[cpanelben]

I am 100% sure that this is a Fedora kernel bug. I can reliably reproduce this issue on our testing servers with a fresh install, both before and after updating the entire system using yum. This is also irrelevant of the kernel version (supplied by Fedora).

The only thing that I've seen that will effectively resolve this issue is building a new kernel from source.

[javelin]

cpanelben
the current kernel that we are running (2.6.7) is custom build, although i didnt base it off rh's original config.. mainly due to the fact so they include so much, and our servers dont need to support almost every possible configuration known to man..
that said is there anything specific that you know of to enable / disable in the kernel config to get it going ?
i can post you my config if that would help

regs jav

[[iG]]

For everyone who is still having this problem on a "Fedora Core 2 Machine"

Simply, rpm -ihv one of the following 2.6.7 Kernels

(SMP-i686)
http://files.oktagone.net/linux/kern...1.499.i686.rpm

(x86-i686)
http://files.oktagone.net/linux/kern...1.499.i686.rpm

Once installed, edit your /boot/grub/grub.conf to make the 2.6.7 kernel boot up first, and then simply reboot.

Once your box is back online, run the Initial Quota Setup from within WHM, and you are all set to go.

(Note: These RPM's are the official development RPM's for Fedora Core 3, taken off http://download.fedora.redhat.com)

[javelin]

looking at that kernel config quotas are not enabled..
iG i understand you can get past the initial config of the quotas but without quotas actually configured i bet you get no actual usage readouts


regards jav

[[iG]]

looking at that kernel config quotas are not enabled..
iG i understand you can get past the initial config of the quotas but without quotas actually configured i bet you get no actual usage readouts


regards jav

Yes, that kernel has quotas compiled in it, AND quotas are working fine for users/domains.

[javelin]

iG my bad.. copied the rpm config into my source directory then went and edited the standard .config not the config-2.6.7-1.499smp


snatched from their config file
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
# CONFIG_XFS_RT is not set
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m


my custom config
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y

[DragonflyWHD]

ok i tried the last kernel post and my server is yelling back at me that its older then what is installed and will not let me do it any suggestions??

[AbeFroman]

2 x 200GB SATA drives using software raid through the Fedora installs Disk Druid

Do you need a Raid controller for that?

[GufyMike]

Just haven't seen this postted yet. but the 2.6.8 kernel is buggy with disk io, I use FC2 on my personal computers and these problems are relavent: CDs can only be burnt as root and Games from loki soft work under 2.6.7 but are broken under 2.6.8 nfs only root can write to it.

now for nfs. the client was running 2.6.8 and need root to write but when running the 2.6.7 as the client I was able to write as a normal usr. FYI: for both the server was using the 2.6.8 kernel. This is a known bug and has been addressed in the kernel mailing list.

I personally haven't used diskquota on any of my boxes so I can't fully atest to this being the problem. If you use yum to update your OS just add:

exclude=kernel-2.6.8-1.521

to the main section of /etc/yum.conf up2date also has an exclude option. not sure on that one.


I also know alot of you are using custom kernels of the 2.6.7 version so this might not apply.

[gvard]

Good evening from Greece,

I'm experiencing the same problem with a new server in my rack, a dual Xeon 3.06GHz w/ SCSI disks. The box has Fedora core 2 with 2.6.5 kernel, as yours guys.

My question: rack911.com (who will secure up my server) insists in installing 2.4.27 kernel with grsecurity, since they say that some security problems exist in 2.6.x (and no grsecurity yet in 2.6.8.1). Will 2.4.27 give me the same problems? Has anyone tried that?

[Sheldon]

rack911 is a trustworthy guy...

I know him... if he says to use 2.4.27 ... id do it..

Thats the standard kernel anyhow I believe. The 2.6.81 has problems has he probably suggested.

[StevenC]

Just haven't seen this postted yet. but the 2.6.8 kernel is buggy with disk io, I use FC2 on my personal computers and these problems are relavent: CDs can only be burnt as root and Games from loki soft work under 2.6.7 but are broken under 2.6.8 nfs only root can write to it.

now for nfs. the client was running 2.6.8 and need root to write but when running the 2.6.7 as the client I was able to write as a normal usr. FYI: for both the server was using the 2.6.8 kernel. This is a known bug and has been addressed in the kernel mailing list.

I personally haven't used diskquota on any of my boxes so I can't fully atest to this being the problem. If you use yum to update your OS just add:

exclude=kernel-2.6.8-1.521

to the main section of /etc/yum.conf up2date also has an exclude option. not sure on that one.


I also know alot of you are using custom kernels of the 2.6.7 version so this might not apply.

Self compiled 2.6.8.1 works great no io issues compared to 2.4 on dual proc boxes.


2.6.7 has a security vuln in it so i strongly suggest not using it.