Dnia 26-07-2007 o godz. 13:31 Robert Milkowski napisał(a):
Hello Victor,
Wednesday, June 27, 2007, 1:19:44 PM, you wrote:
VL Gino wrote:
Same problem here (snv_60).
Robert, did you find any solutions?
VL Couple of week ago I put together an implementation of space maps
which
VL
Accessibility of the data is also a reason, in dual boot scenarios.
Doesn't need to be a native Windows driver, but something that still
ties into the Explorer. There's still the option of running Solaris in
VMware, but that's a bit heavy handed.
-mg
TT You like Windows /that much/ ? Note Sun
Windows has a user mode driver frame work thingy - came across it recently in
the lsit of services on my XP box. Perhaps this could be used to host a ZFS
driver on Windows?
Andrew.
This message posted from opensolaris.org
___
zfs-discuss mailing
Mark Furner wrote:
Hi
Sorry for the cross-posting, I'd sent this to zfs-code originally. Wrong
forum.
and I've already replied there:
http://mail.opensolaris.org/pipermail/zfs-code/2007-July/000557.html
--
Darren J Moffat
___
zfs-discuss
Hi
Sorry for the cross-posting, I'd sent this to zfs-code originally. Wrong
forum.
I'm looking into forensic aspects of ZFS, in particular ways to use ZFS tools
to investigate ZFS file systems without writing to the pools. I'm working on
a test suite of file system images within VTOC
Same problem here (snv_60).
Robert, did you find any solutions?
gino
check this http://www.opensolaris.org/jive/thread.jspa?threadID=34423tstart=0
Check spa_sync function time
remember to change POOL_NAME !
dtrace -q -n fbt::spa_sync:entry'/(char *)(((spa_t*)arg0)-spa_name) ==
POOL_NAME/{
Hi,
what is necessary to get it working from the solaris side. Is a driver on board
or is there no special one needed?
I just got a packed MM-5425CN with 256M. However i am lacking a pci-x 64bit
connector and not sure if it is worth the whole effort for my personal purposes.
Any comment are
A quick look through the source would seem to indicate that the
PERSISTENT RESERVE commands are not supported by the Solaris ISCSI
target at all.
Correct. There is an RFE outstanding for iSCSI Target to implement
PGR for both raw SCSI-3 devices, and block devices.
Hello Toby,
Thursday, July 26, 2007, 6:18:46 PM, you wrote:
TT On 26-Jul-07, at 1:24 PM, Robert Milkowski wrote:
Hello Matthew,
Thursday, July 26, 2007, 2:56:32 PM, you wrote:
MA Robert Milkowski wrote:
Hello Matthew,
Monday, June 18, 2007, 7:28:35 PM, you wrote:
MA FYI, we're already
Date: Thu, 26 Jul 2007 20:39:09 PDT
From: Anton B. Rang [EMAIL PROTECTED]
That said, I?m not sure exactly what this buys you for disk replication.
What?s special about files which have been closed? Is the point that
applications might close a file and then notify some other process of the
Hello the list,
I thought that it should be easy to do a clone (not in the term of zfs) of a
disk with zpool. This manipulation is strongly inspired by
http://www.opensolaris.org/jive/thread.jspa?messageID=135038
and
http://www.opensolaris.org/os/community/zfs/boot/
But unfortunately this
On Fri, Jul 27, 2007 at 08:32:48AM -0700, Adolf Hohl wrote:
what is necessary to get it working from the solaris side. Is a
driver on board or is there no special one needed?
I'd imagine so.
I just got a packed MM-5425CN with 256M. However i am lacking a
pci-x 64bit connector and not sure if
Adolf,
Yes, there was a separate driver, that I believe came from Micro
Memories. I installit from a package umem_Sol_Drv_Cust_i386_v01_10.pkg.
I just use pkgadd on it and it just worked. Sorry, I don't know if it's
publicly available or will even work for your device.
I gave details of that
Kevin wrote:
After a scrub of a pool with 3 raidz2 vdevs (each with 5 disks in them) I see
the following status output. Notice that the raidz2 vdev has 2 checksum
errors, but only one disk inside the raidz2 vdev has a checksum error. How is
this possible? I thought that you would have to
I've filed:
6586537 async zio taskqs can block out userland commands
to track this issue.
eric
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
Matthew Ahrens Matthew.Ahrens at sun.com writes:
So the errors on the raidz2 vdev indeed indicate that at least 3 disks below
it gave the wrong data for a those 2 blocks; we just couldn't tell which 3+
disks they were.
Something must be seriously wrong with this server. This is the first
16 matches
Mail list logo
