Displaying 5 results from an estimated 5 matches for "lock_journ".
Did you mean:
lock_journal
2005 Jan 04
0
[PATCH] BUG on error handlings in Ext3 under I/O failure condition
...checkpoint.c
--- linux-2.4.29-pre3-bk2/fs/jbd/checkpoint.c 2002-11-29 08:53:15.000000000 +0900
+++ linux-2.4.29-pre3-bk2_fix/fs/jbd/checkpoint.c 2005-01-04
19:58:32.000000000 +0900
@@ -142,7 +142,7 @@
spin_unlock(&journal_datalist_lock);
log_start_commit(journal, transaction);
unlock_journal(journal);
- log_wait_commit(journal, tid);
+ (void) log_wait_commit(journal, tid);
goto out_return_1;
}
diff -Nru linux-2.4.29-pre3-bk2/fs/jbd/commit.c
linux-2.4.29-pre3-bk2_fix/fs/jbd/commit.c
--- linux-2.4.29-pre3-bk2/fs/jbd/commit.c 2004-02-18 22:36:31.000000000 +0900
+++ linux-...
2001 Mar 30
1
Re: Bug in __invalidate_buffers?
...oops
problem for me (running LVM pvscan while writing into an ext3-0.0.6b fs).
Cheers, Andreas
===========================================================================
--- fs/jfs/checkpoint.c.orig Thu Mar 1 16:35:40 2001
+++ fs/jfs/checkpoint.c Thu Mar 29 17:08:51 2001
@@ -106,8 +106,15 @@
lock_journal(journal);
return 1;
}
-
- if (!buffer_dirty(bh) && !buffer_jdirty(bh) &&
+
+ if (bh->b_dev == B_FREE) {
+ if (bh->b_cp_transaction) {
+ unlock_journal(journal);
+ journal_remove_checkpoint(bh);
+ lock_journal(journal);
+ return 1;
+ }
+ } else if...
2001 May 16
1
Re: [linux-lvm] lvm deadlock with 2.4.x kernel?
..._head bit checks and then calls refile_buffer(). Mine currently
looks like the following:
if (!buffer_dirty(bh) && !buffer_jdirty(bh) &&
!buffer_journaled(bh) &&
bh->b_list != BUF_CLEAN) {
unlock_journal(journal);
refile_buffer(bh);
lock_journal(journal);
return 1;
}
Note the addition of the !buffer_journaled(bh) check.
Okay, so using all of the above, I have now been running multiple vgscan
loops and a pvsc...
2002 Jan 07
2
Assertion failure in journal_flush()
Hi Steven, Hi ext3-users list!
We encountered a reproduceable problem with ext3:
When issuing a FIBMAP ioctl for a block written right before while
the FS is under high load (RH build universe), the assertion
!journal->j_running_transaction fails at the bottom of journal_flush()
in fs/jbd/journal.c.
We encountered this problem with the arch=s390x (64 bit big endian)
bootloader zipl, I'll
2003 Jan 18
2
[patch 2.4] Fix ext3 scheduling storm and lockup
...N fs/jbd/transaction.c~ext3-scheduling-storm fs/jbd/transaction.c
--- 24/fs/jbd/transaction.c~ext3-scheduling-storm 2003-01-16 02:45:19.000000000 -0800
+++ 24-akpm/fs/jbd/transaction.c 2003-01-16 02:45:19.000000000 -0800
@@ -669,7 +669,8 @@ repeat:
spin_unlock(&journal_datalist_lock);
unlock_journal(journal);
/* commit wakes up all shadow buffers after IO */
- sleep_on(&jh2bh(jh)->b_wait);
+ wait_event(jh2bh(jh)->b_wait,
+ jh->b_jlist != BJ_Shadow);
lock_journal(journal);
goto repeat;
}
_