marmistrz | # 261 | 2014-09-28, 10:26 | Report

Show current shows a list of 3 swaps: one internal, 2 usd.

I agree that the banner about finishing is useful, but a banner can be easily missed when it comes to e.g. checking current write.

---

Last edited by marmistrz; 2014-09-28 at 10:37.

sixwheeledbeast | # 262 | 2014-09-29, 17:34 | Report

Hmm, I am still not sure how that has happened.

Have you modified your upstart or sysytem-services at all?
Does the file /etc/event.d/relocateswap exist?

marmistrz | # 263 | 2014-09-29, 18:02 | Report

I guess no. I probably reflashed the phone after this. But there's a faint possibility that I purged and reinstalled system-services because of problems with ereswap. I don't have ereswap installed now and rcS-late doesn't have ereswap modifications.

Yes it exists and `sudo start relocateswap` does what it should

sixwheeledbeast | # 264 | 2014-09-29, 18:32 | Report

Quick reply.....

What are the permissions for relocateswap?

When I get a moment I will remove, purge and reinstall flopswap to make sure I can't reproduce this.

If it exists and works then I can only assume it is something else in the boot process.

marmistrz | # 265 | 2014-09-29, 18:42 | Report

So I'll try purging flopswap and reinstalling it and then I'll add something to debug to the relocateswap script.

sixwheeledbeast | # 266 | 2014-10-16, 21:36 | Report

Flopswap 0.1.10 uploaded to extras-devel

* Minor fixes to some scripts
* Switch to external swap on boot enabled as default
* Busy indication
* Check status on start option (thanks pichlo)

As you can see I have included busy indication exactly as above into Flopswap. This was a good idea and makes the application look like it's doing something while switching.

Also thanks to pichlo for his guidance on my startup check code.

I am still working on outputting the current status somehow.
For now checkout "cat /tmp/flopswapcur"

As always let me know if you have any issues, enjoy.

malfunctioning | # 267 | 2014-10-20, 17:12 | Report

Thank you for your work, sixwheeledbeast.

I am seeing an issue in FlopSwap 0.1.9 and I didn't see this reported in the thread.

When I look in Check Status, I'm getting 7Mb out of 770Mb used. However, the free command reports almost 70Mb of swap space used (a factor of 10 larger).

Is this known? And, would it affect when the swap switch takes place, since it is set to kick in at a specific percentage of swap use?

My setup is with 2 Linux Swap partitions in microSD, and everything seems to be fine otherwise.

Also, quick question: Does the geometry/block size of the swap partition affect these calculations?

---

Last edited by malfunctioning; 2014-10-20 at 17:18.

sixwheeledbeast | # 268 | 2014-10-20, 17:37 | Report

No, thank you for the feedback.

free is not equal to flopswap's values.
You see flopswap is measuring the fresh (clean) swap that has been written not the amount in use.

To make this clear in an example, when flopswap hits 100% it doesn't mean you have no swap left, it means you have no "fresh" swap left and you may now see the slowing effect of swap fragmentation.

Swap switching is not done automatically. You maybe in the middle of a task when you reach your switching threshold. You don't want flopswap to be memory thrashing then This would also require having a daemon running all the time, which I didn't want.
To refresh your swap manually you need to press the Fresh Swap button.

For automatic switching I recommend setting up a cronjob early in the morning while your asleep.
See the wiki page for more details on this.
http://wiki.maemo.org/Flopswap


Flopswap knows how large your current uSD swap space is and uses this value for the percentage. This is why two equal size uSD swaps is recommended.

---

Last edited by sixwheeledbeast; 2014-10-21 at 14:39.

misiak | # 269 | 2014-10-20, 17:54 | Report

This still smells fishy... If N900 uses 70mb of swap (example from above malfunctioning's post), then even after reswaping, right at the beginning, the amount of used swap (in your application) should show no less then 70 mb, right? (I understand that these number can be different, but I don't understand how value reported by flopswap could be lower then value reported by free - I undestand it that this must be always true: value_reported_by_free <= value_reported_by_flopswap)

malfunctioning | # 270 | 2014-10-20, 18:35 | Report

Thank you for your explanations, sixwheeledbeast.

Everything makes sense and is clear, except the objection misiak proposed (I actually thought about this before I even saw his response ).

It seems (at first sight, anyway) that the percentage of fresh swap remaining should be <= the total amount of swap space remaining reported by free.

But I'm sure I'm wrong and you will clarify things.

EDIT: One way I see this being possible is if the way FlopSwap works is by partitioning the swap space. So you might keep internally a cursor where you start writing sequentially (which is set for example when you make a fresh swap), but which is different of how free swap space is calculated by the free command.

Just speculating.

---

Last edited by malfunctioning; 2014-10-20 at 18:47.