Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!uwvax!oddjob!mimsy!chris From: chris@mimsy.UUCP (Chris Torek) Newsgroups: comp.unix.wizards,comp.unix.questions Subject: Re: How to recover from fsck "Cannot read block"? Message-ID: <7526@mimsy.UUCP> Date: Wed, 15-Jul-87 14:03:53 EDT Article-I.D.: mimsy.7526 Posted: Wed Jul 15 14:03:53 1987 Date-Received: Sat, 18-Jul-87 00:37:09 EDT References: <412@acornrc.UUCP> <3224@cit-vax.Caltech.Edu> <693@gargoyle.UChicago.EDU> Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 23 Keywords: disk, fsck, help! Xref: mnetor comp.unix.wizards:3257 comp.unix.questions:3207 >In article <3225@cit-vax.Caltech.Edu> mangler@cit-vax.UUCP writes: >>... There aren't BLKDEV_IOSIZE bytes left in the partition, so you >>get an error. Make sure that you fsck the raw device, not the block >>device. In article <693@gargoyle.UChicago.EDU> chris@gargoyle.UChicago.EDU (Chris Johnston) writes: >This is a bug pure and simple. Pure perhaps: but not so simple. >Note: One cannot run fsck on the raw root device! True; but then, Berkeley's distributions always have 15884 sectors in the root file system, or some other multiple of 4, since BLKDEV_IOSIZE is 2048 and sectors are 512 bytes. If you are willing to make block I/O more expensive, you can make arbitrary block file system sizes work by changing BLKDEV_IOSIZE to 512. Alternatively, you can make sure all your file systems are multiples of four sectors. -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690) Domain: chris@mimsy.umd.edu Path: seismo!mimsy!chris