Date: Sat, 15 Aug 2020 12:30:09 -0700 From: Matthew Macy <mmacy@freebsd.org> To: Daniel Nebdal <dnebdal@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org>, freebsd-fs <freebsd-fs@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: CFT for vendor openzfs - week 5 reminder + memdisk images Message-ID: <CAPrugNpKVqNbL25wPQN88Fxam=87PcXW7ZiaSugO=H7e_C0ZmA@mail.gmail.com> In-Reply-To: <CA%2Bt49PLE=RYKKF8y=R9nON4LGq95B8W8TBK7pe8rLTnnrnotkQ@mail.gmail.com> References: <CAPrugNqP655r%2BARuP=3QnuO=aTk_UK7wgN_1nt-_T8aV2i_veg@mail.gmail.com> <CA%2Bt49PLE=RYKKF8y=R9nON4LGq95B8W8TBK7pe8rLTnnrnotkQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Hi. I have some problems downloading the amd64 image: > > baymax /home/djn > fetch -a > https://people.freebsd.org/~freqlabs/freebsd-openzfs/latest/freebsd-openzfs-amd64-2020081100-memstick.img.xz > freebsd-openzfs-amd64-2020081100-memstick.img. 19% of 655 MB 2179 kBps 04m07s > fetch: freebsd-openzfs-amd64-2020081100-memstick.img.xz appears to be > truncated: 134152192/687158140 bytes > baymax /home/djn > fetch -ar > https://people.freebsd.org/~freqlabs/freebsd-openzfs/latest/freebsd-openzfs-amd64-2020081100-memstick.img.xz > freebsd-openzfs-amd64-2020081100-memstick.img. 20% of 655 MB 882 kBps 09m10s > fetch: freebsd-openzfs-amd64-2020081100-memstick.img.xz appears to be > truncated: 139132928/687158140 bytes > baymax /home/djn > fetch -ar > https://people.freebsd.org/~freqlabs/freebsd-openzfs/latest/freebsd-openzfs-amd64-2020081100-memstick.img.xz > freebsd-openzfs-amd64-2020081100-memstick.img. 20% of 655 MB 647 kBps 12m23s > fetch: freebsd-openzfs-amd64-2020081100-memstick.img.xz appears to be > truncated: 142065664/687158140 bytes > baymax /home/djn > > > It also fails using Firefox on windows on a different machine. (It's > also much slower from that machine, about 200 kB/sec. I have no idea > if that's relevant.) Yes, this appears to have been going on for at least the last week. The FreeBSD infrastructure directly available to developers appears to be unreliable for serving large files. Individuals with accounts on freefall have been able to scp the files. It's possible that we may just end up sharing images more widely by way of releng generated images after commit. I'll see if there's an alternative for the last week of the CFT. Cheers. -M > > -- > Daniel Nebdal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPrugNpKVqNbL25wPQN88Fxam=87PcXW7ZiaSugO=H7e_C0ZmA>