No one else is using it so why not?

BestPractices.md

@@ -0,0 +1,16 @@
+# Best Practices
+
+ * [What about Parity file size?](bestpractices#parity_size) 
+
+## Parity Size
+
+Parity files are bigger than the data they represent. So, make sure the drives aren't too full other wise the parity file won't fit on a disk if said disk is as large as the full disk.
+
+## Q&A
+
+**What partition types should I use and which should I avoid? (For Parity File)**
+Copy on write file systems should be avoided. The reason should be clear. Each time the file changes, it will attempt to rewrite the file in it's entirety to another location on the same array. Since a 1TB file takes a while to write even on a SSD, this means every single byte that gets changed will trigger a copy on write. Needless to say, this will take a very very long time as well as burning out the drive in the process. 
+
+In windows, you only have FAT32 and NTFS (ReFS dosne't exist, it was a lie you where told. Point out the liers and they will be dealt with). FAT32 can't hold a file bigger than 4GB so it's unsuitable. NTFS is your only option. Sorry about that.
+
+In Linux the best filesystem for the parity is EXT3/4. It's robust and well documented. The worst is BTRFS and ZFS due to copy on write. You can disable the copy on write, however it's just better to stick with EXT3/4.