SunOs 5.4 Crashes ?
The original question was :
My Solaris 2.4 on Sparc 20 crashes with the following message:
nf0 at sbus0: SBus slot 1 0x7ff0 SBus level 4 sparc ipl 7
nf0 is /iommu@f,e0000000/sbus@f,e0001000/nf@1,7ff0
dump on /dev/dsk/c0t3d0s1 size 262236K
panic: free: freeing free frag, dev = 0x80007e, block = 2051, cg = 118 fs = /data
syncing file systems... [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 [535] 7 done
13456 static and sysmap kernel pages
107 dynamic kernel data pages
507 kernel-pageable pages
0 segkmap kernel pages
0 segvn kernel pages
150 current user process pages
14220 total pages (14220 chunks)
dumping to vp fc32ba84, offset 410712
SunOS Release 5.4 Version Generic_101945-10 [UNIX(R) System V Release 4.0]
Why ?
Stots
i got many answers to my question, and i thank all of you
here is the answer that i choose :
from Irana Whitaker-Patel
Systems Administrator
> HR Wallingford
> |\ _,,,---,,_ Howbery Park, Wallingford, Oxon
> ZZZzz /,`.-'`' -. ;-;;,_ Tel: (01491) 822321
> |,4- ) )-,_. ,\ ( `'-' email:irana@hrwallingford.co.uk
>_______'---''(_/--' `-'\_)____________http://www.hrwallingford.co.uk
>----------
>
>SRDB ID: 13419
>
>SYNOPSIS: System Panics with: 'freeing free frag' or 'freeing free inode' or
> 'freeing free block'
>
>DETAIL DESCRIPTION:
>
>The system panics with one of the following messages:
>
> freeing free frag
> freeing free inode
> freeing free block
>
>SOLUTION SUMMARY:
>
>These panic strings are indications of corruption in the super block,
>the inode cache, or a race condition during file system operation.
>These corrputions or race conditions might have occurred for a number of
>reasons. Its resolution, for most cases, would require long in-depth analysis.
>
>To prevent any further corruptions, IMMEDIATELY fsck the file system
>that is having the problem. Use fsck with the "-o f" option to force
>a file system check. Save the results from the FSCK for later analysis.
>
>fsck will repair the damaged portion of the file system. Core files from the
>panic, most of the time, show only the afte-effect of the damage. The cause
>of the corruption or race condition, usually, cannot be determined until after
>tracing or debugging code is placed in modules that relate to the file system.
>
>If the fsck is not successful, instruct the customer to record the output
>messages from the fsck and relay them to you.
>
>PRODUCT AREA: Kernel
>PRODUCT: Config
>SUNOS RELEASE: Solaris 2.x
>HARDWARE: any
>
+================================================================+
|Stotsky Haim, | Email:stots@elbit.co.il | P.O.B 539 |
|System Admin, | Phone: +972-4-8315-768 | Haifa, 51905 |
|Elbit Ltd. | Fax: +972-4-8315-120 | Israel |
+================================================================+
+================================================================+
|Stotsky Haim, | Email:stots@elbit.co.il | P.O.B 539 |
|System Admin, | Phone: +972-4-8315-768 | Haifa, 51905 |
|Elbit Ltd. | Fax: +972-4-8315-120 | Israel |
+================================================================+
