On Sep 23, 2010, at 1:11 AM, Stephan Ferraro wrote:
>>
>> He had problems with ZFS. It turned out to be faulty
>> RAM. ZFS is so sensitive it detects and reports
>> problems to you. No other filesystem does that, so
>> you think ZFS is problematic and switch. But the
>> other filesystems is slowl
> Did you see this thread?
> http://opensolaris.org/jive/thread.jspa?messageID=5006
> 59
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
Did you see this thread?
http://opensolaris.org/jive/thread.jspa?messageID=500659
He had problems with ZFS. It turned out to be faulty RAM. ZFS is so sensitive
it detects and reports problems to you. No other filesystem does that, so you
think ZFS is problematic and switch. But the other filesy
On Sep 18, 2010, at 11:37 AM, Stephan Ferraro wrote:
> I'm really angry against ZFS:
Emotions rarely help to get to the root cause...
> 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
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
zfs-discu
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
