----- Start Original Message ----- Sent: Wed, 26 Jul 2006 10:33:32 -0500 From: J Leslie Turriff <[EMAIL PROTECTED]> To: LINUX-390@VM.MARIST.EDU Subject: Re: Bad Linux backups
> Sounds to me, then, like the use of the > snapshot/mirror/peer-to-peer copy features of storage devices e.g. > Shark, SATABeast, etc. are currently dangerous to use with Linux > filesystems. They would need to be able to coordinate their activities > with the filesystem lock/unlock components of the kernel to be made > safe? One point not mentioned yet, is that FLASHCOPY is an asynchronous process. You can start a FLASHCOPY operation and it *can* return an error status asynchronously. 90+% of the time this is not apparent, the request is made and the Shark goes happily on its way. However if the request that is queued within the Shark has to be terminated (Resource shortages, target volume errors etc.) then beware! Mark ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
