search for: sleep_on

...with an external journal, and accessed mostly via NFS. v1 quotas are enabled. The stacktrace lines below are from a lightly editted "echo t > /proc/sysrq-trigger" output. A substantial number of nfsd threads a waiting to "start a handle": nfsd Call Trace: [sleep_on+75/124] [start_this_handle+205/368] [journal_start+149/196] [ext3_dirty_inode+116/268] [__mark_inode_dirty+50/168] [update_atime+75/80] [do_generic_file_read+1158/1172] [generic_file_read+147/400] [file_read_actor+0/224] [nfsd_read+477/636] [nfsd3_proc_r...

...[<c0107286>] kernel_thread [kernel] 0x26 [<f8a841f0>] nfsd [nfsd] 0x0 The qmail-local processes (that should be delivering mail to the data parition) are in the following state: qmail-local D C02F3488 2400 11369 13960 11371 11348 (NOTLB) Call Trace: [<c0118ecb>] sleep_on [kernel] 0x4b [<f885d225>] start_this_handle [jbd] 0xc5 [<f885d37d>] journal_start_Rsmp_89deb980 [jbd] 0xbd [<f887297e>] ext3_dirty_inode [ext3] 0x6e [<c014ce7e>] link_path_walk [kernel] 0xa3e [<c0156f2e>] __mark_inode_dirty [kernel] 0x2e [<c01588b1>] updat...

I have ext3 0.0.6b + 2.2.19 and cannot get ext3 to compile as a module. If I try to modularize it, or turn in off completely, the kernel build fails. Is there an easy fix for this, or is there something that I am missing? Thanks. Peter

...keep quiet for the next couple releases :-) Greetings, Juri Test was with kernel 2.2.19pre9 + ext3-0.0.5e UP "normal" kjournald: kdb> btp 2024 EBP EIP Function(args) 0xc67bbfb0 0xc0111f23 schedule+0x157( 0xc7a8d81c, 0xc7a8d7e0) 0xc67bbfc8 0xc01122b2 interruptible_sleep_on+0x36( ) 0xc67bbfec 0xc0154ec0 kjournald+0x11c( 0xc7a8d7e0, 0xc7a8d7e0, 0xc7a8d7e0, 0x0, 0x0) 0xc15a7e24 0xc010923f kernel_thread+0x23) 0xc01d8175 0x0 kernel_thread+0x3fef6de4) 0x8b9019eb 0x39480842 kernel_thread "locked up" kjournald: kdb> btb 1935 EBP EIP Functi...

When trying to build ext3 as a module, I get the follwing errors during the kernel link: /usr/bin/kgcc -D__KERNEL__ -I/home/brian/src/kernel-2.2.19-pre6mvd/linux-2.2.19pre6-kdb-ext3/include -c -o dummy_sym.o dummy_sym.c ld -m elf_i386 -T /home/brian/src/kernel-2.2.19-pre6mvd/linux-2.2.19pre6-kdb-ext3/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_t ask.o -Map map

...m.patch Anyone who is using tasks which have realtime scheduling policy on ext3 systems should apply this change. Details: At the start of do_get_write_access() we have this logic: repeat: lock_buffer(jh->bh); ... unlock_buffer(jh->bh); ... if (jh->j_list == BJ_Shadow) { sleep_on_buffer(jh->bh); goto repeat; } The problem is that the unlock_buffer() will wake up anyone who is sleeping in the sleep_on_buffer(). So if task A is asleep in sleep_on_buffer() and task B now runs do_get_write_access(), task B will wake task A by accident. Task B will then sleep on the b...

...vent_interruptible_timeout(smbiod_wait, 0, 10*HZ); + smb_lock_server(server); + if (signal_pending(current)) + printk(KERN_INFO "smb_retry: caught signal\n"); +#else + /* + * We don't want to be interrupted. For example, what if 'current' + * already has received a signal? sleep_on would terminate immediately + * and smbmount would not be able to re-establish connection. + * + * smbmount should be able to reconnect later, but it can't because + * it will get an -EIO on attempts to open the mountpoint! + * + * FIXME: go back to the interruptable version now that smbm...

...ied commit to complete. * The caller may not hold the journal lock. */ -void log_wait_commit (journal_t *journal, tid_t tid) +int log_wait_commit (journal_t *journal, tid_t tid) { + int err = 0; + lock_kernel(); #ifdef CONFIG_JBD_DEBUG lock_journal(journal); @@ -600,6 +602,12 @@ sleep_on(&journal->j_wait_done_commit); } unlock_kernel(); + + if (unlikely(is_journal_aborted(journal))) { + printk(KERN_EMERG "journal commit I/O error\n"); + err = -EIO; + } + return err; } /* @@ -1326,7 +1334,7 @@ /* Wait for the log commit to complete... */ if (tran...