[Stgt-devel] data corruption problems with stgt (aborted journal, remounting ro)?
Sat Feb 2 01:56:38 CET 2008
On Fri, 01 Feb 2008 13:05:41 +0100
Tomasz Chmielewski <mangoo at wpkg.org> wrote:
> Tomasz Chmielewski schrieb:
> > Doesn't look my posts get to this list... or is it just lagged a lot?
> > Resending.
> > Perhaps I'm doing something wrong - but with stgt I'm facing problems I
> > didn't have with IET or SCST.
> > Whenever I kill tgtd daemon and start it again (i.e., target server
> > restart), the initiator detects an aborted journal and remount the
> > device ro.
> > Why is it so?
> > What is the recommended way to kill the tgtd daemon? It doesn't seem to
> > react on TERM signal.
> Hello, anyone there?
> Is there a way to restart tgtd daemon or a machine running tgtd, so that
> iSCSI connections don't break?
What does your 'restart tgtd daemon' mean? For me, 'restart' involves
stopping tgtd daemon and it closes all the iSCSI connections.
More information about the stgt