T o n g:
> Ok, hope I'm reporting a real bug this time -- aubrsync need to use real
> path:
I am afraid you didn't install aufs2-util correctly.
Confirm the latest aufs2-util is installed first, particularly
/sbin/mount.aufs and /etc/default/aufs.
----------------------------------------------------------------------
> Subject: Detailed aufs mount info
:::
> I used to be able to get detailed aufs mount info in "mount -v" or just
> "mount" w/o any parameters, I mean those xino=...,br:... info.
>
> Now, "mount" just reports:
>
> type aufs (rw,relatime,si=a5a291796916262e)
>
> and nothing more, no brach & xino info any more.
>
> Is this a compile-time feature? Can I control showing those info at run
> time?
If you installed aufs2-util correctly, then /etc/mtab is maintained.
Also you should read the aufs manual too.
(from the aufs manual)
----------------------------------------------------------------------
.SH Module Parameters
.TP
.B brs=1 | 0
Specifies to use the branch path data file under sysfs or not.
If the number of your branches is large or their path is long
and you meet the limitation of mount(8) ro /etc/mtab, you need to
enable CONFIG_SYSFS and set aufs module parameter brs=1.
When this parameter is set as 1, aufs does not show `br:' (or dirs=)
mount option through /proc/mounts (and /etc/mtab). So you can
keep yourself from the page limitation of
mount(8) or /etc/mtab.
Aufs shows branch paths through <sysfs>/fs/aufs/si_XXX/brNNN.
Actually the file under sysfs has also a size limitation, but I don't
think it is harmful.
There is one more side effect in setting 1 to this parameter.
If you rename your branch, the branch path written in /etc/mtab will be
obsoleted and the future remount will meet some error due to the
unmatched parameters (Remember that mount(8) may take the options from
/etc/mtab and pass them to the systemcall).
If you set 1, /etc/mtab will not hold the branch path and you will not
meet such trouble. On the other hand, the entries for the
branch path under sysfs are generated dynamically. So it must not be obsoleted.
But I don't think users want to rename branches so often.
If CONFIG_SYSFS is disable, this parameter is always set to 0.
----------------------------------------------------------------------
J. R. Okajima
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
