Is there any way to stop a resilver?
We gotta stop this thing - at minimum, completion time is 300,000 hours, and
maximum is in the millions.
Raidz2 array, so it has the redundancy, we just need to get data off.
___
zfs-discuss mailing list
Has it been running long? Initially the numbers are way off. After a while
it settles down into something reasonable.
How many disks, and what size, are in your raidz2?
-Scott
On 9/29/10 8:36 AM, LIC mesh licm...@gmail.com wrote:
Is there any way to stop a resilver?
We gotta stop this
It's always running less than an hour.
It usually starts at around 300,000h estimate(at 1m in), goes up to an
estimate in the millions(about 30mins in) and restarts.
Never gets past 0.00% completion, and K resilvered on any LUN.
64 LUNs, 32x5.44T, 32x10.88T in 8 vdevs.
On Wed, Sep 29, 2010
What version of OS?
Are snapshots running (turn them off).
So are there eight disks?
On 9/29/10 8:46 AM, LIC mesh licm...@gmail.com wrote:
It's always running less than an hour.
It usually starts at around 300,000h estimate(at 1m in), goes up to an
estimate in the millions(about 30mins
What caused the resilvering to kick off in the first place?
Lin
On Sep 29, 2010, at 8:46 AM, LIC mesh wrote:
It's always running less than an hour.
It usually starts at around 300,000h estimate(at 1m in), goes up to an
estimate in the millions(about 30mins in) and restarts.
Never gets
Most likely an iSCSI timeout, but that was before my time here.
Since then, there have been various individual drives lost along the way on
the shelves, but never a whole LUN, so, theoretically, /except/ for iSCSI
timeouts, there has been no great reason to resilver.
On Wed, Sep 29, 2010 at
Can you post the output of 'zpool status'?
Thanks,
George
LIC mesh wrote:
Most likely an iSCSI timeout, but that was before my time here.
Since then, there have been various individual drives lost along the way
on the shelves, but never a whole LUN, so, theoretically, /except/ for
iSCSI
