Paul B. Henson wrote:
On Thu, 8 May 2008, Mark Shellenbaum wrote:
we already have the ability to allow users to create/destroy snapshots
over NFS. Look at the ZFS delegated administration model. If all you
want is snapshot creation/destruction then you will need to grant
I have a server thumper1 which exports its root (UFS) filesystem to one
specific server hoss via /etc/dfs/dfstab so that we can backup various system
files. When I added a ZFS pool mypool to this system, I shared it to hoss and
several other machines using the ZFS sharenfs property.
Prior to
I can now see the snapshots in the CLI if i do a mkdir from the windows command
line as opposed to getting stuck with a New Folder, which seems to confuse
the CLI (maybe snapshots cant have spaces in the name?
I was wondering, if there was an easy way for us to script zfs home filesystem
We had a panic around noon on Saturday, which it mostly recovered
itself. All ZFS NFS exports just remounted, but the UFS on zdev NFS
exports did not, needed manual umount mount on all clients for some
reason.
Is this a known bug we should consider a patch for?
May 10 11:49:46
OK, this is a pretty damn poor panic report if I may say no, not had
much sleep.
Solaris Express Developer Edition 9/07 snv_70b X86
Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Dumping to /dev/dsk/c6t0d0s1
certainly looks like a non-mirrored dump dev...
You might try a manual savecore telling it to ignore the dump valid
header and see what you get...
savecore -d
and perhaps try telling it to look directly at the dump device...
savecore -f device
You should also,
savecore -d
System dump time: Sat May 10 11:51:56 2008
Constructing namelist /var/crash/x4500/unix.1
Constructing corefile /var/crash/x4500/vmcore.1
45% done
When we get the second x4500 in we can do more testing in that area. But
more importantly we need try to work out why the UFS exported
