search for: blockpointer

Does ZFS currently attempt to group metadata in large sector-ranges on the disk? Can this be expected to happen "automagically" - i.e. during each TXG close we have to COW-update whole branches of the blockpointer tree, so these new blocks might "just happen" to always coalesce into larger sector groups? Rationale: larger regions dedicated to smallish block pointers might be better cached (i.e. with VDEV prefetch) and speed up housekeeping including scrubs and zfs sends. They could also reduce fra...

...ure my original mail got through to the list (I haven''t received it back), so I attach it below. Anyhow, now I have a saved kernel crash dump of the system panicking when it tries to - I believe - deferred-release the corrupted deduped blocks which are no longer referenced by the userdata/blockpointer tree. As I previously wrote in my thread on unfixeable corruptions vs. dedup, there may be some single- or multiple-block references from DDT pointing into "nowhere" - the block pointed to contains non-matching data, and now the BP tree does not point to those blocks either. And there ar...

> > Offlist/OT - Sheer guess, straight out of my parts - maybe a cronjob to > rebuild the locate db or something similar is hammering it once a week? In the problem condition, there appears to be very little going on on the system. eg., root at server5:/tmp# /usr/local/bin/top last pid: 3828; load avg: 4.29, 3.95, 3.84; up 6+23:11:4407:12:47 79 processes: 78 sleeping, 1 on

...this apply to metadata in particular? ;) Does this large factor apply to ZVOLs with fixed block size being defined "small" (i.e. down to the minimum 512b/4k available for these disks)? 3***) In fact, for the considerations above, what is metadata? :) Is it only the tree of blockpointers, or is it all the two or three dozen block types except userdata (ZPL file, ZVOL block) and unallocated blocks? AND ON A SIDE NOTE: I do hope to see answers from the gurus on the list to these and other questions I posed recently. One frequently announced weakness in ZFS is the relativ...

hi, i have raid1 on zfs with 2 device on pool first device died and boot from second not working... i try to get http://mfsbsd.vx.sk/ flash and load from it with zpool import http://puu.sh/2402E when i load zfs.ko and opensolaris.ko i see this message: Solaris: WARNING: Can''t open objset for zroot/var/crash Solaris: WARNING: Can''t open objset for zroot/var/crash zpool status:

Hello all, I understand that relatively high fragmentation is inherent to ZFS due to its COW and possible intermixing of metadata and data blocks (of which metadata path blocks are likely to expire and get freed relatively quickly). I believe it was sometimes implied on this list that such fragmentation for "static" data can be currently combatted only by zfs send-ing existing