xfs
[Top] [All Lists]

Re: strange result of an XFS crash test

To: Michal Szymanski <msz@xxxxxxxxxxxxxx>
Subject: Re: strange result of an XFS crash test
From: Johan Mulder <johan@xxxxxxxxxxx>
Date: Wed, 27 Oct 2004 17:00:38 +0200
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20041027101200.GB30788@xxxxxxxxxxxxxx>
References: <20041027101200.GB30788@xxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Wed, 2004-10-27 at 12:12 +0200, Michal Szymanski wrote:
> BTW, with a "standard" /etc/fstab entry:
>   /dev/sda1   /export/data2  xfs   defaults    1 2
> is it going to be checked/repaired if needed at boot time?
> With EXT2/3 FS, "fsck" does both check and repair. With XFS, this job
> seems to be splitted into xfs_check and xfs_repair? Is the system
> "fsck" wrapper aware of that?

I can't give you any comments on the other stuff you mentioned, but most
linux scripts run /sbin/fsck.$filesystem to check if it's alright. So,
if it's an XFS filesystem, it will run /sbin/fsck.xfs to check it.
Because the XFS system checks the filesystem on mount
time, /sbin/fsck.xfs is rather useless. That's why it doesn't really do
anything. The manual even states so:


-- NAME
       fsck.xfs - do nothing, successfully

SYNOPSIS
       fsck.xfs [ ...]

DESCRIPTION
       fsck.xfs  is  called by the generic Linux fsck(8) program at startup to 
check and repair an XFS filesystem.  XFS is a journaling filesystem
       and performs recovery at mount(8) time if necessary, so fsck.xfs simply 
exits with a zero exit status.



<Prev in Thread] Current Thread [Next in Thread>