From owner-cvs-all  Fri Oct 16 21:13:09 1998
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA24769
          for cvs-all-outgoing; Fri, 16 Oct 1998 21:13:09 -0700 (PDT)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24764;
          Fri, 16 Oct 1998 21:12:59 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA31312;
	Sat, 17 Oct 1998 14:12:38 +1000
Date: Sat, 17 Oct 1998 14:12:38 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199810170412.OAA31312@godzilla.zeta.org.au>
To: bde@zeta.org.au, dag-erli@ifi.uio.no
Subject: Re: cvs commit: src/sbin/mount mount.8
Cc: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, des@FreeBSD.ORG
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

>> > > >  Warn about "mount -u" bug.
>> > > FUD.
>> > I'm afraid it's very, very real, and 100% reproducable.
>> Please give details.  Which file system?  (-u is supposed to apply to
>> all file systems).  Did recent -u fixes (ffs_vfsops.c rev.1.84 and 1.88)
>> affect it?
>
>FFS, and no, I've experienced corruption on a file system that was
>newfs'd in the beginning of October (and I've been making world and
>building kernels every other day for a month)

By details, I meant complete details.  How to reproduce the problem,
and whether rev.1.84 and 1.88 caused the problem.  Does it happen on
other file systems?  ext2fs uses essentially the same mount -u code
as ffs, but is slightly simpler and closer to the CSRG version (for
mount -u), so it might be easier to debug and less broken.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message