public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: fstests <fstests@vger.kernel.org>
Subject: Re: generic/459 requires thin_check?
Date: Sun, 29 Oct 2017 14:41:34 +0800	[thread overview]
Message-ID: <20171029064134.GB17339@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20171028204029.GA4908@magnolia>

On Sat, Oct 28, 2017 at 01:40:29PM -0700, Darrick J. Wong wrote:
> Hi,
> 
> I noticed a test failure when running generic/459 -- it seems that this
> test wants thin_check to be installed, doesn't explicitly check for it
> (possibly because it is indirectly run by lvcreate), and therefore the
> thin pool fails to activate.  I think this test needs to look for
> thin_check and _notrun if it's not found.  Comments?

>From lvmthin(7):

"
When a thin pool LV is activated, lvm runs the thin_check command to check the correctness of the metadata on the pool metadata LV.

lvm.conf(5) thin_check_executable
can be set to an empty string ("") to disable the thin_check step.  This is not recommended.
"

and in my RHEL7 system 'thin_check_executable' config is commented out
in /etc/lvm/lvm.conf, which means it uses the default
/usr/sbin/thin_check command to do the metadata check. And thin_check is
provided by package device-mapper-persistent-data.

So IMHO it's totally valid to create thin-pool with lvcreate without
thin_check command (i.e. it's not a distro bug that messed up the lvm
dependency), and it makes sense to check the existence of thin_check in
generic/459.

Thanks,
Eryu

> 
> --D
> 
> results/generic/459.out is as follows:
> 
> meta-data=/dev/pmem4             isize=512    agcount=4, agsize=16000 blks
>          =                       sectsz=4096  attr=2, projid32bit=1
>          =                       crc=1        finobt=1, sparse=1, rmapbt=1, reflink=1
> data     =                       bsize=4096   blocks=64000, imaxpct=25
>          =                       sunit=0      swidth=0 blks
> naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
> log      =internal log           bsize=4096   blocks=3609, version=2
>          =                       sectsz=4096  sunit=1 blks, lazy-count=1
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> File descriptor 3 (/tmp/log) leaked on lvm invocation. Parent PID 11865: /bin/bash
>   Wiping xfs signature on /dev/pmem4.
>   Physical volume "/dev/pmem4" successfully created
> File descriptor 3 (/tmp/log) leaked on lvm invocation. Parent PID 11865: /bin/bash
>   Volume group "vg_459" successfully created
> File descriptor 3 (/tmp/log) leaked on lvm invocation. Parent PID 11865: /bin/bash
>   Logical volume "pool_459" created.
> File descriptor 3 (/tmp/log) leaked on lvm invocation. Parent PID 11865: /bin/bash
>   /usr/sbin/thin_check: execvp failed: No such file or directory
>   WARNING: Integrity check of metadata for pool vg_459/pool_459 failed.
>   WARNING: Sum of all thin volume sizes (200.00 MiB) exceeds the size of thin pool vg_459/pool_459 (100.00 MiB)!
>   For thin pool auto extension activation/thin_pool_autoextend_threshold should be below 100.
>   /usr/sbin/thin_check: execvp failed: No such file or directory
>   Check of pool vg_459/pool_459 failed (status:2). Manual repair required!
>   Failed to activate thin pool vg_459/pool_459.

      reply	other threads:[~2017-10-29  6:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28 20:40 generic/459 requires thin_check? Darrick J. Wong
2017-10-29  6:41 ` Eryu Guan [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=20171029064134.GB17339@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@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