|
Description
|
It appears that ZFS writes to an offlined disk after its "zpool offline" command successfuly returns.
See the following script for a way to reproduce this:
----------
#!/bin/sh
mkfile 128m /tmp/file1
mkfile 128m /tmp/file2
dev1=`lofiadm -a /tmp/file1`
dev2=`lofiadm -a /tmp/file2`
zpool create test mirror $dev1 $dev2
zpool offline test $dev1
bef=`digest -a md5 $dev1`
echo "before: $bef"
sleep 5
aft=`digest -a md5 $dev1`
echo "after: $aft"
zpool destroy test
lofiadm -d $dev1
lofiadm -d $dev2
rm /tmp/file1
rm /tmp/file2
----------
On my snv_86 OpenSolaris system, when running that script I always get different checksums, e.g.:
before: 9e8c29b0e6304523bc9dfe641c3c3f22
after: 755269b069c3f57df699dc8d193127f6
|
