From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] /lib/rfc
Date: Fri, 2 May 2008 11:27:09 -0400 [thread overview]
Message-ID: <e2050e3885474bd523029dbe921508ca@coraid.com> (raw)
In-Reply-To: <4df9fa23fb84158408fd7ed61bc15fb4@quanstro.net>
> > Yes, /lib/rfc/grabfc. Uncomment this line:
> >
> > /cron/sys/cron:#30 9 * * * local /lib/rfc/grabrfc
>
> thank you. unfortunately, it turns out that this script causes
> something that looks like deadlock between ramfs and ftpfs.
> i didn't get a bead on ramfs before ftpfs exited but it was in
> state Pread as was ramfs.
>
> here's where ftpfs was
>
> tyty# cd /proc/389580
> tyty# cat fd
> /lib/rfc
> 0 r c 0 (000000000000000a 0 00) 0 0 /dev/null
> 1 w c 0 (000000000000000a 0 00) 0 0 /dev/null
> 2 w M 256525 (0000000000000001 0 00) 8192 337626 /mnt/term/dev/cons
> 3 rw | 0 (000000000023e801 0 00) 65536 17056533 #|/data
> 4 rw M 258155 (0000000000000141 0 00) 8192 7835 /tmp/ftpo0000389580
> 5 r c 0 (0000000000000001 0 00) 0 75912 /dev/bintime
> 6 rw M 258155 (0000000000000142 0 00) 8192 83648 /tmp/ftp00000389580
> 7 rw I 1 (00000000000201ad 0 00) 0 86141 /net.alt/tcp/13/data
> 8 rw M 258155 (0000000000000143 0 00) 8192 156468 /tmp/ftpa0000389580
> 9 rw M 258155 (0000000000000144 0 00) 8192 24637 /tmp/ftpb0000389580
[...]
actually, i tracked this a bit further. the passive connection
gets crossed up. if killed in this state, ftpfs will exit with
part of the downloading file in its exit status. this only happens
with larger files.
- erik
next prev parent reply other threads:[~2008-05-02 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 17:11 erik quanstrom
2008-04-22 17:44 ` geoff
2008-04-22 21:38 ` erik quanstrom
2008-05-02 15:27 ` erik quanstrom [this message]
2008-04-22 17:46 ` Lyndon Nerenberg
2008-04-22 17:47 ` Lyndon Nerenberg
2008-04-22 17:50 john
2008-04-22 18:58 ` erik quanstrom
2008-04-22 19:12 ` Francisco J Ballesteros
2008-04-22 20:05 ` Gorka Guardiola
2008-04-22 20:27 ` Francisco J Ballesteros
2008-04-22 21:26 ` Charles Forsyth
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=e2050e3885474bd523029dbe921508ca@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).