I have a huge problem with space maps on thumper. Space maps takes over 3GB
and write operations generates massive read operations.
Before every spa sync phase zfs reads space maps from disk.
I decided to turn on compression for pool ( only for pool, not filesystems )
and it helps.
Now space map
On Sep 14, 2007, at 8:16 AM, Łukasz wrote:
> I have a huge problem with space maps on thumper. Space maps takes
> over 3GB
> and write operations generates massive read operations.
> Before every spa sync phase zfs reads space maps from disk.
>
> I decided to turn on compression for pool ( only
>
> On Sep 14, 2007, at 8:16 AM, Łukasz wrote:
>
> > I have a huge problem with space maps on thumper.
> Space maps takes
> > over 3GB
> > and write operations generates massive read
> operations.
> > Before every spa sync phase zfs reads space maps
> from disk.
> >
> > I decided to turn on com
?ukasz wrote:
> I have a huge problem with space maps on thumper. Space maps takes over 3GB
> and write operations generates massive read operations.
> Before every spa sync phase zfs reads space maps from disk.
>
> I decided to turn on compression for pool ( only for pool, not filesystems )
> a
> > Now space maps, intent log, spa history are compressed.
>
> All normal metadata (including space maps and spa history) is always
> compressed. The intent log is never compressed.
Can you tell me where space map is compressed ?
Buffer is filled up with:
468 *entry++ = SM_
Łukasz K wrote:
>>> Now space maps, intent log, spa history are compressed.
>> All normal metadata (including space maps and spa history) is always
>> compressed. The intent log is never compressed.
>
> Can you tell me where space map is compressed ?
we specify that it should be compressed in db
