From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs still looks for not existing devices
Date: 14 Oct 2011 17:43:00 +0200 [thread overview]
Message-ID: <BvpRYk9D1uB@helmut.hullen.de> (raw)
In-Reply-To: <20111014150824.GK21931@carfax.org.uk>
Hallo, Hugo,
Du meintest am 14.10.11:
>> I've just tried
>>
>> git clone git://git.darksatanic.net/repo/btrfs-progs-unstable.git
>>
>> and got the answer
>>
>> + git clone git://git.darksatanic.net/repo/btrfs-progs-unstable.git
>> git.darksatanic.net[0: 212.13.194.111]: errno=Connection refused
>> git.darksatanic.net[0: 2001:ba8:1f1:f1d9:216:3eff:fe14:aef9]:
>> errno=Network is unreachable fatal: unable to connect a socket
>> (Network is unreachable)
>>
>> -----------------------------
>>
>> Have I got just another typo (or user mistake), or is there another
>> problem?
> It seems to be OK for me from here (the server is in a totally
> different network to where I am), so I think it must be a problem
> local to you. The IP addresses (both v4 and v6) look like the right
> ones, and I'm not aware of having any blocking in place from my
> service provider. Do you have a "transparent" proxy in the way?
Changing from "git://" to "http://" solved the problem!
Compiling worked, see
<http://arktur.shuttle.de/CD/Testpakete/btrfs-progs-20111014-i486-1Mills_hln.txz>
But "btrfs filesystem show" still shows lots of nonexistent devices -
sorry.
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-10-14 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 13:51 btrfs still looks for not existing devices Helmut Hullen
2011-10-14 14:05 ` Hugo Mills
2011-10-14 14:17 ` Helmut Hullen
2011-10-14 14:59 ` Helmut Hullen
2011-10-14 15:08 ` Hugo Mills
[not found] ` <20111014151432.GA19381@mother.jarsat.pl>
2011-10-14 15:21 ` Hugo Mills
2011-10-14 15:43 ` Helmut Hullen [this message]
2011-10-14 21:26 ` Goffredo Baroncelli
2011-10-15 2:57 ` Helmut Hullen
2011-10-21 8:21 ` Helmut Hullen
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=BvpRYk9D1uB@helmut.hullen.de \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--cc=linux-btrfs@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