From: Bruno Thomsen <bth@kamstrup.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] automatic root-fs fsck at boottime with autorepair
Date: Thu, 25 Jun 2015 06:10:03 +0000 [thread overview]
Message-ID: <915054555B5659448ACF8A70E114824D01A4C05BBF@Exchange2010.kamstrup.dk> (raw)
In-Reply-To: <alpine.DEB.2.20.1504211143520.16262@hp-ws8>
Hi Marc,
> Just fyi in the syslog I found these lines:
>
> Apr 21 11:50:11 [..] [ 1.854104] EXT3-fs: barriers not enabled
> Apr 21 11:50:11 [..] [12.856129] kjournald starting. Commit interval 5 seconds
> Apr 21 11:50:11 [..] [12.856223] EXT3-fs (mmcblk0p1): warning: maximal mount count reached, running e2fsck is recommended
> Apr 21 11:50:11 [..] [13.091387] EXT3-fs (mmcblk0p1): using internal journal
> Apr 21 11:50:11 [..] [13.091398] EXT3-fs (mmcblk0p1): recovery complete
> Apr 21 11:50:11 [..] [13.093917] EXT3-fs (mmcblk0p1): mounted filesystem with ordered data mode
>
> We just encountered an issue in a mysqld-logfile upon an unexpected power-off but
> this was actually not an issue of the filesystem. Anyway I thought a fsck might be helpful sometimes.
You are using the ext3 filesystem in a unsafe manner (default) that can cause data corruption.
Enable barriers and change data mode to journal. The downside to safety is lower R/W performance.
/Bruno
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-06-25 4:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 11:11 Marc Michalewicz
2015-01-22 15:59 ` Tim Sander
2015-01-26 13:51 ` Michael Olbrich
2015-04-21 9:58 ` Marc Michalewicz
2015-06-25 6:10 ` Bruno Thomsen [this message]
2015-04-22 9:14 ` Marc Michalewicz
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=915054555B5659448ACF8A70E114824D01A4C05BBF@Exchange2010.kamstrup.dk \
--to=bth@kamstrup.com \
--cc=ptxdist@pengutronix.de \
/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