Path: utzoo!attcan!uunet!mcsun!hp4nl!svin02!debra
From: debra@svin02.info.win.tue.nl (Paul de Bra)
Newsgroups: comp.unix.sysv386
Subject: Re: SV1K reliability (summary)
Keywords: SV1K reliability
Message-ID: <1630@svin02.info.win.tue.nl>
Date: 10 Dec 90 16:05:19 GMT
References: <7454@suns302.cel.co.uk>
Organization: Eindhoven University of Technology, The Netherlands
Lines: 23

In article <7454@suns302.cel.co.uk> ir@cel.co.uk (ian reid) writes:
>In brief the question was why did my system lose files when a power loss
>occurred.  I can accept I would lose files which were being modified at the
>time, but I was losing (or having corrupted) some indeterminate files
>which made my system unbootable....

I have been running AT&T sVr3.2u for well over a year now and never
ever lost files after a power-fail or panic (the panics were because i had
a bad block in the swap space, not because of bugs in the os).
This experience is with both the 1K and 2K file systems.
There is a process which updates the disk in a more continuous fashion than
the old /etc/update did.

I have experimented with sVr4.0 version 2.0 and can only say that the
ufs file system is horribly unreliable. Shortly after reading about
100 mbytes from a tape (but well after the time the automatic update
program waits to write the stuff out to the disk) I got a panic,
and fsck went on and on complaining about my file systems...
I went back to sVr3.2.
Apparently the sVr4.0 ufs file system doesn't get sync-ed properly
by the automatic syncing deamon...

Paul.
(debra@research.att.com, debra@win.tue.nl)