wrote:
>
>
>
> Paul Jochum wrote:
>>What the lsiutil does for me is clear the persistent mapping for
>> all of the drives on a card.
> Since James confirms that I'm doomed to ad hoc methods tracking
> device-ids to bays, I'm interested in knowing
ic. What I really want is to disable
> to persistent mapping logic completely - is the `lsiutil` doing that
> for you?
>
> Thanks,
> Kent
>
>
>
> Paul Jochum wrote:
>> Hi Kent:
>>
>> I have run into the same problem before, and have worked with LSI and
s helps. I happened to need it last night again (I normally have to
run it after re-imaging a box, assuming that I don't want to save the data that
was on those drives).
Paul Jochum
This message posted from opensolaris.org
___
zfs-discuss mai
I agree, being able to delete the snapshot that a clone is attached to would be
a nice feature. Until we get that, this is what I have done (in case this
helps anyone else):
1) snapshot the filesystem
2) clone the snapshot into a seperate pool
3) only nfs mount the seperate pool with clones
Th
Hi Richard:
I just tried your suggestion, unfortunately it doesn't work. Basically:
make a clone of the snapshot - works bine
in the clone, remove the directories - works fine
make a snapshot of the clone - works fine
destroy the clone - fails, because ZFS reports that the "filesystem has
child
Hi All:
Actually, I am running into the same case (need to remove certain files from a
snapshot), let me give you a good example of why we need to do it.
In our case, we use zfs snapshots to store online backups of home file systems
(that is, readily accessable to employees if they need to reco
