Hi, "Fernando A. P. Gomes": > > > What did your rc script do? > > Nothing anormal, it's in attach.
I will wait for your next mail. :-) > > Are there something about mounting, module loading/unloading, chroot(2) > > and operating around /var/log/squid? > > Aufs module is builtin I can't loading/unloading. The only operation > around /var/log/squid is /etc/init.d/squid start (open log files > in /var/log/squid). How about another modules? I want to make sure that all necessary modules are loaded correctly, and there is no kernel messages. > What you mean with chroot? Is I do a chroot and a pivot_root. What I want to know is whether you did chroot(2) in your rc script, or not. Do you mean that you did both? > > And after your rc script, is the aufs entry in /proc/mounts correct? > > Yes Will you show me your /proc/mounts? > > Is /cdrom/tmpdir/3 working correctly, how about ls(1) to it? Which type > > is its filesystem? > > It's a cramfs filesystem mountend looped and unionctl to aufs. > > I realize that the bug is in more locations that de /var/log, in /etc I've > the > same problem with some files ( ex: /etc/wvdial.conf ). Yes, I read your another mails. Your aufs seems to handling ghosts of inodes. They seems to be gone. But aufs believes they are still existing, and shows you almost NULL data or garbages. So you can ls(1) to your branches directly, and it succeeded, right? Then, how about ls to your aufs after direct ls? Junjiro Okajima ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
