[email protected] wrote:
>>> And your log shows
>>>> [  241.753731] EXT2-fs warning: mounting unchecked fs, running e2fsck is 
>>>> recommended
>>> I am afraid your "mount -o remount,ro /ro" didn't work.
>>> can you check it by /proc/mounts or something?
>> But remount read-only doesn't output anything to dmesg, does it? This 
>> message was from remount read-write.
> 
> I am unsure whether remount read-only leave something in dmesg or not.
> Anyway try inserting "fgrep -w /ro /proc/mounts" or something to your
> script. It won't hurt anything.
> And if the message came from remount read-write, was it correct?
> I thought your /dev/hda1 was always checked and cleaned at system boot
> time.


It used to be when mounted as ext3. With ext2 I had to do this manually, 
maybe I was in hurry and forgot, but in my next email it was definitely 
clean.


>> Since I'm doing all the testing in a virtual machine, maybe I will 
>> upload a vmware or qemu image with freshly installed system with this 
>> configuration, so you can play with it directly if you're interested?
> 
> Ok, send me the image with instructions in detail. I don't have much
> experiences about qemu.


When it's ready I will send all info in a separate email.


> And, as you might know, your version is very very old.
> Aufs1 is obsoleted and not maintained now. Additionally, your problem
> doesn't look aufs's to me, currently.


Interesting, if not aufs then what?

Firstly, I can prove it this way: There are two identical copies of root 
partition. Both are mounted read-only in initramfs. One of them becomes 
a branch of aufs. On shutdown, I rsync changes to both copies and only 
the one under control of aufs gets dirty.

Secondly, it doesn't happen when both aufs and unionfs are installed and 
I replace mount -t aufs with mount -t unionfs.


> If the problem is a bug of aufs, I will fix it for aufs2 first and may
> NOT fix for aufs1.


Yes, I understand.


-- 
bl4

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

Reply via email to