From: Eric A <eric225125-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: df reports used space gradually growing.
Date: Sun, 26 Jul 2009 19:00:09 -0700 (PDT) [thread overview]
Message-ID: <450036.15299.qm@web58805.mail.re1.yahoo.com> (raw)
In-Reply-To: <874oszhsip.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1367 bytes --]
Ok, thanks that makes sense. Well now that nilfs_cleanerd has been running for about 9 hours, it is actually starting to free up some space! It's freed up about 1GB so far of the 12GB that should be freed. So, I suppose it is working correctly, just rather slowly. So, the only real problem is that it is not being started on mount, but for now I can just manually start it.
Eric
________________________________
From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Sent: Sunday, July 26, 2009 8:35:42 PM
Subject: Re: [NILFS users] df reports used space gradually growing.
Hi,
> Using lscp, I see no snapshots, but several thousand checkpoints. I tried
> deleting the checkpoints with rmcp, but that didn't free up any space. The
> disk is still slowly filling.
Unfortunately that's the way rmcp works for now.
rmcp only tells the cleanerd the checkpoint is ready to remove even
in the protection period and nilfs_cleanerd is the only process that
collect garage from the storage and create free space for new logs.
thanks,
regards,
--
Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users
[-- Attachment #1.2: Type: text/html, Size: 2406 bytes --]
[-- Attachment #2: Type: text/plain, Size: 158 bytes --]
_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users
next prev parent reply other threads:[~2009-07-27 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 15:18 df reports used space gradually growing Eric A
[not found] ` <675178.67834.qm-MMAiOCDKa4SB9c0Qi4KiSlZ8N9CAUha/QQ4Iyu8u01E@public.gmane.org>
2009-07-26 16:05 ` Jérôme Poulin
[not found] ` <debc30fc0907260905w76ccec51g421ab08ecf3f67bd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-26 17:40 ` Eric A
[not found] ` <288232.83823.qm-GoVOXiws8HGB9c0Qi4KiSlZ8N9CAUha/QQ4Iyu8u01E@public.gmane.org>
2009-07-26 18:57 ` Ryusuke Konishi
[not found] ` <20090727.035744.118657598.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-07-26 19:35 ` Eric A
[not found] ` <826723.64411.qm-CSBWnlGNI82B9c0Qi4KiSlZ8N9CAUha/QQ4Iyu8u01E@public.gmane.org>
2009-07-27 0:35 ` Jiro SEKIBA
[not found] ` <874oszhsip.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2009-07-27 2:00 ` Eric A [this message]
[not found] ` <450036.15299.qm-tDJBJ58iwLuB9c0Qi4KiSlZ8N9CAUha/QQ4Iyu8u01E@public.gmane.org>
2009-07-27 5:02 ` Ryusuke Konishi
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=450036.15299.qm@web58805.mail.re1.yahoo.com \
--to=eric225125-/e1597as9lqavxtiumwx3w@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox