All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: udev auto-mount not doing fsck
Date: Thu, 10 Apr 2014 16:48:49 +0200	[thread overview]
Message-ID: <li6b0g$9m6$1@ger.gmane.org> (raw)
In-Reply-To: <CAFZh4h9SFyWK76jsumww+5JPbUzovK+wzcjYbGbAsaCxbmkCGw@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brian Hutchinson schreef op 10-04-14 15:10:
> OK an update.  I decided to stub the automount.rules for the moment to
> try and get things working the old way and I'm seeing some curious
> behavior. The target is running Yocto 1.5 so it is a fairly recent
> distro.
> 
> I made an entry in /etc/fstab for my eUSB with the sixth column set to
> 2. On reboot fsck doesn't run.  Hmmm, curious.  I still see the:
> 
> EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is 
> recommended EXT4-fs (sda1): mounted filesystem with ordered data mode.
> Opts: (null)
> 
> ... messages at boot.
> 
> So I do touch /forcefsck and reboot.   Same result. shutdown -rF ... same
> result.
> 
> I can't figure out why none of these methods is checking my eUSB drive.

To ask the obvious question: is fsck.ext{2,3,4} present on your system?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFTRq9RMkyGM64RGpERAoV7AJ41jAQXvVid86l2Ntdeb7eR91H19wCcDx2I
y+BA/pyMjlOg2C+S8p5/lHM=
=36Lo
-----END PGP SIGNATURE-----



  reply	other threads:[~2014-04-10 14:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 20:53 udev auto-mount not doing fsck Brian Hutchinson
2014-04-10 13:10 ` Brian Hutchinson
2014-04-10 14:48   ` Koen Kooi [this message]
2014-04-10 15:12     ` Brian Hutchinson
2014-04-10 16:56       ` Denys Dmytriyenko
2014-04-10 18:00         ` Brian Hutchinson
2014-04-10 21:47           ` Brian Hutchinson
2014-04-10 22:22             ` Denys Dmytriyenko

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='li6b0g$9m6$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.