Revision history [back]

I am a bit astonished that the search does not turn up any match for "btrfs scrub".

After using my device for less then 6 months with pretty modest data volumes (not a single piece of music, just some pictures and videos from the device camera) my Jolla got pretty slow compared to when it was new.

So I decided to run "btrfs balance" as mention repeatedly in this forum. That run never to completion, first it reported out of space (although several GB free). So I copied a couple of bigger videos out of the device using scp. Already scp complained that 2 of the videos could not be read because of I/O error. (I only deleted those, which could be copied successfully.) Further "btrfs balance" attempts got a bit further, but eventually I got stuck with I/O errors.

So I found the "btrfs scrub" command. It also seem to stop at the first uncorrectable I/O error. I found 2 videos, which could not be read by scp and also their inodes where reported by scrub. I found out that ffmpeg happily copies them until the first error (also the Jolla player plays that part), so I could at least salvage the first parts of the videos (actually more than 80%). After deleting those offenders, both "btrfs scrub" and "btrfs balance" completed without further complaints.

(I'm really astonished that "btrfs scrub" is so much faster than "btrfs balance".)

That was about 3 weeks ago. Yesterday again I had a corrupted file [1]. Not sure whether the corruption happened on the network or in the storage side. Anyway I run "btrfs scrub" again and it reported one

WARNING: errors detected during scrubbing, corrected.

I could not find an inode or any other info from dmesg this time.

So long story, shorter questions:

Has anybody else seen file corruption? Any opinions whether these are HW problems (flash memory) or software problems (btrfs in Jollas somewhat dated kernel probably still has quite some bugs)? Of course flash has a limited life length, but 6 months with very moderate usage sounds a bit too short.

[1] currently last comment of the original post at https://together.jolla.com/question/30926/howto-install-google-play/ (I cannot find out how to created direct links to comments and the 13 hours ago is not good reference either...)

I am a bit astonished that the search does not turn up any match for "btrfs scrub".

After using my device for less then 6 months with pretty modest data volumes (not a single piece of music, just some pictures and videos from the device camera) my Jolla got pretty slow compared to when it was new.

So I decided to run "btrfs balance" as mention repeatedly in this forum. That run never to completion, first it reported out of space (although several GB free). So I copied a couple of bigger videos out of the device using scp. Already scp complained that 2 of the videos could not be read because of I/O error. (I only deleted those, which could be copied successfully.) Further "btrfs balance" attempts got a bit further, but eventually I got stuck with I/O errors.

So I found the "btrfs scrub" command. It also seem to stop at the first uncorrectable I/O error. I found 2 videos, which could not be read by scp and also their inodes where reported by scrub. I found out that ffmpeg happily copies them until the first error (also the Jolla player plays that part), so I could at least salvage the first parts of the videos (actually more than 80%). After deleting those offenders, both "btrfs scrub" and "btrfs balance" completed without further complaints.

(I'm really astonished that "btrfs scrub" is so much faster than "btrfs balance".)

That was about 3 weeks ago. Yesterday again I had a corrupted file [1]. Not sure whether the corruption happened on the network or in the storage side. Anyway I run "btrfs scrub" again and it reported one

WARNING: errors detected during scrubbing, corrected.

I could not find an inode or any other info from dmesg this time.

So long story, shorter questions:

Has anybody else seen file corruption? Any opinions whether these are HW problems (flash memory) or software problems (btrfs in Jollas somewhat dated kernel probably still has quite some bugs)? Of course flash has a limited life length, but 6 months with very moderate usage sounds a bit too short.

[1] currently last comment of the original post at https://together.jolla.com/question/30926/howto-install-google-play/ (I cannot find out how to created direct links to comments and the 13 hours ago is not good reference either...)

[45175.680384] btrfs csum failed ino 135610 off 63725568 csum 1759428533 private 68200767
[45175.682734] btrfs csum failed ino 135610 off 63725568 csum 1759428533 private 68200767
[45178.607440] btrfs csum failed ino 111540 off 241664 csum 3887731566 private 2339636708
[45178.609332] btrfs csum failed ino 111540 off 241664 csum 3887731566 private 2339636708
[45180.916428] btrfs csum failed ino 135565 off 48885760 csum 3301422542 private 2819203908
[45180.918565] btrfs csum failed ino 135565 off 48885760 csum 3301422542 private 2819203908
[45184.222120] btrfs csum failed ino 111523 off 90112 csum 253123999 private 1675119381
[45184.224501] btrfs csum failed ino 111523 off 90112 csum 253123999 private 1675119381