On Mon, Feb 01, 2010 at 12:22:55PM -0800, Lutz Schumann wrote:
> > > Created a pool on head1 containing just the cache
> > device (c0t0d0). 
> > 
> > This is not possible, unless there is a bug. You
> > cannot create a pool
> > with only a cache device.  I have verified this on
> > b131:
> > # zpool create norealpool cache /dev/ramdisk/rc1
> > 1                    
> > invalid vdev specification: at least one toplevel
> > l vdev must be specified
> > 
> > This is also consistent with the notion that cache
> > devices are auxiliary
> > devices and do not have pool configuration
> > information in the label.
> 
> Sorry for the confustion ...  a little misunderstanding. I created a Pool 
> who's only data disk is the disk formally used as cache device in the pool 
> that switched. Then I exported this pool mad eform just a single disk (data 
> disk). And switched back. The exported pool was picked up as cache device ... 
> this seems really problematic. 

This is exactly the scenario I was concerned about earlier in the
thread.  Thanks for confirming that it occurs.  Please verify that the
pool had autoreplace=off (just to avoid that distraction), and file a
bug.  

Cache devices should not automatically destroy disk contents based
solely on device path, especially where that device path came along
with a pool import.  Cache devices need labels to confirm their
identity. This is irrespective of whether the cache contents after the
label are persistent or volatile, ie should be fixed without waiting
for the CR about persistent l2arc.

--
Dan.

Attachment: pgpjdt4tg1JNp.pgp
Description: PGP signature

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to