与udev斗争
与udev斗争
提问于 2019-11-13 10:08:29
我想在Ubuntu上automount我的SD卡。我使用udevadm (或/lib/systemd/systemd-udevd)尝试了以下规则。
KERNEL!="sd[a-z][0-9]", GOTO="media_by_label_auto_mount_end"
# Import FS infos
IMPORT{program}="/sbin/blkid -o udev -p %N"
# Get a label if present, otherwise specify one
ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
# Global mount options
ACTION=="add|change", ENV{mount_options}="relatime"
# Filesystem-specific mount options
ACTION=="add|change", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},utf8,gid=100,umask=002"
# Mount the device
ACTION=="add|change", RUN+="/bin/mkdir -p /media/%E{dir_name}", RUN+="/bin/mount -o $env{mount_options} /dev/%k /media/%E{dir_name}", RUN+=" echo /bin/mount -o $env{mount_options} /dev/%k /media/%E{dir_name\
} > /tmp/debug_out.txt"
#ACTION=="add|change"
# Clean up after removal
ACTION=="remove", ENV{dir_name}!="", RUN+="/bin/umount -l /media/%E{dir_name}", RUN+="/bin/rmdir /media/%E{dir_name}"
# Exit
LABEL="media_by_label_auto_mount_end"网络密码。
`udevadm monitor` indicates that the card is detected
KERNEL[1778159.935932] change /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host11/target11:0:0/11:0:0:0/block/sdc (block)
KERNEL[1778159.939553] remove /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host11/target11:0:0/11:0:0:0/block/sdc/sdc1 (block)
KERNEL[1778159.942501] change /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host11/target11:0:0/11:0:0:0/block/sdc (block)
KERNEL[1778159.942615] add /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host11/target11:0:0/11:0:0:0/block/sdc/sdc1 (block)
UDEV [1778160.026230] change /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host11/target11:0:0/11:0:0:0/block/sdc (block)
UDEV [1778160.101285] remove /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host11/target11:0:0/11:0:0:0/block/sdc/sdc1 (block)
UDEV [1778160.184648] change /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host11/target11:0:0/11:0:0:0/block/sdc (block)
KERNEL[1778160.320013] add /kernel/slab/ext4_inode_cache/cgroup/ext4_inode_cache(14341:systemd-udevd.service) (cgroup)
UDEV [1778160.322555] add /kernel/slab/ext4_inode_cache/cgroup/ext4_inode_cache(14341:systemd-udevd.service) (cgroup)
KERNEL[1778160.387280] add /kernel/slab/fat_inode_cache/cgroup/fat_inode_cache(14341:systemd-udevd.service) (cgroup)
UDEV [1778160.388849] add /kernel/slab/fat_inode_cache/cgroup/fat_inode_cache(14341:systemd-udevd.service) (cgroup)
UDEV [1778160.418509] add /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host11/target11:0:0/11:0:0:0/block/sdc/sdc1 (block)而且udevadm test /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host11/target11:0:0/11:0:0:0/block/sdc/sdc1的输出看起来也很好
[...]
run: '/bin/mkdir -p /media/usbhd-sdc1'
run: '/bin/mount -o relatime /dev/sdc1 /media/usbhd-sdc1'
run: '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdc1'
[...]但是，规则只创建目录，但它不挂载卡片。使用sudo权限手动执行上述规则将按预期工作(创建目录将无法与sudo一起工作，因此这不是问题所在)
(小的跟进问题:我想复制卡片上的文件，触发一个作业，然后unmount卡。)我也是从unmount这样做，还是使用另一种机制)
========================
如下所述，更改了所有内容：
Udev/rules.d
KERNEL!="sd[a-z][0-9]", GOTO="media_by_label_auto_mount_end"
ACTION=="add", SUBSYSTEM=="block",TAG+="systemd", ENV{SYSTEMD_WANTS}=sd-automounter@%k.service
ACTION=="change", SUBSYSTEM=="block",TAG+="systemd", RUN+="systemctl start sd-automounter@%k"
# Clean up after removal
ACTION=="remove", ENV{dir_name}!="", RUN+="/bin/umount -l /media/%E{dir_name}", RUN+="/bin/rmdir /media/%E{dir_name}"
# Exit 服务描述
# /etc/systemd/system/sd-automounter@.service
[Service]
Type=oneshot
ExecStart=/usr/local/libexec/sd-automounter %I(base)和服务
#!/bin/sh
# /usr/local/libexec/sd-automounter
echo "" > /tmp/debug.out
DEVICE_NAME=/dev/"$1"
echo $DEVICE_NAME >>/tmp/debug.out
udevadm info --query=property --export $DEVICE_NAME >> /tmp/debug.out
echo "" >> /tmp/debug.out
CARD_NAME=$(udevadm info --query=property --export $DEVICE_NAME | grep ID_FS_LABEL= | awk -F\' '{print $2}')
echo $CARD_NAME >> /tmp/debug.out
#CARD_NAME=$(/sbin/blkid | grep "$DEVICE_NAME" | awk -F\" '{print $2}' |sed 's/ /_/g')
udevadm info --query=property --export /dev/sdc1
echo $CARD_NAME
mkdir -p /media/$CARD_NAME
mount -t vfat $DEVICE_NAME /media/$CARD_NAME
thanks for all help in advance手动执行它，systemctl start sd-automounter@sdd1就像一种魅力。
但是在udevadm monitor显示时，删除和插入什么都不会发生
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[1977111.519970] change /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host12/target12:0:0/12:0:0:0/block/sdd (block)
KERNEL[1977111.523252] remove /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host12/target12:0:0/12:0:0:0/block/sdd/sdd1 (block)
KERNEL[1977111.526457] change /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host12/target12:0:0/12:0:0:0/block/sdd (block)
KERNEL[1977111.526572] add /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host12/target12:0:0/12:0:0:0/block/sdd/sdd1 (block)
UDEV [1977111.612257] change /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host12/target12:0:0/12:0:0:0/block/sdd (block)
UDEV [1977111.614914] remove /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host12/target12:0:0/12:0:0:0/block/sdd/sdd1 (block)
UDEV [1977111.697870] change /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host12/target12:0:0/12:0:0:0/block/sdd (block)
UDEV [1977111.791344] add /devices/pci0000:00/0000:00:14.0/usb4/4-3/4-3:1.0/host12/target12:0:0/12:0:0:0/block/sdd/sdd1 (block)回答 2
Unix & Linux用户
回答已采纳
发布于 2019-11-23 06:26:02
第二个选项的问题是我必须使用完整的路径。
ACTION=="add", SUBSYSTEM=="block",TAG+="systemd", RUN+="/bin/systemctl start sd-automounter@%k"
ACTION=="change", SUBSYSTEM=="block",TAG+="systemd", RUN+="/bin/systemctl start sd-automounter@%k"并使用run选项添加
Unix & Linux用户
发布于 2019-11-13 13:35:16
systemd-udev真的不希望您再直接从规则中挂载文件系统了。你可以在这个网站上找到很多关于它的问题:-)。
在systemd的最新版本中，udev服务文件具有SystemCallFilter=@system-service @module @raw-io。这不允许挂载文件系统所需的系统调用。
(而且，我认为如果您曾经直接将mount用于FUSE文件系统，例如ntfs-3g，则会与systemd发生冲突。如果启动FUSE服务器进程，最好是在专用系统单元(如.mount单元)中。如果让FUSE进程停留在当前单元中，则FUSE流程的生存期将与正在运行的单元的生存期相耦合)。
为了避免RUN+=中的命令将来(或当前)出现问题，您的规则可以使用ENV{SYSTEMD_WANTS}=my-automounter@%k.service，然后
# /etc/systemd/system/my-automounter@.service
[Service]
Type=oneshot
ExecStart=/usr/local/libexec/my-automounter %I#!/bin/sh
# /usr/local/libexec/my-automounter
DEV=/dev/"$1"
# You can make this script as complicated as you want.
# You can read udev properties if you want, using
# eval "$(udevadm info --query=property --export "$DEV")"
...如果要手动测试调用单元，可以使用systemctl start my-automounter@sdc1。
如果在systemd运行脚本时发生错误，则可以使用systemctl status my-automounter@*或journalctl -b -u my-automounter@*查看错误消息。
这也避免了您必须处理udev-specific错误报告。我认为sh和systemd都有有用的错误报告，以防程序突然死亡。例如，他们应该报告某个程序是否被信号SIGSYS杀死，因为它试图调用使用SystemCallFilter=：-阻止的系统调用。
页面原文内容由Unix & Linux提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://unix.stackexchange.com/questions/551912
复制相关文章
相似问题
腾讯云开发者
