[LTP] Running LTP results in read-only filesystem

[LTP] Running LTP results in read-only filesystem

[Steve Ellcey]

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

[LTP] Running LTP results in read-only filesystem

[Cyril Hrubis]

Hi!
> 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?

I remember some FS journal corruptions on cheap SD cards being reported
some time agoI remember some FS journal corruptions on cheap SD cards
being reported some time ago. What filesystem do you use? Have you
checked dmesg output, is there anything related there?

-- 
Cyril Hrubis
chrubis@suse.cz

[LTP] Running LTP results in read-only filesystem

[Steve Ellcey]

On Wed, 2017-03-08 at 12:19 +0100, Cyril Hrubis wrote:
> Hi!
> > 
> > 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?
> I remember some FS journal corruptions on cheap SD cards being reported
> some time agoI remember some FS journal corruptions on cheap SD cards
> being reported some time ago. What filesystem do you use? Have you
> checked dmesg output, is there anything related there?

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.

Steve Ellcey

[LTP] Running LTP results in read-only filesystem

[Cyril Hrubis]

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...

-- 
Cyril Hrubis
chrubis@suse.cz

[LTP] Running LTP results in read-only filesystem

[Steve Ellcey]

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

[LTP] Running LTP results in read-only filesystem

[Cyril Hrubis]

Hi!
> 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.

That tends to happen a lot. Even compiling LTP is a stress test that
found bug in VFS :-).

-- 
Cyril Hrubis
chrubis@suse.cz