On 08/07/2010 11:05 AM, Benjamin Franz wrote:
> On 08/07/2010 10:55 AM, James Bensley wrote:
>
>> On 7 August 2010 17:41, Laurent Wandrebeck<l.wandrebeck@xxxxxxxxx> wrote:
>>
>>
>>
>>> so a mount -t ext4 should work, as kernel-2.6.18-194.8.1.el5 provides /lib/modules/2.6.18-194.8.1.el5/kernel/fs/ext4/ext4.ko.
>>>
>>>
>> This is probably going ot provide the answer (to you atleast, its not
>> so clear to me);
>>
>> `uname -r` tells me I'm on kernel 2.6.18-92.el5.
>>
>> Within /lib/modules/2.6.18-92.el5/kernel/fs/ thers is no ext4, but I
>> have do have a /lib/modules/2.6.18-194.8.1.el5 folder and in there is
>> kernel/fs/ext4/ext4.ko so a newer kernel is preset with the required
>> module but its not active, or something? I'm going to say I need to
>> recompile my kernel and include the module since its present on my box
>> or work out why the newer kernel files are present but not in use?
>>
>>
>>
> You are *WAY* behind on your running kernel. Check /boot/grub/grub.cfg
> and, assuming you have the more recent kernels installed, change it to
> default to the current kernel and reboot. Alternatively, if you don't
> want to edit grub.cfg just yet, reboot and *choose* the most current
> kernel from the grub boot menu to test it.
>
> I use ext4 all the time and don't have any problems with it.
>
>
Correction: I forgot that on CentOS you want /boot/grub/grub.conf instead.
--
Benjamin Franz
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
