All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jignesh <jignesh.prajapati@cmcltd.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "Bhavin.Joshi@Cmcltd.Com" <bhavin.joshi@cmcltd.com>,
	"Gaurang.Patel@Cmcltd.Com" <gaurang.patel@cmcltd.com>,
	Ravi <m.ravindran@cmcltd.com>,
	xfs@oss.sgi.com
Subject: Re: XFS Realtime Replication problem
Date: Thu, 03 Jul 2014 14:51:28 +0530	[thread overview]
Message-ID: <53B52098.2090104@cmcltd.com> (raw)
In-Reply-To: <20140703090253.GT4453@dastard>

Dear Dave,

Thanks for your reply.

Regards,

Jignesh P.

On 03-07-2014 14:32, Dave Chinner wrote:
> On Thu, Jul 03, 2014 at 11:57:03AM +0530, Jignesh wrote:
>> Dear Dave,
>>
>> Thanks for your quick response.
>>
>> This is not SGI Proprietary Storage product and not using any SGI
>> proprietary kernel module. SGI IS3500 is normal Intel Server with 36
>> HDDs. ( Storage Server), We have installed RHEL 6.2 on this Server
>> and configured XVM and XFS.
> XVM is SGI proprietary software:
>
> http://www.sgi.com/products/storage/software/xvm.html
>
> As it is, if you are using RHEL, you should talk to your Red Hat
> support contact. They'll be able to tell you if it's a known problem
> w/ XFS on RHEL and which version of RHEL 6.x it is fixed in.
>
> Cheers,
>
> Dave.


-- 
Jignesh Prajapati
Sr. IT Manager-CS
CMC Limited
(A TATA Enterprise)
6th Floor, Premier House-1, Bodakdev, S G Highway, Ahmedabad-380054
Direct Line: +91 79 66090924 | Email: jignesh.prajapati@cmcltd.com
www.cmcltd.com
----------------------------------------------------------------------------------------------------------
System Engineering | Integration | Solution & Sales
----------------------------------------------------------------------------------------------------------

______________________________________________________________________________

DISCLAIMER

The information contained in this e-mail message and/or attachments to it may
contain confidential or privileged information. If you are not the intended
recipient, any dissemination, use, review, distribution, printing or copying
of the information contained in this e-mail message and/or attachments to it
are strictly prohibited. If you have received this communication in error,
please notify us by reply e-mail or directly to netsupport@cmcltd.com or
telephone and immediately and permanently delete the message and any
attachments. Thank you.

______________________________________________________________________________

This email has been scrubbed for your protection by SecureMX.
For more information visit http://securemx.in
_____________________________________________________________________________

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-07-03  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03  4:54 XFS Realtime Replication problem Jignesh
2014-07-03  5:25 ` Jignesh
2014-07-03  6:15 ` Dave Chinner
2014-07-03  6:27   ` Jignesh
2014-07-03  9:02     ` Dave Chinner
2014-07-03  9:21       ` Jignesh [this message]
2014-07-03 13:50         ` Troy McCorkell

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=53B52098.2090104@cmcltd.com \
    --to=jignesh.prajapati@cmcltd.com \
    --cc=bhavin.joshi@cmcltd.com \
    --cc=david@fromorbit.com \
    --cc=gaurang.patel@cmcltd.com \
    --cc=m.ravindran@cmcltd.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 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.