SlackWiki - User contributions [en]

Zip 2GB Limit

2009-06-24T05:39:32Z

RobRistroph:

[[Category:Tips]]

== Fixing the 2GB file size limit in unzip ==

On some SlackWare versions, up to at least 12.0, the "unzip" command cannot unpack a file that is bigger than 2 GB. This applies to the file that is created being 2 GB, the .zip compressed file might be less than 2 GB. When the unzip command attempts to create the greater than 2 GB file, it makes the file up until it is 2 GB, and then produces this error message (PROP_ENT.TXT is the file that is bigger than 2 GB in this case) :

<pre>
PROP_ENT.TXT: write error (disk full?). Continue? (y/n/^C) y
</pre>

This procedure will update the unzip command to fix this. It may also fix problems in creating a .zip file that is bigger than 2 GB, but I have not been able to test that.

With these commands I retrieved the source package and unpacked the source trees:

<pre>
mkdir infozip
cd infozip
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/infozip.SlackBuild
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/slack-desc
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/unzip552.tar.bz2
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/zip232.tar.bz2
tar xjvf unzip552.tar.bz2
tar xjvf zip232.tar.bz2
</pre>

I next modified the Makefiles in the two source trees to use the flags "-DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" as described here: http://www.info-zip.org/FAQ.html#limits

To do that, I edited the file unzip-5.52/unix/Makefile and changed line 776 from "<nowiki>CF="-O3 -Wall -I. -DASM_CRC $(LOC)"</nowiki>" to "<nowiki>CF="-O3 -Wall -I. -DASM_CRC $(LOC) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64"</nowiki>".

I then editted zip-2.32/unix/Makefile and changed line 49 from "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP)" to "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" .

The second Makefile edit might not be necessary, it should fix any problems you are having with the "zip" command (the first Makefile fixes problems with the "unzip" command).

After editing those files, I re-tarred up the directories with the now fixed Makefiles, and then removed the source trees:

<pre>
tar cjvf unzip552.tar.bz2 unzip-5.52/
tar cjvf zip232.tar.bz2 zip-2.32/
rm -rf unzip-5.52/ zip-2.32/
</pre>

I then ran the SlackBuild to make the package:

<pre>
chmod a+x infozip.SlackBuild
./infozip.SlackBuild
</pre>

At this point the slackware package will be in /tmp/infozip-5.52-i486-2.tgz. You might wish to copy it somewhere if you are going to install it on a number of computers or save it. You can install it with "installpkg /tmp/infozip-5.52-i486-2.tgz" like a normal package.

If someone knows this is fixed in recent SlackWare versions, or has uploaded a precompiled package somewhere, please update this wiki.

Zip 2GB Limit

2009-06-24T05:37:35Z

RobRistroph: /* Fixing the 2GB file size limit in unzip */

[[Catagory:Tips]]

== Fixing the 2GB file size limit in unzip ==

On some SlackWare versions, up to at least 12.0, the "unzip" command cannot unpack a file that is bigger than 2 GB. This applies to the file that is created being 2 GB, the .zip compressed file might be less than 2 GB. When the unzip command attempts to create the greater than 2 GB file, it makes the file up until it is 2 GB, and then produces this error message (PROP_ENT.TXT is the file that is bigger than 2 GB in this case) :

<pre>
PROP_ENT.TXT: write error (disk full?). Continue? (y/n/^C) y
</pre>

This procedure will update the unzip command to fix this. It may also fix problems in creating a .zip file that is bigger than 2 GB, but I have not been able to test that.

With these commands I retrieved the source package and unpacked the source trees:

<pre>
mkdir infozip
cd infozip
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/infozip.SlackBuild
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/slack-desc
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/unzip552.tar.bz2
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/zip232.tar.bz2
tar xjvf unzip552.tar.bz2
tar xjvf zip232.tar.bz2
</pre>

I next modified the Makefiles in the two source trees to use the flags "-DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" as described here: http://www.info-zip.org/FAQ.html#limits

To do that, I edited the file unzip-5.52/unix/Makefile and changed line 776 from "<nowiki>CF="-O3 -Wall -I. -DASM_CRC $(LOC)"</nowiki>" to "<nowiki>CF="-O3 -Wall -I. -DASM_CRC $(LOC) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64"</nowiki>".

I then editted zip-2.32/unix/Makefile and changed line 49 from "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP)" to "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" .

The second Makefile edit might not be necessary, it should fix any problems you are having with the "zip" command (the first Makefile fixes problems with the "unzip" command).

After editing those files, I re-tarred up the directories with the now fixed Makefiles, and then removed the source trees:

<pre>
tar cjvf unzip552.tar.bz2 unzip-5.52/
tar cjvf zip232.tar.bz2 zip-2.32/
rm -rf unzip-5.52/ zip-2.32/
</pre>

I then ran the SlackBuild to make the package:

<pre>
chmod a+x infozip.SlackBuild
./infozip.SlackBuild
</pre>

At this point the slackware package will be in /tmp/infozip-5.52-i486-2.tgz. You might wish to copy it somewhere if you are going to install it on a number of computers or save it. You can install it with "installpkg /tmp/infozip-5.52-i486-2.tgz" like a normal package.

If someone knows this is fixed in recent SlackWare versions, or has uploaded a precompiled package somewhere, please update this wiki.

Zip 2GB Limit

2009-06-23T21:57:08Z

RobRistroph:

[[Catagory:Tips]]

== Fixing the 2GB file size limit in unzip ==

On some SlackWare versions, up to at least 12.0, the "unzip" command cannot unpack a file that is bigger than 2 GB. This applies to the file that is created being 2 GB, the .zip compressed file might be less than 2 GB. When the unzip command attempts to create the greater than 2 GB file, it makes the file up until it is 2 GB, and then produces this error message (PROP_ENT.TXT is the file that is bigger than 2 GB in this case) :

<pre>
PROP_ENT.TXT: write error (disk full?). Continue? (y/n/^C) y
</pre>

This procedure will update the unzip command to fix this. It may also fix problems in creating a .zip file that is bigger than 2 GB, but I have not been able to test that.

With these commands I retrieved the source package and unpacked the source trees:

<pre>
mkdir infozip
cd infozip
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/infozip.SlackBuild
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/slack-desc
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/unzip552.tar.bz2
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/zip232.tar.bz2
tar xjvf unzip552.tar.bz2
tar xjvf zip232.tar.bz2
</pre>

I next modified the Makefiles in the two source trees to use the flags "-DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" as described here: http://www.info-zip.org/FAQ.html#limits

To do that, I edited the file unzip-5.52/unix/Makefile and changed line 50 from "CF = -O -I. -DUNIX $(LOC)" to "CF = -O -I. -DUNIX $(LOC) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64". I then editted zip-2.32/unix/Makefile and changed line 49 from "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP)" to "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" . The second Makefile edit might not be necessary, it should fix any problems you are having with the "zip" command (the first Makefile fixes problems with the "unzip" command).

After editing those files, I re-tarred up the directories with the now fixed Makefiles, and then removed the source trees:

<pre>
tar cjvf unzip552.tar.bz2 unzip-5.52/
tar cjvf zip232.tar.bz2 zip-2.32/
rm -rf unzip-5.52/ zip-2.32/
</pre>

I then ran the SlackBuild to make the package:

<pre>
chmod a+x infozip.SlackBuild
./infozip.SlackBuild
</pre>

At this point the slackware package will be in /tmp/infozip-5.52-i486-2.tgz. You might wish to copy it somewhere if you are going to install it on a number of computers or save it. You can install it with "installpkg /tmp/infozip-5.52-i486-2.tgz" like a normal package.

If someone knows this is fixed in recent SlackWare versions, or has uploaded a precompiled package somewhere, please update this wiki.

Zip 2GB Limit

2009-06-23T21:55:02Z

RobRistroph: Created page with 'Catagory:Tips On some SlackWare versions, up to at least 12.0, the "unzip" command cannot unpack a file that is bigger than 2 GB. This applies to the file that is created ...'

[[Catagory:Tips]]

On some SlackWare versions, up to at least 12.0, the "unzip" command cannot unpack a file that is bigger than 2 GB. This applies to the file that is created being 2 GB, the .zip compressed file might be less than 2 GB. When the unzip command attempts to create the greater than 2 GB file, it makes the file up until it is 2 GB, and then produces this error message (PROP_ENT.TXT is the file that is bigger than 2 GB in this case) :

<pre>
PROP_ENT.TXT: write error (disk full?). Continue? (y/n/^C) y
</pre>

This procedure will update the unzip command to fix this. It may also fix problems in creating a .zip file that is bigger than 2 GB, but I have not been able to test that.

With these commands I retrieved the source package and unpacked the source trees:

<pre>
mkdir infozip
cd infozip
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/infozip.SlackBuild
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/slack-desc
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/unzip552.tar.bz2
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/zip232.tar.bz2
tar xjvf unzip552.tar.bz2
tar xjvf zip232.tar.bz2
</pre>

I next modified the Makefiles in the two source trees to use the flags "-DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" as described here: http://www.info-zip.org/FAQ.html#limits

To do that, I edited the file unzip-5.52/unix/Makefile and changed line 50 from "CF = -O -I. -DUNIX $(LOC)" to "CF = -O -I. -DUNIX $(LOC) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64". I then editted zip-2.32/unix/Makefile and changed line 49 from "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP)" to "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" . The second Makefile edit might not be necessary, it should fix any problems you are having with the "zip" command (the first Makefile fixes problems with the "unzip" command).

After editing those files, I re-tarred up the directories with the now fixed Makefiles, and then removed the source trees:

<pre>
tar cjvf unzip552.tar.bz2 unzip-5.52/
tar cjvf zip232.tar.bz2 zip-2.32/
rm -rf unzip-5.52/ zip-2.32/
</pre>

I then ran the SlackBuild to make the package:

<pre>
chmod a+x infozip.SlackBuild
./infozip.SlackBuild
</pre>

At this point the slackware package will be in /tmp/infozip-5.52-i486-2.tgz. You might wish to copy it somewhere if you are going to install it on a number of computers or save it. You can install it with "installpkg /tmp/infozip-5.52-i486-2.tgz" like a normal package.

If someone knows this is fixed in recent SlackWare versions, or has uploaded a precompiled package somewhere, please update this wiki.

Forced Fsck

2009-06-23T20:29:14Z

RobRistroph: /* Bypassing A Hung Forced Fsck */

[[Category:Tips]]

A Forced Fsck (forced file check) happens on boot up due to one of three things:

:1) The system was not cleanly shutdown previously (you just turned off the power) and the file system was not cleanly un-mounted.

:2) The maximum number of sucessive re-boots (re-mounts ([[Mount Count|mount count]])) between fsck checks has been reached (you have reached [[Maximum Mount Count]]).

:3) A period of time has passed between fscks that exceed the filesystem's last checked criteria.

==Manually Forcing a Forced Fsck==

To force a check on the next boot, simply create the file '/etc/forcefsck' and reboot:
:<code>touch /etc/forcefsck</code>

==Bypassing A Forced Fsck==

METHOD 1: Increase the Mount Count/Last-checked time span- 
The only way to bypass a Forced Fsck is to boot the machine from another boot medium (e.g. a boot CD) and use <code>tune2fs</code> to increase the Maximum Mount Count or the Last-checked Time span.

To increase the Maximum Mount Count: <code>tune2fs -c new_mount_count filesystem</code> 
EXAMPLE: <code>tune2fs -c 50 /dev/hda1</code> - This will cause a fsck after 50 re-mounts.

To increase the Last-checked Time span: <code>tune2fs -i new_time_span filesystem</code> 
EXAMPLE: <code>tune2fs -i 3m /dev/hda1</code> - This will cause a fsck after 3 months.

GOTCHA: If you are running a RAID Array, make sure you load a kernel image that supports RAID when booting! See the RAID Array tips.

METHOD 2: Manually run fsck- 
See Bypassing A Hung Forced Fsck instructions below.

==Bypassing A Hung Forced Fsck==
Sometimes, a forced fsck will occur and may not complete. It may hang or just keep starting over. To (down and dirty) fix this, boot the machine from a bootable disk (3.5" or CD), DO NOT mount the unchecked filesystem and manually run fsck. You may have to run any one of three modes to complete the check: 
::<code>fsck -f filesystem</code> - Force checking even if the file system seems clean. 
::<code>fsck -c filesystem</code> - This option causes e2fsck to run the badblocks program to find any blocks which are bad on the filesystem, and then marks them as bad by adding them to the bad block inode. If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test. Be aware that this takes a long time, such as days on large disk with the the double -c set, but it does tend to fix problematic disks when it does complete. 
::<code>fsck -p filesystem</code> - Automatically repair ("preen") the file system without any questions. 
:::NOTE: <code>filesystem</code> = boot partition (e.g. <code>/dev/hda1</code>)

GOTCHA: If you are running a RAID Array, make sure you load a kernel image that supports RAID when booting! See the [[RAID_Array_%28Hardware%29|RAID Array tips]].

After a successful completion of anyone of the above, your filesystem's [[Mount Count|mount count]] will be reset to zero and you should be able to boot normally again.