xfs
[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: Nathan Scott <nscott@xxxxxxxxxx>
Date: Wed, 16 Jan 2008 09:26:52 +1100
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, 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: <478CCEAC.9010008@xxxxxxxxxxx>
Organization: Aconex
References: <d711080c0801140414n48e47140y88f545eba605eff9@xxxxxxxxxxxxxx> <20080114224245.GT155259@xxxxxxx> <d711080c0801150544i53d7abb2hbea659116ce0006b@xxxxxxxxxxxxxx> <478CCEAC.9010008@xxxxxxxxxxx>
Reply-to: nscott@xxxxxxxxxx
Sender: xfs-bounce@xxxxxxxxxxx
On Tue, 2008-01-15 at 09:18 -0600, Eric Sandeen wrote:
> 
> > 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? :)
> 

This would be good to know.  If you absolutely must use inode numbers
instead of path names, you should use the "by-handle" interface (like
xfsdump, xfs_fsr, etc) and not use the ondisk structures directly -
doing so is always "broken by design" and you'll get little sympathy
here for doing so. :)

cheers.

-- 
Nathan


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