public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Gopala Krishna <gopalakrishna.n.m@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Question related to XFS sync , especially fsync
Date: Tue, 15 Jan 2008 09:42:45 +1100	[thread overview]
Message-ID: <20080114224245.GT155259@sgi.com> (raw)
In-Reply-To: <d711080c0801140414n48e47140y88f545eba605eff9@mail.gmail.com>

On Mon, Jan 14, 2008 at 05:44:22PM +0530, Gopala Krishna wrote:
> Hi,
> I am seeing some strange problem with XFS and would like to know  the
> expected behavior and if it is faulty is there any patches to resolve the
> problem.
> 
> Problem:
> ======
> Basically I am extracting metadata information for a given file by reading
> the inode structure from the particular disk offset (based on it's  position
> calculated by published inode structure and super block structure
>  information). Before reading the metada data information from the disk, I
> am calling fsync (I used to call sync, but later I changed to fsync, since
> sync is not guranteed to flush all meta data)  to ensure all metadata
> related to file is flushed to disk. Later I am reading particular disk
> offset as per calculation.   I am getting XFS magic field properly after
> mapping to XFs inode structure. However I am not getting dimode properly in
> some cases (not all cases) and it shows 00000 even for regular file and
> directory.

How are you finding and reading the inode off disk?

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  parent reply	other threads:[~2008-01-14 22:42 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 [this message]
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
     [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=20080114224245.GT155259@sgi.com \
    --to=dgc@sgi.com \
    --cc=gopalakrishna.n.m@gmail.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