From: Martin Steigerwald <Martin@lichtvoll.de>
To: stan@hardwarefreak.com
Cc: Eric Sandeen <sandeen@sandeen.net>,
Subranshu Patel <spatel.ml@gmail.com>,
xfs@oss.sgi.com
Subject: Re: Xfs_repair and journalling
Date: Tue, 19 Mar 2013 09:24:28 +0100 [thread overview]
Message-ID: <201303190924.29362.Martin@lichtvoll.de> (raw)
In-Reply-To: <5148037B.5010706@hardwarefreak.com>
Am Dienstag, 19. März 2013 schrieb Stan Hoeppner:
> Martin, I didn't state that ext4 cannot perform journal recovery, which
> you previously misunderstood. As mentioned above I stated it made a
> call to e2fsck to perform the task. And, again, apparently this is not
> the case. If you want to excoriate me for getting this wrong, that's
> fine. But don't do it in a way that suggests it was intentional, or
> that I made no effort to verify the information before I stated it. I
> spent at least 30 minutes Googling trying to track down documents
> explaining the ext4 journal recovery code in the kernel. I simply
> didn't find any. The only thing I found were descriptions of e2fsck
> based journal recovery.
Stan, you are still a XFS expert, you are still a hardware expert, and I
love reading your posts at debian-user, I sometimes even search for those,
you still know a lot and heck you are still Stan and as such without any
achievement or knowledge at all a precious being.
Just like anyone else on this list (and elsewhere) is a precious being just
as they are.
So whats so difficult with admitting that what you wrote about Ext4 and
journal replay as at least misleading?
Heck, even I was confused at first. Cause the manpage of fsck.ext4 IMHO is
not really clear about that topic to say the least. I tested it out for a
reason.
I am concerned about the tendency I perceive in open source, heck general
computer communities to bind own value to being right on a topic. There is
no, absolutely no connection at all. You and everyone else is valuable and
precious without any prerequisite at all.
I also take some to learn out of this myself: Cause I was obsessed with
being right myself and bound my value to it as well. I have overdone my
previous mails. Sorry for that.
Thanks,
--
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-19 8:24 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
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 [this message]
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=201303190924.29362.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=sandeen@sandeen.net \
--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