When operating systems mark a cluster as used but not allocated, the cluster is considered as

A "lost cluster" is the correct technical term for a cluster that the file system's allocation table (e.g., FAT or MFT) marks as being in use, but which is not linked to any specific file or directory in the directory structure. This represents a logical inconsistency in the file system's metadata. Disk utility programs like CHKDSK (on Windows) or fsck (on Unix-like systems) are designed to detect these orphaned clusters. They can either free the space by marking the cluster as unallocated or recover the data by converting the lost cluster(s) into a file (e.g., FILExxxx.CHK) for user inspection.

A. Corrupt: This term is too general. While a lost cluster is a form of file system corruption, "corrupt" can also refer to unreadable data within a cluster or other metadata errors, not specifically this condition.

B. Bad: A "bad cluster" refers to a physically damaged section of the disk that can no longer reliably store data. The operating system marks these clusters to prevent future use, which is a hardware issue, not a logical file system error.

D. Unallocated: This is the opposite of the described state. An unallocated cluster is marked as free and available for new data, whereas the question specifies the cluster is "marked as used."

1. Microsoft Corporation. (2021). chkdsk. Microsoft Docs. In the documentation for the chkdsk command, the utility's function is described as finding and fixing file system errors. One of the common messages reported is finding "lost allocation units in chains" and converting them to files, which directly corresponds to the definition of a lost cluster. (Reference: chkdsk command-line documentation).

2. Silberschatz, A., Galvin, P. B., & Gagne, G. (2018). Operating System Concepts (10th ed.). Wiley. In Chapter 17, "File-System Implementation," Section 17.6.2 "Recovery," the authors describe consistency checking utilities. They state, "Another problem is a block that is not free but that is not pointed to by any file... Such a block is called a lost block (or lost cluster)." (p. 788).

3. Arpaci-Dusseau, R. H., & Arpaci-Dusseau, A. C. (2018). Operating Systems: Three Easy Pieces. Arpaci-Dusseau Books. In Chapter 40, "File System Checker (FSCK)," the text explains the process of checking for inconsistencies. It details a check where the tool scans all inodes and indirect blocks to build a correct map of allocated blocks, then compares it to the on-disk allocation structures. Any block marked as allocated on disk but not found in the scan is identified as a "lost" block. (Section 40.4, "Check 4: Block Counts").