Sorry, forgot to reply that I did also install the aufs-utils package. It
   shows version in /etc/default/aufs as "3.x-rcN-20111205". This seems very
   old to me, it is the supplied package from Ubuntu. Do you think this old
   aufs-utils is part of the problem?

   On Tue, Jul 29, 2014 at 1:30 PM, Jacob Burkamper <[1]jac...@cipafilter.com>
   wrote:

     Ok. Just to make sure, the steps should be like this. Is it ok?
     auplink / flush
     mount -o remount,udba=notify /
     mount -o remount,rw /ro
     ... changes on /ro ...
     mount -o remount,ro /ro
     mount -o remount,udba=reval /
     auplink / list

   That is not the procedure I was using. The procedure I was using looks like
   this:
   mount -o remount,udba=notify /
   mount -o remount,rw /ro
   ...changes to /ro
   auplink / flush
   mount -o remount,ro /ro
   mount -o remount,udba=reval /
   I was not calling the 'auplink / list' call. What should I expect for output
   from there? I will change the order to match yours, test, and reply with the
   results.
   We do not specify any xino= mount option, but we do use trunc_xino. My
   testing environment (but not the production unit) does have the new patch
   you supplied against tmpfs. We were previously having issues with the tmpfs
   /rw being filled, even with trunc_xino option. The tmpfs-ibr.patch does seem
   to  have  alleviated  the problems, but I have not yet put it onto our
   production unit, only the testing one.

     I'd suggest you to try fsck in the beginning, ie. before mounting your
     /dev/sda1. If it passes without error, then mount it as readonly, mount
     aufs, and then try fsck once more. Obviously it should not have
     errors. But it might be better to confirm it in every step.
     Also it might be better to try fsck
     - after chroot/switch_root
     - after bind-mount /usr/configdir, vardir
     - after the completion of all boot and init procedures

   I will add some additional fsck checks in order to test and attempt to
   better locate when the errors occur. However, I do not like the idea of
   leaving the fsck in different places. I don't like the idea of fsck running
   on its own without being attended in production.Â
   I hope to have more information soon.

   On Mon, Jul 28, 2014 at 8:13 PM, <[2]sf...@users.sourceforge.net> wrote:

     Hello Jacob,
     Jacob Burkamper:

   > Under normal operation, the ext2 filesystem is indeed mounted read-only.
   > When changes need to be made, a script is used which calls mount -o
   > remount,rw /ro. In addition, we call mount -o remount,udba=notify /. Once
   > all of the writes have been made, we then change the /ro mountpoint back
   to
   > read-only. When we do this, we call auplink first, followed by a sync
   call,
   > then the remount,ro call. Once we have set the ext2 back to ro, we then
   > mount --remount,udba=reval /.

     Ok. Just to make sure, the steps should be like this. Is it ok?
     auplink / flush
     mount -o remount,udba=notify /
     mount -o remount,rw /ro
     ... changes on /ro ...
     mount -o remount,ro /ro
     mount -o remount,udba=reval /
     auplink / list
     During these operation, I'd confirm that you have never met any errors.
     Did you install aufs-util on your system? If so, what is the version?
     And did you specify "xino=" aufs mount option?

   >  The system that this takes place on is remote. When we make version
   changes
   > to our system, we pull those changes using a script which runs an rsync
   > directly to the /ro mount. before this firmware-upgrade script runs, it
   > ensures the ext2 is mounted ro, and then runs an fsck on it. When this
   fsck
   > runs, it almost always reports many errors. I will paste some of them into

     Â  Â  Â  Â  :::
     I'd suggest you to try fsck in the beginning, ie. before mounting your
     /dev/sda1. If it passes without error, then mount it as readonly, mount
     aufs, and then try fsck once more. Obviously it should not have
     errors. But it might be better to confirm it in every step.
     Also it might be better to try fsck
     - after chroot/switch_root
     - after bind-mount /usr/configdir, vardir
     - after the completion of all boot and init procedures
     J. R. Okajima

   --
   Jacob Burkamper
   CIPAFilter Development
   Email:Â  [3]jac...@cipafilter.com
   ----------------------
   CIPAFilter Beta Program
   Email: [4]b...@cipafilter.com
   Web:Â Â Â Â Â  [5]http://www.cipafilter.com

   --
   Jacob Burkamper
   CIPAFilter Development
   Email:Â  [6]jac...@cipafilter.com
   ----------------------
   CIPAFilter Beta Program
   Email: [7]b...@cipafilter.com
   Web:Â Â Â Â Â  [8]http://www.cipafilter.com

References

   1. mailto:jac...@cipafilter.com
   2. mailto:sf...@users.sourceforge.net
   3. mailto:jac...@cipafilter.com
   4. mailto:b...@cipafilter.com
   5. http://www.cipafilter.com/
   6. mailto:jac...@cipafilter.com
   7. mailto:b...@cipafilter.com
   8. 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

Reply via email to