Ga tan Harter: > However, I would switch to a "snapshot" mode, where only the files differen= > t from the basic image would be monitored. > So I could still reduce the number of shared files to follow, and the memor= > y footprint on the server. > = > > server# mount -t aufs -o br:/mnt/linux_basic_image_read_only=3Dro,/m= > nt/board_1_files=3Dro,/mnt/image_differences_for_user_1=3Drw /export/im= > age_board_1
I don't understand again. How can you reduce the number of monitored files? Hmm, you might misunderstand that "=rw" makes setting inotify. If so, you are wrong. Aufs sets inotify even if the branch is "=ro" since the files on the branch can be changed. You might want to specify "=rr" I wonder. And your stacking order is correct? Why do you put the writable branch on the last. It means the "bottom" of stacking. Are you sure? > In my case, the mounts should only last a few hours, when the nodes are use= > d, the image_difference will be quite limited and can then be discarded whe= > n the reservation is over. ?? Are you talking about the free space of /image_differences_for_user_1? I am afraid you cannot use the bottom writable branch in many operations. J. R. Okajima ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
