The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Swap on Fuse deadlocks?
Date: Mon, 25 Sep 2006 17:43:36 -0400	[thread overview]
Message-ID: <45184D88.1010203@comcast.net> (raw)

I just tried to set up an LZOlayer swap partition:

http://north.one.pl/~kazik/pub/LZOlayer/

The layout was as such:

/tmp/swap_base  - tmpfs (run1), disk (run2)
/tmp/swap - lzolayer swap_base
/tmp/swap/swap0 - 200M swap file
/dev/loop0 - /tmp/swap/swap0 loopback

I turned on loop0, crept anywhere over 10 megs into swap and it seized
up (otherwise it was fine).  This happened in both run1 (swap on tmpfs)
and run2 (swap on disk).

The swap on tmpfs I can understand; it'll essentially loop trying to
allocate new swap, swap in and out parts of the swap file to itself, and
eventually hit a condition where it's trying to swap an area of the swap
file into itself, creating an infinite loop.

Swap on disk I don't get.  A little slow perhaps due to the LZO or zlib
compression in the middle (lzolayer lets you pick either); but a total
freeze?  What's wrong here, is lzo_fs data getting swapped out and then
not swapped in because it's needed to decompress itself?


-- 
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.

    Creative brains are a valuable, limited resource. They shouldn't be
    wasted on re-inventing the wheel when there are so many fascinating
    new problems waiting out there.
                                                 -- Eric Steven Raymond

    We will enslave their women, eat their children and rape their
    cattle!
                  -- Bosc, Evil alien overlord from the fifth dimension

             reply	other threads:[~2006-09-25 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 21:43 John Richard Moser [this message]
2006-09-25 22:04 ` Swap on Fuse deadlocks? Pavel Machek
2006-09-26 17:54   ` Miklos Szeredi
2006-09-26  0:08 ` David Schwartz
2006-09-26 12:13   ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45184D88.1010203@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox