From: Steve Ellcey <sellcey@caviumnetworks.com>
To: ltp@lists.linux.it
Subject: [LTP] Running LTP results in read-only filesystem
Date: Tue, 07 Mar 2017 10:40:47 -0800 [thread overview]
Message-ID: <1488912047.22552.6.camel@caviumnetworks.com> (raw)
Has anyone run into a problem where running the LTP tests as root
results in a read-only filesystem? I have been running LTP as root on
an ubuntu 16.04 aarch64 system and it appears that when I do that my
root filesystem gets set to read-only and then, when I reboot to try
and fix the problem, the machine can't fsck itself and come back up
without some human intervention. Has anyone else seen this problem?
Steve Ellcey
sellcey@cavium.com
next reply other threads:[~2017-03-07 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 18:40 Steve Ellcey [this message]
2017-03-08 11:19 ` [LTP] Running LTP results in read-only filesystem Cyril Hrubis
2017-03-08 18:41 ` Steve Ellcey
2017-03-22 15:40 ` Cyril Hrubis
2017-03-22 15:49 ` Steve Ellcey
2017-03-22 15:51 ` Cyril Hrubis
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=1488912047.22552.6.camel@caviumnetworks.com \
--to=sellcey@caviumnetworks.com \
--cc=ltp@lists.linux.it \
/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