RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2155314 - Allow mount and device units with very long paths
Summary: Allow mount and device units with very long paths
Keywords:
Status: CLOSED DUPLICATE of bug 1940973
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-20 19:17 UTC by Amey
Modified: 2023-01-05 14:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-05 14:01:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-142994 0 None None None 2022-12-20 19:26:09 UTC

Description Amey 2022-12-20 19:17:25 UTC 
Description of problem:

** I am cloning this BZ from BZ #1779813 which was for RHEL 7, as the customer has confirmed that the fix is NOT needed in RHEL 7 but is now needed in RHEL 8 I am creating this new BZ to track changes in RHEL 8 **

A customer has a SAS Expander that expands their devices out to a name longer than 256 characters when the path is exploded.

    # systemd-escape /devices/pci0000:00/0000:00:02.0/0000:02:00.0/host10/port-10:0/expander-10:0/port-10:0:0/expander-10:1/port-10:1:0/expander-10:2/port-10:2:0/expander-10:3/port-10:3:13/end_device-10:3:13/target10:0:89/10:0:89:0/scsi_device/10:0:89:0 | wc
	  1       1     263

This causes the systemd to fail on the device with:

    systemd: Failed to set up device unit: Invalid argument

And then the systemd job times out and the mounts fail.

This value appears to be arbitrarily increased over time.  We gave the customer a test patch that raised UNIT_NAME_MAX in shared/unit-name.h to 512 and it resolved their issue.

Requesting that this value be raised to 512.


Version-Release number of selected component (if applicable):
systemd-239-68.el8.x86_64

How reproducible:
Every time if the device name is over 256 characters.


Steps to Reproduce:
1.  Attach a device with a path over 256 characters.
2.  Boot the server
3.  Check the logs for errors.

Actual results:

systemd errors with:

    systemd: Failed to set up device unit: Invalid argument

And times out the device.

Expected results:

System boots without any issues.

Additional info:
Comment 1 David Tardon 2023-01-05 14:01:38 UTC 

*** This bug has been marked as a duplicate of bug 1940973 ***
Note You need to log in before you can comment on or make changes to this bug.