[Top] [All Lists]

Re: Question related to XFS sync , especially fsync

To: Gopala Krishna <gopalakrishna.n.m@xxxxxxxxx>
Subject: Re: Question related to XFS sync , especially fsync
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 15 Jan 2008 09:18:04 -0600
Cc: David Chinner <dgc@xxxxxxx>, Chris Wedgwood <cw@xxxxxxxx>, Matthias Schniedermeyer <ms@xxxxxxx>, Olaf Fra;czyk <olaf@xxxxxxxxxxxxx>, Andi Kleen <andi@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <d711080c0801150544i53d7abb2hbea659116ce0006b@xxxxxxxxxxxxxx>
References: <d711080c0801140414n48e47140y88f545eba605eff9@xxxxxxxxxxxxxx> <20080114224245.GT155259@xxxxxxx> <d711080c0801150544i53d7abb2hbea659116ce0006b@xxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird (Macintosh/20071031)
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? :)


<Prev in Thread] Current Thread [Next in Thread>