From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9PI kernel stability
Date: Mon, 9 Feb 2015 15:52:57 +0000 [thread overview]
Message-ID: <6c32917d6e26e91710344664d5f9bde3@hamnavoe.com> (raw)
In-Reply-To: <e89441254e792a4c8ba8314311a6ee21@posteo.de>
>>> 2. When writing large files to an USB memory stick FAT file system
>>> (say,
>>> a large TAR archive), the mount is lost, leading to a truncated file.
>>
>> Try putting the memory stick on a powered usb hub and see if that works
>> better.
>
> I did, and for this reason I suspect the USB driver and not the power
> supply.
Where is the large file coming from? I've just copied some 100MB files
from /dev/zero and from a 9p server to /n/sdU0.0, with no problem.
Maybe something about your particular memory stick is less compatible
with Plan 9?
next prev parent reply other threads:[~2015-02-09 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 8:23 Dante
2015-02-09 9:48 ` Richard Miller
2015-02-09 13:58 ` Dante
2015-02-09 15:52 ` Richard Miller [this message]
2015-02-09 18:20 ` Dante
2015-02-09 22:41 ` Lyndon Nerenberg
2015-02-10 8:27 ` Dante
2015-02-10 14:00 ` erik quanstrom
2015-02-10 14:44 ` Dante
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=6c32917d6e26e91710344664d5f9bde3@hamnavoe.com \
--to=9fans@hamnavoe.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).