Hi,
On Tue, 26 Oct 1999 14:56:50 +0200, [EMAIL PROTECTED]
(Miklos Szeredi) said:
> I will try to make more tests with a cleaner configuration...
OK, thanks --- the more information you can provide, the better. A
reliable reproducer for any problems would be best of all.
--Stephen
Hi!
> Are you sure you applied _both_ 0.0.2a and 0.0.2b, not just 0.0.2b?
I did apply both patches.
> This sounds exactly like a problem in truncate on 0.0.2a. I
> absolutely cannot reproduce any recovery failures with both applied.
> Alternatively, are you running on software raid? There's
Hi,
On Tue, 26 Oct 1999 10:19:13 +0200, [EMAIL PROTECTED]
(Miklos Szeredi) said:
> Hi,
> Sorry, I forgot to say, that it was with 0.0.2b. Also I reproduced
> this twice, so the second time, it _was_ a clean fs before converting
> to ext3.
Are you sure you applied _both_ 0.0.2a and 0.0.2b, not j
Hi,
Sorry, I forgot to say, that it was with 0.0.2b. Also I reproduced
this twice, so the second time, it _was_ a clean fs before converting
to ext3.
Miklos
> > 5) boot, then mount ext3 filesystem - it says:
> > JFS DEBUG: (recovery.c, 411): journal_recover: JFS: recovery, exit status 0,
>re
Hi,
On Mon, 25 Oct 1999 18:41:09 +0200, [EMAIL PROTECTED]
(Miklos Szeredi) said:
> 5) boot, then mount ext3 filesystem - it says:
> JFS DEBUG: (recovery.c, 411): journal_recover: JFS: recovery, exit status 0,
>recovered transactions 130 to 133
> 6) unmount the fs, and with debugfs turn off jo
Hi!
I did the following experiment:
1) make an ext3 filesystem
2) everything works OK
3) start copying a big file
4) reset the system while it is still copying
5) boot, then mount ext3 filesystem - it says:
JFS DEBUG: (recovery.c, 411): journal_recover: JFS: recovery, exit status 0,
recovered
