Hello,
wanted to know if there are any updates on this topic ?
Regards,
Robert
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I plan on filing a support request with Sun, and will try to post back with any
results.
Scott
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
That sounds very interesting and for me it sounds like a bug.
I expect this is what happened:
1) Create a zvol with meta data in the first 64k (so data starts at 64k)
2) Updated to 124
3) Comstar propably still using the first 64k of the zvol no tmigrating the
data off (so data starts at 64k)
4
That is likely it. I create the volume using 2009.06, then later upgraded to
124. I just now created a new zvol, connected it to my windows server,
formatted, and added some data. Then I snapped the zvol, cloned the snap, and
used 'pfexec sbdadm create-lu'. When presented to the windows server,
Ah, I didn't see the original post. If you're using an old COMSTAR
version prior to build 115, maybe the metadata placed at the first 64K
of the volume is causing problems?
http://mail.opensolaris.org/pipermail/storage-discuss/2009-September/007192.html
The clone and create-lu process works fo
Sure, but that will put me back into the original situation.
-Scott
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Use create-lu to give the clone a different GUID:
sbdadm create-lu /dev/zvol/rdsk/data01/san/gallardo/g-testandlab
--
Dave
On 2/8/10 10:34 AM, Scott Meilicke wrote:
Thanks Dan.
When I try the clone then import:
pfexec zfs clone
data01/san/gallardo/g...@zfs-auto-snap:monthly-2009-12-01-00:00
Thanks Dan.
When I try the clone then import:
pfexec zfs clone
data01/san/gallardo/g...@zfs-auto-snap:monthly-2009-12-01-00:00
data01/san/gallardo/g-testandlab
pfexec sbdadm import-lu /dev/zvol/rdsk/data01/san/gallardo/g-testandlab
The sbdadm import-lu gives me:
sbdadm: guid in use
which mak
On Thu, Feb 04, 2010 at 04:17:17PM -0800, Scott Meilicke wrote:
> At this point, my server Gallardo can see the LUN, but like I said, it looks
> blank to the OS. I suspect the 'sbdadm create-lu' phase.
Yeah, try the import version of that command.
--
Dan.
pgphS37DCPdV0.pgp
Description: PGP sig
I have a single zfs volume, shared out using COMSTAR and connected to a Windows
VM. I am taking snapshots of the volume regularly. I now want to mount a
previous snapshot, but when I go through the process, Windows sees the new
volume, but thinks it is blank and wants to initialize it. Any ideas
10 matches
Mail list logo
