1 |
On 17/05/14 08:08, William Kenworthy wrote: |
2 |
> On 17/05/14 04:15, Marc Joliet wrote: |
3 |
>> So, a week has passed since my conversion to btrfs. |
4 |
>> |
5 |
>... |
6 |
>> |
7 |
>> Have a nice weekend, |
8 |
>> |
9 |
> |
10 |
> Don't forget to have a maintenance program - run a scrub regularly once |
11 |
> a week or so - I have enough btrfs drives (22 qemu files, 4 WD Greens |
12 |
> att) to see about one or two scrub fixable errors a week with no obvious |
13 |
> cause, sometimes serious (in a critical file). My experience is that if |
14 |
> you ignore these errors they seem to increase over time resulting in a |
15 |
> crash and burn. Keep an eye on your logs as btrfs will list the errors |
16 |
> there as well ("grep -i btrfs /var/log/messages"). For the ones scrub |
17 |
> cant fix, delete the file and restore from backup. Errors that require |
18 |
> off-line fixing (btrfsck) are the ones where I have lost file systems - |
19 |
> though I have not seen this in the last 6 months. |
20 |
> |
21 |
> I am quite practised in restoring from backups because of btrfs :) |
22 |
> |
23 |
> BillK |
24 |
> |
25 |
> |
26 |
> |
27 |
This is from this mornings grep of the log: |
28 |
May 15 07:00:34 myth kernel: btrfs: checksum error at logical 1775247360 |
29 |
on dev /dev/vda3, sector 5580816, root 5, inode 6423718, offset 1839104, |
30 |
length 4096, links 1 (path: |
31 |
var/log/mythtv/old/mythbackend.20140421061150.6275.log-20140515) |
32 |
May 15 07:00:34 myth kernel: btrfs: bdev /dev/vda3 errs: wr 0, rd 0, |
33 |
flush 0, corrupt 1, gen 0 |
34 |
May 15 07:00:34 myth kernel: btrfs: unable to fixup (regular) error at |
35 |
logical 1775247360 on dev /dev/vda3 |
36 |
May 15 07:41:40 myth kernel: btrfs: bdev /dev/vda3 errs: wr 0, rd 0, |
37 |
flush 0, corrupt 1, gen 0 |
38 |
|
39 |
and |
40 |
|
41 |
May 16 20:40:33 moriah kernel: btrfs: bdev /dev/mapper/vg1-backups errs: |
42 |
wr 0, rd 250, flush 0, corrupt 13, gen 0 |
43 |
|
44 |
sigh .... |
45 |
|
46 |
BillK |