Robert Wotzlaw: > The question is, why AUFS reacts during the remount of the ext3 file > system and produce the kernel message?
Aufs doesn't react the remouting ext3. The script remounts aufs as if it were ext3 (and failed). Your /proc/mounts contains both of these lines? /dev/sda11 /tmp/jailcache.ro.var ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0 varonaufs /tmp/jail/var aufs rw,relatime,si=89f694af8e016535 0 0 And the script runs # mount -o remount,brabra /tmp/jailcache.ro.var # mount -o remount,brabra /tmp/jail/var doesn't it? In the chrooted environment, both are aufs, right? > In my opinion, the kernel message isn't caused by the script journal- > commit. Again, the script does what it shall. The script remounts > only file systems with the type ext3 and ext4. That answers your > first suggestion. How did you confirm it? > - Feature request concerning a list function for aubusy. Could I > convince you to provide a list function for aubusy. Something that > mount does if we invoke mount without any option. The pure mount > command shows all current mounts. The tool aubusy should show all > current union and their branches like the following example: It may be a good feature, but I don't think the aubusy script should have such feature. If such feature is implemented, it will be anoter script. But you may want to try the aufs module parameter 'brs'. Try setting it to 0. 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
