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
On Sat, 2001-10-13 at 16:13, L A Walsh wrote:
> 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
I had the same problem awhile back it it was attributed to using
outdated fileutils. I recommend getting new ones from http://www.gnu.org and
seeing if that fixes the problem. It fixed it when I had a similar
problem.
--
John Tobin
[email protected]; AOL IM: ogre7929
http://ogre.rocky-road.net
http://ogre.rocky-road.net/cdr.shtml
John J Tobin wrote:>
> I had the same problem awhile back it it was attributed to using
> outdated fileutils. I recommend getting new ones from http://www.gnu.org and
> seeing if that fixes the problem. It fixed it when I had a similar
> problem.
---
Hmmm. I have a server at work installed from RH7.1 running 2.4.4.
I did a grep of many files into redirected into a file and that fails at
2G. But my version of 7.2 Suse doesn't. I take it this is a recent update
to the file utils?
-linda
-- - _ - _ - _ - _ - _ - _ - _ -
L A Walsh, law at sgi dot com | Senior Engineer
01-650-933-5338 | Trust Technology, Core Linux, SGI
Followup to: <[email protected]>
By author: L A Walsh <[email protected]>
In newsgroup: linux.dev.kernel
>
> Hmmm. I have a server at work installed from RH7.1 running 2.4.4.
> I did a grep of many files into redirected into a file and that fails at
> 2G. But my version of 7.2 Suse doesn't. I take it this is a recent update
> to the file utils?
>
No, it's a matter of if the distributor, who compiled fileutils,
compiled with -D_FILE_OFFSET_BITS=64 or not.
-hpa
--
<[email protected]> at work, <[email protected]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <[email protected]>
> > 2G. But my version of 7.2 Suse doesn't. I take it this is a recent update
> > to the file utils?
>
> No, it's a matter of if the distributor, who compiled fileutils,
> compiled with -D_FILE_OFFSET_BITS=64 or not.
>
Well grep isnt actually gnu fileutils but the point is mostly valid. grep
also uses mmap so there are some other minor points of consideration