mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Marc Michalewicz <Marc.Michalewicz@railtec-systems.ch>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] automatic root-fs fsck at boottime with autorepair
Date: Tue, 21 Apr 2015 11:58:11 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1504211143520.16262@hp-ws8> (raw)
In-Reply-To: <20150126135132.GC30319@pengutronix.de>

Hi,

thanks for your hint; the issue is still open and I have no clue what to do next
although your answer helped a little bit.

But how/where do I have to install the check ?
Can you detail your idea a little bit more ?

I tried "fsck.ext3 -p /dev/mmvblk0p1" on the line before "mount -a ..." in rcS but this 
did not work: 
"fsck.ext3: No such file or directory while trying to open /dev/mmcblk0p1"


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

What does all this mean in detail - especially "recovery complete" ?
so another question would be: do you think a (automatic) fsck is needed at all ?
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.

Thanks for any help,

Marc


On Mon, 26 Jan 2015, Michael Olbrich wrote:

> On Thu, Jan 22, 2015 at 04:59:45PM +0100, Tim Sander wrote:
>>> how can I configure an automatic filesystemcheck of the root filesystem at
>>> boottime ?
>> I think you need an initrd image for that?
>
> No, the rootfs can be checked and fixed, if it is mounted read-only.
> Systemd will do this automatically. For a busybox init you need to add the
> check yourself.
>
> Michael
>
> -- 
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>
> -- 
> ptxdist mailing list
> ptxdist@pengutronix.de
>

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-04-21 12:44 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 [this message]
2015-06-25  6:10       ` Bruno Thomsen
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=alpine.DEB.2.20.1504211143520.16262@hp-ws8 \
    --to=marc.michalewicz@railtec-systems.ch \
    --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