linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] xfsprogs: document environment variables
Date: Wed, 26 Sep 2018 16:13:41 -0700	[thread overview]
Message-ID: <20180926231341.GY20086@magnolia> (raw)
In-Reply-To: <959fd8f0-b03d-decd-3048-e1c7d88051fa@sandeen.net>

On Wed, Sep 26, 2018 at 04:27:27PM -0500, Eric Sandeen wrote:
> From: Eric Sandeen <sandeen@redhat.com>
> 
> Document the various environment variables used in the code,
> almost all are for debugging.
> 
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
> 
> diff --git a/doc/README-env-vars.txt b/doc/README-env-vars.txt
> new file mode 100644
> index 0000000..eec59a8
> --- /dev/null
> +++ b/doc/README-env-vars.txt
> @@ -0,0 +1,26 @@
> +Several environment variables are used within the code, primarily for
> +for debugging purposes; they are documented here.  In most cases simply
> +setting the environment variable enables the behavior, but in some
> +cases the value assigned influences behavior as well, as noted below.
> +
> +General
> +-------
> +LIBXFS_LEAK_CHECK            -- warn and exit(1) if zone-allocated memory
> +                                is leaked at exit.
> +xfs_fsr
> +-------
> +FSRXFSTEST                   -- enable -C nfrag in theory coalesces into
> +                                nfrag extents.  Doesn't work.

<eyeroll> Maybe someone should fix/remove that?

Anyway, for the documentation,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

--D

> +xfs_scrub
> +---------
> +Known debug tweaks (pass -d and set the environment variable):
> +XFS_SCRUB_FORCE_ERROR        -- pretend all metadata is corrupt
> +XFS_SCRUB_FORCE_REPAIR       -- repair all metadata even if it's ok
> +XFS_SCRUB_NO_KERNEL          -- pretend there is no kernel ioctl
> +XFS_SCRUB_NO_SCSI_VERIFY     -- disable SCSI VERIFY (if present)
> +XFS_SCRUB_PHASE              -- run only this scrub phase
> +XFS_SCRUB_THREADS            -- start exactly this number of threads
> +
> +Available even in non-debug mode:
> +SERVICE_MODE                 -- compress all error codes to 1 for LSB
> +                                service action compliance
> 

      reply	other threads:[~2018-09-27  5:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 21:23 [PATCH 0/2] xfsprogs: env var stuff Eric Sandeen
2018-09-26 21:25 ` [PATCH 1/2] scrub: remove redundant debug test Eric Sandeen
2018-09-26 23:12   ` Darrick J. Wong
2018-09-26 21:27 ` [PATCH 2/2] xfsprogs: document environment variables Eric Sandeen
2018-09-26 23:13   ` Darrick J. Wong [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=20180926231341.GY20086@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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).