All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: Martin Doucha <martin.doucha@suse.com>
Subject: [LTP] TMPDIR minimal size requirement
Date: Thu, 1 Feb 2024 11:16:03 +0100	[thread overview]
Message-ID: <20240201101603.GA78772@pevik> (raw)

Hi all,

recent LTP change 3626124a4 ("fallocate06: Increase test loop device size to
1GB") [1] increased requirement on TMPDIR size for syscalls. That hits the size
of tmpfs we use in openSUSE Tumbleweed on /tmp. While we can workaround easily
this in openQA framework we use for LTP testing (use TMPDIR=/var/tmp for
fallocate06 or even for whole runtest syscalls), I wonder if we should have some
LTP upstream fix.

What comes to mi mind, we could use as TMPDIR default /var/tmp (only if it does
not exists, we would fallback to /tmp). We could also warn against tmpfs use.
Or at least document on README that although many tests need 300 MB for a block
device, some tests require more and suggest to use /var/tmp.

Also, Cyril asked for a patch with minimal device size per filesystem (IMHO
still would be done). At least for Btrfs and XFS some people complains 300
MB is not a real testing scenario, therefore if we implement it and use 1 GB
e.g. for Btrfs and XFS we will hit limits on "low resource" devices.

Kind regards,
Petr

[1] https://github.com/linux-test-project/ltp/commit/3626124a42adfe536af2abff63213fa1ccc63795

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2024-02-01 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 10:16 Petr Vorel [this message]
2024-02-06 18:53 ` [LTP] TMPDIR minimal size requirement Petr Vorel

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=20240201101603.GA78772@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=martin.doucha@suse.com \
    /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.