Displaying 4 results from an estimated 4 matches for "bforget".
Did you mean:
forget
2001 Apr 20
1
Just stirring the waters...
Hi, now that Ingo+redhat have discovered the cause
of the ext2 corruption under heavy load of 2.4.x
a couple of -preX patches ago (BTW ext2/3 gurus - what is the
difference between bforget() and brelse() - I'm a bit too dense
to understand the explanation given in the -pre patch?)
I wonder whether you folks are still finding
heavy load corruption problems for 2.4?
[My production servers are running ext3(6b)+2.2.19.]
Of course the real reason for asking is...are the showstoppers...
2001 Aug 08
5
BUG: Assertion failure with ext3-0.95 for 2.4.7
Hello ext3-users,
I tested ext3 on a Linux for S/390 with several stress and benchmark test
tests and faced a kernel bug message.
The console showed the following output:
Message from syslogd@boeaet34 at Fri Aug 3 11:34:16 2001 ...
boeaet34 kernel: Assertion failure in journal_forget() at
transaction.c:1184: "!
jh->b_committed_data"
I tried the Patch from
2001 Aug 09
2
Debugging help: BUG: Assertion failure with ext3-0.95 for 2.4.7
Hello ext3-developers,
Just to summarize, I reported a kernel bug message with ext3 on S/390 in
transaction.c. I was able to reproduce it with a ext3 on LVM and on MD.
Tom Rini reported a similar problem on PPC. (both big endian). I have sent
a backtrace and with jbd-debug set to 5 I was not able to reproduce the
problem until now.
On S/390 there are some more debug possibilities. I would
2006 Sep 24
1
Retaining undelete data on ext3
Having just spent a day trying to recover a deleted ext3 file
for a friend, I'm wondering about this way of maintining
undelete information in ext3, like is done for ext2:
The last step in the deletion process would be to put back
the (previously zeroed) block pointers. Since it gets logged
to the journal, I _think_ that this should be safe. The worst
that would happen is that, if the plug