Date: Sat, 11 Apr 1998 18:26:34 -0400 (EDT) From: Chuck Robey <chuckr@glue.umd.edu> To: FreeBSD-current@FreeBSD.ORG Subject: disk damage Message-ID: <Pine.BSF.3.96.980411182001.440A-100000@localhost>
next in thread | raw e-mail | index | archive | help
I just had my first panic in about 9 months, and I think I took some real disk damage on one of my disks. I was doing a buildworld, and the disk that had obj on it took a big hit. I found the normal fsck failing because it told me that link counts were rising, so I did that manually and told it not to make fixes for link counts that were too low. fsck completed then, and I successfully mounted, and the only damage I can really see is in obj. When I subsequently tried to rm -rf the obj dir, I got errors from rm of: rm: usr/src/usr.bin: Bad file descriptor rm: usr/src/usr.sbin: Bad file descriptor [extra error list, about 8, removed] I tried to do an ls of those directories, and got: ls: usr.bin: Bad file descriptor ls: usr.sbin: Bad file descriptor Should I continue to delete these guys, and if so, how? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980411182001.440A-100000>