Subject: Re: kern/21296: more file corruption since UFS2
To: Frank van der Linden <email@example.com>
From: Sean Davis <firstname.lastname@example.org>
Date: 04/24/2003 08:23:29
On Thu, Apr 24, 2003 at 01:34:59PM +0200, Frank van der Linden wrote:
> On Thu, Apr 24, 2003 at 07:57:11PM +0900, enami tsugutomo wrote:
> > Gregory McGarry <email@example.com> writes:
> > > I think it is because ffs1_din is not being cleared during allocation.
> > > Before ufs2 went in, memset() on the inode would have also cleared the
> > > dinode structure.
> > For ffs, it is a job of newfs isn't it?
> Correct. newfs(8) initializes all inode blocks to 0; FFS just loads
> the inode from disk (ffs_vget doesn't know if it's gettting an
> allocated inode or not).
> If you're using an UFS2 filesystem, the inode blocks are initialized
> on the fly. But the bug report doesn't seem to be about a UFS2 filesystem.
No, it is not. All the filesystems in question are FFS, not UFS2. (or
s/FFS/UFS/ if that is the proper name)
/~\ The ASCII
\ / Ribbon Campaign Sean Davis
X Against HTML aka dive
/ \ Email!