| bigbiff bigbiff | 9c75405 | 2013-01-09 09:09:08 -0500 | [diff] [blame^] | 1 | dosfsck, version 1 |
| 2 | ================== |
| 3 | |
| 4 | WARNING: This is ALPHA test software. Use at your own risk. |
| 5 | |
| 6 | dosfsck is the Linux equivalent of PC/MS-DOS' CHKDSK. It checks the |
| 7 | consistency of PC/MS-DOS file systems and optionally tries to repair |
| 8 | them. The tests dosfsck performs are described in the man page. |
| 9 | |
| 10 | dosfsck needs header files from dosfs.9 (or later) to compile. |
| 11 | |
| 12 | Before using dosfsck to repair a file system that contains data of any |
| 13 | value, you should verify that dosfsck is able to correct all reported |
| 14 | errors. (Except fatal errors and those reported as unfixable, of |
| 15 | course.) In order to do this, run it with the -V option, e.g. |
| 16 | |
| 17 | dosfsck -V /dev/sda1 (automatic check) |
| 18 | or dosfsck -V -r /dev/sda1 (interactive check and repair) |
| 19 | |
| 20 | dosfsck will perform two passes: in the first pass, inconsistencies are |
| 21 | detected and a list of changes to correct the problems is generated. In |
| 22 | the second pass, those changes are applied whenever dosfsck reads data |
| 23 | from disk. Hence no fixable errors should be reported in the second |
| 24 | pass if the first pass was successful. |
| 25 | |
| 26 | Please notify the author if fixable errors are reported in the second |
| 27 | pass. |
| 28 | |
| 29 | After verifying that dosfsck appears to be able to perform the desired |
| 30 | operations, either confirm that you want the changes to be performed |
| 31 | (if dosfsck was started with -r) or re-run dosfsck with the -a option |
| 32 | (if it was started without -r). |
| 33 | |
| 34 | Please send bug reports, comments, flames, etc. to |
| 35 | almesber@nessie.cs.id.ethz.ch or almesber@bernina.ethz.ch |
| 36 | |
| 37 | - Werner |
| 38 | |
| 39 | FAT32 and LFN support |
| 40 | ===================== |
| 41 | |
| 42 | I've finally implemented some of the new features of MS-DOS |
| 43 | filesystems: FAT32 and long filenames. |
| 44 | |
| 45 | FAT32 is automatically detected and of course the different FAT |
| 46 | structure is handled. (Internally many changes were needed, so 32 bit |
| 47 | variables for all cluster numbers and 64 bit vars for offsets inside |
| 48 | the filesystem.) New checks for FAT32 are most notably on the backup |
| 49 | boot sector and the new info sector. Also the possibility that the |
| 50 | root directory resides in a cluster chain (instead of in a static |
| 51 | area) on FAT32 is handled. |
| 52 | |
| 53 | dosfscheck also knows about VFAT long filenames now. It parses those |
| 54 | names and uses them in listings etc. when available. There are also |
| 55 | some checks on the (cruel) structure of how LFNs are stored and some |
| 56 | attempts to fix problems. |
| 57 | |
| 58 | - Roman <roman@hodek.net> |
| 59 | |
| 60 | BTW, version 2 isn't ALPHA anymore :-) |