Before a maintenance window you want to know whether the unmounted XFS filesystem on /dev/sdb1 is damaged, without letting anything be modified. Type the complete command that checks it and reports what it would do, in no-modify mode.

LPIC-1 Exam 101-500, objective 104. Devices, Linux filesystems, filesystem hierarchy standard medium

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.

Answer

Type the answer.

Accepted answer

Case sensitive — Linux is, and grading LS as ls would teach a falsehood.

Why

xfs_repair -n scans the filesystem and prints the repairs it would carry out, but opens the device read-only and changes nothing. It is the XFS counterpart of e2fsck -n (xfs_repair takes short options only, so there is no --no-modify spelling), and the safe first move whenever the extent of the damage is unknown. Note that plain fsck does almost nothing on XFS, and that xfs_repair still requires the filesystem to be unmounted even in no-modify mode.

Where this comes from

Cited
manual page xfs_repair(8)

Practise this

Reading one question is not practice. The trainer will draw a short set from objective 104 and space the ones you get wrong.

Practise LPIC-1 Exam 101-500

More questions on this objective

All questions on Devices, Linux filesystems, filesystem hierarchy standard

Practise LPIC-1 Exam 101-500