From: Stan Hoeppner <stan@hardwarefreak.com>
To: Subranshu Patel <spatel.ml@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Xfs_repair and journalling
Date: Sun, 17 Mar 2013 09:50:32 -0500 [thread overview]
Message-ID: <5145D838.8050003@hardwarefreak.com> (raw)
In-Reply-To: <CAEUQceie41dh7h6uZSMu4-JB_BDu82X5CrKxHb=9wVQVAPzKgQ@mail.gmail.com>
On 3/17/2013 6:42 AM, Subranshu Patel wrote:
> What I understand is that, XFS being a journalling filesystem makes running
> xfs_repair after a unclean unmount unnecessary.
>
> After a system crash or force power down, one can mount the filesystem
> which causes the journal to be replayed and handles the half finished
> writes. This is one part. But there can be other file corruption as well
> and these can be handled by xfs_repair.
> So the crux is to mount the filesystem so that journal will be replayed,
> and then unmount the filesystem and run xfs_repair. (Assuming xfs_repair
> may not be a mandatory step always)
>
> In case of EXT4, journal will not be replayed on performing mount. One need
> to invoke fsck which performs journal playback and then other corruption
> checks/recovery.
> Correct me if I am wrong.
Enough with the foreplay. Get to your point please. I'm assuming you
think you have an exception, a bug, to report.
--
Stan
>
> On Sun, Mar 17, 2013 at 10:56 AM, Stan Hoeppner <stan@hardwarefreak.com>
> wrote:
>>
>> 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.
>>
>> --
>> Stan
>>
>
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-17 14:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 15:56 Xfs_repair and journalling Subranshu Patel
2013-03-17 2:22 ` Stan Hoeppner
2013-03-17 3:01 ` Michael L. Semon
2013-03-17 5:26 ` Stan Hoeppner
2013-03-17 11:42 ` Subranshu Patel
2013-03-17 14:50 ` Stan Hoeppner [this message]
2013-03-17 15:18 ` Matthias Schniedermeyer
2013-03-17 23:20 ` Dave Chinner
2013-03-18 18:22 ` Ben Myers
2013-03-18 20:58 ` Martin Steigerwald
2013-03-18 20:50 ` Martin Steigerwald
2013-03-19 4:02 ` Eric Sandeen
2013-03-19 6:19 ` Stan Hoeppner
2013-03-19 8:24 ` Martin Steigerwald
2013-03-19 10:14 ` Stan Hoeppner
2013-03-30 12:49 ` Xfs_repair and journalling -- EXT4 journal replay discussion Stan Hoeppner
2013-03-30 17:40 ` Eric Sandeen
2013-03-30 18:52 ` Stan Hoeppner
2013-03-30 20:21 ` Eric Sandeen
2013-03-31 11:24 ` Stan Hoeppner
2013-03-31 2:03 ` Dave Chinner
2013-03-31 1:35 ` Dave Chinner
2013-03-18 20:37 ` Xfs_repair and journalling Martin Steigerwald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5145D838.8050003@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=spatel.ml@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.