From: Zirong Lang <zlang@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org, eguan@redhat.com
Subject: Re: [PATCH] generic/084: check inotify limit before tail many files
Date: Sun, 16 Aug 2015 21:05:19 -0400 (EDT) [thread overview]
Message-ID: <55490920.9057342.1439773519504.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20150817000336.GE20596@dastard>
Hi Dave,
Thanks for your reply.
----- 原始邮件 -----
> 发件人: "Dave Chinner" <david@fromorbit.com>
> 收件人: "Zorro Lang" <zlang@redhat.com>
> 抄送: fstests@vger.kernel.org, eguan@redhat.com
> 发送时间: 星期一, 2015年 8 月 17日 上午 8:03:36
> 主题: Re: [PATCH] generic/084: check inotify limit before tail many files
>
> On Fri, Aug 14, 2015 at 12:16:32AM +0800, Zorro Lang wrote:
> > generic/084 try to run 'tail' command, tail will use
> > inotify, and there're some limit about inotify. I think
> > the most important is fs.inotify.max_user_instances, then
> > fs.inotify.max_user_watches is importand too.
> >
> > When I test on a machine with 154 cpu cores, this case
> > run failed, and hit many warning likes:
> >
> > tail: inotify cannot be used, reverting to polling: Too many
> > open files
> >
> > Because the fs.inotify.max_user_instances is 128, so if
> > we try to tail 154 files, it will be failed.
>
> We use 'tail' all over the place in xfstests, so why is only
> generic/084 affected?
Because generic/084 use try to create $nr_cpu tail processes:
for i in `seq 1 $nr_cpu`; do
...
tail -f $testfile &
...
done
And nr_cpu=`$here/src/feature -o`.
Generally fs.inotify.max_user_instances is 128, when a machine
have more than(or nearly the same) this number, this test will
failed.
Maybe other cases don't try to create so many tail processes, so
they passed.
>
> And really, this seems more like a distro/environment bug and
> doesn't need xfstests help to work around. i.e. changing the
> sysctl before starting xfstests seems much more appropriate than
> hacking it a random test. Especially as there may be more than one
> test that is affected by this, and when run in a random order this
> would cause those other tests to pass/fail depending on whether
> generic/084 had already been run on that machine....
As this situation generally won't effect other cases, so I try to
make the patch don't effect more other cases. Because I don't know
if someone try to test fs.inotify...
But if maintainer think it'll be better, I will change the patch:)
Thanks,
Zorro Lang
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
>
next prev parent reply other threads:[~2015-08-17 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 16:16 [PATCH] generic/084: check inotify limit before tail many files Zorro Lang
2015-08-14 6:58 ` Eryu Guan
2015-08-17 0:03 ` Dave Chinner
2015-08-17 1:05 ` Zirong Lang [this message]
2015-08-17 5:06 ` Dave Chinner
2015-08-17 13:55 ` Zirong Lang
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=55490920.9057342.1439773519504.JavaMail.zimbra@redhat.com \
--to=zlang@redhat.com \
--cc=david@fromorbit.com \
--cc=eguan@redhat.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 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.