Problems with LVM and kernel
Problems with LVM and kernel
Device uses an OrangePi Zero running the newest Armbian build with their custom kernel. I opted for LVM instead of compiling from source to avoid setup hassles. Two USB3.0 HDDs were connected via internal USB2.0 headers, functioning well when mounted separately but needed consolidation into a logical volume for better file management. I successfully set up LVM and all drives are working, though large torrent downloads cause unexpected behavior—volume becomes unresponsive, showing a "ghost" load without any user or system activity. The issue persists even after changing USB ports, checking discs, and running diagnostics. No clear size threshold is identified, but files larger than 3-4GB seem problematic. Physical access is limited due to the device's location. I’m unsure if this points to a kernel bug; commands targeting LVM cause the device to stall, and it takes over 40 minutes to boot after shutdown, only reaching full readiness in about 3-4 minutes. Any suggestions on how to investigate further?
It raises the question about a potential 32-bit addressing problem in the system.
Only when the transmission daemon writes to the LVM volume does it work. The 40G file copied via Samba is fine. This device uses Uboot; any suggestions on using Uboot for this task? It seems cache-related, as the issue occurs at longer intervals when the transmission daemon runs in turtle mode.