Opened 5 months ago

Closed 4 months ago

#14763 closed bug (invalid)

KERN: Failed to decompress chunk data: Bad data

Reported by: rhialto Owned by: bonefish
Priority: normal Milestone: Unscheduled
Component: File Systems/packagefs Version: R1/beta1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86-64

Description

The file system seems really unstable to me. I have installed Haiku to an usb stick, and this is the second that I get seemingly serious file system corruption.

In this case, I tried to run a 'git clone' command, and a dialog popped up telling me that it had crashed. It was very repeatable.

Looking in the syslog (attached) there are several errors like

KERN: unknown [484014145:  1028] KERN: Failed to decompress chunk data: Bad data
KERN: unknown [484014260:  1028] KERN: CachedDataReader::_ReadCacheLine(): Failed to read into cache (offset: 28180480, length: 65536), trying uncached read (offset: 28212642, length: 4096)
KERN: unknown [484015169:  1028] KERN: Failed to decompress chunk data: Bad data
KERN: reading page from cache 0xffffffff96b03620 returned: Bad data!

I tried it several times so it is

I have attached a copy of the syslog, and of the debugging report.

checkfs /boot reports no problems. checkfs /boot/system doesn't want to do anything.

Is there a way to check which packages are corrupted, and replace them?

Attachments (2)

haiku-syslog (260.7 KB) - added by rhialto 5 months ago.
The syslog file
git-remote-https orig-901-debug-16-12-2018-16-49-02.report (6.9 KB) - added by rhialto 5 months ago.
The debugging report

Download all attachments as: .zip

Change History (6)

Changed 5 months ago by rhialto

Attachment: haiku-syslog added

The syslog file

Changed 5 months ago by rhialto

The debugging report

comment:1 Changed 5 months ago by waddlesplash

Please try with a nightly build; these have kernel asserts and paranoia checks turned on which sometimes catch these issues as KDLs instead of errors.

comment:2 Changed 5 months ago by rhialto

Thanks, I'll try that as soon as I can.

comment:3 Changed 4 months ago by rhialto

I think I have to write this off as a bad USB stick. I have had a lot of bad sticks from this brand (Intenso) :-(

comment:4 Changed 4 months ago by waddlesplash

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.