From: Christoph Hellwig <hch@infradead.org>
To: Slawomir Nowakowski <slawomir.nowakowski@open-e.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Artur Piechocki <artur.piechocki@open-e.com>,
xfs@oss.sgi.com,
'Ryszard Stawiarski' <ryszard.stawiarski@open-e.com>,
??ukasz Wittig <lukasz.wittig@open-e.com>
Subject: Re: Problem with file system on iSCSI FileIO
Date: Fri, 24 Sep 2010 03:55:05 -0400 [thread overview]
Message-ID: <20100924075505.GA24664@infradead.org> (raw)
In-Reply-To: <4C9B6B27.5050606@open-e.com>
On Thu, Sep 23, 2010 at 04:58:47PM +0200, Slawomir Nowakowski wrote:
> iSCSI FileIO is using struct file that serves it as block level
> device via iSCSI technology:
>
> http://en.wikipedia.org/wiki/ISCSI
Thanks, I know ISCSI very well. But what is "iSCSI FileIO" ? The above
sounds like it's an iscsi target, is that correct?
> There are RAID level 6 unit on the Areca RAID controller (1680). On
> the unit is created a volume group. In the volume group we have
> several logical volumes. The iSCSI FileIO volume is mounted and the
> file (lun) is served via SCST target as iSCSI LUN.
>
> We have checked RAM with memtest+ and verified RAID unit health and
> no issues were found.
I still can't make any sense of the actual setups.
The above seems to be the backend storage. Then there's SCST somewhere
in which is in a out of tree kernel module. And then you use XFS
somewhere. Please provide a full description of the setup.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-24 7:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 13:35 Problem with file system on iSCSI FileIO Slawomir Nowakowski
2010-09-23 14:32 ` Christoph Hellwig
2010-09-23 14:58 ` Slawomir Nowakowski
2010-09-24 7:55 ` Christoph Hellwig [this message]
2010-09-24 11:11 ` Slawomir Nowakowski
2010-09-24 13:18 ` Emmanuel Florac
2010-09-24 13:46 ` Slawomir Nowakowski
2010-09-25 15:56 ` Christoph Hellwig
2010-09-25 16:54 ` Richard Sharpe
2010-09-25 17:01 ` Christoph Hellwig
2010-09-25 17:14 ` Richard Sharpe
2010-09-24 13:18 ` Emmanuel Florac
2010-09-24 13:49 ` Slawomir Nowakowski
2010-09-24 14:04 ` Emmanuel Florac
2010-09-24 15:10 ` Richard Sharpe
2010-09-24 18:18 ` Emmanuel Florac
2010-09-24 20:46 ` Ryszard Stawiarski
2010-09-25 14:13 ` Emmanuel Florac
2010-09-25 14:18 ` Richard Sharpe
2010-09-25 19:01 ` Vladislav Bolkhovitin
2010-09-25 21:23 ` Emmanuel Florac
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=20100924075505.GA24664@infradead.org \
--to=hch@infradead.org \
--cc=artur.piechocki@open-e.com \
--cc=lukasz.wittig@open-e.com \
--cc=ryszard.stawiarski@open-e.com \
--cc=slawomir.nowakowski@open-e.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