public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@caviumnetworks.com>
To: ltp@lists.linux.it
Subject: [LTP] Running LTP results in read-only filesystem
Date: Wed, 22 Mar 2017 08:49:30 -0700	[thread overview]
Message-ID: <1490197770.19074.24.camel@caviumnetworks.com> (raw)
In-Reply-To: <20170322154013.GB4960@rei.lan>

On Wed, 2017-03-22 at 16:40 +0100, Cyril Hrubis wrote:
> Hi!
> > 
> > I am using an ext4 filesystem on a hard disk drive. ??dmesg is empty, it
> > may have gotten deleted during the reboot and/or the fsck that was done
> > during the reboot to get the system to come back up.
> The dmesg output is not reboot persistent, the log is normally logged to
> /var/log/messages via the syslog daemon, but once the FS gets read-only
> the daemon can't write the logs so they end up lost on reboot...

I may have been too fast to blame LTP for my system crashes.  I had
another crash when not running LTP and where the filesystem became
read-only and now I think the machine has a hardware issue.  LTP may
have caused the problem to appear more frequently by stressing the
system but I don't think the underlying bug of the filesystem becoming
read-only was due to LTP.

Steve Ellcey

  reply	other threads:[~2017-03-22 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 18:40 [LTP] Running LTP results in read-only filesystem Steve Ellcey
2017-03-08 11:19 ` Cyril Hrubis
2017-03-08 18:41   ` Steve Ellcey
2017-03-22 15:40     ` Cyril Hrubis
2017-03-22 15:49       ` Steve Ellcey [this message]
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=1490197770.19074.24.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