Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!accuvax.nwu.edu!eecs.nwu.edu!phil From: phil@eecs.nwu.edu (Bill LeFebvre) Newsgroups: comp.sys.encore Subject: What is this garbage? Or, file system woes. Message-ID: <936@accuvax.nwu.edu> Date: 21 Jul 89 13:54:48 GMT Sender: news@accuvax.nwu.edu Reply-To: phil@eecs.nwu.edu (Bill LeFebvre) Organization: Northwestern U, Evanston IL, USA Lines: 31 System: multimax 210 running UMAX V4.2. I've seen file system problems in conjunction with hardware failures, but this time it "just happened" with no other failures in sight. Here's what met me this morning: Fri Jul 21 00:03:00 1989: Bad special file size 1914725486 (inode 33464, type 060000, FS /p0). Fri Jul 21 00:03:00 1989: Bad special file size 2037148026 (inode 33465, type 060000, FS /p0). Fri Jul 21 00:03:00 1989: Bad special file size 7631983 (inode 33467, type 060000, FS /p0). Fri Jul 21 00:04:19 1989: Bad special file size 1835081801 (inode 33468, type 020000, FS /p0). Fri Jul 21 00:08:18 1989: Bad block major number 117 (inode 33470 on FS /p0). Fri Jul 21 00:08:32 1989: Bad special file size 1685283617 (inode 33470, type 060000, FS /p0). Fri Jul 21 00:08:38 1989: Bad special file size 757935405 (inode 33469, type 020000, FS /p0). Fri Jul 21 00:10:16 1989: Bad special file size 1701080931 (inode 33464, type 060000, FS /p1). Fri Jul 21 00:11:27 1989: Bad special file size 537554287 (inode 33466, type 060000, FS /p1). Fri Jul 21 00:12:10 1989: Bad special file size 1634689657 (inode 33471, type 060000, FS /p1). Fri Jul 21 00:14:22 1989: Bad special file size 1701994784 (inode 33468, type 020000, FS /p1). Fri Jul 21 00:14:24 1989: Bad special file size 1635000693 (inode 33469, type 020000, FS /p1). Fri Jul 21 00:15:09 1989: Bad special file size 1869815920 (inode 33465, type 060000, FS /p1). Fri Jul 21 00:17:25 1989: Bad special file size 63403122 (inode 26558, type 060000, FS /p3). So what's the scoop? Are all my large file systems going to fly apart if I dare to look at them cross-eyed? This machine has only been up for 3 days. I can't afford to take my machine down once or twice a week to run fsck. Anyone got a clue? William LeFebvre Department of Electrical Engineering and Computer Science Northwestern University