On Sun, 3 Feb 2008, Kostik Belousov wrote:
KB> > (kgdb) p *vp
KB> > $2 = {v_type = VDIR, v_tag = 0x8039319c "ufs", v_op =
KB> > 0x804e98e0, v_data = 0xff003fab0480, v_mount =
0xff00050dc650,
KB> The *v_mount and *(struct ufs_mount *)(v_mount->mnt_data) content shall
KB>
On Sun, Feb 03, 2008 at 12:05:44PM +0300, Dmitry Morozovsky wrote:
> On Sun, 3 Feb 2008, Kostik Belousov wrote:
>
> KB> Di you have the UFS volume mounted from the eSATA drive ? If yes, then the
> KB> panic is the natural consequence of the device disappearing from under the
> KB> UFS. If not, and
On Sun, 3 Feb 2008, Kostik Belousov wrote:
KB> Di you have the UFS volume mounted from the eSATA drive ? If yes, then the
KB> panic is the natural consequence of the device disappearing from under the
KB> UFS. If not, and fault address 0x3020e0b30 looks suspicious, it could mean
KB> some kernel me
On Sun, Feb 03, 2008 at 03:04:52AM +0300, Dmitry Morozovsky wrote:
> Dear colleagues,
>
> during rsycn from eSATA drive connected to Promise TX4 (ad12) to ZFS pool
> eSATA disk got disconnected. With the next access, system crashed:
>
> Unread portion of the kernel message buffer:
>
>
> Fatal
Dear colleagues,
during rsycn from eSATA drive connected to Promise TX4 (ad12) to ZFS pool
eSATA disk got disconnected. With the next access, system crashed:
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual addres
