Today we had another panic, at least it was during work time :) Just a
shame the 999GB ufs takes 80+ mins to fsck. (Yes, it is mounted 'logging').
panic[cpu3]/thread=ff001e70dc80:
free: freeing free block, dev:0xb60024, block:13144, ino:1737885,
fs:/export
/saba1
On Saturday the X4500 system paniced, and rebooted. For some reason the
/export/saba1 UFS partition was corrupt, and needed fsck. This is why
it did not come back online. /export/saba1 is mounted logging,noatime,
so fsck should never (-ish) be needed.
SunOS x4500-01.unix 5.11 snv_70b i86pc
Jorgen Lundman wrote:
On Saturday the X4500 system paniced, and rebooted. For some reason the
/export/saba1 UFS partition was corrupt, and needed fsck. This is why
it did not come back online. /export/saba1 is mounted logging,noatime,
so fsck should never (-ish) be needed.
SunOS
Since the panic stack only ever goes through ufs, you should
log a call with Sun support.
We do have support, but they only speak Japanese, and I'm still quite
poor at it. But I have started the process of having it translated and
passed along to the next person. It is always fun to see what
Jorgen Lundman wrote:
Since the panic stack only ever goes through ufs, you should
log a call with Sun support.
We do have support, but they only speak Japanese, and I'm still quite
poor at it. But I have started the process of having it translated and
passed along to the next person.
I don't know, I'm not a UFS expert (heck, I'm not an expert
on _anything_). Have you investigated putting your paying
customers onto zfs and managing quotas with zfs properties
instead of ufs?
Yep, we spent about 6 weeks during the trial period of the x4500 to try
to find a way for ZFS to be
