From: Andreas Dilger <adilger@turbolabs.com>
To: "Peter H. R|egg" <pruegg@eproduction.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with mke2fs on huge RAID-partition
Date: Fri, 8 Feb 2002 10:47:39 -0700 [thread overview]
Message-ID: <20020208104739.M15496@lynx.turbolabs.com> (raw)
In-Reply-To: <3C640C90.E71E3F70@eproduction.ch>
In-Reply-To: <3C640C90.E71E3F70@eproduction.ch>; from pruegg@eproduction.ch on Fri, Feb 08, 2002 at 06:36:16PM +0100
On Feb 08, 2002 18:36 +0100, Peter H. R|egg wrote:
> My problem is: If I start mke2fs [1] on the device, it writes everything
> down until "Writing Superblocks...". The system then completly hangs.
> And yes, I did wait long enough (well, at least I think 15 hours should
> be enough ;-)
>
> Is there a limitation in the maximum size of a partition (well, 400 GB is
> not that small...), may it be a (known) problem of mke2fs or the particular
> Kernel-Version, or does anyone have any suggestions where else to seek?
Well, I know for a fact that people have created such large ext2 filesystems.
> All RAID is done in software, using (at the moment) a Standard RedHat 7.2
> Kernel 2.4.7.
The first thing to do would be to update to the latest RH kernel.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-02-08 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 17:36 Problem with mke2fs on huge RAID-partition Peter H. Rüegg
2002-02-08 17:47 ` Andreas Dilger [this message]
2002-02-08 18:18 ` Alan Cox
2002-02-09 19:57 ` Francois Romieu
2002-02-11 18:16 ` Bill Davidsen
2002-02-11 18:57 ` Francois Romieu
2002-02-11 20:57 ` Bill Davidsen
2002-02-12 9:10 ` Francois Romieu
2002-02-09 20:44 Rüegg, Peter H.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020208104739.M15496@lynx.turbolabs.com \
--to=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pruegg@eproduction.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).