Re: Scrub on btrfs single device only to detect errors, not correct them?

Jon Panozzo posted on Mon, 07 Dec 2015 08:43:14 -0600 as excerpted: [On single-device dup data] > Thanks for the additional feedback. Two follow-up questions to this is: > > Can the --mixed option only be applied when first creating the fs, or > can you simply add this to the balance command

Re: Scrub on btrfs single device only to detect errors, not correct them?

Austin S Hemmelgarn posted on Mon, 07 Dec 2015 10:39:05 -0500 as excerpted: > On 2015-12-07 10:12, Jon Panozzo wrote: >> This is what I was thinking as well. In my particular use-case, parity >> is only really used today to reconstruct an entire device due to a >> device failure. I think if

Re: Scrub on btrfs single device only to detect errors, not correct them?

And I'll throw this question out to everyone: Let's say I have a means of providing parity for a btrfs device, but in a way that's external to btrfs (imagine a btrfs single device as part of a hardware or software RAID). If BTRFS detected an error during a scrub, and parity wasn't updated as a

Re: Scrub on btrfs single device only to detect errors, not correct them?

On 2015-12-07 09:47, Jon Panozzo wrote: And I'll throw this question out to everyone: Let's say I have a means of providing parity for a btrfs device, but in a way that's external to btrfs (imagine a btrfs single device as part of a hardware or software RAID). If BTRFS detected an error during

Re: Scrub on btrfs single device only to detect errors, not correct them?

This is what I was thinking as well. In my particular use-case, parity is only really used today to reconstruct an entire device due to a device failure. I think if btrfs scrub detected errors on a single device, I could do a "reverse reconstruct" where instead of syncing TO the parity disk, I

Re: Scrub on btrfs single device only to detect errors, not correct them?

Duncan, Thanks for the additional feedback. Two follow-up questions to this is: Can the --mixed option only be applied when first creating the fs, or can you simply add this to the balance command to take an existing filesystem and add this to it? So it sounds like there are really three ways

Re: Scrub on btrfs single device only to detect errors, not correct them?

On 2015-12-07 10:12, Jon Panozzo wrote: This is what I was thinking as well. In my particular use-case, parity is only really used today to reconstruct an entire device due to a device failure. I think if btrfs scrub detected errors on a single device, I could do a "reverse reconstruct" where

Re: Scrub on btrfs single device only to detect errors, not correct them?

Chris Murphy posted on Sun, 06 Dec 2015 13:42:57 -0700 as excerpted: > On Sun, Dec 6, 2015 at 12:15 PM, Jon Panozzo > wrote: >> Just to confirm, is the sole purpose of supporting scrub on single >> btrfs devices to detect errors, but not to correct them? > > If that

Scrub on btrfs single device only to detect errors, not correct them?

Just to confirm, is the sole purpose of supporting scrub on single btrfs devices to detect errors, but not to correct them? Best Regards, Jonathan Panozzo Lime Technology, Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to

Re: Scrub on btrfs single device only to detect errors, not correct them?

On Sun, Dec 6, 2015 at 12:15 PM, Jon Panozzo wrote: > Just to confirm, is the sole purpose of supporting scrub on single btrfs > devices to detect errors, but not to correct them? If that single device metadata profile is DUP, then it will correct those. If there is