As described in the 'status' section, ZFS was able to recover from the
error and applications are unaffected. To be sure, can you
'fmdump -e' output? You can also do a 'zpool scrub' and see if that
produces an error.
>From the ZFS perspective, you had one disk return a single failure, but
we we
Hi Jeff,
You should take a look at this:
http://blogs.sun.com/erickustarz/entry/poor_man_s_cluster_end
We added the hostid/hostname to the vdev label. What this means is
that we stop you from importing a pool onto multiple machines (which
would have lead to corruption).
eric
On May 30, 2
Hi guys, please help to clarify.
Do usual postgresql pg_dump today and have got an error.
-
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: compressed data is corrupt
pg_dump: The command was: COPY public.candidates (id, name, surname, mid_name,
compen
Hi,
I have been trying to setup a boot ZFS filesystem since b63 and found out about
bug 6553537 that was preventing boot from ZFS filesystems starting from b63.
First question is whether b65 has solved the problem as was planned on the bug
page. Second question is: as I cannot boot successfully
On Fri, Jun 01, 2007 at 06:37:21PM -0700, Richard L. Hamilton wrote:
> > I'd love to be able to server zvols out as SCSI or FC
> > targets. Are
> > there any plans to add this to ZFS? That would be
> > amazingly awesome.
>
> Can one use a spare SCSI or FC controller as if it were a target?
Most
On Jun 2, 2007, at 8:27 PM, Jesus Cea wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toby Thain wrote:
Sorry, I should have cited it. Blew my chance to moderate by
posting to
the thread :)
http://ask.slashdot.org/comments.pl?sid=236627&cid=19319903
I computed the FUD factor by sorti
I wrote
> Instead of compiling opensolaris for 4-6 hours, I've now used
> the following find / grep test using on-2007-05-30 sources:
>
> 1st test using Nevada build 60:
>
> % cd /files/onnv-2007-05-30
> % repeat 10 /bin/time find usr/src/ -name "*.[hc]" -exec grep FooBar {} +
This find + grep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harold Ancell wrote:
> Those of us who don't want to be part of the "debug ZFS boot" effort
> could very possibly get along for now by having a minimal toe hold in,
> say, a SVM RAID-1 UFS / filesystem, and after that gets started, mount
> as ZFS files
DISCLAIMERS:
ZFS bits on this server are old:
# pkginfo -l SUNWzfsr |grep -i version
VERSION: 11.11,REV=2006.01.03.01.17
OS is an old build of Nevada:
SunOS 5.11 snv_31
Experts,
I have what is hopefully a simple question. We have a ZFS pool
(dilbert) consisting of 6 2
> > > Just curious,is there any manual way of telling ZFS
> > to flush the
> > > buffers after queiscing the db other than taking a
> > ZFS snapshot?.
> >
> > If you're not taking a snapshot, why would you want
> > ZFS to flush the
> > buffers?
> >
>
> Maybe just a way to confirm some really i
> > Patching zfs_prefetch_disable = 1 has helped
> It's my belief this mainly aids scanning metadata. my
> testing with rsync and yours with find (and seen with
> du & ; zpool iostat -v 1 ) pans this out..
> mainly tracked in bug 6437054 vdev_cache: wise up or die
> http://www.opensolaris.org/jive/
You are right... I shouldn't post in the middle of the night... nForce
chipsets don't support AHCI.
On 6/4/07, J. David Beutel <[EMAIL PROTECTED]> wrote:
"Marko Milisavljevic" <[EMAIL PROTECTED]> wrote on 06/02/2007
02:03:56 AM:
> I think nForce 430 would be using AHCI driver if you set you BIOS
On Fri, 1 Jun 2007, Ben Bressler wrote:
> When I do the zfs send | ssh zfs recv part, the file system (folder) is
> getting created, but none of the data that I have in my snapshot is
> sent. I can browse on the source machine to view the snapshot data
> pool/.zfs/snapshot/snap-name and I see the
The following occurred to me as I'm in the process of debugging a SCSI
boot problem (immediate reboot after I tell GRUB to "go" on a Tyan
S2865 with a LSI Logic LSI20160B-F; every other possible use of the
LSI board works.):
While for the sake of simplicity and robustness we'd *like* everything
to
***
# cryptoadm list -p
Provider at user level:
=
/usr/lib/security/$ISA/pkcs11_kernel.so: All mechanisms are activated.
/usr/lib/security/$ISA/pkcs11_softtoken.so: All mechanisms are activated.
random is activated.
What about the /dev/random issue? Is there any way to fix this? I'd be
delighted to name a provider with cryptoadm, but I have no clue at all how this
works ...
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@openso
"Marko Milisavljevic" <[EMAIL PROTECTED]> wrote on 06/02/2007
02:03:56 AM:
I think nForce 430 would be using AHCI driver if you set you BIOS for
it, in current Nevada builds anyway, and I think that uses SATA
framework.
I don't see any BIOS option for AHCI, but when I get back in a couple
week
On 5/30/07, James C. McPherson <[EMAIL PROTECTED]> wrote:
Louwtjie Burger wrote:
> I know the above mentioned kit (2530) is new, but has anybody tried a
> direct attached SAS setup using zfs? (and the Sun SG-XPCIESAS-E-Z
> card, 3Gb PCI-E SAS 8-Port Host Adapter, RoHS:Y - which is the
> prefered
18 matches
Mail list logo
