Markus Kovero nebula.fi> writes:
>
>
> > Sync was disabled on the main pool and then let to inherrit to everything
else. The > reason for disabled
> this in the first place was to fix bad NFS write performance (even with > Zil
on an X25e SSD it was under 1MB/s).
> > I've also tried setting the
Am 28.04.11 15:16, schrieb Victor Latushkin:
On Apr 28, 2011, at 5:04 PM, Stephan Budach wrote:
Am 28.04.11 11:51, schrieb Markus Kovero:
failed: space_map_load(sm, zfs_metaslab_ops, SM_FREE, smo,
spa->spa_meta_objset) == 0, file ../zdb.c, line 571, function dump_metaslab
Is this something I s
On Apr 28, 2011, at 5:04 PM, Stephan Budach wrote:
> Am 28.04.11 11:51, schrieb Markus Kovero:
>>> failed: space_map_load(sm, zfs_metaslab_ops, SM_FREE, smo,
>>> spa->spa_meta_objset) == 0, file ../zdb.c, line 571, function dump_metaslab
>>> Is this something I should worry about?
>>> uname -a
>>
Am 28.04.11 11:51, schrieb Markus Kovero:
failed: space_map_load(sm, zfs_metaslab_ops, SM_FREE, smo,
spa->spa_meta_objset) == 0, file ../zdb.c, line 571, function dump_metaslab
Is this something I should worry about?
uname -a
SunOS E55000 5.11 oi_148 i86pc i386 i86pc Solaris
I thought we were ta
Sync was disabled on the main pool and then let to inherrit to everything else.
The> reason for disabled this in the first place was to fix bad NFS write
performance (even with> Zil on an X25e SSD it was under 1MB/s).
I've also tried setting the logbias to throughput and latency but they bot
> failed: space_map_load(sm, zfs_metaslab_ops, SM_FREE, smo,
> spa->spa_meta_objset) == 0, file ../zdb.c, line 571, function dump_metaslab
> Is this something I should worry about?
> uname -a
> SunOS E55000 5.11 oi_148 i86pc i386 i86pc Solaris
I thought we were talking about solaris 11 express,
On 4/27/11 4:00 AM, Markus Kovero wrote:
Sync was disabled on the main pool and then let to inherrit to everything else.
The> reason for disabled this in the first place was to fix bad NFS write
performance (even with> Zil on an X25e SSD it was under 1MB/s).
I've also tried setting the log
On 27 April, 2011 - Matthew Anderson sent me these 3,2K bytes:
> Hi All,
>
> I've run into a massive performance problem after upgrading to Solaris 11
> Express from oSol 134.
>
> Previously the server was performing a batch write every 10-15 seconds and
> the client servers (connected via NFS
> Sync was disabled on the main pool and then let to inherrit to everything
> else. The > reason for disabled this in the first place was to fix bad NFS
> write performance (even with > Zil on an X25e SSD it was under 1MB/s).
> I've also tried setting the logbias to throughput and latency but t
fs-discuss@opensolaris.org'
Subject: Re: [zfs-discuss] No write coalescing after upgrade to Solaris 11
Express
Matthew Anderson wrote:
> Hi All,
>
> I've run into a massive performance problem after upgrading to Solaris 11
> Express from oSol 134.
>
> Previously the server wa
Matthew Anderson wrote:
Hi All,
I've run into a massive performance problem after upgrading to Solaris 11
Express from oSol 134.
Previously the server was performing a batch write every 10-15 seconds and the
client servers (connected via NFS and iSCSI) had very low wait times. Now I'm
seeing
11 matches
Mail list logo
