[CentOS] Ext4 on CentOS 5.5 x64

Fri Jan 28 08:54:14 UTC 2011
Giuseppe Tanzilli - ServerPlan <giuseppe at serverplan.com>

Hi,
it works just fine for me, but there is no quota support in the 5.5 ext4
release

Giuseppe

Il 28/01/2011 08:51, Sorin Srbu ha scritto:
>> -----Original Message-----
>> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
>> Behalf Of compdoc
>> Sent: Thursday, January 27, 2011 5:09 PM
>> To: 'CentOS mailing list'
>> Subject: Re: [CentOS] Ext4 on CentOS 5.5 x64
>>
>>> For those of you that have been using the ext4 technology preview on
>> CentOS 5.5, how has it panned out? Does it perform as expected? How do you
> feel the
>> stability, creation of the FS and the administration of it is? Ideas and
>> comments welcome.
>>
>>
>> I've recently been using ext4 because I have servers with large(ish)
> storage
>> volumes, and because I know that the next version of centos will support it
>> better than 5.5.
>>
>> I only use it for storage, where I use rsync to copy terabytes of data to
>> and from the servers.
>>
>> It works fine - it's been set and forget so far. Very fast read/write
>> speeds.
> Same story here. I'm building a new backup server from scratch (with no old
> data on it), and while ext3 is nice and stable it's also pretty slow when we
> start talking sevenish terabytes.
>
> My main concern is all the writing on the interweb regarding running an fsck
> and a tune2fs after having formatted the filesystem to ext4; some say you
> should while some say it isn't necessary. 
> 	Anyway, I get a bad block message when running fsck, and am not sure
> whether this is a interface problem between the chair and the monitor or
> something with the tech preview.
>
>
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos/attachments/20110128/90c30df8/attachment-0005.html>