this zpool?
-Galen
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
-ordered?
-Galen
On Dec 22, 2009, at 12:40 PM, James Risner wrote:
Can you post a zpool import -f for us to see?
One thing I ran into recently is that if the drives arrangement was changed
(like drives swapped) it can't recover. I moved an 8 drive array recently,
and didn't worry about
I have a raidz1 zpool (Companion) I am unable to import. One of the
disks has physically failed and cannot be recognized by any computer,
and it is unlikely physical repairs or data recovery is possible.
No other disks are reporting errors. One other disk (not the failed
one) threw
all disks as 'online' as well, even if they are physically
not present.
Suggestions anybody?
-Galen
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I'm still struggling with slow resilvering performance. There doesn't seem to
be any clear bottleneck at this point.. and it's going glacially slow.
scrub: resilver in progress for 11h2m, 27.86% done, 28h35m to go
Load averages are like 0.13-0.15 range, CPU usage is 10%, the machine is doing
media. And the whole
point of a zpool is so that it manages the storage so I don't have to
do stupid things like this.
Ideas anybody?
-Galen
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs
to go
copy off the offending device. Again.
I wish I had a better solution, because the zpool functions fine, no
data errors, but resilvering loops forever. I love ZFS as an on-disk
format. I increasingly hate the implementation of ZFS software.
-Galen
On Jul 13, 2009, at 5:34 AM, Ross
amount of unreadable data.
-Galen
On Jul 13, 2009, at 6:50 AM, Ross Walker wrote:
Maybe it's the disks firmware that is bad or maybe they're jumpered
for 1.5Gbps on a 3.0 only bus? Or maybe it's a problem with the disk
cable/bay/enclosure/slot?
It sounds like there is more then ZFS
.
Is there a more proper way to approach this issue? Should I be filing
a bug report?
-Galen
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On Jul 10, 2009, at 3:32 PM, Miles Nordin wrote:
g == Galen gal...@zinkconsulting.com writes:
g the disk being resilvered is 1 to 3 MB/sec.
see:
6592835 resilvering is at least 10x too slow
6602697 pool has small write throughput during resilver
http://bugs.opensolaris.org/view_bug.do
I've never used snapshotting on this zpool and I can't imagine how it
would snapshot without my involvement.
-Galen
On Jul 11, 2009, at 2:22 PM, Thomas Burgess wrote:
do you have auto-snapshots on? i think old versions would restart on
every single new snapshot
On Sat, Jul 11, 2009 at 5
On Jul 11, 2009, at 2:24 PM, Andrew Gabriel wrote:
Galen wrote:
I have a situation where my zpool (with two radiz2s) is resilvering
and reaches a certain point, then starts over.
There no read, write or checksum errors. The disks do have a fair
amount of resilvering to do, as I've had
On Jul 11, 2009, at 6:10 PM, Miles Nordin wrote:
g == Galen gal...@zinkconsulting.com writes:
g I'm running OpenSolaris 2009.06, and while those are
g interesting to read, none of them really explain or solve my
g issues.
read this again:
In particular 6333409 in snv_102
far, and I have to
resilver at least once more. Each resilvering takes a day or two, and
I cant see why... it's not CPU, it's not sustained read throughput,
it's not IOPS, so what is it??
Galen
___
zfs-discuss mailing list
zfs-discuss
I am NOT on a notebook and I am having this problem. It the hang/pause is less
intense when I don't use compression with ZFS. This issue happens on my large
zpool as well as my boot zfs volume (single disk)
Here's my scanpci output:
pci bus 0x cardnum 0x00 function 0x00: vendor 0x10de
15 matches
Mail list logo