--- On Fri, 2/18/11, sf...@users.sourceforge.net <sf...@users.sourceforge.net>
wrote:
> From: sf...@users.sourceforge.net <sf...@users.sourceforge.net>
> Subject: Re: Umounting the boot device at shutdown
> To: "Yioryos Asprobounitis" <mavrot...@yahoo.com>
> Cc: aufs-users@lists.sourceforge.net
> Date: Friday, February 18, 2011, 8:35 AM
>
> Hello Yioryos,
>
> Yioryos Asprobounitis:
> > In the puppylinux (aufs2.1-31 or 35) shutdown process,
> the journal of the boot device (if it has an ext3 file
> system) stays open, or at least some files leave behind the
> "open flag" bit. This triggers a boot device journal
> recovery in every boot. The file system per se is clean
> however. Is just the journal that is not properly closed
> because of some open files.
>
> Have you tried the instrunction in the aufs manual?
>
> (from the aufs manual)
> ----------------------------------------------------------------------
> When your aufs is the root directory of your system, and
> your system
> tells you some of the filesystem were not unmounted
> cleanly, try these
> procedure when you shutdown your system.
> .nf
> # mount -no remount,ro /
> # for i in $writable_branches
> # do mount -no remount,ro $i
> # done
> .fi
> If your xino file is on a hard drive, you also need to
> specify
> `noxino' option or `xino=/your/tmpfs/xino' at remounting
> root
> directory.
> ----------------------------------------------------------------------
>
> And you should install aufs2-util.git.
Yes I do have aufs2.1-utils compiled against the kernel and hopefully I'll gets
some time to RTFM :-)
In the mean time tried to mount xino in tmp like that:
`busybox mount -no remount,xino=/tmp/xino -t aufs / /'
but did not solve the issue.
Instead I get this warning now:
`Unnotified UDBA or repeatedly renamed dir, b1 squashfs, ld-linux.so.2, hi
9856, i11'
Any thoughts before I do my reading?
Thx
>
>
> J. R. Okajima
>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
