From: Ivan Shmakov <oneingray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: NILFS2 under stress
Date: Sun, 17 Jun 2012 19:55:05 +0700 [thread overview]
Message-ID: <86vciqrtcm.fsf@gray.siamics.net> (raw)
In-Reply-To: CAPLqH6x7OCXS95w7-J+DLdiVkKAuKm=-8ofGwL-rcC19Z679bw@mail.gmail.com
>>>>> Zavi Zavi writes:
> I've been experimenting with NILFS2 on a 8GB USB stick. I repeatedly
> created and deleted a 128MB file. After about 60 attempts, the disk
> got 100% full, and would not respond anymore.
I've tried to install a Debian Wheezy instance onto an 8 GiB
logical volume via debootstrap(8) from Debian Squeeze (Linux
2.6.32-5-amd64, nilfs-tools 2.0.18-2) and have witnessed pretty
much the same behavior.
> So I tried repeating this setup after changing the GC settings to be
> much more agressive GC policy
> protection_period 0
[…]
I've restarted nilfs_cleanerd(8) with the protection period set
to only 60 seconds (see below; the rest of the configuration is
as per the Debian defaults), and the free space began to rise,
albeit somewhat slowly (around a few MiB's per second), until it
reached 1.7 GiB, when it's stopped.
(I guess that it's quite normal, though I'm yet to become
familiar with NILFS2.)
# nilfs_cleanerd -p 60 \
/dev/mapper/vgXXX-host--2012--06--17.chroot \
/srv/chroot/2012-06-17
--
FSF associate member #7257
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-06-17 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 9:07 NILFS2 under stress Zavi Zavi
[not found] ` <CAPLqH6x7OCXS95w7-J+DLdiVkKAuKm=-8ofGwL-rcC19Z679bw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-15 16:50 ` Christian Smith
[not found] ` <20120615165024.GI16953-Ng8wz+J301SNY5Lh21HnMTHS2PGA244I9dF7HbQ/qKg@public.gmane.org>
2012-06-16 11:49 ` Tim Bannister
[not found] ` <985C1135657081458B80476678A9AF7F3ADDAC29-AwGyfWOFj6xM8+wRG0yK8vXRex20P6io@public.gmane.org>
2012-06-16 19:09 ` Christian Smith
[not found] ` <20120616190906.GJ16953-Ng8wz+J301SNY5Lh21HnMTHS2PGA244I9dF7HbQ/qKg@public.gmane.org>
2012-06-17 15:07 ` Tim Bannister
[not found] ` <985C1135657081458B80476678A9AF7F3ADDACF0-AwGyfWOFj6xM8+wRG0yK8vXRex20P6io@public.gmane.org>
2012-06-17 16:22 ` Ryusuke Konishi
2012-06-17 12:55 ` Ivan Shmakov [this message]
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=86vciqrtcm.fsf@gray.siamics.net \
--to=oneingray-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.