Metadata Block ChangesPermissions ChangeFolder DeletionsRenaming FolderCopying FolderAdding ContentCompressing Folder

Metadata Block Changes After Folder Modifications

The table below shows how the metadata blocks are populated differently after the different actions are applied to the folder. Items with a * next to them, will be discussed in their respective sections due to changes from the metadata structure.

The colour coded table shows the folder name at the respective metadata block.

Metadata Block Offset

Starting Bytes

Original hellofolder

Permissions Change

Deleted

Shift & Delete

Renamed

Copy Folder

.txt Added to Folder

.doc Added to Folder

.exe Added to Folder

0x0750000

94 01

 

 

hellofolder

hellofolder

importantinformation

hellofolder

hellofolder

hellofolder

hellofolder

0x0754000

95 01

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder*

hellofolder

hellofolder

hellofolder

0x0758000

96 01

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

0x075C000

97 01

New folder

New folder

New folder

New folder

New folder

New folder

New folder

New folder

New folder

0x07B0000

AC 01

New folder

hellofolder

 

New folder

importantinformation

hellofolder

hellofolder

hellofolder

hellofolder

0x07B4000

AD 01

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

hellofolder

0x07B8000

AE 01

 

hellofolder

 

 

 

 

hellofolder

hellofolder

hellofolder

0x07BC000

AF 01

 

hellofolder

 

 

 

 

 

hellofolder

hellofolder

0x07C0000

B0 01

 

hellofolder

hellofolder*

 

 

repeatthatplease

 

hellofolder

hellofolder

 

 

 

 

 

 

 

 

 

 



Looking at the table above, it is interesting to note that throughout the modifications, one "New folder" entry and one "hellofolder" entry always stays in the same position. Depending on the behaviour of ReFS when large amounts of data are added, this could be useful to a forensic examiner to prove that a file or folder previously existed on a ReFS system.

Using the table above it looks like when the permissions have been changed, all the original instances of "hellofolder" were copied before the modifications were made, as there are three more metadata entries for it (which was the original number of "hellofolder" entries in the first place). It would be expected for this to be the same behaviour when the folder gets renamed, but it doesn't appear to be the case.

Another question arising from the number of metadata entries, is that when files are added why are there two more entries for .exe and .doc files than there are .txt file.

The table above only displays the folder name at the respective block. One common change between the metadata blocks (excluding the first two bytes) was the eighth byte, the table below shows this.

Offset

Value

 

Original

hellofolder

Perms Change

Deleted

Shift & Del

Renamed

Copy

.txt

.doc

.exe

0x0750008

0A

0A

15

15

15

15

16

16

15

0x0754008

0D

0D

0D

15

0D

15

0D

0D

16

0x0758008

0E

0E

0E

0E

0E

0E

0E

0E

0E

0x075C008

0C

0C

0C

0C

0C

0C

0C

0C

0C

0x07B0008

0C

15

15

0C

15

15

15

15

15

0x07B4008

0D

0D

0D

0D

0D

0D

0D

0D

0D

0x07B8008

 

15

 

 

 

 

16

15

15

0x07BC008

 

16

 

 

 

 

 

15

15

0x07C0008

 

16

 

 

 

15

 

16

15

 

The eighth byte of the metadata block changes to 15 quite often. This could be signifying that the block may be overwritten.