Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!sequoia!rpp386!jfh From: jfh@rpp386.cactus.org (John F Haugh II) Newsgroups: comp.unix.wizards Subject: Re: Help! There's a slash '/' in my filename. Message-ID: <19025@rpp386.cactus.org> Date: 5 Feb 91 13:36:49 GMT References: <821@nddsun1.sps.mot.com> <11714@helios.TAMU.EDU> <1991Feb3.041129.16590@uncle.uucp> Reply-To: jfh@rpp386.cactus.org (John F Haugh II) Distribution: comp Organization: Lone Star Cafe and BBS Service Lines: 23 X-Clever-Slogan: Recycle or Die. In article marc@arnor.uucp writes: >An alternative is to make a new directory with the same parent as the >bad one. Then HARD link all the other files into the new directory. >Then blow away the bad one. You will probably have to unlink the bad >directory to blow it away. Having done that, you should fsck the file >system to clean up. This is a lousey idea. By merely hard linking, and not moving, you will have a large number of link counts which must be corrected when the filesystem is cleaned. The most painless method is to move all the files and directories out of the directory with the bad entry, unmount the filesystem, zero out the directory's i-node, fsck the filesystem, remount, rename the new directory to the old name, then move the file from lost+found to the new directory with a less dangerous filename. fsdb and adb are best left to people who already knew the answer to this problem. -- John F. Haugh II UUCP: ...!cs.utexas.edu!rpp386!jfh Ma Bell: (512) 832-8832 Domain: jfh@rpp386.cactus.org "I've never written a device driver, but I have written a device driver manual" -- Robert Hartman, IDE Corp.