search for: journal_s

Hi all, We have a problem with our system which is a Siemens PRIMERGY, 8xPentium III Xeon, 8GB Memory, 280GB HD, running as DB2 server. We have some kind of error message like below in /var/log/messages:

I've pushed a new tool called "virt-log" upstream, so you can now just do: virt-log -d Guest or: virt-log -a disk.img It will automatically fetch the journal or traditional syslog file as appropriate, and we can add Windows support in future. Unfortunately the journal_* API calls are rather slow because they have to fetch each single line from the journal. So there's

The following 6 patches cleanup the jbd code and kill about 200 lines. First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2. The rest of them can apply to 2.6.13-mm2. fs/jbd/checkpoint.c | 179 +++++++++++-------------------------------- fs/jbd/commit.c | 101 ++++++++++-------------- fs/jbd/journal.c | 11 +- fs/jbd/revoke.c | 158

Hi, I'm trying to make sense of the options for multiple comparisons options in R. I've found the following options: pairwise.t.test, which provides standard t-tests, with options for choosing an appropriate correction for multiple comparisons TukeyHSD, which provides the usual Tukey test glht(package multcomp), which provides a variety of options >From the help list, it appears

...ue_flush(journal->j_fs_dev, GFP_KERNEL, NULL); if (!(journal->j_flags & JBD2_ABORT)) jbd2_journal_update_superblock(journal, 1); diff --git a/fs/jbd2/commit.c b/fs/jbd2/commit.c index f3ad159..e90ec0d 100644 --- a/fs/jbd2/commit.c +++ b/fs/jbd2/commit.c @@ -134,8 +134,7 @@ static int journal_submit_commit_record(journal_t *journal, set_buffer_uptodate(bh); bh->b_end_io = journal_end_buffer_io_sync; - if (journal->j_flags & JBD2_BARRIER && - !JBD2_HAS_INCOMPAT_FEATURE(journal, + if (!JBD2_HAS_INCOMPAT_FEATURE(journal, JBD2_FEATURE_INCOMPAT_ASYNC_COM...

Heya, Thanks Rich for the hints on IRC about journal bindings for libguestfs. The below script is what I ended up with. At least I learnt how to iterate over the systemd journal entries. $ sudo python find-ip.py 192.162.122.118 Obviously, this only searches for the _first_ occurance of the IP address and doesn't take into account the guest may have acquired a new IP on a later

...17:57:39 boeaet34 kernel: ei.c, 663): ext3_orphan_addxtet_writopy 0 Aug 9 17:57:39 boeaet34 kernel: < force_l_dirty_metadat7e90 Aug 9 17:57:39 boeaet34 kernel: <77e6transaction.er_head 1de27f20, force_copy 0 Aug 9 17:57:39 boeaet34 kernel: <7, 525): do_get_w ssaction.cn, 1069):, 1069): jjournal_stop: Handle e: Newandle: Hl 117, free 714, 52ef0, force_copy, 1069): journa1de27ef0 Aug 9 17:57:39 boeaet34 kernel: <.c, 695): e_get_writournal_dirty_mr_get_write_acourn_get_wournal_dirty_mee_ 5transaction.c, 1069): journal_dirty_metadata: journal_head 1de27ec0 Aug 9 17:57:39 boeaet34 kernel: &...

...ing_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use atomic variables to avoid taking t_handle_lock in jbd2_journal_stop jbd2: Change j_state_lock to be a rwlock_t jbd2: Remove t_handle_lock from start_this_handle() fs/ext4/inode.c | 4 +- fs/ext4/super.c | 4 +- fs/jbd2/checkpoint.c | 18 +++--- fs/jbd2/commit.c | 42 ++++++------ fs/jbd2/journal.c | 94 +++++++++++++-------...