Subject: Re: kern/21296: more file corruption since UFS2
To: Jaromir Dolecek <firstname.lastname@example.org>
From: Sean Davis <email@example.com>
Date: 04/24/2003 06:28:23
On Thu, Apr 24, 2003 at 11:45:16AM +0200, Jaromir Dolecek wrote:
> Gregory McGarry wrote:
> > 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.
> > Quite a few file-systems will exhibit this problem.
> This is consistent with what I see on my system. I have a new kernel
> (the one with the bitmap corruption fixed), and new fsck, and
> recently the EBADF problem appeared for one directory
> (fortunately just /var/chroot/named/usr).
So, does this mean I should expect it to keep happening? so far I've only
had it nuke files that were easily replaced, but I don't feel like waiting
for it to happen to something not so easily replaced. If the root of the
problem is known, why hasn't it been fixed yet?
/~\ The ASCII
\ / Ribbon Campaign Sean Davis
X Against HTML aka dive
/ \ Email!