From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <81d62ec1df1079fe157c72cfa698435c@quanstro.net> To: 9fans@9fans.net From: erik quanstrom Date: Sun, 13 Jul 2008 16:54:17 -0400 In-Reply-To: <487A61D1.9020202@proweb.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Anatomy of a vblade image Topicbox-Message-UUID: e491ab5c-ead3-11e9-9d60-3106f5b1d025 > I'm serving drives to WinXP64 via AOE with http://winaoe.org/ > I've had a few blue screens but I think they have been caused by the > server side serving bad data. what do you mean by "server side"? > If the vblade goes away after being > mounted the NT kernel keeps trying to read it which amounts to waiting > for network packets to arrive and of course they never do so any NT > syscalls take forever (though they run eventually). It does come back to > life even if you vblade a different sized disk. it is expected behavior for aoe devices to be able to take short vacations. our main fs uses aoe. we can upgrade the shelf without bringing down the fs. it does sounds like the free windows aoe driver needs to handle the case where storage goes away more gracefully. it may be that it is retransmitting too agressively. - erik