Am 19.09.2010 um 18:59 schrieb Victor Latushkin:
On Sep 19, 2010, at 12:08 AM, Stephan Ferraro wrote:
Is there a way to fsck the spacemap?
Does scrub helps for this?
No, because issues that you see are internal inconsistencies with unclear
nature.
Though as actual issue varies from
Am 19.09.2010 um 19:24 schrieb Victor Latushkin:
On Sep 19, 2010, at 9:06 PM, Stephan Ferraro wrote:
Am 19.09.2010 um 18:59 schrieb Victor Latushkin:
On Sep 19, 2010, at 12:08 AM, Stephan Ferraro wrote:
Is there a way to fsck the spacemap?
Does scrub helps for this?
No, because
Did you see this thread?
http://opensolaris.org/jive/thread.jspa?messageID=5006
59#500659
I get on this link:
Tomcat http error 500:
The server encountered an internal error () that prevented it from fulfilling
this request.
He had problems with ZFS. It turned out to be faulty
RAM. ZFS
I'm really angry against ZFS:
My server no more reboots because the ZFS spacemap is again corrupt.
I just replaced the whole spacemap by recreating a new zpool from scratch and
copying back the data with zfs send zfs receive.
Did it copied corrupt spacemap?!
For me its now terminated. I loss to
For the developpers, this is my error message:
Sep 18 09:43:56 global genunix: [ID 361072 kern.warning] WARNING: zfs: freeing
free segment (offset=379733483520 size=4096)
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
Is there a way to fsck the spacemap?
Does scrub helps for this?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
This is new for me:
$ zpool status
pool: rpool
state: ONLINE
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
I can't edit now my /etc/system file because system is not booting.
Is there a way to force this parameters to Solaris kernel on booting with Grub?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
If I launch opensolaris with -kd I'm able to do this:
aok/W 1
but if I type:
zfs_recover/W 1
then I get an unkown symbol name error.
Any idea how I could force this variables?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
when I execute
::load zfs
I get kernel panic because of this $...@#(*($...@# space_map_add problem.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
Here is the solution (thanks to Gavin Maltby from mdb forum):
Boot with -kd option to enter in kmdb and type the following commands:
aok/W 1
::bp zfs`zfs_panic_recover
:c
wait that it stops at breakpoint then type this:
zfs_recover/W1
:z
:c
--
This message posted from opensolaris.org
11 matches
Mail list logo
