Hello all,
While waiting for that resilver to complete last week,
I caught myself wondering how the resilvers (are supposed
to) work in ZFS?
Based on what I see in practice and read in this list
and some blogs, I've built a picture and would be grateful
if some experts actually familiar with
On Fri, May 18, 2012 at 03:05:09AM +0400, Jim Klimov wrote:
> While waiting for that resilver to complete last week,
> I caught myself wondering how the resilvers (are supposed
> to) work in ZFS?
The devil finds work for idle hands... :-)
> Based on what I see in practice and read in this lis
On Fri, May 18, 2012 at 04:18:12PM +1000, Daniel Carosone wrote:
>
> When doing a scrub, you start at the root bp and walk the tree, doing
> reads for everything, verifying checksums, and letting repair happen
> for any errors. That traversal is either a breadth-first or
> depth-first traversal of
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Jim Klimov
I'm reading the ZFS on-disk spec, and I get the idea that there's an uberblock
pointing to a self-balancing tree (some say b-tree, some say avl-tree, some say
nv-tree), where data
First of all, thank you Daniel for taking the time to post a
lengthy reply! I do not get that kind of high-quality feedback
very often :)
I hope the community and googlers would benefit from that
conversation sometime. I did straighten out some thoughts
and (mis-)understandings, at least, more on
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Jim Klimov
I'm reading the ZFS on-disk spec, and I get the idea that there's an
uberblock pointing to a self-balancing tree (some say b-tree, some say
avl-tree, some say nv-tree), where data is
2012-05-18 19:08, Edward Ned Harvey wrote:
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Jim Klimov
I'm reading the ZFS on-disk spec, and I get the idea that there's an
uberblock pointing to a self-balancing tree (some say b-tree, some say
I hope there is some good outcome of this thread after all, below...
I wonder if anyone else thinks the following proposal is reasonable? ;)
2012-05-18 10:18, Daniel Carosone wrote:
Let's go over those, and clarify terminology, before going through the
rest of your post:
...* Replace: A device h
On Mon, 21 May 2012, Jim Klimov wrote:
This is so far a relatively raw idea and I've probably missed
something. Do you think it is worth pursuing and asking some
zfs developers to make a POC? ;)
I did read all of your text. :-)
This is an interesting idea and could be of some use but it would
On Mon, May 21, 2012 at 09:18:03PM -0500, Bob Friesenhahn wrote:
> On Mon, 21 May 2012, Jim Klimov wrote:
>> This is so far a relatively raw idea and I've probably missed
>> something. Do you think it is worth pursuing and asking some
>> zfs developers to make a POC? ;)
>
> I did read all of your t
Thank you for reading and replying :-)
2012-05-22 6:18, Bob Friesenhahn wrote:
On Mon, 21 May 2012, Jim Klimov wrote:
This is so far a relatively raw idea and I've probably missed
something. Do you think it is worth pursuing and asking some
zfs developers to make a POC? ;)
I did read all of y
2012-05-22 7:30, Daniel Carosone wrote:
On Mon, May 21, 2012 at 09:18:03PM -0500, Bob Friesenhahn wrote:
On Mon, 21 May 2012, Jim Klimov wrote:
This is so far a relatively raw idea and I've probably missed
something. Do you think it is worth pursuing and asking some
zfs developers to make a POC
On Tue, May 22, 2012 at 12:42:02PM +0400, Jim Klimov wrote:
> 2012-05-22 7:30, Daniel Carosone wrote:
>> I've done basically this kind of thing before: dd a disk and then
>> scrub rather than replace, treating errors as expected.
>
> I got into similar situation last night on that Thumper -
> it is
comments far below...
On May 22, 2012, at 1:42 AM, Jim Klimov wrote:
> 2012-05-22 7:30, Daniel Carosone wrote:
>> On Mon, May 21, 2012 at 09:18:03PM -0500, Bob Friesenhahn wrote:
>>> On Mon, 21 May 2012, Jim Klimov wrote:
This is so far a relatively raw idea and I've probably missed
som
2012-05-23 20:54, Richard Elling wrote:
comments far below...
Thank you Richard for taking notice of this thread and the
definitive answers I needed not quote below, for further
questions ;)
2) How did you "treat errors as expected" during scrub?
As I've discovered, there were hoops to jump t
On May 23, 2012, at 1:32 PM, Jim Klimov wrote:
> 2012-05-23 20:54, Richard Elling wrote:
>> comments far below...
>
> Thank you Richard for taking notice of this thread and the
> definitive answers I needed not quote below, for further
> questions ;)
>
>>> 2) How did you "treat errors as expecte
Thanks again,
2012-05-24 1:01, Richard Elling wrote:
At least the textual error message infers that if a hotspare
were available for the pool, it would kick in and invalidate
the device I am scrubbing to update into the pool after the
DD-phase (well, it was not DD but a hung-up resilver in this
On May 23, 2012, at 2:56 PM, Jim Klimov wrote:
> Thanks again,
>
> 2012-05-24 1:01, Richard Elling wrote:
>>> At least the textual error message infers that if a hotspare
>>> were available for the pool, it would kick in and invalidate
>>> the device I am scrubbing to update into the pool after
Let me try to formulate my idea again... You called a similar
process "pushing the rope" some time ago, I think.
I feel like I'm passing some exam and am trying to pick answers
for a discipline like philosophy and I have no idea about the
examinator's preferences - is he an ex-Communism teacher o
big assumption below...
On May 24, 2012, at 6:06 AM, Jim Klimov wrote:
> Let me try to formulate my idea again... You called a similar
> process "pushing the rope" some time ago, I think.
>
> I feel like I'm passing some exam and am trying to pick answers
> for a discipline like philosophy and I
2012-05-24 18:55, Richard Elling wrote:
This is a big assumption -- that the disk will operate normally, even
for data it cannot read. In my experience, this assumption is not valid
for the majority of HDD failure modes. Also, in the case of consumer-grade
disks, a single sector media error could
On 5/23/12 11:28 PM, Richard Elling wrote:
The man page is clear on this topic, IMHO
Indeed, even in snv_117 the zpool man page says that. But the
console/dmesg message was also quite clear, so go figure whom
to trust (or fear) more ;)
The FMA message is consistent with the man page.
The ma
On May 25, 2012, at 1:53 PM, zfs user wrote:
> On 5/23/12 11:28 PM, Richard Elling wrote:
The man page is clear on this topic, IMHO
>>>
>>> Indeed, even in snv_117 the zpool man page says that. But the
>>> console/dmesg message was also quite clear, so go figure whom
>>> to trust (or fear) m
2012-05-26 1:07, Richard Elling wrote:
On May 25, 2012, at 1:53 PM, zfs user wrote:
The man page seems to not mention the critical part of the FMA msg
that OP is worried about.
OP said that his motivation for clearing the errors and fearing the
degraded state was because he feared this:
>> AUTO
24 matches
Mail list logo