public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <markgw@sgi.com>
To: Gopala Krishna <gopalakrishna.n.m@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Chris Wedgwood <cw@f00f.org>,
	nscott@aconex.com, xfs@oss.sgi.com
Subject: Re: Question related to XFS sync , especially fsync
Date: Wed, 16 Jan 2008 22:52:16 +1100	[thread overview]
Message-ID: <478DEFF0.40004@sgi.com> (raw)
In-Reply-To: <d711080c0801160100r7ae091f8k9c8f0f0152b9f203@mail.gmail.com>

Gopala,

it sounds like you want something like NDMP. Check that out first.

-- Mark

Gopala Krishna wrote:
> Thanks for the suggestions!.  I will relook at the my idea and
> design....implemetation. As of now what we are doing is in experimental
> stage.
> 
> Thanks,
> Gopal.
> 
> 
> On 1/16/08, Christoph Hellwig <hch@infradead.org> wrote:
>> On Wed, Jan 16, 2008 at 12:55:17PM +0530, Gopala Krishna wrote:
>>> While  replying  to Eric, I mentioned why we are doing that. We are
>>> basically providing interfaces to back up applications in a pure storage
>>> environment that deals with the  back up at block level (sector level)
>> and
>>> hence depending upon different file system, we need to get information
>> about
>>> file like it's extent information and associated block numbers etc.
>> This basically can't work.  If you do a plain block based backup you
>> need to freeze the filesystem first and then either backup through a
>> newly created snapshot or the raw device.  Alternatively you can do
>> file-based backups assisted by the bulkstat interface as done by
>> xfsdump.  If you try to mix the two layers you get into deep trouble
>> due to various issues:
>>
>> - knowledge of the disk format.  The ondisk format can change anytime
>>   and will break your application.  And yes, additions to the ondisk
>>   format do happen quite frequently.
>> - no coherency between the filesystem and the block device node.  This
>>   is especially true for backup applications which use the buffered
>>   block device nodes because there is a real-life chance that stale
>>   cache is around
>> - no guarantee that the ondisk image is actually update.  XFS like
>>   most other current filesystems uses an intent log to provide
>>   reliabily and sync is only guaranteed to push updates into the log
>>   but not actually write it back to it's "normal" location on disk.
>>
>> In short what you're trying to do is a road to disaster, so don't do it!
>>
>> Note that the problems apply to any filesystem in one way or another,
>> not just XFS.
>>
>>
> 
> 
> [[HTML alternate version deleted]]
> 
> 

-- 

  Mark Goodwin                                  markgw@sgi.com
  Engineering Manager for XFS and PCP    Phone: +61-3-99631937
  SGI Australian Software Group           Cell: +61-4-18969583
-------------------------------------------------------------

  reply	other threads:[~2008-01-16 11:52 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
     [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 [this message]
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=478DEFF0.40004@sgi.com \
    --to=markgw@sgi.com \
    --cc=cw@f00f.org \
    --cc=gopalakrishna.n.m@gmail.com \
    --cc=hch@infradead.org \
    --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