From: L A Walsh <law@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: Maximum size of ext2 files on ia32 is?
Date: Sat, 13 Oct 2001 14:13:40 -0700 [thread overview]
Message-ID: <3BC8AE84.48808982@sgi.com> (raw)
I was hesitantly and pleasantly surprised when I was copying across an
unmounted 8G unmounted file partition via dump to an NFS partition. Until
August, regular backups splitted the dump image (used the "-M" flag to
dump) to into 4 2G files. My backup disk died so it took some time to
replace it and just got around to doing so (I know, running w/out backups
is like unprotected sex, but lets ignore that critique). So I startup
dump and it produced 1 9G file. I was a bit concerned that NFS had
a screwed up mapping of the local file, but the server confirmed the file
size. 'du' confirmed it was 8.8G, I even unmounted, forced an fsck on it
and remounted -- still 8.8G. I was allocating special partitions to
backup non-dump compatible partitions (win) to the server but find now they
can be backed up into a single 8G+ file. I notice some utils from my latest
suse72 install (stat) don't know about it either:
> du -sh *
14M BOOT_101101.dump
8.8G HOME_101201.dump.001
...
> stat HOME_101201.dump.001
HOME_101201.dump.001: Value too large for defined data typ
So, I have been a bit busy and distracted and all, but when did large
file support go in for the i386 arch and what is the new max files size?
Congratulations and great work for addressing that limitation!
Linda
p.s. -- I hope this is a real feature and not considered a bug...:-)
-- - _ - _ - _ - _ - _ - _ - _ -
L A Walsh, law at sgi dot com | Senior Engineer
01-650-933-5338 | Trust Technology, Core Linux, SGI
next reply other threads:[~2001-10-13 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 21:13 L A Walsh [this message]
2001-10-13 22:52 ` Maximum size of ext2 files on ia32 is? John J Tobin
2001-10-13 23:04 ` L A Walsh
2001-10-13 23:29 ` H. Peter Anvin
2001-10-14 1:30 ` Alan Cox
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=3BC8AE84.48808982@sgi.com \
--to=law@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/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