OpenWrt/LEDE Project

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity Medium
  • Priority Very Low
  • Reported Version Trunk
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Joel Johnson - 21.10.2020

FS#3396 - fstools block insufficient target length

In testing a new setup using a current trunk build on a ClearFog Base device with two SSD drives, I ran into the issue where the LVM path name for my preferred volume naming was too long for the fstools handling.

In at least mount_action() and mount_device() a local char[32] is used which in my case ended up being insufficient when attempting to use paths such as “/dev/mapper/vgA_samplehostname-volnamesomething”. For the time being I happen to be able to use the shorter version of “/dev/vgA_samplehostname/volnamesomething”, but it should be considered to expand the full device name buffer to a larger size.

Joel Johnson commented on 21.10.2020 06:49

Of course my sample names don't line up (the "shorter version" as provided is still too long). In reality, I happen to be using something that is too long with the "mapper" path segment, but just short enough when not using it, something more like:

  /dev/mapper/vgA_hostname/volnameXYZ
  /dev/vgA_hostname/volnameXYZ

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing