From: Duncan Roe <duncan_roe@optusnet.com.au>
To: cygwin@cygwin.com
Subject: Re: odd prob for cygwin 'dd' from a character device on network disk
Date: Thu, 10 Jun 2021 12:23:03 +1000 [thread overview]
Message-ID: <20210610022303.GA14223@dimstar.local.net> (raw)
In-Reply-To: <60C168AF.4070400@tlinx.org>
On Wed, Jun 09, 2021 at 06:19:43PM -0700, L A Walsh wrote:
> I've been using a character device on linux in my
> home directory named 'zero' that is a copy of the
> 'zero' device in /dev:
> crwxrwxrw- 1 1, 5 Jun 15 2015 zero
>
> to do read benchmarks using 'dd' (and write benchmarks
> using a file named 'null' thats a copy of /dev/null).
>
> I run it "occasionally", but not on a regular basis, since
> it stays a bit boring. Nevertheless, ballpark numbers
> consistent with historical norms verify correct network
> function (separate from read/write files). Read/write speeds
> at last check a few weeks ago were typical with
> reads at 700MB/s and writes at about 300MB/s.
>
> A few hours ago I tried it again due to some strange network
> probs where I seemed to be getting file xfer speeds as low
> as 200K/s.
>
> I tried the bench script, and its half broken now -- because
> I can no longer get anything back from the zero device
> on my server via the network. Locally, I can do 'dd' from
> /dev/zero (or the zero file) and it takes a few seconds and
> gave about 800MB/s. So seemed to have been working fine,
> but remotely -- still nada... reads 0 bytes from /dev/zero
> and about 300MB/s write speed.
>
> Can anyone think of anything that might have changed in
> cygwin such that it would know the remote device is a
> "/dev/zero". Wondered if the 'dd' prog might have changed,
> but just realize it did same with 'cat' as well.
>
> Anyway -- I'm a bit stumped as to possible causes...
> The writing to a remote /dev/null part is still working,
> so not sure why one would change and not the other.
>
> If anyone can think of anything, please let me know -- I'm
> also gonna ping the samba list and maybe my distro list
>
> Thanks!
> -linda
>
nfs / nodev?
next prev parent reply other threads:[~2021-06-10 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 1:19 L A Walsh
2021-06-10 2:23 ` Duncan Roe [this message]
2021-06-11 3:20 ` L A Walsh
2021-06-12 1:32 ` Duncan Roe
2021-06-14 23:34 ` L A Walsh
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=20210610022303.GA14223@dimstar.local.net \
--to=duncan_roe@optusnet.com.au \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).