ly@prism.TMC.COM (10/26/89)
I have Xenix on an AT clone.
When I run "fsck /dev/usr",
I get the message: possible file size error i=552
during phase 1 - check blocks and sizes.
The system does not attempt to fix this error so the message comes up
every time I run fsck.
What should I do to get rid of this error?
Thanks.davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr) (10/26/89)
It's not an error, it's a warning. Files may have "holes" in them, in which the file was written with random writes. Databases and core dumps are examples. -- bill davidsen (davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen) "The world is filled with fools. They blindly follow their so-called 'reason' in the face of the church and common sense. Any fool can see that the world is flat!" - anon
chip@ateng.com (Chip Salzenberg) (10/27/89)
According to ly@prism.TMC.COM: >When I run "fsck /dev/usr", >I get the message: possible file size error i=552 >during phase 1 - check blocks and sizes. Like it says, it's a "possible" file size error. You've got a named pipe, or a normal file with holes (unallocated blocks). No harm. -- You may redistribute this article only to those who may freely do likewise. Chip Salzenberg at A T Engineering; <chip@ateng.com> or <uunet!ateng!chip> "'Why do we post to Usenet?' Naturally, the answer is, 'To get a response.'" -- Brad "Flame Me" Templeton