From: Ben Myers <bpm@sgi.com>
To: "杨苏立 Yang Su Li" <yangsuli@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS journal documentation?
Date: Tue, 3 Dec 2013 15:03:42 -0600 [thread overview]
Message-ID: <20131203210342.GO1935@sgi.com> (raw)
In-Reply-To: <CABK4GYMABHhU-afrgViOU0s4cpks7mGZ-dYoB7iFAmq-SZAX=A@mail.gmail.com>
Hi,
On Tue, Dec 03, 2013 at 02:55:23PM -0600, 杨苏立 Yang Su Li wrote:
> I am trying to understand XFS a little bit better, especially its journal
> process. Unfortunately, I am having trouble find documentation in this
> regard.
>
> The general XFS documentation (
> http://xfs.org/docs/xfsdocs-xml-dev/XFS_Filesystem_Structure//tmp/en-US/html/index.html)
> has been quite helpful, but it doesn't describe the journal part of XFS. I
> also found some kernel documentation ablout XFS's delayed logging (
> https://www.kernel.org/doc/Documentation/filesystems/xfs-delayed-logging-design.txt),
> which talks about the journal process a bit. But it seems to assume a lot
> of prior knowledge of how the original XFS logging works to completely
> understand what the author is talking about; and the term it uses (like
> checkpoint) seem to have complete different meaning from, say, ext4.
>
> So I am wondering, is there some kind of (any kind of ) documentation on
> XFS journaling? Ideally it will cover the major data structure and major
> code flow, but even a very high level, incomplete overview would be better
> than what I have now, which is essentially nothing. And if so, where can I
> find it?
The original design docs are posted here:
http://oss.sgi.com/projects/xfs/design_docs/xfsdocs93_pdf/
log_mgr.pdf might be what you need.
Regards,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-03 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 20:55 XFS journal documentation? 杨苏立 Yang Su Li
2013-12-03 21:03 ` Ben Myers [this message]
2013-12-03 21:18 ` Dave Chinner
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=20131203210342.GO1935@sgi.com \
--to=bpm@sgi.com \
--cc=xfs@oss.sgi.com \
--cc=yangsuli@gmail.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