From: Emmanuel Florac <eflorac@intellique.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: 'Ryszard Stawiarski' <ryszard.stawiarski@open-e.com>,
??ukasz Wittig <lukasz.wittig@open-e.com>,
Artur Piechocki <artur.piechocki@open-e.com>,
xfs@oss.sgi.com,
Slawomir Nowakowski <slawomir.nowakowski@open-e.com>
Subject: Re: Problem with file system on iSCSI FileIO
Date: Fri, 24 Sep 2010 15:18:46 +0200 [thread overview]
Message-ID: <20100924151846.1208611c@harpe.intellique.com> (raw)
In-Reply-To: <20100924075505.GA24664@infradead.org>
Le Fri, 24 Sep 2010 03:55:05 -0400
Christoph Hellwig <hch@infradead.org> écrivait:
> Thanks, I know ISCSI very well. But what is "iSCSI FileIO" ? The
> above sounds like it's an iscsi target, is that correct?
It's an IO Mode that goes through the kernel VFS cache, as opposed to
blockIO that does direct IO.
> 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.
If the iSCSI targets are actually block devices (lvm lvs, disk
partitions, etc), than using FileIO is a mistake, it may bring up all
kind of weird behaviours, though normally no real errors - though I
don't really know how scst fares in this regard.
My understanding : he planned to create a file on the mounted XFS
volume with dd but instead he dd'ed the lv itself, which obviously
destroyed the filesystem. Or something else, I don't really know :)
Slawomir, please show us the scst config file. Did you use mkfs
and dd on the target or the initiator? This isn't clear.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-24 13:17 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
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 [this message]
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=20100924151846.1208611c@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=artur.piechocki@open-e.com \
--cc=hch@infradead.org \
--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