search for: snv_131

...o export/home , everything behaves properly. If I create sub-filesystem export/home/newuser and chown it, then on NFS client I see new owner. I checked, both filesystems (export/home and export/test1) have exactly the same ZFS properties and ACLs. Only difference is that export/home was created on snv_131 (AFAIR) and export/test1 was created on snv_134 (and every filesystem I create on 134 has the same problem with child filesystems). what could be the problem? It is annoying to umount/chown/mount every time when I need to change owner. -- This message posted from opensolaris.org

Hi All, I used the following script from the dtrace manual to measure how long a particular process runs on the cpu. Modified it to look at the exact timestamps: [i] sched:::on-cpu { self->ts = timestamp; printf("on=%d\n", self->ts) } sched:::off-cpu /self->ts/ { printf("off=%d\n", timestamp) self->ts = 0; } [/i] The output looks like this: [i]on=24591 off=24603

According to various posts the LSI SAS3081E-R seems to work well with OpenSolaris. But I''ve got pretty chilled-out from my recent problems with Areca-1680''s. Could anyone please confirm that the LSI SAS3081E-R works well ? Is hotplug supported ? Anything else I should know before buying one of these cards ? Thanks, Arnaud

...tive messages could be found in logs. The issue was reproducible. The same happened for ''zfs destroy pool/dataset at snapshot'' Thus, the conclusion was that the snapshot was indeed the problem. Solution: After trying several things, including updating the system to snv_130 and snv_131, I had the idea to restore the dataset to the snapshot before doing another zfs destroy attempt. ''zfs rollback pool/dataset at snapshot'' ''zfs unmount -f pool/dataset'' ''zfs destroy -r pool/dataset'' Et voil?! It worked. Conclusion: I guess the...