From: Tomasz Torcz <tomek@pipebreaker.pl>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs not iSCSI-target safe?
Date: Thu, 23 Jul 2009 15:28:52 +0200 [thread overview]
Message-ID: <20090723132852.GA23960@mother.pipebreaker.pl> (raw)
In-Reply-To: <20090722144031.GC29886@think>
On Wed, Jul 22, 2009 at 10:40:31AM -0400, Chris Mason wrote:
> On Wed, Jul 22, 2009 at 01:27:06PM +0200, Tomasz Torcz wrote:
> >
> > Hi,
> >
> > I tried to export file from btrfs volume using iSCSI target.
> > As soon as some initiator have read it over network, server
> > oopsed: http://www.kerneloops.org/submitresult.php?number=557979
> > Kernel is Fedora's 2.6.29.6-213.fc11.x86_64. I'm aware that
> > target iSCSI functionality is out-of-tree (I'm using iscsitarget-0.4.17-3),
> > so it may not be safe. But is there any known incompatibility
> > between iscsi-target and btrfs?
>
> Sorry, I don't know of any problems between btrfs and iscsi. Is the
> iscsi target configured to use linux aio? That could be the problem.
I'm not sure, I'm a mere user. This target software seems to read
files from kernelspace, which as I understand is frowned upon.
If you are interested, sourcecode is at http://iscsitarget.sourceforge.net/
Ooops occured in fileio_make_request(), in iscsitarget-0.4.17/kernel/file-io.c
file.
--
Tomasz Torcz "God, root, what's the difference?"
xmpp: zdzichubg@chrome.pl "God is more forgiving."
next prev parent reply other threads:[~2009-07-23 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 11:27 btrfs not iSCSI-target safe? Tomasz Torcz
2009-07-22 14:40 ` Chris Mason
2009-07-23 13:28 ` Tomasz Torcz [this message]
2009-07-23 16:50 ` Tomasz Chmielewski
2009-08-07 12:57 ` Tomasz Torcz
2009-07-23 22:22 ` FUJITA Tomonori
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=20090723132852.GA23960@mother.pipebreaker.pl \
--to=tomek@pipebreaker.pl \
--cc=linux-btrfs@vger.kernel.org \
/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