Andrew,
> I woke up yesterday morning, only to discover my system kept
> rebooting..
>
> It's been running fine for the last while. I upgraded to snv 98 a
> couple weeks back (from 95), and had upgraded my RaidZ Zpool from
> version 11 to 13 for improved scrub performance.
>
> After some research it turned out that, on bootup, importing my 4tb
> raidZ array was causing the system to panic (similar to this OP's
> error). I got that bypassed, and can now at least boot the system..
>
> However, when I try anything (like mdb -kw), it advises me that
> there is no command line editing because: "mdb: no terminal data
> available for TERM=vt320. term init failed: command-line editing and
> prompt will not be available". This means I can't really try what
> aldredmr had done in mdb, and I really don't have any experience in
> it. I upgraded to snv_100 (November), but experiencing the exact
> same issues
>
> If anyone has some insight, it would be greatly appreciated. Thanks
I have the same problem SSH'ing in from my Mac OS X, which sets the
TERM type to 'xterm-color', also not supported.
Do the following, depending on your default shell. and you should be
all set.
TERM=vt100; export TERM
or
setenv TERM vt100
>
> --
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Jim
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
