[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: creating filesystem on huge disks in RHEL3



Arjan van de Ven wrote:

On Thu, 2005-04-07 at 17:37 -0400, Viktor Hornak wrote:

Hi,

I was wondering if someone could advice on how to create an (ext3) filesystem on a huge disk (by current measures). The disk is actually a hardware RAID, so it presents itself as /dev/sdb and is about 1.4TB big. I created one big partition (/dev/sdb1) with fdisk and was trying to create an ext3 filesystem afterwards (simply running mkfs.ext3 /dev/sdb1). The problem is that after a while, the "Writing inode tables: ..." slowed down to a crawl and now it's about 0.8% (!) through with inode creation and has been running for about 4 hours. It looks like this is not the way to go. Is ext3 not scaling well for such big partitions? Should I use a different filesystem? Or should I specify some switches for mkfs.ext3? Also, maybe this is not how one should go about it - maybe I need to create several partitions and merge them somehow (LVM?).


you first of all really want to use the U5 (beta) kernel and e2fsprogs, anything prior to that has some issues > 1Tb..

Thanks for quick reply! However it's not that easy to go to U5 - I am using RocksClusters (www.rocksclusters.org) and I cannot easily change the base install (which is replicated to cluster nodes). Would there be any possible workaround? I could use our other servers which have official versions of RHEL3/4 but that would complicate access to RAID from within the cluster. I'd be greatful for any advice about how to resolve this issue...

Thanks!
-Viktor

P.S.
uname -a -> Linux nexus.bio.sunysb.edu 2.4.21-20.EL #1 SMP Fri Oct 1 09:12:23 PDT 2004 x86_64 x86_64 x86_64 GNU/Linux
rpm -q e2fsprogs -> e2fsprogs-1.32-15



------------------------------------------------------------------------


--
Taroon-list mailing list
Taroon-list redhat com
http://www.redhat.com/mailman/listinfo/taroon-list



--
Viktor Hornak
SUNY at Stony Brook




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]