Thanks a lot to:
-------------------------------------------------------
Ted Nolan SRI Ft Gordon <ted@ags.ga.erg.sri.com>
Hal Stern - Distinguished Systems Engineer
<stern@sunrise.east.sun.com>
kurt.stype@babss.com
"Daniel J Blander - Sr. Systems Engineer for ACS"
<Daniel.Blander@ACSacs.com>
Jeff Wasilko <jeffw@triple-i.com>
Matthias Kurz <mk@baerlap.north.de>
"Mark S. Anderson" <anderson@neon.mitre.org>
Patrick Wolfe <pwolfe@mcs.com>
George L Roman <george@dbms.com>
Gregory M Polanski <gmp@adc.com>
"Marks, Evan R" <A700102@aetna.com>
Jerry Weber <gldw@lanl.gov>
Herbert Wengatz <hwe@uebemc.siemens.de>
Vahsen Rob <vahsenr@ce.philips.nl>
Tim Boemker <tjb839@zacatecas.optimum.com>
Michael J. Shon {*Prof Services} Sun Rochester"
<mshon@sunrock.east.sun.com>
Rick Leir <rleir%aji@atlsci.com>
--------------------------------------------------------
Herbert Wengatz <hwe@uebemc.siemens.de> gives me the answer I want:
"At first, make an fsck over that filesystem, then an ls -i onto
the files and after that you can use "clri" on these files."
Some other suggestions are:
1) Move critical data out of the directory, and rm -r the whole directory
2) Using file manager
3) unlink
4) Some people think I have a "strange named" file, and give me some
suggestions and scripts to rm it, which I don't have.
-Judy
HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
Judy Huang
email:zh@cc.bellcore.com Tel:(908)699-3551 Beeper:(908)633-3181
Bellcore, 6 Corporate Place, Piscatway, NJ 08854-4199
HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:51 CDT