RE: [Xen-API] [PATCH 0 of 4] CA-38567: Make Xapi more I/O error sensitive

[Dave Scott <Dave.Scott@xxxxxxxxxxxxx>]

Hi Daniel,

Thanks for sending these patches! My only question is: can you explain when you 
would expect to see this new error? Does it imply the storage server or the 
storage network has failed (e.g. some iSCSI or NFS softmount timeout)? Should 
we ask the user to go check their cabling, storage server logs etc?

Cheers,
Dave

> -----Original Message-----
> From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-api-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Daniel Stodden
> Sent: 05 March 2010 23:21
> To: Xen API
> Subject: [Xen-API] [PATCH 0 of 4] CA-38567: Make Xapi more I/O error
> sensitive
> 
> 
> VDI copy/init/provision ops in xapi are all buffered. Means I/O
> completes only deferred. The agent should carefully sync back buffers
> to disk and test file status, or gust corruption goes unnoticed.
> 
> Presently covers:
>  * XVA import
>  * Raw VDI import
>  * VDI.copy
>  * VM.provision (e.g. the Debian Etch post-installation script)
> 
> There might be more, which I've been missing then.
> 
> Some of the changes below just use O_SYNC on the output fd. Most
> assume a prior xen-api-libs patch to make Unixext.fsync provide the
> necessary error detail. See related hg-email.
> 
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api