mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nuno Ferreira <nuno.ferreira@graycell.biz>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Process hangs on blk_congestion_wait copying large file to cifs filesystem
Date: Fri, 28 May 2004 17:04:20 +0100	[thread overview]
Message-ID: <1085760260.2422.11.camel@taz.graycell.biz> (raw)
In-Reply-To: <20040528142239.GK20657@suse.de>

On Sex, 2004-05-28 at 16:22 +0200, Jens Axboe wrote:
> On Fri, May 28 2004, Nuno Ferreira wrote:
> > On Qui, 2004-05-27 at 16:45 +0100, Nuno Ferreira wrote:
> > > Hi,
> > > I'm trying to copy a large file (200Mb or bigger) from an ext3
> > > filesystem to a windows share mounted using CIFS and the cp process
> > > hangs, sometimes for a long time (several minutes).
> > > Calling ps, I can see that it's blocking on blk_congestion_wait. 
[...]
> 
> A sysrq-t back trace of that process would be interesting to see.

OK, apparently now the cp never finishes and nothing gets written to
disk, so i could not get the full output from sysrq-t.
I wrote the call stack from the process, it that enough?
The call stack from the cp process:
__make_request
schedule_timeout
process_timeout
io_schedule_timeout
blk_congestion_wait
autoremove_wake_function
autoremove_wake_function
get_dirty_limits
balance_dirty_pages
generic_file_aio_write_nolock
__copy_to_user_ll
file_read_actor
__generic_file_aio_read
file_read_actor
generic_file_write_nolock
do_sync_read
do_IRQ
common_interrupt
generic_file_write
cifs_write_wrapper
do_sync_read
vfs_write
sys_write
syscall_call

Also the call from a vi process that was called after the cp reached
that state and was also blocked
schedule_timeout
ext3_mark_inode_dirty
process_timeout
io_schedule_timeout
blk_congestion_wait
autoremove_wake_function
get_dirty_limits
balance_dirty_pages
generic_file_aio_write_nolock
buffered_rmqueue
__alloc_pages
generic_file_aio_write
ext2_file_write
do_sync_write
do_lookup
path_release
sys_access
vfs_write
sys_write
syscall_call

If more detail is needed I can try to capture it but syslog not writing
to disk I don't know how to capture the sysrq-t output

Thanks
-- 
Nuno Ferreira


  reply	other threads:[~2004-05-28 16:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 15:45 Nuno Ferreira
2004-05-28 14:07 ` Nuno Ferreira
2004-05-28 14:22   ` Jens Axboe
2004-05-28 16:04     ` Nuno Ferreira [this message]
2004-06-03 14:30       ` Nuno Ferreira
2004-06-23 11:44       ` Process hangs " Nuno Ferreira

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1085760260.2422.11.camel@taz.graycell.biz \
    --to=nuno.ferreira@graycell.biz \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®