On , ein wrote:
> On 10/23/2017 10:39 AM, Wolf wrote:
> > [...]
> >
> > Is this and issue somewhere inside btrfs or is disk HW related problem?
>
> Highly unlikely hardware related. According to SMART and dmsg, there's
> no indication which would suggest disk failure.
That's my thinking too (and
On , Qu Wenruo wrote:
> [27240.680874] perf: interrupt took too long (3952 > 3942), lowering
> kernel.perf_event_max_sample_rate to 50400
> > [30658.875802] BTRFS warning (device dm-12): checksum error at logical
> > 37889245122560 on dev /dev/mapper/data7, sector 2743145096, root 23674,
> > ino
On 10/23/2017 10:39 AM, Wolf wrote:
> [...]
>
> Is this and issue somewhere inside btrfs or is disk HW related problem?
Highly unlikely hardware related. According to SMART and dmsg, there's
no indication which would suggest disk failure.
--
To unsubscribe from this list: send the line "unsubscrib
On 2017年10月23日 17:17, Qu Wenruo wrote:
>
>
> On 2017年10月23日 16:39, Wolf wrote:
>> Hi,
>> I'm having problem with corruption in one file on my disk array. This is
>> third time it happened (probably). First time I didn't checked the
>> offending file so I'm not sure but it's likely. Btrfs scrub
On 2017年10月23日 16:39, Wolf wrote:
> Hi,
> I'm having problem with corruption in one file on my disk array. This is
> third time it happened (probably). First time I didn't checked the
> offending file so I'm not sure but it's likely. Btrfs scrub finds the
> corruption, according to both dmesg and
Hi,
I'm having problem with corruption in one file on my disk array. This is
third time it happened (probably). First time I didn't checked the
offending file so I'm not sure but it's likely. Btrfs scrub finds the
corruption, according to both dmesg and it's output it fixes it.
However, next run fi
