thr3ads.net - zfs discuss - [zfs-discuss] HELP!! I can''t mount my zpool!! [Mar 2007]

If this information is useful, please help other people find it:
Share via:

Gino Ruopolo

2007-Mar-21 10:45 UTC

[zfs-discuss] HELP!! I can''t mount my zpool!!

Hi all.
One of our server had a panic and now can''t mount the zpool anymore!
Here is what I get at boot:


Mar 21 11:09:17 SERVER142 ^Mpanic[cpu1]/thread=ffffffff90878200:
Mar 21 11:09:17 SERVER142 genunix: [ID 603766 kern.notice] assertion failed:
ss->ss_start <= start (0x670000b800 <= 0x67
00009000), file: ../../common/fs/zfs/space_map.c, line: 126
Mar 21 11:09:17 SERVER142 unix: [ID 100000 kern.notice]
Mar 21 11:09:17 SERVER142 genunix: [ID 802836 kern.notice] fffffe800047e320
fffffffffb9ad0b9 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e3a0
zfs:space_map_remove+1a3 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e3d0
zfs:space_map_claim+32 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e410
zfs:zfsctl_ops_root+2f9db09d ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e450
zfs:zfsctl_ops_root+2f9db30c ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e470
zfs:zio_dva_claim+1d ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e480
zfs:zio_next_stage+72 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e490
zfs:zio_gang_pipeline+1e ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e4a0
zfs:zio_next_stage+72 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e4d0
zfs:zio_wait_for_children+49 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e4e0
zfs:zio_wait_children_ready+15 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e4f0
zfs:zfsctl_ops_root+2f9f41e6 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e520
zfs:zio_wait+2d ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e550
zfs:zil_claim_log_block+60 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e650
zfs:zil_parse+181 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e690
zfs:zil_claim+ce ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e840
zfs:dmu_objset_find+b6 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e9f0
zfs:dmu_objset_find+12f ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047eba0
zfs:dmu_objset_find+12f ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ec10
zfs:spa_load+51a ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ec80
zfs:spa_load+35d ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ecc0
zfs:spa_open_common+15b ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ed00
zfs:spa_get_stats+42 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ed40
zfs:zfs_ioc_pool_stats+3f ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ed80
zfs:zfsdev_ioctl+144 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ed90
genunix:cdev_ioctl+1d ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047edb0
specfs:spec_ioctl+50 ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ede0
genunix:fop_ioctl+1a ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047eec0
genunix:ioctl+ac ()
Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ef10
unix:sys_syscall32+101 ()
Mar 21 11:09:17 SERVER142 unix: [ID 100000 kern.notice]
Mar 21 11:09:17 SERVER142 genunix: [ID 672855 kern.notice] syncing file
systems...
 
 
This message posted from opensolaris.org

Victor Latushkin

2007-Mar-21 11:04 UTC

head link

[zfs-discuss] HELP!! I can''t mount my zpool!!

Hi Gino,

What version of Solaris your server is running?

What happens here is while opening your pool ZFS is trying to process 
ZFS Intent Log of this poll and discovers some inconsistency between 
on-disk state and ZIL contents.

What was the first panic you refer to?

Wbr,
Victor

Gino Ruopolo ?????:> Hi all.
> One of our server had a panic and now can''t mount the zpool
anymore!
> Here is what I get at boot:
>
>
> Mar 21 11:09:17 SERVER142 ^Mpanic[cpu1]/thread=ffffffff90878200:
> Mar 21 11:09:17 SERVER142 genunix: [ID 603766 kern.notice] assertion
failed: ss->ss_start <= start (0x670000b800 <= 0x67
> 00009000), file: ../../common/fs/zfs/space_map.c, line: 126
> Mar 21 11:09:17 SERVER142 unix: [ID 100000 kern.notice]
> Mar 21 11:09:17 SERVER142 genunix: [ID 802836 kern.notice] fffffe800047e320
fffffffffb9ad0b9 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e3a0
zfs:space_map_remove+1a3 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e3d0
zfs:space_map_claim+32 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e410
zfs:zfsctl_ops_root+2f9db09d ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e450
zfs:zfsctl_ops_root+2f9db30c ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e470
zfs:zio_dva_claim+1d ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e480
zfs:zio_next_stage+72 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e490
zfs:zio_gang_pipeline+1e ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e4a0
zfs:zio_next_stage+72 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e4d0
zfs:zio_wait_for_children+49 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e4e0
zfs:zio_wait_children_ready+15 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e4f0
zfs:zfsctl_ops_root+2f9f41e6 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e520
zfs:zio_wait+2d ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e550
zfs:zil_claim_log_block+60 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e650
zfs:zil_parse+181 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e690
zfs:zil_claim+ce ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e840
zfs:dmu_objset_find+b6 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047e9f0
zfs:dmu_objset_find+12f ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047eba0
zfs:dmu_objset_find+12f ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ec10
zfs:spa_load+51a ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ec80
zfs:spa_load+35d ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ecc0
zfs:spa_open_common+15b ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ed00
zfs:spa_get_stats+42 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ed40
zfs:zfs_ioc_pool_stats+3f ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ed80
zfs:zfsdev_ioctl+144 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ed90
genunix:cdev_ioctl+1d ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047edb0
specfs:spec_ioctl+50 ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ede0
genunix:fop_ioctl+1a ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047eec0
genunix:ioctl+ac ()
> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] fffffe800047ef10
unix:sys_syscall32+101 ()
> Mar 21 11:09:17 SERVER142 unix: [ID 100000 kern.notice]
> Mar 21 11:09:17 SERVER142 genunix: [ID 672855 kern.notice] syncing file
systems...
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>

Victor Latushkin

2007-Mar-21 12:00 UTC

head link

[zfs-discuss] HELP!! I can''t mount my zpool!!

Gino,> S10U2Ok, then if you have a support contract for this system you may want to 
open new case for this issue.>
> unfortunately we have nothing on the logs about the first panic!This is not good... Without it may be impossible to find out what went 
wrong. You may have nothing on the logs, but crash dumps can still be 
there. Have you checked this?> Is there a way to force the mount of the zpool? We have some important 
> data on it!This may be impossible to achieve on the version of Solaris this system 
is running.

Victor>
> Thank you,
> Gino
>
>
>> From: Victor Latushkin <Victor.Latushkin at Sun.COM>
>> To: Gino Ruopolo <ginoruopolo at hotmail.com>
>> CC: zfs-discuss at opensolaris.org
>> Subject: Re: [zfs-discuss] HELP!! I can''t mount my zpool!!
>> Date: Wed, 21 Mar 2007 14:04:45 +0300
>>
>> Hi Gino,
>>
>> What version of Solaris your server is running?
>>
>> What happens here is while opening your pool ZFS is trying to process 
>> ZFS Intent Log of this poll and discovers some inconsistency between 
>> on-disk state and ZIL contents.
>>
>> What was the first panic you refer to?
>>
>> Wbr,
>> Victor
>>
>> Gino Ruopolo ??????????:
>>> Hi all.
>>> One of our server had a panic and now can''t mount the
zpool anymore!
>>> Here is what I get at boot:
>>>
>>>
>>> Mar 21 11:09:17 SERVER142 ^Mpanic[cpu1]/thread=ffffffff90878200:
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 603766 kern.notice]
assertion
>>> failed: ss->ss_start <= start (0x670000b800 <= 0x67
>>> 00009000), file: ../../common/fs/zfs/space_map.c, line: 126
>>> Mar 21 11:09:17 SERVER142 unix: [ID 100000 kern.notice]
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 802836 kern.notice] 
>>> fffffe800047e320 fffffffffb9ad0b9 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e3a0 zfs:space_map_remove+1a3 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e3d0 zfs:space_map_claim+32 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e410 zfs:zfsctl_ops_root+2f9db09d ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e450 zfs:zfsctl_ops_root+2f9db30c ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e470 zfs:zio_dva_claim+1d ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e480 zfs:zio_next_stage+72 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e490 zfs:zio_gang_pipeline+1e ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e4a0 zfs:zio_next_stage+72 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e4d0 zfs:zio_wait_for_children+49 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e4e0 zfs:zio_wait_children_ready+15 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e4f0 zfs:zfsctl_ops_root+2f9f41e6 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e520 zfs:zio_wait+2d ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e550 zfs:zil_claim_log_block+60 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e650 zfs:zil_parse+181 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e690 zfs:zil_claim+ce ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e840 zfs:dmu_objset_find+b6 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047e9f0 zfs:dmu_objset_find+12f ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047eba0 zfs:dmu_objset_find+12f ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047ec10 zfs:spa_load+51a ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047ec80 zfs:spa_load+35d ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047ecc0 zfs:spa_open_common+15b ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047ed00 zfs:spa_get_stats+42 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047ed40 zfs:zfs_ioc_pool_stats+3f ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047ed80 zfs:zfsdev_ioctl+144 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047ed90 genunix:cdev_ioctl+1d ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047edb0 specfs:spec_ioctl+50 ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047ede0 genunix:fop_ioctl+1a ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047eec0 genunix:ioctl+ac ()
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>> fffffe800047ef10 unix:sys_syscall32+101 ()
>>> Mar 21 11:09:17 SERVER142 unix: [ID 100000 kern.notice]
>>> Mar 21 11:09:17 SERVER142 genunix: [ID 672855 kern.notice] syncing 
>>> file systems...
>>> This message posted from opensolaris.org
>>> _______________________________________________
>>> zfs-discuss mailing list
>>> zfs-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>>>
>>
>
> _________________________________________________________________
> Scarica Messenger 8.1 e chiama gratis in tutto il mondo! 
> http://get.live.com/it-it/messenger/features
>

Victor Latushkin

2007-Mar-21 12:12 UTC

head link

[zfs-discuss] HELP!! I can''t mount my zpool!!

Gino,

Gino Ruopolo ?????:>
> Victor,
> can we try to mount the zpool on a S10U3 system?No, this may require to use one of the recent Solaris Nevada builds.
I''m
trying to check relevant build number.

What about answers to other my questions?


Wbr,
Victor>> From: Victor Latushkin <Victor.Latushkin at Sun.COM>
>> To: Gino Ruopolo <ginoruopolo at hotmail.com>
>> CC: zfs-discuss at opensolaris.org
>> Subject: Re: [zfs-discuss] HELP!! I can''t mount my zpool!!
>> Date: Wed, 21 Mar 2007 15:00:26 +0300
>>
>> Gino,
>>> S10U2
>> Ok, then if you have a support contract for this system you may want 
>> to open new case for this issue.
>>>
>>> unfortunately we have nothing on the logs about the first panic!
>> This is not good... Without it may be impossible to find out what 
>> went wrong. You may have nothing on the logs, but crash dumps can 
>> still be there. Have you checked this?
>>> Is there a way to force the mount of the zpool? We have some 
>>> important data on it!
>> This may be impossible to achieve on the version of Solaris this 
>> system is running.
>>
>> Victor
>>>
>>> Thank you,
>>> Gino
>>>
>>>
>>>> From: Victor Latushkin <Victor.Latushkin at Sun.COM>
>>>> To: Gino Ruopolo <ginoruopolo at hotmail.com>
>>>> CC: zfs-discuss at opensolaris.org
>>>> Subject: Re: [zfs-discuss] HELP!! I can''t mount my
zpool!!
>>>> Date: Wed, 21 Mar 2007 14:04:45 +0300
>>>>
>>>> Hi Gino,
>>>>
>>>> What version of Solaris your server is running?
>>>>
>>>> What happens here is while opening your pool ZFS is trying to 
>>>> process ZFS Intent Log of this poll and discovers some 
>>>> inconsistency between on-disk state and ZIL contents.
>>>>
>>>> What was the first panic you refer to?
>>>>
>>>> Wbr,
>>>> Victor
>>>>
>>>> Gino Ruopolo ??????????:
>>>>> Hi all.
>>>>> One of our server had a panic and now can''t mount
the zpool anymore!
>>>>> Here is what I get at boot:
>>>>>
>>>>>
>>>>> Mar 21 11:09:17 SERVER142
^Mpanic[cpu1]/thread=ffffffff90878200:
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 603766 kern.notice] 
>>>>> assertion failed: ss->ss_start <= start (0x670000b800
<= 0x67
>>>>> 00009000), file: ../../common/fs/zfs/space_map.c, line: 126
>>>>> Mar 21 11:09:17 SERVER142 unix: [ID 100000 kern.notice]
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 802836 kern.notice] 
>>>>> fffffe800047e320 fffffffffb9ad0b9 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e3a0 zfs:space_map_remove+1a3 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e3d0 zfs:space_map_claim+32 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e410 zfs:zfsctl_ops_root+2f9db09d ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e450 zfs:zfsctl_ops_root+2f9db30c ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e470 zfs:zio_dva_claim+1d ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e480 zfs:zio_next_stage+72 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e490 zfs:zio_gang_pipeline+1e ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e4a0 zfs:zio_next_stage+72 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e4d0 zfs:zio_wait_for_children+49 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e4e0 zfs:zio_wait_children_ready+15 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e4f0 zfs:zfsctl_ops_root+2f9f41e6 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e520 zfs:zio_wait+2d ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e550 zfs:zil_claim_log_block+60 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e650 zfs:zil_parse+181 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e690 zfs:zil_claim+ce ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e840 zfs:dmu_objset_find+b6 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047e9f0 zfs:dmu_objset_find+12f ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047eba0 zfs:dmu_objset_find+12f ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047ec10 zfs:spa_load+51a ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047ec80 zfs:spa_load+35d ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047ecc0 zfs:spa_open_common+15b ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047ed00 zfs:spa_get_stats+42 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047ed40 zfs:zfs_ioc_pool_stats+3f ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047ed80 zfs:zfsdev_ioctl+144 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047ed90 genunix:cdev_ioctl+1d ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047edb0 specfs:spec_ioctl+50 ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047ede0 genunix:fop_ioctl+1a ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047eec0 genunix:ioctl+ac ()
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072 kern.notice] 
>>>>> fffffe800047ef10 unix:sys_syscall32+101 ()
>>>>> Mar 21 11:09:17 SERVER142 unix: [ID 100000 kern.notice]
>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 672855 kern.notice]
syncing
>>>>> file systems...
>>>>> This message posted from opensolaris.org
>>>>> _______________________________________________
>>>>> zfs-discuss mailing list
>>>>> zfs-discuss at opensolaris.org
>>>>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>>>>>
>>>>
>>>
>>> _________________________________________________________________
>>> Scarica Messenger 8.1 e chiama gratis in tutto il mondo! 
>>> http://get.live.com/it-it/messenger/features
>>>
>>
>
> _________________________________________________________________
> Push the button! Crea il tuo blog e fatti vedere... 
> http://pushthebutton2006.spaces.live.com/
>

Victor Latushkin

2007-Mar-21 13:19 UTC

head link

[zfs-discuss] HELP!! I can''t mount my zpool!!

Gino,

Gino Ruopolo ?????:> Victor,
>
> 1) crash dump dir has moved on the crashed zpool a few days ago :((((
> Anyway we think the crash is related to mpxio. We had tens of crash in 
> the
> last weeks but never lost a zpool!!
>
> 2) That particular unis is out of Sun contract
>
> We hope there is a way to recover our data ...I thought about one way to recover from some kind of similar situations 
available with putback of "6527325 want more assertions in the space map 
code" but then I looked at the stack backtrace and the source code once 
again and it looks like there is no clean way to try to recover from 
this situation even in the most recent code. I think someone from ZFS 
development team may provide additional input here.

Wbr,
Victor
>
> Thank you,
> Gino
>
>> From: Victor Latushkin <Victor.Latushkin at Sun.COM>
>> To: Gino Ruopolo <ginoruopolo at hotmail.com>
>> CC: zfs-discuss at opensolaris.org
>> Subject: Re: [zfs-discuss] HELP!! I can''t mount my zpool!!
>> Date: Wed, 21 Mar 2007 15:12:13 +0300
>>
>> Gino,
>>
>> Gino Ruopolo ??????????:
>>>
>>> Victor,
>>> can we try to mount the zpool on a S10U3 system?
>> No, this may require to use one of the recent Solaris Nevada builds. 
>> I''m trying to check relevant build number.
>>
>> What about answers to other my questions?
>>
>>
>> Wbr,
>> Victor
>>>> From: Victor Latushkin <Victor.Latushkin at Sun.COM>
>>>> To: Gino Ruopolo <ginoruopolo at hotmail.com>
>>>> CC: zfs-discuss at opensolaris.org
>>>> Subject: Re: [zfs-discuss] HELP!! I can''t mount my
zpool!!
>>>> Date: Wed, 21 Mar 2007 15:00:26 +0300
>>>>
>>>> Gino,
>>>>> S10U2
>>>> Ok, then if you have a support contract for this system you may
>>>> want to open new case for this issue.
>>>>>
>>>>> unfortunately we have nothing on the logs about the first
panic!
>>>> This is not good... Without it may be impossible to find out
what
>>>> went wrong. You may have nothing on the logs, but crash dumps
can
>>>> still be there. Have you checked this?
>>>>> Is there a way to force the mount of the zpool? We have
some
>>>>> important data on it!
>>>> This may be impossible to achieve on the version of Solaris
this
>>>> system is running.
>>>>
>>>> Victor
>>>>>
>>>>> Thank you,
>>>>> Gino
>>>>>
>>>>>
>>>>>> From: Victor Latushkin <Victor.Latushkin at
Sun.COM>
>>>>>> To: Gino Ruopolo <ginoruopolo at hotmail.com>
>>>>>> CC: zfs-discuss at opensolaris.org
>>>>>> Subject: Re: [zfs-discuss] HELP!! I can''t
mount my zpool!!
>>>>>> Date: Wed, 21 Mar 2007 14:04:45 +0300
>>>>>>
>>>>>> Hi Gino,
>>>>>>
>>>>>> What version of Solaris your server is running?
>>>>>>
>>>>>> What happens here is while opening your pool ZFS is
trying to
>>>>>> process ZFS Intent Log of this poll and discovers some 
>>>>>> inconsistency between on-disk state and ZIL contents.
>>>>>>
>>>>>> What was the first panic you refer to?
>>>>>>
>>>>>> Wbr,
>>>>>> Victor
>>>>>>
>>>>>> Gino Ruopolo ?????????????????????:
>>>>>>> Hi all.
>>>>>>> One of our server had a panic and now
can''t mount the zpool
>>>>>>> anymore!
>>>>>>> Here is what I get at boot:
>>>>>>>
>>>>>>>
>>>>>>> Mar 21 11:09:17 SERVER142
^Mpanic[cpu1]/thread=ffffffff90878200:
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 603766
kern.notice]
>>>>>>> assertion failed: ss->ss_start <= start
(0x670000b800 <= 0x67
>>>>>>> 00009000), file: ../../common/fs/zfs/space_map.c,
line: 126
>>>>>>> Mar 21 11:09:17 SERVER142 unix: [ID 100000
kern.notice]
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 802836
kern.notice]
>>>>>>> fffffe800047e320 fffffffffb9ad0b9 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e3a0 zfs:space_map_remove+1a3 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e3d0 zfs:space_map_claim+32 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e410 zfs:zfsctl_ops_root+2f9db09d ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e450 zfs:zfsctl_ops_root+2f9db30c ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e470 zfs:zio_dva_claim+1d ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e480 zfs:zio_next_stage+72 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e490 zfs:zio_gang_pipeline+1e ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e4a0 zfs:zio_next_stage+72 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e4d0 zfs:zio_wait_for_children+49 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e4e0 zfs:zio_wait_children_ready+15 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e4f0 zfs:zfsctl_ops_root+2f9f41e6 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e520 zfs:zio_wait+2d ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e550 zfs:zil_claim_log_block+60 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e650 zfs:zil_parse+181 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e690 zfs:zil_claim+ce ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e840 zfs:dmu_objset_find+b6 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047e9f0 zfs:dmu_objset_find+12f ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047eba0 zfs:dmu_objset_find+12f ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047ec10 zfs:spa_load+51a ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047ec80 zfs:spa_load+35d ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047ecc0 zfs:spa_open_common+15b ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047ed00 zfs:spa_get_stats+42 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047ed40 zfs:zfs_ioc_pool_stats+3f ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047ed80 zfs:zfsdev_ioctl+144 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047ed90 genunix:cdev_ioctl+1d ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047edb0 specfs:spec_ioctl+50 ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047ede0 genunix:fop_ioctl+1a ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047eec0 genunix:ioctl+ac ()
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 655072
kern.notice]
>>>>>>> fffffe800047ef10 unix:sys_syscall32+101 ()
>>>>>>> Mar 21 11:09:17 SERVER142 unix: [ID 100000
kern.notice]
>>>>>>> Mar 21 11:09:17 SERVER142 genunix: [ID 672855
kern.notice]
>>>>>>> syncing file systems...
>>>>>>> This message posted from opensolaris.org
>>>>>>> _______________________________________________
>>>>>>> zfs-discuss mailing list
>>>>>>> zfs-discuss at opensolaris.org
>>>>>>>
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>>>>>>>
>>>>>>
>>>>>
>>>>>
_________________________________________________________________
>>>>> Scarica Messenger 8.1 e chiama gratis in tutto il mondo! 
>>>>> http://get.live.com/it-it/messenger/features
>>>>>
>>>>
>>>
>>> _________________________________________________________________
>>> Push the button! Crea il tuo blog e fatti vedere... 
>>> http://pushthebutton2006.spaces.live.com/
>>>
>>
>
> _________________________________________________________________
> Calcio, Quiz, Dama, Scacchi? Prova tutti i nuovi giochi di Messenger? 
> Gratis! http://get.live.com/it-it/messenger/features
>

Possibly Parallel Threads

Search for more reasonably related threads

zfs discuss - Mar 2007 - HELP!! I can''t mount my zpool!!

[zfs-discuss] HELP!! I can''t mount my zpool!!

[zfs-discuss] HELP!! I can''t mount my zpool!!

[zfs-discuss] HELP!! I can''t mount my zpool!!

[zfs-discuss] HELP!! I can''t mount my zpool!!

[zfs-discuss] HELP!! I can''t mount my zpool!!

Possibly Parallel Threads