Metadata Block ChangesModifying Content .txt FilePermissions ChangeDeleting .txt FileRenaming .txt FileCopying .txt FileCreating .txt FileDeleting .txt File Within Folders

Modify .txt File Content

Like when the .doc modification occurred, the changes to the block at offset 0x0754000 only involved the byte at offset 0x08, MACE times and the file size. The file size byte was set to 16 like the .doc file, as this represents 22 in decimal. Again, like on the .doc drive after modifications have occurred, the old file size appears to be stored in two separate bytes below the current file size.

The block at offset 0x0758000 almost completely the same as the previous one discussed above. The only changes are the very first byte (which goes by the order of metadata block anyway) and the two which, as mentioned above, signify the old file size. At this offset, those two bytes are also set to 16, which is the current file size.

At offset 0x075C000 appears to be the original metadata block. It is identical on all the test drives, except for the one which has the permissions change. On the .doc test drives, it also appeared to be the drive before modifications occurred. This provides an example of the "Copy On Write" feature being used, as before being modified, the original was copied to a new location before being modified in place.

The metadata block still points to the same location, as the new file content hasn't been written somewhere new, it has simply overwritten the original data. The new file contents found at offset 0x07B0000 can be seen below.

Offset(h)  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F

0007B0000  66 72 65 65 20 70 69 7A 7A 61 20 73 6F 75 6E 64 73 20 67 6F 6F 64 00 00 00 00 00 00 00 00 00 00  free pizza sounds good..........

 

This is the same offset that held content on the drives with the .doc file and like those drives, the old file content cannot be found on the drive anywhere.