From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Cc: Ben Myers <bpm@sgi.com>,
stan@hardwarefreak.com, Subranshu Patel <spatel.ml@gmail.com>
Subject: Re: Xfs_repair and journalling
Date: Mon, 18 Mar 2013 21:58:30 +0100 [thread overview]
Message-ID: <201303182158.31100.Martin@lichtvoll.de> (raw)
In-Reply-To: <20130318182202.GD22182@sgi.com>
Am Montag, 18. März 2013 schrieb Ben Myers:
> Hi Subranshu,
[…]
> > 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.
>
> I can't speak for ext4. I do think that your expectation that
> fsck/repair be able to replay a journal is pretty reasonable. That's
> just not how it is implemented here. In xfs, log recovery is in the
> kernel and xfs_repair knows just enough about the log to avoid
> clobbering your precious metadata when it needs to be recovered. There
> was some discussion in the past about making xfs_repair able to recover
> the log but I wouldn't expect that any time soon.
Yes, fsck.ext4 is able to replay the journal, and also able to *just* replay
the journal and do nothing else. I just checked its manpage.
Thanks for not speaking for Ext4 unless you really think you know it.
Being able to replay in userspace might help when the filesystem cannot be
mounted correctly due to reasons laying outside the journal. Cause then one
can attempt to replay the journal in userspace and run a repair on the
filesystem then.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-18 20:58 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
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 [this message]
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=201303182158.31100.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=bpm@sgi.com \
--cc=spatel.ml@gmail.com \
--cc=stan@hardwarefreak.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox