Hi all,

I'm seeing some puzzling behaviour with my RAID-Z.

loki# uname -a
FreeBSD loki.local 8.2-RELEASE-p1 FreeBSD 8.2-RELEASE-p1 #4: Sat Apr 30 
10:39:46 PDT 2011     

loki# zpool status storage
  pool: storage
 state: DEGRADED
 scrub: none requested

        NAME           STATE     READ WRITE CKSUM
        storage        DEGRADED     0     0     0
          raidz1       DEGRADED     0     0     0
            da2        ONLINE       0     0     0
            replacing  DEGRADED     0     0     0
              da0/old  OFFLINE      0     0     0
              da0      ONLINE       0     0     0
            da1        ONLINE       0     0     0
            da3        ONLINE       0     0     0
            da4        ONLINE       0     0     0
            da5        ONLINE       0     0     0
          da2          ONLINE       0     0     0

errors: No known data errors

This was after a drive (da0) died, which I replaced, resilvered then upgraded 
the pool to v15.

My strong belief is that da2 has always been a cache drive (a 256Gb SSD) and 
has never been a part of "storage". The drive labelled da2 in "storage" had 
previously been da6, but obviously there's now some kind of weird label 
duplication issue, in addition to a never ending "replacing" process for da0.

loki# ls /dev/da?
/dev/da0        /dev/da1        /dev/da2        /dev/da3        /dev/da4        
/dev/da5        /dev/da6

All other da? drives are 2Tb spinning discs and seem to be in good working 
order. The filesystems are all accessible and operational with no corruption 
that I can see. It should be noted that da2 in the pool had 2 checksum errors 
prior to clearing and da2 in caches reported corruption immediately after I 
replaced da0.

I've tried exporting/importing, scrubbing, clearing, removing da2, removing 
da0/old and even rebooting the whole machine. Not made any headway and stumped 
as to what I should try next. Any advice would be greatly appreciated.

- Andrew
zfs-discuss mailing list

Reply via email to