From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Jan Stancek <jstancek@redhat.com>, "Theodore Ts'o" <tytso@mit.edu>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
lkft-triage@lists.linaro.org, ltp@lists.linux.it,
LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org,
Arthur Marsh <arthur.marsh@internode.on.net>,
Richard Weinberger <richard.weinberger@gmail.com>
Subject: Re: [LTP] LTP: Syscalls: 274 failures: EROFS(30): Read-only file system
Date: Tue, 14 May 2019 11:20:54 +0200 [thread overview]
Message-ID: <20190514092054.GA6949@osiris> (raw)
In-Reply-To: <1723398651.22256606.1557731771283.JavaMail.zimbra@redhat.com>
On Mon, May 13, 2019 at 03:16:11AM -0400, Jan Stancek wrote:
> ----- Original Message -----
> > We have noticed 274 syscall test failures on x86_64 and i386 due to
> > Make the temporary directory in one shot using mkdtemp failed.
> > tst_tmpdir.c:264: BROK: tst_tmpdir:
> > mkdtemp(/scratch/ltp-7D8vAcYeFG/OXuquJ) failed: EROFS
>
> Looks like ext4 bug:
>
> [ 1916.032087] EXT4-fs error (device sda): ext4_find_extent:909: inode #8: comm jbd2/sda-8: pblk 121667583 bad header/extent: invalid extent entries - magic f30a, entries 8, max 340(340), depth 0(0)
> [ 1916.073840] jbd2_journal_bmap: journal block not found at offset 4455 on sda-8
> [ 1916.081071] Aborting journal on device sda-8.
> [ 1916.348652] EXT4-fs error (device sda): ext4_journal_check_start:61: Detected aborted journal
> [ 1916.357222] EXT4-fs (sda): Remounting filesystem read-only
>
> So best place for report is likely linux-ext4@vger.kernel.org
Actually adding the mailing list, since there has been at least one
other report about ext4 filesystem corruption.
FWIW, I've seen the above also at least once on s390 when using a
kernel built with git commit 47782361aca2.
> >
> > Failed log:
> > ------------
> > pread01 1 TBROK : tst_tmpdir.c:264: tst_tmpdir:
> > mkdtemp(/scratch/ltp-7D8vAcYeFG/preAUvXAE) failed: errno=EROFS(30):
> > Read-only file system
> > pread01 2 TBROK : tst_tmpdir.c:264: Remaining cases broken
> >
> > full test log,
> > --------------
> > https://lkft.validation.linaro.org/scheduler/job/711826#L7834
> >
> > LTP Version: 20190115
> >
> > Kernel bad commit:
> > ------------
> > git branch master
> > git commit dd5001e21a991b731d659857cd07acc7a13e6789
> > git describe v5.1-3486-gdd5001e21a99
> > git repo https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> >
> > Kernel good commit:
> > ------------
> > git branch master
> > git commit d3511f53bb2475f2a4e8460bee5a1ae6dea2a433
> > git describe v5.1-3385-gd3511f53bb24
> > git repo https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> >
> > Best regards
> > Naresh Kamboju
> >
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
parent reply other threads:[~2019-05-14 9:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1723398651.22256606.1557731771283.JavaMail.zimbra@redhat.com>]
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=20190514092054.GA6949@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=arthur.marsh@internode.on.net \
--cc=jstancek@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=naresh.kamboju@linaro.org \
--cc=richard.weinberger@gmail.com \
--cc=tytso@mit.edu \
/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).