hfs+ filesystems fail reading / writing large files

Bug #1891768 reported by Richard J Uschold
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I noticed a problem reading hfs+ partitions on a USB flash drive after I installed Ubuntu 20.04 on two laptop machines. I have a Mini Mac that I share files via an USB flash drive formatted with hfs+ from the laptops with Ubuntu installed. I had no issues with Ubuntu Mate 18.10.

I noticed that very large files, typicality larger than 100 MB, would have read errors or sometimes have a zero file size. One particular file about 500MB fails nearly every time. Other files, down to about 100MB fail sometimes.

I bought a new USB flash drive, but have the same failures on that.
I have an identical flash drive formatted with ext4 which has no issues. I'm currently booting to Ubuntu Mate 18.10 to write the hfs+ USB flash drive.

1007 ceres ~ cat /proc/version_signature
Ubuntu 5.4.0-42.46-generic 5.4.44

1000 ceres ~ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04

1005 admin@ceres ~ sudo lspci -vnvn > lspci-vnvn.log
pcilib: sysfs_read_vpd: read failed: Input/output error
pcilib: sysfs_read_vpd: read failed: Input/output error
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: uschcld 1581 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-05-17 (91 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. HD WebCam
 Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp.
 Bus 001 Device 002: ID 046d:c06c Logitech, Inc. Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-576
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=75021464-0e3f-4ad2-a466-cf655a6c4dd7 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic N/A
 linux-firmware 1.187.2
Tags: focal
Uname: Linux 5.4.0-42-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip fax floppy plugdev tape video www-data
_MarkForUpload: True
dmi.bios.date: 09/06/2018
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.47
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: KBL
dmi.board.version: V1.47
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:svnAcer:pnAspireE5-576:pvrV1.47:rvnKBL:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Aspire E 15
dmi.product.name: Aspire E5-576
dmi.product.sku: 0000000000000000
dmi.product.version: V1.47
dmi.sys.vendor: Acer

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1891768/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Richard J Uschold (gilliganu1) wrote : Re: [Bug 1891768] Re: hfs+ filesystems fail reading / writing large files

I understand that robots don't understand English well, so, I hope a
person reads this.

I don't know what package handles hfs+ file system read/writes. I don't
understand the innards of Linux well enough to figure that out. All I
know, is that is is deep in the guts of Linux.

Richard

On 8/15/20 16:25, Ubuntu Foundations Team Bug Bot wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It seems that your bug report is not filed about a
> specific source package though, rather it is just filed against Ubuntu
> in general. It is important that bug reports be filed about source
> packages so that people interested in the package can find the bugs
> about it. You can find some hints about determining what package your
> bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
> You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
>
> To change the source package that this bug is filed about visit
> https://bugs.launchpad.net/ubuntu/+bug/1891768/+editstatus and add the
> package name in the text box next to the word Package.
>
> [This is an automated message. I apologize if it reached you
> inappropriately; please just reply to this message indicating so.]
>
> ** Tags added: bot-comment
>

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1891768

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: focal
Revision history for this message
Richard J Uschold (gilliganu1) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Richard J Uschold (gilliganu1) wrote : CRDA.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : IwConfig.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : Lspci.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : Lspci-vt.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : Lsusb-t.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : Lsusb-v.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : ProcEnviron.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : ProcModules.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : PulseList.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : RfKill.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : UdevDb.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote : WifiSyslog.txt

apport information

Revision history for this message
Richard J Uschold (gilliganu1) wrote :

I ran the apport-collect 1891768
Results are above.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Richard J Uschold (gilliganu1) wrote :

I set status to Confirmed, as requested.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Not seeing any relevant log in dmesg.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Richard J Uschold (gilliganu1) wrote :

I have no idea how to generate the log you are looking for.
Please be specific.

Revision history for this message
Richard J Uschold (gilliganu1) wrote :

Can someone please estimate when someone may work on this?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Richard J Uschold (gilliganu1) wrote :

A recent update to Ubuntu 20.04.1 installed kernel 5.8.0-44-generic. This bug is FIXED in this kernel!

Revision history for this message
Richard J Uschold (gilliganu1) wrote :

I'm not sure which bug officially fixed this. I searched and didn't find any related bugs.
I marked it "Fixed Released"

Changed in linux (Ubuntu):
status: Expired → Fix Released
Revision history for this message
Richard J Uschold (gilliganu1) wrote :

OOPS! I discovered that this is NOT REALLY FIXED!
I changed it from "Fixed Released" to "New" I'm sure this is not appropriate, but no other available options made any sense whatsoever.

I will resubmit this in a few days. I have more information to supply.

Changed in linux (Ubuntu):
status: Fix Released → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Richard - you could try installing linux-oem-5.10. There are a few bug fixes between v5.4 and v5.10 releases.

sudo apt-get install linux-oem-5.10

Revision history for this message
Richard J Uschold (gilliganu1) wrote :

Since I wrote this, I have tested a number of other kernels.

These fail:
vmlinuz-4.19.0-14-amd64 - MX Linux 19.3
vmlinuz-4.19.0-16-amd64 - MX Linux 19.3
vmlinuz-5.4.0-65-generic - Linux Mint 20.1
vmlinuz-5.4.0-66-generic - Linux Mint 20.1
vmlinuz-5.4.0-67-generic - Linux Mint 20.1
vmlinuz-5.4.0-47-generic - Ubuntu 20.04
vmlinuz-5.8.0-41-generic - Ubuntu 20.04
vmlinuz-5.11.0-051100-generic - Linux Mint 20.1
vmlinuz-5.11.7-051107-generic - Linux Mint 20.1

These WORK:
vmlinuz-4.9.240-antix.1-amd64-smp - MX Linux 19.3
vmlinuz-4.18.0-25-generic - Ubuntu Mate 18.10

These started working in late March, 2021:
vmlinuz-5.8.0-44-generic Ubuntu 20.04.1
vmlinuz-5.8.0-48-generic Ubuntu 20.04.1
vmlinuz-5.11.8-051108-generic - Ubuntu 20.04.1

I checked the change log for 5.11 at https://kernelnewbies.org/Linux_5.11
The string "hfs" does NOT appear anywhere in the change log!

Obviously, what ever bug was fixed affected something else, in addition to hfs. Is there any way to find out what this bug was?

More importantly, is there any way to estimate when this bug fix will propagate to other supported kernels (such as 4.19.0-16-amd64 used by MX Linux 19.3 and me)?

Thanks

Revision history for this message
Juerg Haefliger (juergh) wrote :

Sorry but MX Linux (whatever that is) is not something we support with an Ubuntu kernel. If you find a kernel problem in a supported Ubuntu release we'll do our best to fix that.

Revision history for this message
Richard J Uschold (gilliganu1) wrote :

FYI: MX Linux currently is the most downloaded distro on distro watch.

I erroneously assumed that there was only ONE Linux kernel bug fix team. My mistake.

So, what is the process where kernel bugs fixed by Ubuntu migrate to the other distro kernels and vice versa?

How do I figure out what official bug number fixed my hfs+ bug, as there is no reference to hfs in 5.11 change log?

Thanks

Revision history for this message
Juerg Haefliger (juergh) wrote :

If we find a problem in Ubuntu that has not already been fixed in the latest upstream kernel then we'll try to fix it ourselves and send the patch upstream. But most of the time we backport already existing upstream fixes to affected Ubuntu kernels.

The process of finding the fix for a specific problem is:
1) Find the first kernel version that works (good kernel).
2) Look at the changes between the previous (bad) and the good kernel.
3) If nothing jumps out that might indicate which commit fixed the problem: git bisect to narrow it further down.

But typically, if a user reports that a specific problem has been fixed with a kernel update then that's good enough for us even without knowing exactly which specific commit fixed it. Sometimes there are a lot of upstream changes that we pull into an update.

It's the distros responsibilities to keep their kernels up-to-date and every distro does it differently. Ubuntu updates kernels every 3 weeks (roughly): https://wiki.ubuntu.com/StableReleaseUpdates

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.