From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Yoann CONGAL <yoann.congal@smile.fr>,
Randy MacLeod <randy.macleod@windriver.com>,
Josef Holzmayr <jester@theyoctojester.info>
Subject: [PATCH v2] dev-manual: disk-space: mention faster "find" command to trim sstate cache
Date: Thu, 17 Aug 2023 16:15:28 +0200 [thread overview]
Message-ID: <20230817141528.2869208-1-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <177A5EF47817BA65.8497@lists.yoctoproject.org>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
[YOCTO #15182]
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Yoann CONGAL <yoann.congal@smile.fr>
Reported-by: Randy MacLeod <randy.macleod@windriver.com>
Reported-by: Josef Holzmayr <jester@theyoctojester.info>
---
- Changes in V2:
- Using a more universal "-mtime" option to find files to remove
as suggested by Richard Purdie. V1 was using "-atime" which
won't work with systems mounted with the "noatime" option used
to increase disk performance.
- Add more details about sstate-cache-management.sh provided by
Richard Purdie, perhaps not recommended but useful to document
as long as it is shipped in OE-core.
---
documentation/dev-manual/disk-space.rst | 31 ++++++++++++++++++-------
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git a/documentation/dev-manual/disk-space.rst b/documentation/dev-manual/disk-space.rst
index c63591cc7a..01cdf911c4 100644
--- a/documentation/dev-manual/disk-space.rst
+++ b/documentation/dev-manual/disk-space.rst
@@ -27,19 +27,32 @@ Purging Duplicate Shared State Cache Files
==========================================
After multiple build iterations, the Shared State (sstate) cache can contain
-duplicate cache files for a given package, while only the most recent one
-is likely to be reusable. The following command purges all but the
-newest sstate cache file for each package::
+duplicate cache files for a given package, consuming a substantial amount of
+disk space. However, only the most recent cache files are likeky to be reusable.
- sstate-cache-management.sh --remove-duplicated --cache-dir=build/sstate-cache
+The following command is a quick way to purge all the cache files which
+haven't been used for a least a specified number of days::
-This command will ask you to confirm the deletions it identifies.
+ find build/sstate-cache -type f -mtime +$DAYS -delete
-.. note::
+The above command relies on the fact that BitBake touches the sstate cache
+files as it accesses them, when it has write access to the cache.
+
+For more advanced needs, OpenEmbedded-Core also offers a more elaborate
+command. It has the ability to purge all but the newest cache files on each
+architecture, and also to remove files that it considers unreachable by
+exploring a set of build configurations. However, this command
+requires a full build environment to be available and doesn't work well
+covering multiple releases. It won't work either on limited environments
+such as BSD based NAS::
- The duplicated sstate cache files of one package must have the same
- architecture, which means that sstate cache files with multiple
- architectures are not considered as duplicate.
+ sstate-cache-management.sh --remove-duplicated --cache-dir=build/sstate-cache
+This command will ask you to confirm the deletions it identifies.
Run ``sstate-cache-management.sh`` for more details about this script.
+.. note::
+
+ As this command is much more cautious and selective, removing only cache files,
+ it will execute much slower than the simple ``find`` command described above.
+ Therefore, it may not be your best option to trim huge cache directories.
--
2.34.1
next parent reply other threads:[~2023-08-17 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <177A5EF47817BA65.8497@lists.yoctoproject.org>
2023-08-17 14:15 ` michael.opdenacker [this message]
2023-08-17 14:22 ` [docs] [PATCH v2] dev-manual: disk-space: mention faster "find" command to trim sstate cache Richard Purdie
2023-08-17 14:56 ` [PATCH v3] " michael.opdenacker
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=20230817141528.2869208-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=jester@theyoctojester.info \
--cc=randy.macleod@windriver.com \
--cc=yoann.congal@smile.fr \
/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