On 01/28/2014 02:43 PM, Chris Murphy wrote:
> It can repair corrupt metadata however, since there are two copies.
> Same for Btrfs raid0, which by default uses data profile raid0 and
> metadata profile raid1.
Nice to know. Thanks!
--
Jorge
--
users mailing list
users@lists.fedoraproject.org
T
On Jan 28, 2014, at 3:42 AM, Jorge Fábregas wrote:
>
> I didn't know about read-only scrubs. I guess I'll use that because, at
> the moment, I'm just using one single disk and therefore btrfs can't fix
> any corrupt block.
It can repair corrupt metadata however, since there are two copies. Sam
ctions to disk, the volume needs to be mounted rw,
> and then:
>
> btrfs scrub start /mnt
>
> For read only scrubs you need -r flag to get useful information
> of what fixes would be done if they were enabled. This works
> whether the device is mounted ro or rw.
>
> btrfs
UP profile so
two copies.
For scrubs that write corrections to disk, the volume needs to be mounted rw,
and then:
btrfs scrub start /mnt
For read only scrubs you need -r flag to get useful information of what fixes
would be done if they were enabled. This works whether the device is mounted
On 01/27/2014 10:35 AM, Jorge Fábregas wrote:
> #btrfs scrub status /btrfs
>
> scrub status for 543c5220-30ec-472b-a8ec-8c4c49f1fd32
> scrub started at Mon Jan 27 10:26:50 2014 and was aborted after 0
> seconds
> total bytes scrubbed: 0.00 with 0 errors
Arrgh.
Hi all,
I'm experimenting for the first time with btrfs on a scratch partition
and I wanted to test the scrub feature with:
#btrfs scrub start /btrfs
..but this is what I get when I check the status:
#btrfs scrub status /btrfs
scrub status for 543c5220-30ec-472b-a8ec-8c4c49f
