From: Eric Sandeen <sandeen@sandeen.net>
To: Gopala Krishna <gopalakrishna.n.m@gmail.com>
Cc: "David Chinner" <dgc@sgi.com>, "Chris Wedgwood" <cw@f00f.org>,
"Matthias Schniedermeyer" <ms@citd.de>,
"Olaf Fra;czyk" <olaf@cbk.poznan.pl>,
"Andi Kleen" <andi@firstfloor.org>,
xfs@oss.sgi.com
Subject: Re: Question related to XFS sync , especially fsync
Date: Tue, 15 Jan 2008 09:18:04 -0600 [thread overview]
Message-ID: <478CCEAC.9010008@sandeen.net> (raw)
In-Reply-To: <d711080c0801150544i53d7abb2hbea659116ce0006b@mail.gmail.com>
Gopala Krishna wrote:
> Hi All,
> Thanks a lot for your response.
> I never thought it might be in a log and not flushed to disk.
> Very good clue.
>
>>>> It is not XFS problem. It is your problem ;)
> Good comment. Agreed : -).
>
>>> How are you finding and inode off disk
>
> I have lot of code getting in to that. To explain that I have to go through
> that complex part of the code to explain in detail.
>
> Basically once we get indoe number for a given file from the available
> system call, we only depending upon the XFS layout and it's structure. We
> are reading super block from a particular disk offset and calculating
> address for inode offset and its address on the disk and reading directly
> from the disk offset. We are totally depending on XFS on disk layout.
Can I ask why you are doing this? :)
-Eric
next prev parent reply other threads:[~2008-01-15 15:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 12:14 Question related to XFS sync , especially fsync Gopala Krishna
2008-01-14 12:24 ` Gopala Krishna
2008-01-14 12:25 ` Gopala Krishna
2008-01-14 14:06 ` Andi Kleen
2008-01-14 14:32 ` Olaf Frączyk
2008-01-14 14:43 ` ***** SUSPECTED SPAM ***** " Matthias Schniedermeyer
2008-01-14 17:55 ` Chris Wedgwood
2008-01-14 22:42 ` David Chinner
2008-01-15 13:44 ` Gopala Krishna
2008-01-15 15:18 ` Eric Sandeen [this message]
2008-01-15 22:26 ` Nathan Scott
2008-01-16 6:43 ` Gopala Krishna
[not found] ` <20080116064840.GA5725@puku.stupidest.org>
2008-01-16 7:25 ` Gopala Krishna
2008-01-16 7:52 ` Iustin Pop
2008-01-16 8:11 ` Gopala Krishna
2008-01-16 8:25 ` Christoph Hellwig
2008-01-16 9:00 ` Gopala Krishna
2008-01-16 11:52 ` Mark Goodwin
2008-01-16 21:17 ` Martin Steigerwald
2008-01-16 23:38 ` Mark Goodwin
2008-01-17 1:25 ` Andi Kleen
2008-01-17 2:44 ` David 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=478CCEAC.9010008@sandeen.net \
--to=sandeen@sandeen.net \
--cc=andi@firstfloor.org \
--cc=cw@f00f.org \
--cc=dgc@sgi.com \
--cc=gopalakrishna.n.m@gmail.com \
--cc=ms@citd.de \
--cc=olaf@cbk.poznan.pl \
--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