On 05/17/2012 10:10 AM, Tomas M wrote: >> Yes, the xino is stored on the /cow. I think other things >> are probably using /cow as well since *any* modified files >> are automatically put on the /cow. > > Actually, if you remounted the aufs root / as ro, then nothing else > has write access to your /cow any longer EXPECT the aufs (due to > xino). > > So please first try to mount aufs with the xino option, to ensure xino > file is NOT on your /cow > > you can do it this way: > mkdir /memory > mount -t tmpfs tmpfs /memory > mount -t aufs -o xino=/memory/xino ...etc (I don't remember current > aufs mount options) > // add branches here etc > > Then when you remount, do as you did: > mount -o remount,ro / > #set all aufs branches as readonly (I don't remember command for that) > #mount -o remount,ro /cow
Ok, I can try that. >> Maybe after setting / >> to (ro), I should attempt to disable the xino file somehow? > > nope, that's not possible. You must put the xino file to another > filesystem (eg to memory, as explained above) during you INITIALIZE > your aufs root (eg at the boot time) Is there any downside to having the xino file non-persistent, or any way to mitigate that if so? > >> The /cow is definitely in use... > > use 'lsof' command to see what files are opened then... Thanks for the suggestions! Ben -- Ben Greear <gree...@candelatech.com> Candela Technologies Inc http://www.candelatech.com ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
