search for: blocknr

Hello. On a server running 2.4.25, I have the two following errors in the kernel logfile: Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) Should I worry about them (disk failure, filesystem damage) ? Thanks. As an addition what does the pair '08:11' means ? Is this the major/minor of the hard disk partition where the filesystem...

On my Debian box: Package: lilo Version: 1:22.2-5 Severity: normal lilo seems to cause a kernel warning (see subject) when / is a ext3 partition. Maybe a kernel problem? Who knows. I'm running 2.4.19-rc1-ac7 -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux hummus 2.4.19-rc1-ac7 #1 Wed Jul 17 22:14:20 CEST 2002 i686 Locale: LANG=C, LC_CTYPE=C Versions

...ly = >defined once. Yes, I'm sure. I wrote the Pass and the RegisterPass also in a .cpp file, like this: #include<vector> #include"llvm/Pass.h" #include"llvm/Function.h" #include"llvm/BasicBlock.h" #include"llvm/Instruction.h" #include"../blockNrs/blockNrs.h" #include"GenomManager.h" using namespace std; using namespace llvm; namespace { class FunctionAnalysis : public FunctionPass { public: static char ID; FunctionAnalysis() : FunctionPass((intptr_t)&ID) {} // Konstruktor ruft Funktionsdurchlauf auf ~Fu...

...ournal.c =================================================================== --- src/journal.c (revision 1014) +++ src/journal.c (working copy) @@ -583,8 +583,7 @@ * turned off later. */ LOG_ERROR_ARGS("block %lu was modified but never " "dirtied!\n", co->blocknr); - bh = getblk(OCFS_GET_BLOCKDEV(osb->sb), co->blocknr, - osb->sect_size); + bh = sb_getblk(osb->sb, co->blocknr); if (bh == NULL) BUG(); Index: src/file.c =================================================================== --- src/file.c (revision 1014) +++ sr...

...he applications being used are MySQL, Postfix, and a mail filtering application which operates on postfix queue files using mmaped IO. Shortly before the crash, the following messages are logged: Mar 2 14:15:30 test5 kernel: Unexpected dirty buffer encountered at do_get_write_access:618 (03:05 blocknr 3688784) Mar 2 14:16:04 test5 kernel: Unexpected dirty buffer encountered at do_get_write_access:618 (03:05 blocknr 3616336) Mar 2 14:18:38 test5 kernel: Unexpected dirty buffer encountered at do_get_write_access:618 (03:05 blocknr 3692808) I've duplicated it in 2.4.22 and 2.4.25. Here...

...1-full/fs/jbd/revoke.c.old 2005-06-14 03:58:36.000000000 +0200 +++ linux-2.6.12-rc6-mm1-full/fs/jbd/revoke.c 2005-06-14 03:58:41.000000000 +0200 @@ -116,7 +116,8 @@ (block << (hash_shift - 12))) & (table->hash_size - 1); } -int insert_revoke_hash(journal_t *journal, unsigned long blocknr, tid_t seq) +static int insert_revoke_hash(journal_t *journal, unsigned long blocknr, + tid_t seq) { struct list_head *hash_list; struct jbd_revoke_record_s *record;

...gt;used are MySQL, Postfix, and a mail filtering application which operates >on postfix queue files using mmaped IO. > >Shortly before the crash, the following messages are logged: >Mar 2 14:15:30 test5 kernel: Unexpected dirty buffer encountered at >do_get_write_access:618 (03:05 blocknr 3688784) >Mar 2 14:16:04 test5 kernel: Unexpected dirty buffer encountered at >do_get_write_access:618 (03:05 blocknr 3616336) >Mar 2 14:18:38 test5 kernel: Unexpected dirty buffer encountered at >do_get_write_access:618 (03:05 blocknr 3692808) > >I've duplicated it in 2.4...

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

...1-full/fs/jbd/revoke.c.old 2005-06-14 03:58:36.000000000 +0200 +++ linux-2.6.12-rc6-mm1-full/fs/jbd/revoke.c 2005-06-14 03:58:41.000000000 +0200 @@ -116,7 +116,8 @@ (block << (hash_shift - 12))) & (table->hash_size - 1); } -int insert_revoke_hash(journal_t *journal, unsigned long blocknr, tid_t seq) +static int insert_revoke_hash(journal_t *journal, unsigned long blocknr, + tid_t seq) { struct list_head *hash_list; struct jbd_revoke_record_s *record; --- linux-2.6.13-rc3-mm1-full/fs/jbd/journal.c.old 2005-07-19 15:53:16.000000000 +0200 +++ linux-2.6.13-rc3-mm1-full/fs...

Hello, I am not subscribed to this mailing list. My apologies if non-members are not allowed to post in this forum. I have a Linux-2.4.19pre10aa4 computer and I have seen an error message "Unexpected dirty buffer encountered at do_get_write_access:598 (03:05 blocknr 0)" appears in the log. With a little bit of research I found that this message is printed from fs/jbd/journal.c, and understood that it comes out of EXT3 fs. I am afraid I don't have enough knowledge of C and Linux Kernel/EXT3 to debug this message. I have seen Andrea's change lo...

Hi!! This is my first time with llvm. I'm still learning and really need help. I wrote only one Function Pass, which uses another Function Pass (blockNrs), and registered this: RegisterPass<FunctionAnalysis> X("gasched", "Genom Scheduling Pass"); When I compile my sourcecode, everything was okay. But when I tried to test it, i got this error Message: nicole at fpga3:~/test$ make opt -load /iss/fpga3/nicole/llvm-2.2/Debu...

...3-full/fs/jbd/revoke.c.old 2005-04-21 03:44:18.000000000 +0200 +++ linux-2.6.12-rc2-mm3-full/fs/jbd/revoke.c 2005-04-21 03:44:31.000000000 +0200 @@ -116,7 +116,8 @@ (block << (hash_shift - 12))) & (table->hash_size - 1); } -int insert_revoke_hash(journal_t *journal, unsigned long blocknr, tid_t seq) +static int insert_revoke_hash(journal_t *journal, unsigned long blocknr, + tid_t seq) { struct list_head *hash_list; struct jbd_revoke_record_s *record;

Hi!! This is my first time with llvm. I'm still learning and really need help. I wrote only one Function Pass, which uses another Function Pass (blockNrs), and registered this: RegisterPass<FunctionAnalysis> X("gasched", "Genom Scheduling Pass"); When I compile my sourcecode, everything was okay. But when I tried to test it, i got this error Message: nicole at fpga3:~/test$ make opt -load /iss/fpga3/nicole/llvm-2.2/Debu...

...ease check if it works well in kernel 2.6.x. ------------------------------------------------------- --- linux-2.6.4a/fs/jbd/journal.c 2004-03-19 10:40:49.264613984 +0800 +++ linux-2.6.4/fs/jbd/journal.c 2004-03-19 10:41:12.091143824 +0800 @@ -832,10 +832,10 @@ bh = __getblk(journal->j_dev, blocknr, journal->j_blocksize); lock_buffer(bh); memset (bh->b_data, 0, journal->j_blocksize); - BUFFER_TRACE(bh, "marking dirty"); - mark_buffer_dirty(bh); BUFFER_TRACE(bh, "marking uptodate"); set_buffer_uptodate(bh); + BUFFER_TRACE(bh, "marking dirty&quot...

...I notice that the function journal_init_dev() sets the value journal->j_blk_offset = start This means that start can be any arbitrary block number on the device. However, later in the function journal_bmap() it is never actually used. The value of *retp in journal_bmap() is set to *retp = blocknr; /* + journal->j_blk_offset */ A comment on the top of journal_bmap() says that the addition can be included in the above operation if so be the need. Is there any specific reason (related to performance etc) why it has not been done. Please let me know. Thanks Abhishek

...>> root@(none)$ rm test >>>> [ 21.006549] EXT4-fs error (device sda): ext4_mb_generate_buddy:758: group 18 >>>> , block bitmap and bg descriptor inconsistent: 26464 vs 25600 free clusters >>>> [ 21.008249] JBD2: Spotted dirty metadata buffer (dev = sda, blocknr = 0). Th >>>> ere's a risk of filesystem corruption in case of system crash. >>>> >>>> Any special notes of using ext4 in qemu? >>> >>> Ext4 has more runtime consistency checking than ext2. So just because >>> ext4 complains doesn&...

...>> root@(none)$ rm test >>>> [ 21.006549] EXT4-fs error (device sda): ext4_mb_generate_buddy:758: group 18 >>>> , block bitmap and bg descriptor inconsistent: 26464 vs 25600 free clusters >>>> [ 21.008249] JBD2: Spotted dirty metadata buffer (dev = sda, blocknr = 0). Th >>>> ere's a risk of filesystem corruption in case of system crash. >>>> >>>> Any special notes of using ext4 in qemu? >>> >>> Ext4 has more runtime consistency checking than ext2. So just because >>> ext4 complains doesn&...

...u64 size, char *data); - int add_file_disk_extent(struct extent_iterate_data *priv, u64 file_off, u64 disk_off, u64 size) { @@ -861,510 +639,6 @@ int add_file_mem_extent(struct extent_iterate_data *priv, u64 file_off, return 0; } -static int __block_iterate_proc(ext2_filsys fs, blk_t *blocknr, - e2_blkcnt_t blockcnt, blk_t ref_block, - int ref_offset, void *priv_data) -{ - struct extent_iterate_data *idata; - idata = (struct extent_iterate_data *)priv_data; - u64 blocksize = fs->blocksize; - int ret = add_file_disk_extent(idata, blocksize * blockcnt, - b...

This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_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

...dio->logical_offset_in_bio); dio->bio = NULL; dio->boundary = 0; + dio->logical_offset_in_bio = 0; } /* @@ -701,6 +721,7 @@ submit_page_section(struct dio *dio, struct page *page, dio->cur_page_offset = offset; dio->cur_page_len = len; dio->cur_page_block = blocknr; + dio->cur_page_fs_offset = dio->block_in_file << dio->blkbits; out: return ret; } @@ -935,7 +956,7 @@ static ssize_t direct_io_worker(int rw, struct kiocb *iocb, struct inode *inode, const struct iovec *iov, loff_t offset, unsigned long nr_segs, unsigned blkbits, get_blo...