Hi,
Our zfs nfs build server running snv_73 (pool created back before
zfs integrated to ON) paniced I guess from zfs the first time
and now panics on attempted boot every time as below. Is this
a known issue and, more importantly (2TB of data in the pool),
any suggestions on how to recover
Nope. This feature hasn't made it to S10U4. We are anticipating it to be
available in S10U5.
--
Prabahar.
Scott wrote:
Did the ZFS gzip compression feature (i.e. zfs set compression=gzip) make
it in to Solaris 10 U4? I was looking forward to being able to use it in a
production Solaris
Thanks Jürgen,
I was hit by 6423745 (see below) but the main problem is that /sbin/
zpool is linked to /usr/lib/libdiskmgt.so.1 and since /usr was on my
datapool, it failed systematically.
I don't think it makes sense that an executable in /sbin be linked to
a lib in /usr/lib. The only
On 30/09/2007, at 7:45 AM, Kugutsumen wrote:
Thanks Jürgen,
I was hit by 6423745 (see below) but the main problem is that /sbin/
zpool is linked to /usr/lib/libdiskmgt.so.1 and since /usr was on
my datapool, it failed systematically.
I don't think it makes sense that an executable in
OK,
I guess using this ...
set md:mirrored_root_flag=1
for Solaris Volume Manager (SVM) is not supported and could cause problems.
I guess it's back to my first idea ...
With 2 disks, setup three SDR's (State Database Replicas)
Drive 0 = 1 SDR - If this drive fails auto-magically
OpenSolaris builds are like development snapshots...they're not a release and
thus there are no patches.
SXCE is just binary build from these snapshots... it's there are convenience
only, and patches are applied like in every other development project... by
updating from source repository,
