From nobody  Thu Mar 19 01:23:14 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA24993;
          Thu, 19 Mar 1998 01:23:14 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199803190923.BAA24993@hub.freebsd.org>
Date: Thu, 19 Mar 1998 01:23:14 -0800 (PST)
From: wbrian@speakeasy.org
To: freebsd-gnats-submit@freebsd.org
Subject: UFS has filesize incorrectly stated; persistent corruption when trying to fix.
X-Send-Pr-Version: www-1.0

>Number:         6065
>Category:       kern
>Synopsis:       UFS has filesize incorrectly stated; persistent corruption when trying to fix.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Mar 19 01:30:02 PST 1998
>Closed-Date:    Mon May 4 09:14:35 PDT 1998
>Last-Modified:  Mon May  4 09:17:03 PDT 1998
>Originator:     Brian Wehrle
>Release:        2.2.5
>Organization:
None
>Environment:
2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Mon Jan 19 14:40:37 i386
>Description:
It seems that my /stand dir has become corrupted.  At some time certain files took upon the same
file size.  For example, now sed and find have the exact same size.  When I diff the files they are different but yet they 
still both work and report the same size.  When I go to copy rebuilt binaries this changes the file sizes of randomly
selected files!  I am not sure how to explain this better.  The FS is ufs, from /etc/fstab.
In this case both sed and find work (executer properly) (running them as /stand/sed and /stand/find) but they still report being the same size.

>How-To-Repeat:
Absolutely no idea (I wonder if this happened when/if the FS became full ??) I was propp'ing files from /usr/ob
into this directory to replace the old ones.
I guess one could try adding and deleting files from the /stand directory.
	
>Fix:
No idea.
>Release-Note:
>Audit-Trail:

From: FBI BSD <fbibsd@yahoo.com>
To: wbrian@speakeasy.org, freebsd-gnats-submit@FreeBSD.ORG
Cc: fbibsd@rocketmail.com
Subject: Re: kern/6065: UFS has filesize incorrectly stated; persistent corruption when trying to fix.
Date: Thu, 19 Mar 1998 10:47:50 -0800 (PST)

 I think this is perhaps not a bug, but a feature.
 
 ls -li /stand and look at all the files that have the same i-node
 number.
 
 In my distribution many /stand binaries are not only the same size,
 but are links to the same actual disk file (i.e. same i-number).
 
 This was done to provide many common utilities in one 'blob' so that
 the disk space necessary to accomodate all of the utilities would be
 minimized (e.g. so that they can fit on one floppy).
 
 Because they're statically linked, having distinct utility programs
 would be very redundant in that many of the same libc modules would be
 present distinctly in each utility.
 
 You can replace any given utility with a newly built one, but you should
 'rm' the old utility file link first, then copy in the new 'uncrunched'
 utility.
 
 I can only guess that somewhere in the distribution there's a makefile
 that
 remakes these default utilities and crunches them together as you seem
 to see them.  Perhaps you can rebuild from that codebase.
 
 see crunchgen(1) et. al.
 
 Chris
 
 ---wbrian@speakeasy.org wrote:
 >
 > 
 > >Number:         6065
 > >Category:       kern
 > >Synopsis:       UFS has filesize incorrectly stated; persistent
 corruption when trying to fix.
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       high
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Thu Mar 19 01:30:02 PST 1998
 > >Last-Modified:
 > >Originator:     Brian Wehrle
 > >Organization:
 > None
 > >Release:        2.2.5
 > >Environment:
 > 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Mon Jan 19 14:40:37 i386
 > >Description:
 > It seems that my /stand dir has become corrupted.  At some time
 certain files took upon the same
 > file size.  For example, now sed and find have the exact same size. 
 When I diff the files they are different but yet they 
 > still both work and report the same size.  When I go to copy rebuilt
 binaries this changes the file sizes of randomly
 > selected files!  I am not sure how to explain this better.  The FS
 is ufs, from /etc/fstab.
 > In this case both sed and find work (executer properly) (running
 them as /stand/sed and /stand/find) but they still report being the
 same size.
 > 
 > >How-To-Repeat:
 > Absolutely no idea (I wonder if this happened when/if the FS became
 full ??) I was propp'ing files from /usr/ob
 > into this directory to replace the old ones.
 > I guess one could try adding and deleting files from the /stand
 directory.
 > 	
 > >Fix:
 > No idea.
 > >Audit-Trail:
 > >Unformatted:
 > 
 > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > with "unsubscribe freebsd-bugs" in the body of the message
 > 
 
 _________________________________________________________
 DO YOU YAHOO!?
 Get your free @yahoo.com address at http://mail.yahoo.com
 

From: B Wehrle <wbrian@speakeasy.org>
To: FBI BSD <fbibsd@yahoo.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG, fbibsd@rocketmail.com
Subject: Re: kern/6065: UFS has filesize incorrectly stated; persistent corruption when trying to fix.
Date: Mon, 13 Apr 1998 22:27:46 -0700 (PDT)

 Cool, I certainly appreciate that info.  I do believe that i did hit some
 courrption after an ungraceful ssytem shutdown.  After reboot, fsck was
 run and I did see some corruption in the /dev FS, right now I have some
 very odd device files, including some devices that have incorrect major
 numbers.  I.E. I have /dev/wd2 and it's major is 2, another wd device's
 major is 3, this cannot be correct. Your thoughts ?
 	Secondly, what is the recoverability of the FFS ? Strictly in
 terms of file meta-data, not user data ?  If I crash my machine will I
 stand a chance of losing files, or having corrupted directories ?
 	Thirdly, who can I send kernel programming questions to re:Device
 Drivers using file-systems..  can a device open a file for read/write
 access during some stage of initialization ?  The yucky thing about
 device-drivers is getting the configuration information into the module.
 For some devices it would be nice to read that info from a "registry",
 like NT.  Could one write a hook into the loader to load the registry at
 boot time from the / FS, mount it as a FS /reg and use this for init
 routines.  Recompiling to change a device is tedious.
 	Fourthly, (whew lots of questions from me today!) what is the
 difference between /dev/wd0a and /dev/wd0s1 ?  If Slices are partitions
 then what does the "a" connote ?
 Thanks for your time
 Brian Wehrle
 
  On Thu, 19 Mar 1998, FBI BSD wrote:
 
 > 
 > I think this is perhaps not a bug, but a feature.
 > 
 > ls -li /stand and look at all the files that have the same i-node
 > number.
 > 
 > In my distribution many /stand binaries are not only the same size,
 > but are links to the same actual disk file (i.e. same i-number).
 > 
 > This was done to provide many common utilities in one 'blob' so that
 > the disk space necessary to accomodate all of the utilities would be
 > minimized (e.g. so that they can fit on one floppy).
 > 
 > Because they're statically linked, having distinct utility programs
 > would be very redundant in that many of the same libc modules would be
 > present distinctly in each utility.
 > 
 > You can replace any given utility with a newly built one, but you should
 > 'rm' the old utility file link first, then copy in the new 'uncrunched'
 > utility.
 > 
 > I can only guess that somewhere in the distribution there's a makefile
 > that
 > remakes these default utilities and crunches them together as you seem
 > to see them.  Perhaps you can rebuild from that codebase.
 > 
 > see crunchgen(1) et. al.
 > 
 > Chris
 > 
 > ---wbrian@speakeasy.org wrote:
 > >
 > > 
 > > >Number:         6065
 > > >Category:       kern
 > > >Synopsis:       UFS has filesize incorrectly stated; persistent
 > corruption when trying to fix.
 > > >Confidential:   no
 > > >Severity:       serious
 > > >Priority:       high
 > > >Responsible:    freebsd-bugs
 > > >State:          open
 > > >Quarter:
 > > >Keywords:
 > > >Date-Required:
 > > >Class:          sw-bug
 > > >Submitter-Id:   current-users
 > > >Arrival-Date:   Thu Mar 19 01:30:02 PST 1998
 > > >Last-Modified:
 > > >Originator:     Brian Wehrle
 > > >Organization:
 > > None
 > > >Release:        2.2.5
 > > >Environment:
 > > 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Mon Jan 19 14:40:37 i386
 > > >Description:
 > > It seems that my /stand dir has become corrupted.  At some time
 > certain files took upon the same
 > > file size.  For example, now sed and find have the exact same size. 
 > When I diff the files they are different but yet they 
 > > still both work and report the same size.  When I go to copy rebuilt
 > binaries this changes the file sizes of randomly
 > > selected files!  I am not sure how to explain this better.  The FS
 > is ufs, from /etc/fstab.
 > > In this case both sed and find work (executer properly) (running
 > them as /stand/sed and /stand/find) but they still report being the
 > same size.
 > > 
 > > >How-To-Repeat:
 > > Absolutely no idea (I wonder if this happened when/if the FS became
 > full ??) I was propp'ing files from /usr/ob
 > > into this directory to replace the old ones.
 > > I guess one could try adding and deleting files from the /stand
 > directory.
 > > 	
 > > >Fix:
 > > No idea.
 > > >Audit-Trail:
 > > >Unformatted:
 > > 
 > > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > > with "unsubscribe freebsd-bugs" in the body of the message
 > > 
 > 
 > _________________________________________________________
 > DO YOU YAHOO!?
 > Get your free @yahoo.com address at http://mail.yahoo.com
 > 
 > 
 
State-Changed-From-To: open->closed 
State-Changed-By: dt 
State-Changed-When: Mon May 4 09:14:35 PDT 1998 
State-Changed-Why:  
Not a bug - see audit trail. 
>Unformatted:
