[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47A80CB9.9000805@wpkg.org>
Date: Tue, 05 Feb 2008 08:14:01 +0100
From: Tomasz Chmielewski <mangoo@...g.org>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: Bart Van Assche <bart.vanassche@...il.com>,
Vladislav Bolkhovitin <vst@...b.net>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
scst-devel@...ts.sourceforge.net,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [Scst-devel] Integration of SCST in the mainstream Linux kernel
James Bottomley schrieb:
> These are both features being independently worked on, are they not?
> Even if they weren't, the combination of the size of SCST in kernel plus
> the problem of having to find a migration path for the current STGT
> users still looks to me to involve the greater amount of work.
I don't want to be mean, but does anyone actually use STGT in
production? Seriously?
In the latest development version of STGT, it's only possible to stop
the tgtd target daemon using KILL / 9 signal - which also means all
iSCSI initiator connections are corrupted when tgtd target daemon is
started again (kernel upgrade, target daemon upgrade, server reboot etc.).
Imagine you have to reboot all your NFS clients when you reboot your NFS
server. Not only that - your data is probably corrupted, or at least the
filesystem deserves checking...
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists