Puppy Linux Discussion Forum

[raffy]

Now that installing Puppy in Windows XP is quite easy (thanks to drj's posts here), it will be useful to explore the size limits of pup001.

The current resizing utility of pup001 (for non-NTFS filesystems) can resize it up to 512 MB. How much larger can this possibly be?

As to NTFS-resident pup001, resizing from within Puppy is not presently allowed, so is it possible to use a utility for pup001 creation that asks for a preferred size? Or can the user just download a pup001.zip of a given size when decompressed?

Thanks!

[Flash]

I have increased my pup001 file to over 2 GB, by repeatedly using Start->Utilities->Resize/Root filesystem. I'm guessing that the pup001 file can be enlarged until it fills the partition where it is located. One thing to keep in mind is that it takes a while after you tell it to resize, and there is no progress indicator to tell you that anything is happening. So, be patient.

As to resizing a NTFS pup001 file, here's what came up when I searched the forum for "pup001 AND NTFS AND resize"

[raffy]

Thanks, Flash and Rarsa.

EDIT: Given Barry's post below, the pup001 resizing procedure shall be:

Reboot after doing resizing of pup001 and Puppy _actually resizes_ the underlying filesystem (ext2) at bootup.

As to resizing:

Case 1 - Non-NTFS: In Puppy, Start -> utilities -> Resize /root filesystem

Case 2 - NTFS: See PakRat's step 7 below:

[BarryK]

Flash, raffy,
You need to revise those instructions for 1.0.4.

What happens now is at bootup Puppy automatically compares the size of the filesystem inside the pup001 file and resizes it if it is smaller than the file.

So, the "Start -> utilities -> Resize /root filesystem"
now does NOT resize the filesystem, so there is no delay.
The script just resizes pup001 (if it isn't a NTFS partition) then after
rebooting Puppy the ext2 f.s. gets resized at bootup.

In the case of NTFS, no need to run the above script or do anything
at all. After resizing pup001 from XP, boot Puppy, and the ext2 f.s.
will automatically resize.

At least, that is what is supposed to happen...
you should see a resizing progress bar at bootup.

This new arrangement was announced on the News page, and it fixes
a possible corruption problem with resizing pup001 f.s. while it is
mounted.

[raffy]

Intro:

What I did in NTFS: pup001 (256 MB) + pup002 (512000000) = pup001

New pup001 = 780435456 bytes or 762144 KB

Results after rebooting into Puppy 1.04:

"Resizing to fill 744 M file"
resize2fs version xxx
resize2fs: Invalid argument while trying to flush /mnt/home/pup001 failed

Pausing for 60 seconds"

My theory: error could be the number in the last parameter of resize2fs which is expected to be in kbytes (a wild guess )

More experiments: I tried "resize2fs -p /mnt/home/pup001" without ending parameter and it reported "761,857 blocks" (but Barry has already warned against doing this, OK?). Same report even when I specified "762144" after another reboot (I restored my backup pup001 in WinXP before the fresh reboot). Usually, resize2fs requires me to first "e2fsck -f /mnt/home/pup001", which goes well.

EDIT: My error = Forgot to avoid mounting pup001 (forgot to use option 3 at bootup)

PC system: AMD 2+Ghz with Windows XP home edition booting Chubby Puppy from WinGrub (No booting errors in the past).

[BarryK]

raffy,
did you actually try the "e2fsck -f /mnt/home/pup001" in rc.sysinit before the resize?
This has to be done at bootup, before pup001 is mounted on /root.

Note, if resize2fs has no size parameter on the end, it defaults to filling the entire file.

[raffy]

Yes, Barry, I remember that e2fsck is a filesystem check routine.

EDIT: Anyway, perhaps Rarsa's solution is still the best for that bug:

http://www.murga.org/%7Epuppy/viewtopic.php?p=6763