Hello Robert,
Robert Wotzlaw:
> nearly two years ago I send you the script bldchraufs. Since
> that time
> many things have changed. This concerns the Linux kernel - now the
> kernel is dressed with a three as major number - and the current
> Debian
> distribution of the testing domain is called Wheezy. All these
:::
Yes, I remember that I put your product under
aufs2-util.git/sample/auroot.
> The following kernel message is the output that was produced during
> the run of the above mentioned script:
>
> [ 99.881160] aufs: module is from the staging directory, the
> quality
> is unknown, you have been warned.
I guess this message is produced by debian.
> [ 99.884200] aufs 2.1-standalone.tree-3.0-rcN-20110711
Oh, no.
This version is once labeled "don't use".
- for linux-3.x, aufs2 is called "don't use".
- aufs-2.1 is not supported now.
- use aufs3 for linux-3.x.
- if debian people made their own version of aufs, I cannot support it.
> [ 99.984955] aufs test_add:262:mount[2493]: uid/gid/perm
> /tmp/jailcache.ro.usrlocal 0/50/02775, 0/0/0755
> [ 100.071844] aufs test_add:262:mount[2499]: uid/gid/perm
> /tmp/jailcache.ro.home 1000/1000/0755, 0/0/0755
Aufs produces this message as a warning when the (uid,gid,perm) of the
newly add branch don't match the existing branch. If you are sure that
there is no problem, then you can stop the messages by specifying the
aufs mount option "quiet".
> The second kernel message was written during the GNOME Desktop
> session log in:
>
> [ 129.434722] aufs au_opts_parse:1039:mount[3397]: unknown option
> errors=remount-ro
:::
I guess you forgot to install aufs2-util (or aufs-util) which contains the
mount helper /sbin/mount.aufs. Or you passed the incorrect mount options
to aufs.
> [ 3942.141298] WARNING: at /build/buildd-linux-2.6_3.0.0-3-
> amd64-9ClimQ/
> linux-2.6-3.0.0/debian/build/source_amd64_none/fs/
> aufs/
> plink.c:450 au_plink_put+0x39/0x6b [aufs]()
> [ 3942.141531] Hardware name: M720-US3
> [ 3942.141588] pseudo-link is not flushed
The message "pseudo-link is not flushed" means that you may lost some
changes which are left in the upper writable branch.
I guess this warning will be disappear once you install aufs-util.
> 2. Chroot environment removal and forgotten daemons
>
> Another problem I have is the removal of the on AUFS based chroot
> environment. A removal of the chroot environment is only successful
> if no process like a daemon has access to one of the under AUFS
> mounted
> file systems. The problem is the user can't know which daemons or
> background processes he triggers if he executes a command in the
> chroot
> environment.
The aubusy script in aufs-util can tell you the busy inode and the
command which uses it.
> 3. NFS in an on AUFS based chroot environment
:::
> server. Now my questions, is the above statement correct? Do I
> need the
> special kernel module to run the NFS kernel server under AUFS or
> is the
> statement obsolete?
Unfortunately I have never tried NFSD in userspace.
I can just only say,
- aufs supports NFS-exporting
- aufs supports NFS branch.
If the user-space NFS behaves like kernel-space NFS, it should succeed.
J. R. Okajima
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
