From: Jan Stancek <jstancek@redhat.com>
To: Cyril Hrubis <chrubis@suse.cz>,
Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: ltp@lists.linux.it,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
alexey kodanev <alexey.kodanev@oracle.com>,
the hoang0709 <the_hoang0709@yahoo.com>
Subject: Re: Linux-next-20190823: x86_64/i386: prot_hsymlinks.c:325: Failed to run cmd: useradd hsym
Date: Mon, 26 Aug 2019 07:05:20 -0400 (EDT) [thread overview]
Message-ID: <1264279239.8133737.1566817520787.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190826104127.GA14729@haruka>
----- Original Message -----
> Hi!
> > Do you see this LTP prot_hsymlinks failure on linux next 20190823 on
> > x86_64 and i386 devices?
> >
> > test output log,
> > useradd: failure while writing changes to /etc/passwd
> > useradd: /home/hsym was created, but could not be removed
>
> This looks like an unrelated problem, failure to write to /etc/passwd
> probably means that filesystem is full or some problem happend and how
> is remounted RO.
In Naresh' example, root is on NFS:
root=/dev/nfs rw nfsroot=10.66.16.123:/var/lib/lava/dispatcher/tmp/886412/extract-nfsrootfs-tyuevoxm,tcp,hard,intr
10.66.16.123:/var/lib/lava/dispatcher/tmp/886412/extract-nfsrootfs-tyuevoxm on / type nfs (rw,relatime,vers=2,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.66.16.123,mountvers=1,mountproto=tcp,local_lock=all,addr=10.66.16.123)
devtmpfs on /dev type devtmpfs (rw,relatime,size=3977640k,nr_inodes=994410,mode=755)
Following message repeats couple times in logs:
NFS: Server wrote zero bytes, expected XXX
Naresh, can you check if there are any errors on NFS server side?
Maybe run NFS cthon against that server with client running next-20190822 and next-20190823.
>
> I do not see the kernel messages from this job anywhere at the job
> pages, is it stored somewhere?
It appears to be mixed in same log file:
https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190823/testrun/886412/log
WARNING: multiple messages have this Message-ID (diff)
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] Linux-next-20190823: x86_64/i386: prot_hsymlinks.c:325: Failed to run cmd: useradd hsym
Date: Mon, 26 Aug 2019 07:05:20 -0400 (EDT) [thread overview]
Message-ID: <1264279239.8133737.1566817520787.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190826104127.GA14729@haruka>
----- Original Message -----
> Hi!
> > Do you see this LTP prot_hsymlinks failure on linux next 20190823 on
> > x86_64 and i386 devices?
> >
> > test output log,
> > useradd: failure while writing changes to /etc/passwd
> > useradd: /home/hsym was created, but could not be removed
>
> This looks like an unrelated problem, failure to write to /etc/passwd
> probably means that filesystem is full or some problem happend and how
> is remounted RO.
In Naresh' example, root is on NFS:
root=/dev/nfs rw nfsroot=10.66.16.123:/var/lib/lava/dispatcher/tmp/886412/extract-nfsrootfs-tyuevoxm,tcp,hard,intr
10.66.16.123:/var/lib/lava/dispatcher/tmp/886412/extract-nfsrootfs-tyuevoxm on / type nfs (rw,relatime,vers=2,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.66.16.123,mountvers=1,mountproto=tcp,local_lock=all,addr=10.66.16.123)
devtmpfs on /dev type devtmpfs (rw,relatime,size=3977640k,nr_inodes=994410,mode=755)
Following message repeats couple times in logs:
NFS: Server wrote zero bytes, expected XXX
Naresh, can you check if there are any errors on NFS server side?
Maybe run NFS cthon against that server with client running next-20190822 and next-20190823.
>
> I do not see the kernel messages from this job anywhere at the job
> pages, is it stored somewhere?
It appears to be mixed in same log file:
https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190823/testrun/886412/log
next prev parent reply other threads:[~2019-08-26 11:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 9:47 Linux-next-20190823: x86_64/i386: prot_hsymlinks.c:325: Failed to run cmd: useradd hsym Naresh Kamboju
2019-08-26 9:47 ` [LTP] " Naresh Kamboju
2019-08-26 10:41 ` Cyril Hrubis
2019-08-26 10:41 ` [LTP] " Cyril Hrubis
2019-08-26 11:05 ` Jan Stancek [this message]
2019-08-26 11:05 ` Jan Stancek
2019-08-26 13:50 ` Naresh Kamboju
2019-08-26 13:50 ` [LTP] " Naresh Kamboju
2019-08-26 14:38 ` Jan Stancek
2019-08-26 14:38 ` [LTP] " Jan Stancek
2019-08-26 15:58 ` Trond Myklebust
2019-08-26 15:58 ` [LTP] " Trond Myklebust
2019-08-26 23:12 ` Jan Stancek
2019-08-26 23:12 ` [LTP] " Jan Stancek
2019-08-27 0:59 ` Trond Myklebust
2019-08-27 0:59 ` [LTP] " Trond Myklebust
2019-08-27 10:25 ` Jan Stancek
2019-08-27 10:25 ` [LTP] " Jan Stancek
2019-08-27 12:58 ` Trond Myklebust
2019-08-27 12:58 ` [LTP] " Trond Myklebust
2019-08-27 13:20 ` Jan Stancek
2019-08-27 13:20 ` [LTP] " Jan Stancek
2019-08-27 6:34 ` Naresh Kamboju
2019-08-27 6:34 ` [LTP] " Naresh Kamboju
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=1264279239.8133737.1566817520787.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=alexey.kodanev@oracle.com \
--cc=chrubis@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=naresh.kamboju@linaro.org \
--cc=the_hoang0709@yahoo.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.