Re: file systems
- To: email@example.com
- Subject: Re: file systems
- From: Stan Hoeppner <firstname.lastname@example.org>
- Date: Sat, 30 Apr 2011 22:53:27 -0500
- Message-id: <4DBCD937.email@example.com>
- In-reply-to: <4DB76F2C.firstname.lastname@example.org>
- References: <email@example.com> <4DAE0FF0.firstname.lastname@example.org> <4DB513E5.email@example.com> <4DB5CC72.firstname.lastname@example.org> <4DB5EDAB.email@example.com> <4DB60919.firstname.lastname@example.org> <4DB60C9E.email@example.com> <4DB630D1.firstname.lastname@example.org> <4DB646ED.email@example.com> <4DB67726.firstname.lastname@example.org> <4DB6D6C0.email@example.com> <4DB73CB2.firstname.lastname@example.org> <4DB749DE.email@example.com> <4DB75F4D.firstname.lastname@example.org> <BANLkTi=iz+UkxVccwzzgdtsXpE791NC-aQ@mail.gmail.com> <4DB76F2C.email@example.com>
On 4/26/2011 8:19 PM, PMA wrote:
But just in point of fact if possible: What *is* XFS's position
re FSCK -- just that it is excluded from the boot process,
or that it can never be run? And for whichever, does XFS
documentation offer a reason?
I suggest executing 'man fsck'. Here's a relevant snippet from such:
In actuality, fsck is simply a front-end for the various file
system checkers (fsck.fstype) available under Linux. The
file system-specific checker is searched for in /sbin first,
then in /etc/fs and /etc, and finally in the directories
listed in the PATH environment variable. Please see the file
system-specific checker manual pages for further details.
Relevant text from 'man fsck.xfs':
fsck.xfs is called by the generic Linux fsck(8) program at
startup to check and repair an XFS filesystem. XFS is a jour-
naling filesystem and performs recovery at mount(8) time if
necessary, so fsck.xfs simply exits with a zero exit status.
If you wish to check the consistency of an XFS filesystem,
or repair a damaged or corrupt XFS filesystem, see
xfs_check(8) and xfs_repair(8).