public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gopala Krishna" <gopalakrishna.n.m@gmail.com>
To: nscott@aconex.com
Cc: xfs@oss.sgi.com
Subject: Re: Question related to XFS sync , especially fsync
Date: Wed, 16 Jan 2008 12:13:54 +0530	[thread overview]
Message-ID: <d711080c0801152243h7613bbean9daeab8658f75408@mail.gmail.com> (raw)
In-Reply-To: <1200436012.9463.184.camel@edge.scott.net.au>

Is there any XFS call from user level to flush metadata  for a given file or
complete log  to disk?

Thanks,
Gopal.

On 1/16/08, Nathan Scott <nscott@aconex.com> wrote:
>
> 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
>
>


[[HTML alternate version deleted]]

  reply	other threads:[~2008-01-16  6:43 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
2008-01-15 22:26       ` Nathan Scott
2008-01-16  6:43         ` Gopala Krishna [this message]
     [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=d711080c0801152243h7613bbean9daeab8658f75408@mail.gmail.com \
    --to=gopalakrishna.n.m@gmail.com \
    --cc=nscott@aconex.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