Changing the order of calls to auplink, remount, etc, did not seem to make a
difference.
The auplink / list call shows no output.
I added many fsck checks to places you suggested, It seems from them that
the errors are created at some point during the running of the
firmware-upgrade script, presumably the rsync. Once that rsync is completed,
the unit reboots itself. Upon boot, the errors exist immediately and do not
appear to change throughout the boot / init process, and do not go away
until manually repaired with fsck. Once manually repaired, the fsck checks
on the next boot show a clean filesystem. I let the system run over the
weekend, and then checked the filesystem again, still no errors in this
case.
On occasion, the system will refuse to mount /ro as read only, and only a
reboot seems to solve the issue, do you think this is related? Why would /ro
be shown as having files opened by other programs, when I know that no
program points directly there?
It also appears that enabling journaling on the /dev/sda1 (root) drive seems
to eliminate the filesystem issues. With modern wear-leveling on flash
devices, I might be alright to enable journaling on the root drive to safely
solve the fsck issue, but I am worried that I would only be hiding the
problem, rather than solving the underlying issue.
On Tue, Jul 29, 2014 at 3:38 PM, <[1]sf...@users.sourceforge.net> wrote:
Ben Hutchings:
> When you say the $AUFS_VERSION variable, do you mean the macro
> definition in /usr/include/linux/aufs_type.h? Â This is built from the
> kernel source but can again be a different version from the installed
> kernel (it's in the linux-libc-dev package).
In that mail, we were talking about /etc/default/aufs which defines the
shell variable named AUFS_VERSION.
When you build and install aufs-util, the internal command c2sh converts
the C macro AUFS_VERSION defined in aufs_type.h into a shell variable in
a shell script and installs it as /etc/default.aufs.
So $AUFS_VERSION and C macro AUFS_VERSION are equivalent from my point
of view. Both represent the version of aufs module.
On the other hand, aufs-util.git has its own versioning as git
branch. It is defined in aufs-util.git/au_util.h.
> So, which to believe? Â All of them, as they refer to different parts of
> aufs...
No.
$AUFS_VERSION in /etc/default/aufs are generated from C macro
AUFS_VERSION in aufs_type.h.
J. R. Okajima
--------------------------------------------------------------------------
----
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
[2]http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.c
lktrk
--
Jacob Burkamper
CIPAFilter Development
Email:Â [3]jac...@cipafilter.com
----------------------
CIPAFilter Beta Program
Email: [4]b...@cipafilter.com
Web:Â Â Â Â Â [5]http://www.cipafilter.com
References
1. mailto:sf...@users.sourceforge.net
2.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
3. mailto:jac...@cipafilter.com
4. mailto:b...@cipafilter.com
5. http://www.cipafilter.com/
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
