
Before examining the hexadecimal and identifying differences between the ReFS, NTFS and FAT file systems, it was useful to get basic file system information by running file system commands. This was done inside the Windows Server virtual machine, by running "fsutil" commands. The output of these commands is in the table below and is very useful in identifying the number of bytes per sector in each file system.
The output is also interesting as it displays the capabilities of each file system. For example, it identifies that both ReFS and NTFS support Sparse Files, but FAT does not. From this table it is clear to see that ReFS doesn't support as many features as NTFS. This is by design, as other applications have taken some of these tasks. For example, BitLocker, through encrypting entire drives, is now used in place of the encryption that NTFS supports (Lucas, 2013) and other features can be satisfied by interfacing with ReFS through the API set.
Each of the drives tested were 5GB. Having created a 1.5TB
ReFS drive, it can be confirmed that the output below was the same for the 5GB
and 1.5TB drive.
|
Command: fsutil fsinfo sectorinfo |
ReFS |
NTFS |
FAT |
|
LogicalBytesPerSector |
512 |
512 |
512 |
|
PhysicalBytesPerSectorForAtomicity
|
512 |
512 |
512 |
|
PhysicalBytesPerSectorForPerformance |
512 |
512 |
512 |
|
FileSystemEffectivePhysicalBytesPerSectorForAtomicity |
512 |
512 |
512 |
|
Command: fsutil fsinfo volumeinfo |
ReFS |
NTFS |
FAT |
|
Volume Name |
ReFS Drive |
NTFS Drive |
FAT32 DRIVE |
|
Volume Serial Number |
0xc4551c04 |
0x1859ec57 |
0x125e59e5 |
|
Max Component Length |
255 |
255 |
255 |
|
File System Name |
ReFS |
NTFS |
FAT32 |
|
Is ReadWrite |
✔ |
✔ |
✔ |
|
Supports
Case-sensitive filename |
✔ |
✔ |
|
|
Preserves Case of
filenames |
✔ |
✔ |
✔ |
|
Supports Unicode in
filenames |
✔ |
✔ |
✔ |
|
Preserves &
Enforces ACL's |
✔ |
✔ |
|
|
Supports file-based
Compression |
|
✔ |
|
|
Supports Disk Quotas |
|
✔ |
|
|
Supports Sparse files |
✔ |
✔ |
|
|
Supports Reparse Points |
✔ |
✔ |
|
|
Supports Object
Identifiers |
|
✔ |
|
|
Supports Encrypted
File System |
|
✔ |
|
|
Supports Named
Streams |
|
✔ |
|
|
Supports Transactions |
|
✔ |
|
|
Supports Hard Links |
|
✔ |
|
|
Supports Extended
Attributes |
|
✔ |
|
|
Supports Open By FileID |
✔ |
✔ |
|
|
Supports USN Journal |
✔ |
✔ |
|
Having created the test disks and ran file system commands on them using Windows, the next step was to use The Sleuth Kit (TSK) to find out as much information as possible for each of the file systems. One very useful command and the one used here is "fsstat", which is used to disclose crucial information of a file system. This command displays vital information such as the size of MFT entries, the cluster size and the volume type.
When ran, this command displayed everything as expected for NTFS and FAT. But for ReFS, this message was output to screen: "Cannot determine file system type". This suggests that TSK doesn't yet support ReFS.
Below on the left is some of the NTFS output and on the right is some of the FAT32 output.
|
FAT32 |
|
FILE SYSTEM INFORMATION |
|
Next Free Sector (FS Info):
24584 |
|
Free Sector Count (FS
Info): 10455032 |
|
Sectors before file system:
2048 |
|
File
System Layout (in sectors) |
|
Total Range: 0 - 10479615 |
|
* Reserved: 0 - 4153 |
|
** Boot Sector: 0 |
|
** FS Info Sector: 1 |
|
** Backup Boot Sector: 6 |
|
* FAT 0: 4154 - 14364 |
|
* FAT 1: 14365 - 24575 |
|
* Data Area: 24576 -
10479615 |
|
** Cluster Area: 24576 -
10479615 |
|
*** Root Directory: 24576 -
24583 |
|
NTFS |
|
METADATA INFORMATION |
|
First Cluster
of MFT Mirror: 2 |
|
Size of MFT
Entries: 1024 bytes |
|
Size of Index
Records: 4096 bytes |
|
Range: 0 -
255 |
|
Root
Directory: 5 |
|
CONTENT INFORMATION |
|
Sector Size:
512 |
|
Cluster Size:
4096 |
|
Total Cluster
Range: 0 - 1309950 |
|
Total Sector
Range: 0 - 10479614 |