From owner-freebsd-questions@FreeBSD.ORG Mon Sep 10 14:19:11 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DBB72106566B for ; Mon, 10 Sep 2012 14:19:11 +0000 (UTC) (envelope-from pldrouin@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9E2B88FC12 for ; Mon, 10 Sep 2012 14:19:11 +0000 (UTC) Received: by iebc12 with SMTP id c12so4017945ieb.13 for ; Mon, 10 Sep 2012 07:19:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=e2ffpbksGe3dH05Y+ccB/Gcrxan43BEOFwDaoxd69oM=; b=jA140jYyixo1G5PjG0EaedzvHqGkoeNPSFDiMSAKsul2F0z8FTpAU/3E4DqgStv1GF pRIn2V5Bfgsq6PhCpoOXGCpk6pfcKpKb/6bHj7uLM65ivBwHDbod4HujlcG1fZ5ub62g 4wFsiM3InILAyeM9uqgZG5QEKZo0rb51argTTV8vPV59lI3ZLiBCeOUQq9J3uEg3/6ko goPaABt6XBjYEZjayw3pVYdU55lJFddLvSPn5oPRZfBnrGoUG+c2nzfz07QE5o2FLFfG 3FH8VjSIUSpI4s8vC5wrH5XwCMfByUtwWeI4qsAci0ZICEJkm921mzzh2S80so8RY4I0 gsDg== MIME-Version: 1.0 Received: by 10.50.155.129 with SMTP id vw1mr11424527igb.11.1347286750854; Mon, 10 Sep 2012 07:19:10 -0700 (PDT) Received: by 10.64.55.73 with HTTP; Mon, 10 Sep 2012 07:19:10 -0700 (PDT) In-Reply-To: <20120910154335.ebb08b66.freebsd@edvax.de> References: <20120910154335.ebb08b66.freebsd@edvax.de> Date: Mon, 10 Sep 2012 10:19:10 -0400 Message-ID: From: Pierre-Luc Drouin To: FreeBSD Questions Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: portsnap Generating a "Bad file descriptor" Error Message X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 14:19:12 -0000 Hi, Yes, files are written to the /var filesystem. I have tried fetching the file manually and I have even tried to newfs the partition again and to copy the files back. I also tried to delete the portsnap directory completely. None of this fixed the error. Note that I access the web through a proxy, but I tried untaring the file 86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgzand I did not get any error from tar, so I guess the file I got is not corrupted. On Mon, Sep 10, 2012 at 9:43 AM, Polytropon wrote: > On Mon, 10 Sep 2012 08:56:29 -0400, Pierre-Luc Drouin wrote: > > On Tue, Sep 4, 2012 at 10:14 AM, Pierre-Luc Drouin >wrote: > > > > > Hi, > > > > > > so I have been having problems using portsnap lately. I always get a > "Bad > > > file descriptor" message when trying using it on one of my i386 > machine: > > > > > > Looking up portsnap5.freebsd.org mirrors... none found. > > > Fetching snapshot tag from portsnap5.freebsd.org... done. > > > Fetching snapshot metadata... done. > > > Fetching snapshot generated at Mon Sep 3 20:04:44 EDT 2012: > > > 86abb3c6f24b24e7fdadda42805f9ae38f487177dcb949 0% of 67 MB 0 Bps > > > fetch: > > > > http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz > : > > > Bad file descriptor > > > fetch: > > > 86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz: > Bad > > > file descriptor > > > > > > I tried fsck -y the /var, /tmp and /usr partitions and everything seems > > > fine. What could the problem be? > > > > > > Thanks! > > > > > > > Hi, > > > > Anyone has an idea about what could be causing this problem? > > I'm not familiar enough with portsnap (I use CVS) so I can just > throw some guesses around: > > The message "Bad file descriptor" is issued by fetch and seems > to be for _your_ side of the connection, and I assume it is > regarding the place where the requested file will be fetched > to. I don't exactly know _where_ that is. It could be in > the ports tree or in a temporary location (from where the > results are then written to /usr/ports). The manpage mentions > a default workdir of /var/db/portsnap which is on the /var > partition. You checked that, no errors. > > Just check what /var/db/portsnap contains. In worst case, > remove portsnap/ and recreate that directory. I have no > idea what it is supposed to contain, maybe make a copy of > it. You could also try to manually create the file, e. g. > by issuing > > # touch > /var/db/portsnap/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz > > Look if the file is there. Use > > # stat > /var/db/portsnap/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz > > to check if everything is okay. > > You could also try to manually fetch the file using fetch or > maybe even wget, just to see if it can be downloaded and > written properly, to a different location, e. g. > > # cd /tmp > # fetch > http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz > > or > > # cd /tmp > # wget > http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz > > That should be _no_ problem (with the correct file name of course). > > Again, "Bad file descriptor" is often seen in relation to file > system trouble. I've seen that in the past myself. > > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... >