On Mon, Jul 19, 2010 at 01:41:24PM -0700, Jeremy Chadwick wrote:
On Mon, Jul 19, 2010 at 11:55:59AM -0400, Mikhail T. wrote:
19.07.2010 07:31, Jeremy Chadwick написав(ла):
If you boot the machine in single-user, and run fsck manually, are there
any errors?
Thanks, Jeremy... I wish, there
An 8.1-prerelease machine I have throws the panic in subject quite
often. Does anyone care? Is this evidence of some filesystem corruption
here, or a known problem that's (almost) solved already?
The stacks all look the same:
panic: handle_written_inodeblock: bad size
ts_to_ct
:
panic: handle_written_inodeblock: bad size
ts_to_ct(1279145603.245753580) = [2010-07-14 22:13:23]
...
#0 doadump () at pcpu.h:230
#1 0xc05be054 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:416
#2 0xc05be261 in panic (fmt=Variable fmt is not available
On Mon, Jul 19, 2010 at 11:55:59AM -0400, Mikhail T. wrote:
19.07.2010 07:31, Jeremy Chadwick написав(ла):
If you boot the machine in single-user, and run fsck manually, are there
any errors?
Thanks, Jeremy... I wish, there was a way to learn, /which/
file-system is giving trouble... However,
19.07.2010 07:31, Jeremy Chadwick написав(ла):
If you boot the machine in single-user, and run fsck manually, are there
any errors?
Thanks, Jeremy... I wish, there was a way to learn, /which/ file-system
is giving trouble... However, after sending the question out last night,
I tried to
