[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Nbd] (no subject)

Hi Wouter,

we are using nbd in a high storage intensive area - a lot of changes
are written to nbd-devices AND ndb-client- and nbd-server (@solaris)
will be created and destroyed on the fly.

At the moment we have some problems while shutting down a nbd connection
(client, server) without losing data written to the client-nbd
but not available on the storage connected to the nbd-server.

	- startup nbd server (@solaris) & client (@linux)
	- write a lot of data and IMMEDIATELY after
	- shutdown client (nbd-client -d) and IMMEDIATELY after
	- shutdown server (yust kill -TERM <pid>

- Problem
	- the storage behind the nbd-server is not consistent to the data written
	  from the client site to the nbd-connection	

I think it could be a caching topic - maybe kblockd has not flushed the
data ? Or may I'm not allowed to send a TERM to the server ?

Could you tell me how to shutdown safely a client/server nbd-connection in a
high-load area without data corruption/lost ? 

Thx very much

DT Netsolution GmbH   -   Taläckerstr. 30    -    D-70437 Stuttgart
Geschäftsführer: Daniel Schwager, Stefan Hörz - HRB Stuttgart 19870
Tel: +49-711-849910-32, Fax: -932 - Mailto:daniel.schwager@...207...

Reply to: