linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Felix E. Klee" <felix.klee@inka.de>
To: linux-nilfs@vger.kernel.org
Subject: Massive overhead even after deleting checkpoints
Date: Fri, 10 Jan 2025 16:54:03 +0100	[thread overview]
Message-ID: <CA+m_8J37qo6fKFUp0wpRuK1FHawXNmCMiEyVYEwpt2Nc3uX5Og@mail.gmail.com> (raw)

The disk is full close to the max:

    $ df -h /bigstore/
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/bigstore  3.5T  3.3T   65G  99% /bigstore

Yet, not that much is actually used by the files themselves:

    $ du -sh /bigstore/
    2.5T    /bigstore/

Using `rmcp` I deleted all checkpoints, but that didn’t solve the issue.
Furthermore, there are no snapshots:

    $ lscp
             CNO        DATE     TIME  MODE  FLG      BLKCNT       ICNT
          443574  2025-01-10 16:41:44   cp    -    652100924     421961
          443575  2025-01-10 16:41:44   cp    -    652100923     421960

The cleaner daemon is running with default configuration (Arch):

    $ ps ax | grep -i cleanerd
        827 ?        S      0:39 /sbin/nilfs_cleanerd
/dev/mapper/bigstore /bigstore
     117067 pts/1    S+     0:00 grep --color=auto -i cleanerd

I also rebooted the system, causing a remount of the partition. Yet,
still no improvement.

Is there a solution, or is the missing space simply used up by NILFS
data structures? (it would be a bit very much overhead)

             reply	other threads:[~2025-01-10 15:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 15:54 Felix E. Klee [this message]
2025-01-10 17:36 ` Massive overhead even after deleting checkpoints Ryusuke Konishi
2025-01-10 18:25   ` Felix E. Klee
2025-01-11  5:29     ` Ryusuke Konishi
2025-01-11  6:21       ` Ryusuke Konishi
2025-01-16 11:08         ` Felix E. Klee
2025-01-16 18:24           ` Ryusuke Konishi
2025-01-31  8:13             ` Felix E. Klee
2025-02-06  7:07               ` Ryusuke Konishi
2025-02-07  4:00                 ` Felix E. Klee

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=CA+m_8J37qo6fKFUp0wpRuK1FHawXNmCMiEyVYEwpt2Nc3uX5Og@mail.gmail.com \
    --to=felix.klee@inka.de \
    --cc=linux-nilfs@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;
as well as URLs for NNTP newsgroup(s).