From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Mark F <mfaine@knology.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Create very large filesystem on Linux
Date: Wed, 19 Jul 2006 08:29:58 +0100 [thread overview]
Message-ID: <1153294198.13071.0.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <e9jf2i$7hb$1@sea.gmane.org>
On Tue, 2006-07-18 at 15:10 -0500, Mark F wrote:
> Suse Linux Enterprise Server 9 SP3
>
> I've tried to create a large 5TB file system using both reiserfs and ext3 and both have failed.
>
> I end up with only a 1.5TB file system and the rest is free space. Does anyone know why this doesn't work, what to do to fix it?
Use XFS (or JFS if you prefer) and it will work fine.
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
prev parent reply other threads:[~2006-07-19 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 20:10 Create very large filesystem on Linux Mark F
2006-07-19 7:29 ` Anton Altaparmakov [this message]
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=1153294198.13071.0.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mfaine@knology.net \
/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).