From: Matti Aarnio <matti.aarnio@zmailer.org>
To: LA Walsh <law@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 'dd' local works, but not over net, help as to why?
Date: Tue, 2 Oct 2001 11:53:02 +0300 [thread overview]
Message-ID: <20011002115302.L1144@mea-ext.zmailer.org> (raw)
In-Reply-To: <20011002112005.K1144@mea-ext.zmailer.org> <NDBBJDKDKDGCIJFBPLFHAEKACGAA.law@sgi.com>
In-Reply-To: <NDBBJDKDKDGCIJFBPLFHAEKACGAA.law@sgi.com>; from law@sgi.com on Tue, Oct 02, 2001 at 01:35:28AM -0700
On Tue, Oct 02, 2001 at 01:35:28AM -0700, LA Walsh wrote:
> > You are missing one 'dd' from the other system side, but
> > are you also sure that the remote system can support large
> > files, and that the dd in there does support large files ?
> ---
> Missing 'dd' typo. It's on the other system I tried copying the 8G
> to a slightly large 9G partition -- that worked. On the source system
> I can copy 8G to another 8G partition. Just running them over rsh seems to
> be a problem. Same version of 'dd' on each side (SuSE 7.2).
There could be something amiss in the dd when feeding into a pipe
( 2G limit should not matter, but...)
Try following:
dd if=/dev/sdX | cat > /dev/null
Hmm.. And also:
dd if=/dev/sdX | rsh other-host dd of=/dev/null
> Maybe I can fool ftp with symlinks tomorrow into doing the copy and see
> if that works. Just for fun I tried 'cat' as well -- same error -- out of
> space on target.
'cat' local or remote ?
> It transfers a lot of data -- right around 2G the first time I tried it, so
> it looked awfully suspicious.
Yes, suspicuous about something in the rsh barfing.
> Linda
/Matti Aarnio
next prev parent reply other threads:[~2001-10-02 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 7:52 LA Walsh
2001-10-02 8:20 ` Matti Aarnio
2001-10-02 8:35 ` LA Walsh
2001-10-02 8:53 ` Matti Aarnio [this message]
2001-10-02 9:21 ` Alistair Riddell
[not found] <mailman.1002009301.30795.linux-kernel2news@redhat.com>
2001-10-02 17:22 ` Pete Zaitcev
2001-10-02 18:18 ` 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=20011002115302.L1144@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=law@sgi.com \
--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®