From owner-freebsd-questions Mon Nov 17 17:51:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA04290 for questions-outgoing; Mon, 17 Nov 1997 17:51:29 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from mail.netcetera.dk (root@sleipner.netcetera.dk [194.192.97.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA04285 for ; Mon, 17 Nov 1997 17:51:25 -0800 (PST) (envelope-from leifn@darla.swimsuit.roskildebc.dk) Received: (from uucp@localhost) by mail.netcetera.dk (8.8.7/8.8.7) with UUCP id CAA07773 for freebsd-questions@freebsd.org; Tue, 18 Nov 1997 02:15:52 +0100 Received: by swimsuit.roskildebc.dk (0.99.970109) id AA02248; 18 Nov 97 02:01:16 +0100 From: leifn@darla.swimsuit.roskildebc.dk (Leif Neland) Date: 17 Nov 97 19:50:09 +0100 Subject: Re: async fs? Message-ID: <434_9711180201@swimsuit.roskildebc.dk> References: Organization: Fidonet: UNIX-sysadm søger job To: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk g>> Are you aware that losing your system while you are running async is g>> usually fairly safe (often you lose no files, or if you were very busy g>> doing disk activity, maybe a few), but if you are mounted async, you g>> could possibly lose much, much more? Please explain: "running" async vs "mounted" async. Leif Neland leifn@image.dk --- |Fidonet: Leif Neland 2:234/49 |Internet: leifn@image.dk