On 11/ 9/10 01:47 AM, Peter Taps wrote:
My understanding is that there is a way to create a zfs "checkpoint" before
doing any system upgrade or installing a new software. If there is a problem, one can
simply rollback to the stable checkpoint.
I am familiar with snapshots and clones. However,
On 2/25/2010 10:24 PM, Paul B. Henson wrote:
The main ACL problem we've having now (having resolved most of
them, yay) is interaction with chmod() and legacy mode bits, and the
disappointing ease with which an undesired chmod can completely destroy an
ACL.
examples?
Are you using aclmode=passth
dick hoogendijk wrote:
r...@westmark:/# share
-...@store/snaps /store/snaps sec=sys,rw=arwen,root=arwen ""
arwen# zfs send -Rv rp...@0906 > /net/westmark/store/snaps/rpool.0906
zsh: permission denied: /net/westmark/store/snaps/rpool.0906
try sharing with the @ network syntax. See "m
Uwe Dippel wrote:
Next, a power failure, 2 hours later, and this is what zpool status -v
thinks:
Reliability at power failure? That was my question, and I had to learn
Your question should be about HARDWARE reliability after power failure.
Some (cheap) hardware are very unreliable, either t
I wrote:
> Vincent Fox wrote:
>> Ummm, could you name a specific patch number that would apply to a stock
>> install?
>>
>> Or suggest a way to search?
>
> # pca -l missing
or, of course, "smpatch analyze"
___
zfs-discuss mailing list
zfs-discuss@opens
Vincent Fox wrote:
> Ummm, could you name a specific patch number that would apply to a stock
> install?
>
> Or suggest a way to search?
(Google: "pca solaris")
On a "freshly liveupgraded" box:
# pca -l missing
Using /var/tmp/patchdiag.xref from Nov/11/08
Host: hostname (SunOS 5.10/Generic_137
