See below..
- Bruce Evans's Original Message -
> On Sun, 22 Oct 2000 [EMAIL PROTECTED] wrote:
>
> > > Reverting src/sbin/newfs/mkfs.c to revision 1.29 fixes
> > > the problem.
> > >
> > > With just a quick review of the patch, I'm not sure I
> > > understand what forces the last dirty
On Sun, 22 Oct 2000 [EMAIL PROTECTED] wrote:
> > Reverting src/sbin/newfs/mkfs.c to revision 1.29 fixes
> > the problem.
> >
> > With just a quick review of the patch, I'm not sure I
> > understand what forces the last dirty buffer to be
> > written.
This worried me too.
> Try the enclosed pat
Patch appears to fix the problem. Do you want to
commit it? Peter? me?
Thanks,
John
ps: it would be interesting to add a statistic to determine
how often the cache block is flushed due to size or read
interference. May determine that the cache should be
larger (or smaller). Did you
lt;[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: Peter Wemm <[EMAIL PROTECTED]>
> Subject: newfs/fsck problem (bad superblocks)
>
> Hi,
>
>I posted a question concerning fsck yesterday. A number of
> people replied with the 'bad harddisk' comment.
&g
> Reverting src/sbin/newfs/mkfs.c to revision 1.29 fixes
> the problem.
>
> With just a quick review of the patch, I'm not sure I
> understand what forces the last dirty buffer to be
> written.
>
> revert the patch? try to fix it? comments?
Try the enclosed patch. It flushes the dirty buffer b
> I also wonder if this is related to the 'make release' problems.
During "make release", src/release/Makefile does create floppies for
installation. Copying 'mfsroot.gz' (mfsroot imagefile) to a newly
newfs-ed floppy image (mfsroot.flp, 1.44MB size) causes kernel hungup.
-- -
Makoto `MAR' MATS
Reverting src/sbin/newfs/mkfs.c to revision 1.29 fixes
the problem.
With just a quick review of the patch, I'm not sure I
understand what forces the last dirty buffer to be
written.
revert the patch? try to fix it? comments?
-John
- John W. De Boskey's Original Message -
> Hi,
>
>
Hi,
I posted a question concerning fsck yesterday. A number of
people replied with the 'bad harddisk' comment.
I have followed up some more on the problem, and can now
reproduce it on different filesystems.
Below, I umount my /usr/obj, newfs it, mount it, unmount
it, and then fsck it.
