ktprezes · August 23, 2023 19:46
diff --git a/linux-fsck-bad-blocks-search-remarks.txt b/linux-fsck-bad-blocks-search-remarks.txt
 The `fsck` command (file system check) works as a kind of _wrapper_ for file-system-type-dependent specialized commands, 
 and the options allowed MAY VARY depending of the file system type...
 For example:
  - for `fat32` file system the `fsck.vfat` is used, and the `-c N` option selects the `DOS codepage`,
    and the `-t` option tests for bad clusters
  - for `ext4` file system the `e2fsck` is used, and checking for bad blocks requires the `-c` (read-only test) option
    or the `-cc` (read/non-destructive-write test) option - and the `badblocks` command is used then under the hood
  - some linux systems contain the `fsck.ntfs` command, but some don't. And it seems the `ntfsfix` command 
    doesn't offer the `bad blocks` check, and the `badblocks` command lists the bad bocks found, but apparently doesn't 
    update the `bad blocks list` of the device
	The `fsck` command (file system check) works as a kind of _wrapper_ for file-system-type-dependent specialized commands,
	and the options allowed MAY VARY depending of the file system type...
	For example:
	- for `fat32` file system the `fsck.vfat` is used, and the `-c N` option selects the `DOS codepage`,
	and the `-t` option tests for bad clusters
	- for `ext4` file system the `e2fsck` is used, and checking for bad blocks requires the `-c` (read-only test) option
	or the `-cc` (read/non-destructive-write test) option - and the `badblocks` command is used then under the hood
	- some linux systems contain the `fsck.ntfs` command, but some don't. And it seems the `ntfsfix` command
	doesn't offer the `bad blocks` check, and the `badblocks` command lists the bad bocks found, but apparently doesn't
	update the `bad blocks list` of the device