From owner-freebsd-questions@FreeBSD.ORG Thu Dec 24 09:06:56 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 233AA106566B for ; Thu, 24 Dec 2009 09:06:56 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id D821D8FC1E for ; Thu, 24 Dec 2009 09:06:55 +0000 (UTC) Received: from r55.edvax.de (port-92-195-26-31.dynamic.qsc.de [92.195.26.31]) by mx01.qsc.de (Postfix) with ESMTP id 7DA2B3C86B; Thu, 24 Dec 2009 10:06:54 +0100 (CET) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id nBO96qtU001637; Thu, 24 Dec 2009 10:06:53 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Thu, 24 Dec 2009 10:06:52 +0100 From: Polytropon To: Rem P Roberti Message-Id: <20091224100652.35598f38.freebsd@edvax.de> In-Reply-To: <20091223230111.GA1188@bsd.remdog.net> References: <20091223230111.GA1188@bsd.remdog.net> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Subject: Re: What happened to /home? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 09:06:56 -0000 On Wed, 23 Dec 2009 15:01:11 -0800, Rem P Roberti wrote: > Today I booted my laptop and discovered that /home was gone. Well...not > exactly..but for all intents and purposes. The system isn't seeing it > although I can see it when I cd to /. But if I try and cd to /home from > there the system tells me "home:Not a directory." > What happened, and > what can I do about it? Do some diagnostics. First, check inode, using the ls -i command both for the symlink /home and its target /usr/home. Then use fdsb -i /dev/ad0s1a (or the proper device) and use "inode n" (with n = the inode number you discovered by the ls commands above) to check the information. Finally, but that may be risky, run fsck on all partitions that could be affected (e. g. if /home is on ad0s1a, but home data is on ad0s1h). I still have a problem like you described: I cannot cd to my home directory (/home/poly) with the same error message. The problem is: The home directories inode information is gone. It is still mentioned in the higher level inode (/home), but the inode this entry is pointing to isn't existing. Furthermore, all files inside this directory, at least those at the next lower level, refer to the inode with the "back-pointer", which references an inode non-existing. If any symlinks are involved, check them. Check "file x" (with x = the directory name) to see what it is. I hope you won't see something like % cd mnt/poly mnt/poly: Not a directory. % file mnt/poly mnt/poly: cannot open `mnt/poly' (Bad file descriptor) Do you have the Midnight Commander installed? If your /home line is given red color and preceded by a "?", size 0, and dated Jan 1 1970, then... well... it indicates a problem some way similar to mine... Good luck! I hope you have good backups. That's not an impolite joke. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...