Hey again, I'm back with some news from my situation.
I tried taking out the faulty disk 5 and replacing it with a new disk, but
the pool showed up as FAULTED. So I plugged the faulting disk back keeping
the new disk in the machine, then ran a zpool replace.
After the new disk resilvered complete
On Apr 24, 2012, at 8:35 AM, Jim Klimov wrote:
> On 2012-04-24 19:14, Tim Cook wrote:
>> Personally unless the dataset is huge and you're using z3, I'd be
>> scrubbing once a week. Even if it's z3, just do a window on Sunday's or
>> something so that you at least make it through the whole dataset
On 2012-04-24 19:14, Tim Cook wrote:
Personally unless the dataset is huge and you're using z3, I'd be
scrubbing once a week. Even if it's z3, just do a window on Sunday's or
something so that you at least make it through the whole dataset at
least once a month.
+1 I guess
Among other consider
On Tue, Apr 24, 2012 at 12:16 AM, Matt Breitbach
wrote:
> So this is a point of debate that probably deserves being brought to the
> floor (probably for the umpteenth time, but indulge me). I've heard from
> several people that I'd consider "experts" that once per year scrubbing is
> sufficient,
So this is a point of debate that probably deserves being brought to the
floor (probably for the umpteenth time, but indulge me). I've heard from
several people that I'd consider "experts" that once per year scrubbing is
sufficient, once per quarter is _possibly_ excessive, and once a week is
down
2012-04-23 9:35, Daniel Carosone wrote:
I'll try to leave all 6 original disks in the machine while replacing,
maybe zfs will be smart enough to use the 6 drives to build the replacement
disk ?
I don't think it will.. others who know the code, feel free to comment
otherwise.
Well, I've heard
On Mon, Apr 23, 2012 at 05:48:16AM +0200, Manuel Ryan wrote:
> After a reboot of the machine, I have no more write errors on disk 2 (only
> 4 checksum, not growing), I was able to access data which I previously
> couldn't and now only the checksum errors on disk 5 are growing.
Well, that's good, b
Thank you for this very detailed answer !
After a reboot of the machine, I have no more write errors on disk 2 (only
4 checksum, not growing), I was able to access data which I previously
couldn't and now only the checksum errors on disk 5 are growing.
Fortunately, I was able to recover all impor
On Mon, Apr 23, 2012 at 02:16:40PM +1200, Ian Collins wrote:
> If it were my data, I'd set the pool read only, backup, rebuild and
> restore. You do risk further data loss (maybe even pool loss) while the
> new drive is resilvering.
You're definitely in a pickle. The first priority is to try
On 04/23/12 01:47 PM, Manuel Ryan wrote:
Hello, I have looked around this mailing list and other virtual spaces
and I wasn't able to find a similar situation than this weird one.
I have a 6 disks raidz zfs15 pool. After a scrub, the status of the
pool and all disks still show up as "ONLINE" bu
On Mon, 23 Apr 2012, Manuel Ryan wrote:
Do you guys also think I should change disk 5 first or am I missing something ?
From your description, this sounds like the best course of action, but
you should look at your system log files to see what sort of issues
are being logged. Also consult t
11 matches
Mail list logo