Date: Sun, 26 Jun 2005 02:02:21 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Norberto Meijome <freebsd@meijome.net> Cc: freebsd-questions@freebsd.org Subject: Re: gzip from ports vs gzip from system Message-ID: <20050626070220.GA51206@dan.emsphone.com> In-Reply-To: <42BE4F33.6040101@meijome.net> References: <42BE3798.1020200@meijome.net> <20050626052603.GB9894@dan.emsphone.com> <42BE442C.9090502@meijome.net> <42BE4F33.6040101@meijome.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jun 26), Norberto Meijome said: > Norberto Meijome wrote: > >Dan Nelson wrote: > >>In the last episode (Jun 26), Norberto Meijome said: > >>>I had to install gzip from ports as gzip from base system doesn't > >>>seem to support >2GB files. Now I find myself with a set of gzip > >>>utils in /usr/bin/ (system) and one in /usr/local/ (ports). > >> > >>I have never had any problems with gzip and files over 2gb. Do you > >>have an example? > > > >and yes, the error msg from the process was gzip's msg, cant handle > >filesize > 2 GB. sorry, dont have the original msg at hand anymore. > > ok, found a copy of the log - sorry, no direct reference to 2GB... > > DUMP: 66.60% done, finished in 1:32 > > gzip: stdout: File too large > DUMP: Broken pipe > DUMP: The ENTIRE dump is aborted. That looks like whatever filesystem gzip was writing to couldn't handle files over 2gb. You mentioned writing to a remote filesystem using amd, but it defaults to NFSv3. Were you maybe writing to a FAT fs on the remote end? You can also see whether amd actually mounted the remote fs with NFSv2 by uncommenting the "/var/log/all.log" line in /etc/syslog.con, touching /var/log/all.log, and restarting syslog. Then have amd remount the remote system and check the log. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050626070220.GA51206>