Re: Modification date won't update
In my opinion that might be confusing as nothing changed on the topmost branch. Maybe just update the timestamp on the aufs mount on and not touch the topmost branch? Anyway, now that I know the logic I'll keep an eye out for this :) I don't expect it to happen often but might be helpful for others to know this behavior. Daniel On Wed, Jan 21, 2015 at 3:33 PM, [1]sf...@users.sourceforge.net wrote: DaneeL: I just changed to command to /media/hdd3=rw:/media/hdd1=rw swapping the hdd1 and hdd3 and it seems to be working. Thank you again for the help! My pleasure. But I am wondering, when a multiple writable branches exit, and aufs choose the lower one, then aufs should update the timestamps of the parent dir on the topmost branch. In other words, the behaviour in front of you is due to mfs option (most-free-space). And if you use another path (other than _Series/CSI), you will meet the same problem. J. R. Okajima References 1. mailto:sf...@users.sourceforge.net -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet
Re: Modification date won't update
Thanks for the quick reply! I just changed to command to /media/hdd3=rw:/media/hdd1=rw swapping the hdd1 and hdd3 and it seems to be working. Thank you again for the help! Daniel DaneeL - [1]danee...@gmail.com To boldly go where no one has gone before ... On Wed, Jan 21, 2015 at 3:22 PM, [2]sf...@users.sourceforge.net wrote: DaneeL: Example: Date will not update -- xbmc@doboz:~$ touch /media/share/_Series/CSI/testfile xbmc@doboz:~$ ls -l /media/hdd1/_Series/ | grep CSI drwxrwxr-x 2 xbmc xbmc 4096 Jan 5 12:02 CSI xbmc@doboz:~$ ls -l /media/hdd3/_Series/ | grep CSI drwxrwxr-x 2 xbmc xbmc 4096 Jan 21 15:02 CSI xbmc@doboz:~$ ls -l /media/share/_Series/ | grep CSI drwxrwxr-x 2 xbmc xbmc 4096 Jan 5 12:02 CSI Ok, by this touch /media/hdd3/_Series is updated, but /media/share/_Series is not. It is because your branches are /media/hdd1=rw:/media/hdd3=rw. The attributes of an aufs dir inherit the first same-named dir in the branches. In this case, you have /media/hdd1/_Series, /media/share/_Series inherits the /media/hdd1/_Series's timestamps instead of /media/hdd3/_Series. J. R. Okajima References 1. mailto:danee...@gmail.com 2. mailto:sf...@users.sourceforge.net -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet
Re: Modification date won't update
DaneeL: I just changed to command to /media/hdd3=rw:/media/hdd1=rw swapping the hdd1 and hdd3 and it seems to be working. Thank you again for the help! My pleasure. But I am wondering, when a multiple writable branches exit, and aufs choose the lower one, then aufs should update the timestamps of the parent dir on the topmost branch. In other words, the behaviour in front of you is due to mfs option (most-free-space). And if you use another path (other than _Series/CSI), you will meet the same problem. J. R. Okajima -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet
Re: Modification date won't update
Hello Daniel, DaneeL: I noticed lately that the modification time does not change if I copy new files into some directories. If a directory exits on both hdd1 and hdd3 and the files is copied into hdd3 - date does not change in aufs mount but changes on hdd3. If a directory exists on only hdd3 the directory modify date changes on aufs as well. Would you describe these more speicifically? Probably the reproducible command sequence is better. - how and what did you copy? from where to where? - how did you check the mtime? J. R. Okajima -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet
Re: Modification date won't update
DaneeL: Example: Date will not update -- xbmc@doboz:~$ touch /media/share/_Series/CSI/testfile xbmc@doboz:~$ ls -l /media/hdd1/_Series/ | grep CSI drwxrwxr-x 2 xbmc xbmc 4096 Jan 5 12:02 CSI xbmc@doboz:~$ ls -l /media/hdd3/_Series/ | grep CSI drwxrwxr-x 2 xbmc xbmc 4096 Jan 21 15:02 CSI xbmc@doboz:~$ ls -l /media/share/_Series/ | grep CSI drwxrwxr-x 2 xbmc xbmc 4096 Jan 5 12:02 CSI Ok, by this touch /media/hdd3/_Series is updated, but /media/share/_Series is not. It is because your branches are /media/hdd1=rw:/media/hdd3=rw. The attributes of an aufs dir inherit the first same-named dir in the branches. In this case, you have /media/hdd1/_Series, /media/share/_Series inherits the /media/hdd1/_Series's timestamps instead of /media/hdd3/_Series. J. R. Okajima -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet
