SEO

#1 (**permalink**) 02-19-2008, 11:00 AM

Hello group:

I ran into a problem with a fresh install of Zipslack 9.1 in that it will
not use its swap file nor will it use a swap partition. The free program
says the swap space is there but the system doesn't use it when it runs
out of memory so it eventually hangs. Why?

Thanks

#2 (**permalink**) 02-19-2008, 11:00 AM

On Mon, 07 Jun 2004 03:08:22 +0000, Mike Keithley wrote:
> I ran into a problem with a fresh install of Zipslack 9.1 in that it will
> not use its swap file nor will it use a swap partition. The free program
> says the swap space is there but the system doesn't use it when it runs
> out of memory so it eventually hangs. Why?

You've made an assumption above, that the failure to use swap space is
the cause of the hangs. Check your log files and post the last entries
before the hang. Does it hang with you there? If so what are you doing
at the time?

I doubt your assumption is valid. Test it with a cron job to run "date"
and "free -t" and append to a file every 5 minutes until it crashes.

Also, more information would help. Are we talking about a 386 with 4MB
RAM? If so, it's quite possible that you're running out of memory.

--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

#3 (**permalink**) 02-19-2008, 11:02 AM

On 2004-06-07, Mike Keithley <mkeithley@pobox.com> wrote:
>
> I ran into a problem with a fresh install of Zipslack 9.1 in that it will
> not use its swap file nor will it use a swap partition. The free program
> says the swap space is there but the system doesn't use it when it runs
> out of memory so it eventually hangs. Why?
>
Show us your /etc/fstab.

#4 (**permalink**) 02-19-2008, 11:14 AM

Unfortunately I haven't had time to address this problem until now.

Let me thank all who replied and I apologize for not including enough
information.

I fixed the problem! I was trying to use dd to copy my ext2 image to an
external hard disk on a Firewire interface. I was using a block size of 1
K and this was too small; the protocol to the external drive was disturbed
and the logs showed the system lost access to the drive--over and over and
over. A block size of 2K was still too small so a Used a block size of 1
M (it was an 8 GB image) and it worked fine.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Zipslack 9.1 won't use swap partition or file