search for: ll_rw_blk

...ce to `jfs_preclean_buffer_check' fs/fs.o: In function `set_blocksize': fs/fs.o(.text+0x300e): undefined reference to `jfs_preclean_buffer_check' fs/fs.o: In function `refile_buffer': fs/fs.o(.text+0x341f): undefined reference to `journal_remove_checkpoint' drivers/block/block.a(ll_rw_blk.o): In function `add_request': ll_rw_blk.o(.text+0x568): undefined reference to `jfs_preclean_buffer_check' drivers/block/block.a(ll_rw_blk.o): In function `make_request': ll_rw_blk.o(.text+0x75b): undefined reference to `jfs_prelock_buffer_check' ll_rw_blk.o(.text+0xced): undefined...

We've just started getting this. We're running 5.10, kernel 2.6.32-358.18.1.el6.x86_64. Anyone else seen anything like this, or have any ideas? mark Nov 1 14:34:21 <server> kernel: WARNING: at block/ll_rw_blk.c:543 blk_do_ordered() Nov 1 14:34:21 <server> kernel: Nov 1 14:34:21 <server> kernel: Call Trace: Nov 1 14:34:22 <server> kernel: [<ffffffff8014defa>] blk_do_ordered+0x27a/0x2b3 Nov 1 14:34:22 <server> kernel: [<ffffffff8014ac82>] elv_next_request+0x13e/0x...

...bd.org/>),as soon as I try to write to one of its devices, causes "Badness" in the kernel and, ultimately, a spontaneous reboot. Under non-xen 2.6.10-1.1109_FC4 and 2.6.9-1.678_FC3, drbd works fine. The error: Jan 25 21:01:23 turing kernel: Badness in blk_plug_device at drivers/block/ll_rw_blk.c:1217 Jan 25 21:01:23 turing kernel: [<c022942a>] blk_plug_device+0x2e/0x65 Jan 25 21:01:23 turing kernel: [<c8985884>] drbd_make_request_common+0x4a6/0x8b9 [drbd] Jan 25 21:01:23 turing kernel: [<c016abea>] do_open+0xc5/0x2de Jan 25 21:01:23 turing kernel: [<c0146e40>]...

From: Rusty Russell <rusty@rustcorp.com.au> Lguest block driver A simple block driver for lguest. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Cc: Jens Axboe <jens.axboe@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> --- drivers/block/Makefile | 1 drivers/block/lguest_blk.c | 271

From: Rusty Russell <rusty@rustcorp.com.au> Lguest block driver A simple block driver for lguest. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Cc: Jens Axboe <jens.axboe@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> --- drivers/block/Makefile | 1 drivers/block/lguest_blk.c | 271

...-- --do-what-I-say primary all Check everything looks fine: # dmesg | tail ; cat /proc/drbd Make the filesystem: # mkfs.ext3 /dev/drbd0 Mount: # mount /dev/drbd0 /mnt/drbd0 Then I get the following kernel messages: Nov 1 13:52:13 localhost kernel: Badness in blk_plug_device at drivers/block/ll_rw_blk.c:1217 Nov 1 13:52:13 localhost kernel: [blk_plug_device+128/144] blk_plug_device+0x80/0x90 Nov 1 13:52:13 localhost kernel: [pg0+140817474/1002423296] drbd_make_request_common+0x6f2/0x8a0 [drbd] Nov 1 13:52:13 localhost kernel: [mempool_alloc+115/432] mempool_alloc+0x73/0x1b0 Nov 1 13...

...ion is regarding how disk errors are reported to ext3. From my basic understanding of the block driver routines, it seems that all the different types of disk errors (like sector failures, scsi bus timeout, etc) are converted into one single error code (EIO) and passed on to the file system (by the ll_rw_blk.c) So, irrespective of whether the underlying device is a SCSI or IDE, the disk errors are going to be reported as EIO to ext3, right ? Does anyone have any input on how this occurs in other open source operating systems ? I appreciate any help regarding this. Thanks much. Vijayan

Hi, with being exposed to more and more failed hard disks reports, I've accumulated several questions of the logged messages in /var/log/messages file: like how to identifying failed disks(partitions), where is the exact failed sector(s) on the hard disk, and why badblocks reports OK to the reported disk failure. Let me explained the above with the following several example. scenario #1, a

Lo, Is there already a patch out for latest 2.4.6-ac release? I'm pretty sure that the ext3 patch -ac2 can not be applied on this release. Bye. -- the trees the birds the air the grass the water the flies the trees

...tpoll interface. We need to have this facility to cleanup diff -r 489f28021f26 -r 105d5d6b4e0d patches/linux-2.6.16.33/scsi-target.patch --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/patches/linux-2.6.16.33/scsi-target.patch Wed Jan 03 01:34:02 2007 +0900 @@ -0,0 +1,3571 @@ +diff --git a/block/ll_rw_blk.c b/block/ll_rw_blk.c +index 1ce88cf..c631d5a 100644 +--- a/block/ll_rw_blk.c ++++ b/block/ll_rw_blk.c +@@ -2265,6 +2265,84 @@ void blk_insert_request(request_queue_t + + EXPORT_SYMBOL(blk_insert_request); + ++static int __blk_rq_unmap_user(struct bio *bio) ++{ ++ int ret = 0; ++ ++ if (bio) { ++...

...t blk_queue_ctx *ctx = req->queue_ctx; + + if (unlikely(!ctx)) return; if (unlikely(--req->ref_count)) return; - elv_completed_request(q, req); + elv_completed_request(req); /* this is a bio leak */ WARN_ON(req->bio != NULL); /* * Request may not have originated from ll_rw_blk. if not, * it didn't come out of our reserved rq pools */ if (req->cmd_flags & REQ_ALLOCED) { unsigned int flags = req->cmd_flags; BUG_ON(!list_empty(&req->queuelist)); BUG_ON(!hlist_unhashed(&req->hash)); - blk_free_request(q, req); - freed_reques...

...t blk_queue_ctx *ctx = req->queue_ctx; + + if (unlikely(!ctx)) return; if (unlikely(--req->ref_count)) return; - elv_completed_request(q, req); + elv_completed_request(req); /* this is a bio leak */ WARN_ON(req->bio != NULL); /* * Request may not have originated from ll_rw_blk. if not, * it didn't come out of our reserved rq pools */ if (req->cmd_flags & REQ_ALLOCED) { unsigned int flags = req->cmd_flags; BUG_ON(!list_empty(&req->queuelist)); BUG_ON(!hlist_unhashed(&req->hash)); - blk_free_request(q, req); - freed_reques...