resize2fs "F" parameter causes error
resize2fs "F" parameter causes error
# resize2fs -pf /mnt/home/pup001ok 690624
resize2fs 1.34 (25-Jul-2003)
Resizing the filesystem on /mnt/home/pup001ok to 690624 (1k) blocks.
Begin pass 1 (max = 2)
Extending the inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
*** glibc detected *** double free or corruption (!prev): 0x0805ae78 ***
Aborted
# resize2fs -pf /mnt/home/pup001ok 690624
resize2fs 1.34 (25-Jul-2003)
The filesystem is already 690624 blocks long. Nothing to do!
# resize2fs -pfF /mnt/home/pup001ok 690624
resize2fs 1.34 (25-Jul-2003)
resize2fs: Invalid argument while trying to flush /mnt/home/pup001ok
------------
This corresponds to what several people reported.
The first error (glibc) disappears, if resize2fs is run again.
But the "F"-Parameter causes a nasty error.
On my system this leads to a 60 Second-break at every startup (even if I resize pup001ok from within Mandrake-Linux).
So I would suggest not to use the "F"-Parameter in the startup-scripts.
I resized other pup001 -files without any problems, so i have no idea, why "F" causes this error with this file here.
(the file is on a ntfs-partition, to resize it in Mandrake 9.2, I copied it to an ext3-partition)
--
references:
http://www.murga.org/%7Epuppy/viewtopic ... 0931#20931
Other posts with "resize" as keyword
--
Mark
resize2fs 1.34 (25-Jul-2003)
Resizing the filesystem on /mnt/home/pup001ok to 690624 (1k) blocks.
Begin pass 1 (max = 2)
Extending the inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
*** glibc detected *** double free or corruption (!prev): 0x0805ae78 ***
Aborted
# resize2fs -pf /mnt/home/pup001ok 690624
resize2fs 1.34 (25-Jul-2003)
The filesystem is already 690624 blocks long. Nothing to do!
# resize2fs -pfF /mnt/home/pup001ok 690624
resize2fs 1.34 (25-Jul-2003)
resize2fs: Invalid argument while trying to flush /mnt/home/pup001ok
------------
This corresponds to what several people reported.
The first error (glibc) disappears, if resize2fs is run again.
But the "F"-Parameter causes a nasty error.
On my system this leads to a 60 Second-break at every startup (even if I resize pup001ok from within Mandrake-Linux).
So I would suggest not to use the "F"-Parameter in the startup-scripts.
I resized other pup001 -files without any problems, so i have no idea, why "F" causes this error with this file here.
(the file is on a ntfs-partition, to resize it in Mandrake 9.2, I copied it to an ext3-partition)
--
references:
http://www.murga.org/%7Epuppy/viewtopic ... 0931#20931
Other posts with "resize" as keyword
--
Mark
Sorry for not re-reporting it, I sent the bug report and fix a long time ago and it completely slipped my mind:
http://www.murga.org/~puppy/viewtopic.php?p=6764#6764
http://www.murga.org/~puppy/viewtopic.php?p=6764#6764
Here is a bugfixed image.gz from puppy 1.0.6:
http://noforum.de/dotpups/puppy-image.g ... x/image.gz
I removed "F" in the resize2fs -arguments in /etc/rc.d/rc.sysinit
Mark
http://noforum.de/dotpups/puppy-image.g ... x/image.gz
I removed "F" in the resize2fs -arguments in /etc/rc.d/rc.sysinit
Mark
No, the file is 6-7 MB:
http://noforum.de/dotpups/puppy-image.gz-resize-bugfix/
Try to download again.
Mark
http://noforum.de/dotpups/puppy-image.gz-resize-bugfix/
Try to download again.
Mark
http://dotpups.de/puppy-releases/1.0.6/ ... x/image.gz
Here you must RIGHT-click -> save link-target as
I have not found out yet, how to set up Apache there for my needs.
Mark
Here you must RIGHT-click -> save link-target as
I have not found out yet, how to set up Apache there for my needs.
Mark
this is the reason i chose zip for dotpup files rather than tar.gz ... a package could be downloaded from any server, and many servers (and webhosts) are often not configured properly for gz files (more often, they work ok for zip files)Here you must RIGHT-click -> save link-target as
I have not found out yet, how to set up Apache there for my needs
Yes, that was a good choice, G2.
At least at dotpups.de it should work now.
I cannot access httpd.conf there, as it is a virtual server and no rootserver.
But I could add
AddType application/x-gzip gz
AddType application/wxbasic wxb
AddType application/puppybasic pb
to .htaccess, what will do it.
The .pb -entry will allow you to run PuppyBasic -applications from the web, if you choose "open with /usr/bin/puppybasic". Test (displays a simple xmessage): http://dotpups.de/tests/test.pb
Mark
At least at dotpups.de it should work now.
I cannot access httpd.conf there, as it is a virtual server and no rootserver.
But I could add
AddType application/x-gzip gz
AddType application/wxbasic wxb
AddType application/puppybasic pb
to .htaccess, what will do it.
The .pb -entry will allow you to run PuppyBasic -applications from the web, if you choose "open with /usr/bin/puppybasic". Test (displays a simple xmessage): http://dotpups.de/tests/test.pb
Mark