12 commits

Author	SHA1	Message	Date
Hermès Bélusca-Maïto	8c0c90112e	[FASTFAT] Don't mess my debug log when partition SysType is printed! (when invalid chars are printed)	2018-10-13 19:57:24 +02:00
Pierre Schweitzer	4bb1baa860	[FASTFAT] Finally drop the TAG_VFAT allocation tag	2018-08-21 08:36:51 +02:00
Pierre Schweitzer	047479e0a2	[FASTFAT] Don't leak statistics on dismount	2018-08-18 19:03:30 +02:00
Pierre Schweitzer	639e6d635f	[FASTFAT] Reduce the usage of the generic allocation tag ... And use tag compatible with MS FastFAT, to use debug with WinDBG	2018-08-18 19:03:30 +02:00
Pierre Schweitzer	6aa4beeefb	[FASTFAT] Use the FastFAT mechanism for counting clusters already implemented ... This allows us having more accurate statistics regarding available clusters count. Even though FastFAT and chkdsk still don't agree! CORE-3877	2018-06-09 18:23:07 +02:00
Pierre Schweitzer	04640f9264	[FASTFAT] Save the FSINFO sector location	2018-06-09 12:11:43 +02:00
Pierre Schweitzer	7c01587680	[FASTFAT] Completely rewrite support for dirty volumes. ... Until now, our support for dirty volumes was totally broken to a point where, on FAT32 volume, the dirty couldn't even be written nor read from the disk. This commit totally rewrites its handling, for both FAT16 and FAT32 so that it's now fully functionnal. Furthermore, it also gets totally compatible with our vfatlib, and thus, autochk. Now, on mount, FastFAT will check if the volume is dirty or not, and autochk will be able to ask for a repair if dirty. vfatlib will repair the volume and remove the dirty bit. So that, on next reboot, the volume will be mounted clean. As a reminder, the dirty bit is set immediately after mounting the volume, so that, if you crash or have a powercut, autochk will always attempt to repair your volume (with more or less, that's FAT!). If you want to experience without breaking your FAT volume, just boot, open a cmd prompt and type: fsutil dirty set c: and reboot! CORE-13758 CORE-13760 CORE-13759	2018-05-18 23:05:05 +02:00
Pierre Schweitzer	efa75dd5b2	[FASTFAT] Allow locking system volume on boot. ... This is a hack, and totally not the default behavior. But it will allow autochk locking the boot volume in order to verify it on boot, in case it would have been improperly dismounted. CORE-13759	2018-05-18 23:05:05 +02:00
Pierre Schweitzer	d37280efaa	[FASTFAT] Deny dismounting system volume or a volume with a pagefile	2018-05-16 21:45:35 +02:00
Pierre Schweitzer	64bc96558e	[FASTFAT] While closing FCBs on dismount, release from tail to head and not the contrary. ... It fixes assertion failure in vfatDestroyFCB() where we would have release parent before child. This is still not perfect, but less bug prone... With this commits (and ENABLE_SWAPOUT defined), ReactOS seems to unmount FAT volumes quite nice! :-) (Tried with fsutil volume dismount X:)	2017-12-17 18:24:01 +01:00
Pierre Schweitzer	27773dbb3f	[FASTFAT] When not able to lock a volume due to open handles, print open handles	2017-12-17 18:24:01 +01:00
Colin Finck	c2c66aff7d	Git conversion: Make reactos the root directory, move rosapps, rostests, wallpapers into modules, and delete rossubsys.	2017-10-03 07:45:34 +00:00

Renamed from reactos/drivers/filesystems/fastfat/fsctl.c (Browse further)