[Top] [All Lists]

Re: vim file write mode on journaling fs.

To: Bram Moolenaar <Bram@xxxxxxxxxxxxx>
Subject: Re: vim file write mode on journaling fs.
From: Seth Mos <knuffie@xxxxxxxxx>
Date: Fri, 10 Aug 2001 23:19:46 +0200
Cc: Linux XFS Mailing List <linux-xfs@xxxxxxxxxxx>
In-reply-to: <Pine.BSI.4.10.10108102239340.24753-100000@xs3.xs4all.nl>
References: <200108101958.f7AJwmv07495@moolenaar.net>
Sender: owner-linux-xfs@xxxxxxxxxxx
At 22:43 10-8-2001 +0200, Seth Mos wrote:
> Does it only happen when overwriting an existing file?  I would expect the
> same to happen when writing a new file.  E.g. when using:

I asume this is the case.

> cp file1 file2
> rm file1
> Could you end up with an invalid file2 while file1 has been deleted already?

The following script was used.

echo Test > file1
cp file1 file2
rm file1

When the script completes I hit the big red switch and sure enough. After recovery the file1 does not exist (that is ok) but file2 is empty and does not have data but it does have a size of 5 bytes.

So something is biting us. I would expect file2 to be non existant (because it didn't get written yet or the correct file. This is in between.

My brain is starting to hurt.

Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.

<Prev in Thread] Current Thread [Next in Thread>