Re: opening file for reading updates modification time!
Re: opening file for reading updates modification time!
- Subject: Re: opening file for reading updates modification time!
- From: Mark Day <email@hidden>
- Date: Thu, 06 Feb 2014 09:39:47 -0800
I'll bet it's related to checksums. DMG files can have a checksum, used to detect whether the DMG contents were corrupted in transport. If I remember correctly, the Disk Images subsystem will verify the checksum the first time you use that image, and then mark it (with an extended attribute?) so that it won't have to verify the checksum again. I'll bet the modification is it marking the image as being known to match its checksum.
-Mark
On Feb 6, 2014, at 9:30 AM, Alan Snyder <email@hidden> wrote:
> I’ve run into an odd situation involving specific files in two specific encrypted sparse disk images. I open two files for reading and then close them. The file that is closed first has its modification time updated as if it had been modified. The behavior is repeatable if I start with (a copy of) the same DMG files. However, the problem only occurs once in the mounted file system. I’m guessing there is some kind of corruption in the disk image files that is resolved when the files are closed.
>
> Please tell me this problem was discovered and fixed a while ago… :-)
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Filesystem-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden