From: Matthias Schniedermeyer <ms@citd.de>
To: Gopala Krishna <gopalakrishna.n.m@gmail.com>
Cc: xfs@oss.sgi.com
Subject: ***** SUSPECTED SPAM ***** Re: Question related to XFS sync , especially fsync
Date: Mon, 14 Jan 2008 15:43:06 +0100 [thread overview]
Message-ID: <20080114144306.GA4672@citd.de> (raw)
In-Reply-To: <d711080c0801140414n48e47140y88f545eba605eff9@mail.gmail.com>
On 14.01.2008 17:44, 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:
> ======
...
The man-page "xfs_freeze" at least reads like it does what you want,
i.e. it flushes everything(tm).
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2008-01-14 14: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 ` Matthias Schniedermeyer [this message]
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=20080114144306.GA4672@citd.de \
--to=ms@citd.de \
--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