9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Using cwfs
Date: Thu, 27 Aug 2009 16:09:01 +0200	[thread overview]
Message-ID: <8ccc8ba40908270709g3d20b02ck92acf7c6421fd0e0@mail.gmail.com> (raw)
In-Reply-To: <37dfb242c86fe96df379b53ffb630bd0@quanstro.net>

The disk and controllers are doing almost nothing regarding
suspend. that's a  bug. we'll have to go again over it to add the
bits needed to handle suspend/resume of usb ports and devices
in the right way.

regarding the error I don't know what it could be.
but in any case it shouldn't be %r as Erik said.


On Thu, Aug 27, 2009 at 5:29 AM, erik quanstrom<quanstro@quanstro.net> wrote:
>> wrenread: error on w0(1691022): %r
>
> something's wrong here.  %r never prints "%r"
> unless errstr is literaly "%r".  does your source
> match sources?
>
>> where w0 is the disk itself. Note that the final message
>> states 89805 blocks were copied, whereas initially
>> 89806 blocks were queued - was the error on just this one
>> block? If so, what could possibly be the reason? I doubt
>> my USB drive would be acting up.
>
> why couldn't your usb drive have a bad sector or some
> other problem?  you could even get less than the requested
> number of bytes without an error.  read(2) says that it's
> perfectly fine for pread to return less than the requested
> number of bytes.  to be really safe, wrenread should use
> something like preadn.
>
> i would think that usb would be a bit antisocial if pread
> returned less than the requested number of bytes if
> RBUFSIZE <= 64k.  but otoh, if it really is a hardware
> limit, it would make sense.  we'd just call the hardware
> antisocial in that case.  ☺
>
> - erik
>
>



  reply	other threads:[~2009-08-27 14:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-23  7:37 Akshat Kumar
2009-08-23 12:54 ` erik quanstrom
2009-08-23 13:07 ` Anthony Sorace
2009-08-23 20:05   ` Akshat Kumar
2009-08-24  1:45     ` Akshat Kumar
2009-08-24  2:11       ` Akshat Kumar
2009-08-24  3:27         ` erik quanstrom
2009-08-24  3:53           ` Akshat Kumar
2009-08-24 11:10             ` Mathieu L.
2009-08-25 20:55               ` erik quanstrom
2009-08-24 20:38             ` Akshat Kumar
2009-08-24 22:13               ` cinap_lenrek
2009-08-25 20:56             ` erik quanstrom
2009-08-27  1:24               ` Akshat Kumar
2009-08-27  3:29                 ` erik quanstrom
2009-08-27 14:09                   ` Francisco J Ballesteros [this message]
2009-08-27 14:16                     ` erik quanstrom

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=8ccc8ba40908270709g3d20b02ck92acf7c6421fd0e0@mail.gmail.com \
    --to=nemo@lsub.org \
    --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).