public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Olaf Frączyk" <olaf@cbk.poznan.pl>
To: Gopala Krishna <gopalakrishna.n.m@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Question related to XFS sync , especially fsync
Date: Mon, 14 Jan 2008 15:32:32 +0100	[thread overview]
Message-ID: <1200321152.10994.13.camel@venus.local.navi.pl> (raw)
In-Reply-To: <d711080c0801140414n48e47140y88f545eba605eff9@mail.gmail.com>

On Mon, 2008-01-14 at 17:44 +0530, Gopala Krishna wrote:
> So I am suspecting, even after calling fsync (which says it would block
> untill it flushes metadata information to disk ), is not really flushing. So
> only during unmount, it flushes metadata and hence I could get dimode
> properly. since after remounting , by reading metadata information , I could
> get mode properly and differentiate directory or regular file, and also it
> is filling magic etc. properly, I feel the data I am reading is right and
> that I could compare with stat system call and ls commands.
The metadata are put in log. So they are on disk. Just not in the place
you expect them to find.
> 
> If I am doing something wrong and no problem with XFS, then I should not get
> mode field properly even after unmount/remount operation.
At remount the log is replayed and the metadata are in the place where
you expect them to be.
> 
> Is there any problem with XFS fsync? Why dimode is getting updated only
> during unmount? why not when I call fsync? Because fsync says it has to
> flush all meta dat to disk before existing.
And it does.
It is not XFS problem. It is your problem ;)

BTW, the GRUB does similiar thing. And many people reported problems
about it.

Regards,

Olaf

  parent reply	other threads:[~2008-01-14 14:31 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 [this message]
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
     [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=1200321152.10994.13.camel@venus.local.navi.pl \
    --to=olaf@cbk.poznan.pl \
    --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