Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 4 May 2013 10:43:37 -0700 (PDT)
From:      Michael Bird <michael_bird@yahoo.com>
To:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   ls(1), rm(1) - No such file or directory even though they are there.
Message-ID:  <1367689417.83465.YahooMailNeo@web120006.mail.ne1.yahoo.com>

Next in thread | Raw E-Mail | Index | Archive | Help

Hi List,

There is a rather curious problem that I have, which I haven't encountered before.
I make regular backups of my packages and put them onto an external usb drive,
which is mounted read/write via sysutils/fusefs-ntfs.


Now these backups don't exist no more and at the same time they are there. That 
is to say, upon issuing ls and/or rm on the command line I get rather strange results. 
Here are some of my outputs:


mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls
[a long list that has been cut out]
zip-3.0.tbz
mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls zip-3.0.tbz 
ls: zip-3.0.tbz: No such file or directory

Some have files that (don't) exist have i-nodes and some haven't:

mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls -i zip-3.0.tbz 
ls: zip-3.0.tbz: No such file or directory
mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls -i linux-f10-tiff-3.8.2.tbz 
2469 linux-f10-tiff-3.8.2.tbz

Running rm on the folder I get "No such file or directory" for every single entry:

mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % rm *
[a long list that has been cut out]
rm: linux-f10-tiff-3.8.2.tbz: No such file or directory

Yet again some of the files can be test via gzip and some can't:

mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % gzip -t linux-f10-tiff-3.8.2.tbz
mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % echo $?
0
mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % gzip -t zip-3.0.tbz 
gzip: can't stat: zip-3.0.tbz: No such file or directory
mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages %


Looks like the this part of the file system is corrupt. I also booted the drive up under 
Windows and got the same result. The files are there, but can't be read, overwritten
or deleted.


What does the list say about the above mentioned?

Michael
From owner-freebsd-questions@FreeBSD.ORG  Sat May  4 18:22:54 2013
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id EB00C592
 for <freebsd-questions@FreeBSD.ORG>; Sat,  4 May 2013 18:22:54 +0000 (UTC)
 (envelope-from doug@safeport.com)
Received: from bucksport.safeport.com (bucksport.safeport.com
 [204.107.128.242])
 by mx1.freebsd.org (Postfix) with ESMTP id B6FAA9E4
 for <freebsd-questions@FreeBSD.ORG>; Sat,  4 May 2013 18:22:53 +0000 (UTC)
Received: from bucksport.safeport.com (bucksport.safeport.com
 [204.107.128.242])
 by bucksport.safeport.com (8.14.5/8.14.5) with ESMTP id r44I6XRV061724
 for <freebsd-questions@FreeBSD.ORG>; Sat, 4 May 2013 14:06:33 -0400 (EDT)
 (envelope-from doug@safeport.com)
Date: Sat, 4 May 2013 14:06:33 -0400 (EDT)
From: doug@safeport.com
To: freebsd-questions@FreeBSD.ORG
Subject: freebsd-update question
Message-ID: <alpine.BSF.2.00.1305041341120.59878@bucksport.safeport.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (bucksport.safeport.com [204.107.128.242]);
 Sat, 04 May 2013 14:06:33 -0400 (EDT)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2013 18:22:55 -0000

I had an 8.2 system that I wanted to take to 8.4. First I tried upgrade to 8.4, 
getting (in essence) can't do that. So I upgraded 8.2 which worked giving the 
end-of-life warning. But seemed work. I then did an upgrade to 8.3 with:

    freebsd-update -r 8.3-RELEASE upgrade

The first part, downloading the diffs and inspecting the system seemed ok. The 
install seemed ok up to the point it wanted to edit files. It wanted to edit 
freebsd.submit.cf and sendmail.cf neither of which had local changes and then it 
started wanting to delete all the files in /etc. I aborted the process when it 
got to rc.conf. The message was something like, "deleting file hosts.allow no 
longer in 8.3". Happily aborting the process left the system unchanged.

Aside from, what could I have done wrong? My question is should we be able to 
trust freebsd-update on expired systems if it says a mirror exists and then sets 
about doing its thing? Can this happen in the normal process of removing update 
'cruft' from the mirrors?

_____
Douglas Denault
http://www.safeport.com
doug@safeport.com
Voice: 301-217-9220
   Fax: 301-217-9277



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?1367689417.83465.YahooMailNeo>