Forgive the double posts,  they will cease immediately

 

panic[cpu0]/thread=dacac880: BAD TRAP: type=e (#pf Page fault)
rp=d9f61850 addr=1048c0d occurred in module "zfs" due to an illegal
access to a user address

 

net-init: #pf Page fault

Bad kernel fault at addr=0x1048c0d

pid=1069, pc=0xfebab410, sp=0xd1c38018, eflags=0x10296

cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 6b8<xmme,fxsr,pge,pae,pse,de>

cr2: 1048c0dcr3: 7965020

         gs: e7b601b0  fs: fec90000  es:      160  ds:      160

        edi:        0 esi:  1048bf9 ebp: d9f618c4 esp: d9f61888

        ebx:  1048bf9 edx:  1048bfd ecx: dc311900 eax: d9f6192c

        trp:        e err:        0 eip: febab410  cs:      158

        efl:    10296 usp: d1c38018  ss: e43feb72

 

d9f6178c unix:die+93 (e, d9f61850, 1048c0)

d9f6183c unix:trap+1422 (d9f61850, 1048c0d, )

d9f61850 unix:cmntrap+7c (e7b601b0, fec90000,)

d9f618c4 zfs:mze_compare+18 (d9f6192c, 1048bf9, )

d9f61904 genunix:avl_find+39 (d34b2958, d9f6192c,)

d9f619a4 zfs:mze_find+4a (e45fb8c0, d9f61c9c,)

d9f619e4 zfs:zap_lookup_norm+65 (dc2665a8, 21d, 0, d)

d9f61a34 zfs:zap_lookup+31 (dc2665a8, 21d, 0, d)

d9f61a94 zfs:zfs_match_find+ba (dc8fb980, e0ed3460,)

d9f61b04 zfs:zfs_dirent_lock+358 (d9f61b38, e0ed3460,)

d9f61b54 zfs:zfs_dirlook+f7 (e0ed3460, d9f61c9c,)

d9f61ba4 zfs:zfs_lookup+d5 (e0b420c0, d9f61c9c,)

d9f61c04 genunix:fop_lookup+b0 (e0b420c0, d9f61c9c,)

d9f61dc4 genunix:lookuppnvp+3e4 (d9f61e3c, 0, 1, 0, )

d9f61e14 genunix:lookuppnat+f3 (d9f61e3c, 0, 1, 0, )

d9f61e94 genunix:lookupnameat+52 (807b51c, 0, 1, 0, d)

d9f61ef4 genunix:cstatat_getvp+15d (ffd19553, 807b51c, )

d9f61f54 genunix:cstatat64+68 (ffd19553, 807b51c, )

d9f61f84 genunix:stat64+1c (807b51c, 8047b50, 8)

 

From: lori....@sun.com [mailto:lori....@sun.com] 
Sent: Monday, February 23, 2009 1:17 PM
To: Christopher Mera
Cc: zfs-discuss@opensolaris.org
Subject: Re: [zfs-discuss] zfs streams & data corruption

 


I don't know what's causing this, nor have I seen it.  

Can you send more information about the errors you
see when the system crashes and svc.configd fails?

Doing the scrub seems like a harmless and possibly
useful thing to do.  Let us know what you find out
from it.

Lori

On 02/23/09 11:05, Christopher Mera wrote: 

Hi folks,

 

I recently read up on Scott Dickson's blog with his solution for
jumpstart/flashless cloning of ZFS root filesystem boxes.  I have to say
that it initially looks to work out cleanly, but of course there are
kinks to be worked out that deal with auto mounting filesystems mostly.


 

The issue that I'm having is that a few days after these cloned systems
are brought up and reconfigured they are crashing and svc.configd
refuses to start.

 

I thought about using zpool scrub <poolname>  right after completing the
stream as an integrity check.  

 

If you have any suggestions about this I'd love to hear them!

 

 

Thanks,

Christopher Mera

 

 


________________________________



 
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
  

 

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to