Actions
Bug #7144
closed
lofi mapping in non-GZ is not working with default match rules
Start date:
2016-06-27
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
External Bug:
Description
used to work fine back at smartos 20160218, but upgrading to 20160622 doesn't allow loading of /dev/lofi/2 from a non-GZ.
the problem is that lofi real device name changed from /devices/pseudo/lofi@0:1 to /devices/pseudo/lofi@1:disk and whatever is responsible of creating device node in local zone, does not recognize it.
suggested workaround:
<device match="lofi/2" /> <device match="rlofi/2" /> in zone config in /etc/zones/uuid.xml file
the issue here is you can not use * instead of number, as you dont want to include 1, but you can have [2345] like expression
Updated by Toomas Soome almost 7 years ago
- Category changed from filesystems (not ZFS) to driver - device drivers
- Status changed from New to In Progress
- % Done changed from 0 to 90
Updated by Toomas Soome almost 7 years ago
- Subject changed from lofiadm mounting in non-GZ under smartos 20160622 to lofi mapping in non-GZ is not working with default match rules
Updated by Electric Monk almost 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
git commit 450b24a3e08dd5d6007467b18ef9cea400f7385a
commit 450b24a3e08dd5d6007467b18ef9cea400f7385a
Author: Toomas Soome <tsoome@me.com>
Date: 2016-06-29T15:29:51.000Z
7144 lofi mapping in non-GZ is not working with default match rules
Reviewed by: Dan McDonald <danmcd@omniti.com>
Reviewed by: Igor Kozhukhov <ikozhukhov@gmail.com>
Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
Approved by: Robert Mustacchi <rm@joyent.com>
Actions