Hello,
I've had a power kill on a server and the V880 cannot now mount the main
root filesystem.
I can boot the server into single user mode from the network.
However, how can i rectify the corrupted ZFS disk ?
Cheers.
T.
NOTICE:
spa_import_rootpool: error 22
Cannot mou
Ignore this post.
I managed to solve this problem.
On 24/02/2011 08:37, "Thierry Delaitre" wrote:
> Hello,
>
> Sbdadmin create-lu throws an sbdadm: data file error¹ error message on a
> cloned ZFS pool.
>
> The above works ok on a non-cloned FS. Is this no
Hello,
Sbdadmin create-lu throws an sbdadm: data file error¹ error message on a
cloned ZFS pool.
The above works ok on a non-cloned FS. Is this not meant to work with
comstar ?
Thierry.
--
The University of Westminster is a charity and a company limited by
guarantee. Registration number: 97
Hello,
I¹m using ZFS to export some iscsi targets for the virtual box iscsi
initiator.
It works ok if I try to install the guest OS manually.
However, I¹d like to be able to import my already prepared guest os vdi
images into the iscsi devices but I can¹t figure out how to do it.
Each time I tr
Would you recommend a particular distribution to implement a persistent
iscsi server compatible with VDI ?
Thierry.
From: Richard Elling [mailto:richard.ell...@gmail.com]
Sent: 30 January 2011 16:28
To: Thierry Delaitre
Cc: zfs-discuss@opensolaris.org
Subject: Re: [zfs-discuss] VDI, ZFS
Hello,
I¹ve got VDI 3.2.1 and I¹m experiencing ZFS iscsi persistence after
rebooting the ZFS Solaris 10 (s9/10 s10x_u9wos_14a X86) server so I tried to
use NexentaOS_134f as according
to http://sun.systemnews.com/articles/145/5/Virtualization/22991, VDI 3.1.1
supports COMSTAR
However, with nexent
Hello,
A ZFS VDI related question. I'm exporting an iscsi share from a linux
box which i'm mounting on a Solaris 10 VDI broker and subsequently used
by the desktop providers. This is for a proof of concept. This works
fine under VDI 3.2.1 until i reboot the VDI broker.
After the broker rebo
