Well OK, maybe the analogy wasn't absolutely perfect. The point is on
reboot Linux will think it crashed, Linux will attempt to rebuild it's
filesystem, it may or may not work. Don't take the chance with your
corporate data.
Rob van der Heij wrote:
On 6/29/07, Rich Smrcina <[EMAIL PROTECTED]> wrote:
It's exactly like rebooting a Linux PC after some sort of crash, it goes
through a filesystem check (fsck).
There's a big difference. If the PC crashes you have a consistent
state as it was at that time. But when you have z/OS on the other end
copy the disk track by track, it is not consistent.
It's like the panoramic photo's in Google Streetview, composed of
multiple pictures taken short after each other from slightly different
location. A person walking by could show on adjacent pictures and
appear duplicate when you combine the pictures.
If you use snapshot on the ESS, you do get a consistent copy. But then
you still may loose data. Even on a journaled file system because only
meta data is normally recovered.
Rob
----------------------------------------------------------------------
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
--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service: 360-715-2467
rich.smrcina at vmassist.com
http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org
WAVV 2008 - Chattanooga - April 18-22, 2008
----------------------------------------------------------------------
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
