Hi,
The drives and the chassis are fine, what I am questioning is how can it
be resilvering more data to a device than the capacity of the device?
If data on pool has changed during resilver, resilver counter will not update
accordingly, and it will show resilvering 100% for needed time to
On 19 September, 2010 - Markus Kovero sent me these 0,5K bytes:
Hi,
The drives and the chassis are fine, what I am questioning is how can it
be resilvering more data to a device than the capacity of the device?
If data on pool has changed during resilver, resilver counter will not
On 18/09/10 15:25, George Wilson wrote:
Tom Bird wrote:
In my case, other than an hourly snapshot, the data is not
significantly changing.
It'd be nice to see a response other than you're doing it wrong,
rebuilding 5x the data on a drive relative to its capacity is clearly
erratic behaviour,
Hi all
one of our system just developed something remotely similar:
s06:~# zpool status
pool: atlashome
state: DEGRADED
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to
On 09/18/10 06:47 PM, Carsten Aulbert wrote:
Hi all
one of our system just developed something remotely similar:
s06:~# zpool status
pool: atlashome
state: DEGRADED
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a
Hi
On Saturday 18 September 2010 10:02:42 Ian Collins wrote:
I see this all the time on a troublesome Thumper. I believe this
happens because the data in the pool is continuously changing.
Ah ok, that may be, there is one particular active user on this box right now.
Interesting I've never
On 09/18/10 08:58 PM, Carsten Aulbert wrote:
Hi
On Saturday 18 September 2010 10:02:42 Ian Collins wrote:
I see this all the time on a troublesome Thumper. I believe this
happens because the data in the pool is continuously changing.
Ah ok, that may be, there is one particular
On 18/09/10 09:02, Ian Collins wrote:
On 09/18/10 06:47 PM, Carsten Aulbert wrote:
Has someone an idea how it is possible to resilver 678G of data on a 500G
drive?
I see this all the time on a troublesome Thumper. I believe this happens
because the data in the pool is continuously changing.
On Sat, Sep 18, 2010 at 7:01 PM, Tom Bird t...@marmot.org.uk wrote:
All said and done though, we will have to live with snv_134's bugs from now
on, or perhaps I could try Sol 10.
or OpenIllumos. Or Nexenta. Or FreeBSD. Or insert osol distro name.
--
O ascii ribbon campaign - stop html mail -
On 18/09/10 13:06, Edho P Arief wrote:
On Sat, Sep 18, 2010 at 7:01 PM, Tom Birdt...@marmot.org.uk wrote:
All said and done though, we will have to live with snv_134's bugs from now
on, or perhaps I could try Sol 10.
or OpenIllumos. Or Nexenta. Or FreeBSD. Orinsert osol distro name.
...
But all of which have newer code, today, than onnv-134.
On 18 September 2010 22:20, Tom Bird t...@marmot.org.uk wrote:
On 18/09/10 13:06, Edho P Arief wrote:
On Sat, Sep 18, 2010 at 7:01 PM, Tom Birdt...@marmot.org.uk wrote:
All said and done though, we will have to live with snv_134's
Tom Bird wrote:
On 18/09/10 09:02, Ian Collins wrote:
In my case, other than an hourly snapshot, the data is not significantly
changing.
It'd be nice to see a response other than you're doing it wrong,
rebuilding 5x the data on a drive relative to its capacity is clearly
erratic
On 09/19/10 12:01 AM, Tom Bird wrote:
On 18/09/10 09:02, Ian Collins wrote:
On 09/18/10 06:47 PM, Carsten Aulbert wrote:
Has someone an idea how it is possible to resilver 678G of data on a
500G
drive?
I see this all the time on a troublesome Thumper. I believe this happens
because the
Morning,
c7t5000CCA221F4EC54d0 is a 2T disk, how can it resilver 5.63T of it?
This is actually an old capture of the status output, it got to nearly
10T before deciding that there was an error and not completing, reseat
disk and it's doing it all again.
It's happened on another pool as
On Fri, 17 Sep 2010, Tom Bird wrote:
Morning,
c7t5000CCA221F4EC54d0 is a 2T disk, how can it resilver 5.63T of it?
This is actually an old capture of the status output, it got to nearly 10T
before deciding that there was an error and not completing, reseat disk and
it's doing it all again.
On 09/18/10 04:28 AM, Tom Bird wrote:
Bob Friesenhahn wrote:
On Fri, 17 Sep 2010, Tom Bird wrote:
Morning,
c7t5000CCA221F4EC54d0 is a 2T disk, how can it resilver 5.63T of it?
This is actually an old capture of the status output, it got to
nearly 10T before deciding that there was an error
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Tom Bird
We recently had a long discussion in this list, about resilver times versus
raid types. In the end, the conclusion was: resilver code is very
inefficient for raidzN. Someday it may
17 matches
Mail list logo
