[Bug 256205] lseek() with SEEK_HOLE some times wrongly reports holes on ZFS

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 31 May 2021 15:16:56 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256205

--- Comment #8 from Robert Clausecker <fuz_at_fuz.su> ---
(In reply to Alan Somers from comment #7)

Hi Alan,

The cache file /etc/zfs/zpool.cache is there and seems fine.  Here is what zdb
-C outputs:

# zdb -C
tau:
    version: 5000
    name: 'tau'
    state: 0
    txg: 439
    pool_guid: 2019163837599314243
    errata: 0
    hostname: 'eta'
    com.delphix:has_per_vdev_zaps
    vdev_children: 1
    vdev_tree:
        type: 'root'
        id: 0
        guid: 2019163837599314243
        create_txg: 4
        children[0]:
            type: 'disk'
            id: 0
            guid: 12664617697930720246
            path: '/dev/da0p3'
            whole_disk: 1
            metaslab_array: 131
            metaslab_shift: 34
            ashift: 12
            asize: 1991530512384
            is_log: 0
            DTL: 302
            create_txg: 4
            com.delphix:vdev_zap_leaf: 129
            com.delphix:vdev_zap_top: 130
    features_for_read:
        com.delphix:hole_birth
        com.delphix:embedded_data

Though interestingly, this does not match the pool label:

# zdb -l da0s2a
------------------------------------
LABEL 0
------------------------------------
    version: 5000
    name: 'tau'
    state: 0
    txg: 112629
    pool_guid: 12522957766422004777
    errata: 0
    hostname: 'tau.fuz.su'
    top_guid: 16278934493555373134
    guid: 16278934493555373134
    vdev_children: 1
    vdev_tree:
        type: 'disk'
        id: 0
        guid: 16278934493555373134
        path: '/dev/da0s2a'
        whole_disk: 1
        metaslab_array: 65
        metaslab_shift: 31
        ashift: 12
        asize: 231409188864
        is_log: 0
        create_txg: 4
    features_for_read:
        com.delphix:hole_birth
        com.delphix:embedded_data
    labels = 0 1 2 3 


Could the cache file perhaps be stale?  If yes, how do I fix this?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Mon May 31 2021 - 15:16:56 UTC

Original text of this message