All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christine Caulfield <ccaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS + iscsi target + LVM performance and file integrity
Date: Wed, 30 Apr 2008 08:30:08 +0100	[thread overview]
Message-ID: <48182000.3000601@redhat.com> (raw)
In-Reply-To: <3120c9e30804292333m433a6c6bm8ea3fe6ed69c1ab6@mail.gmail.com>

???? Anuj Singh wrote:
> Hi,
> I have a question related to GFS + LVM and iscsi.
> 1). I have a file test.txt on shared GFS file system, some user ramesh
> opens test.txt to read, at the same time some other user Smith on the
> network writes some data to test.txt file.
> What data will Ramesh see in test.txt file which is changed after he
> opened?
> How does GFS handles data integrity?

The same thing happens on GFS as would occur if you did that on a local
file system. GFS does not provide any additional data integrity features
over other file systems. If you can corrupt a file by writing to it from
two places using ext3 on one node, then the same thing will happen using
GFS, regardless of whether the processes are on the same or different nodes.

The point of GFS is not to provide data integrity, but /metadata/
integerity. ie, the filesystem itself does not become corrupted by two
nodes writing to the same inode or directory.

So, the basic rule is: if it would corrupt data if two people on the
same node did it on next3, then it will also corrupt data if two people
on different nodes did it on GFS.

I hope that's clear!
-- 

Chrissie



  reply	other threads:[~2008-04-30  7:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30  6:33 [Cluster-devel] GFS + iscsi target + LVM performance and file integrity अनुज Anuj Singh
2008-04-30  7:30 ` Christine Caulfield [this message]
2008-04-30  9:07   ` अनुज Anuj Singh
2008-04-30 11:05     ` अनुज Anuj Singh

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=48182000.3000601@redhat.com \
    --to=ccaulfie@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.