[Top] [All Lists]

Re: Xfs_repair and journalling

To: Subranshu Patel <spatel.ml@xxxxxxxxx>
Subject: Re: Xfs_repair and journalling
From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Date: Sun, 17 Mar 2013 00:26:32 -0500
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <CAEUQceh-Xcabr0KErxF6EAdafDDP1PY_AeHwgYB82QeUdyGp-g@xxxxxxxxxxxxxx>
References: <CAEUQceh-Xcabr0KErxF6EAdafDDP1PY_AeHwgYB82QeUdyGp-g@xxxxxxxxxxxxxx>
Reply-to: stan@xxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
On 3/16/2013 10:56 AM, Subranshu Patel wrote:

> This is not observed in EXT4, fsck successfully recovers without
> mounting the filesystem.

And this is the real problem.  You're *assuming* XFS should behave in
the same manner as EXT4.  Why would you assume a Ferrari should behave
like a Tata Nano?

XFS is far more sophisticated than EXT4 in many, many ways, including
recovery after unclean shutdown.  XFS kernel code performs journal
playback/recovery automatically when the filesystem is mounted.
xfs_repair is a tool for fixing filesystems that are broken, not simply
in need of journal playback.  Thus xfs_repair has no code to perform
journal recovery.

EXT4 (and EXT3) lacks this sophistication and must call a user space
tool, e2fsck, to perform journal playback/recovery.

XFS is the Ferrari of Linux filesystems and EXT is the Tata.  Keep that
in mind as you discover many of the other differences in the future.


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