If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.

0
U

Property:mountinfo

From BoxMatrix
(Redirected from mountinfo)


BoxMatrix >> System >> mountinfo @ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl
News Selectors Models Accessories Components Environment Config Commands System Webif Software Develop Lexicon Community Project Media

Devices Filesystems Partitions Sockets Netlink Pipes Interfaces Bridges Ports Events Sources Sinks AVMIPC Processes Watchdogs Memory Slab Vmalloc ProcFS SysFS Research

Procfs-Object

Goto:   Examples  -  Dependencies   -   Model-Matrix   -   Help Supportdata2   -   SMW-Browser

Details

mountinfo provides information about mounts in the process's mount namespace.

mountinfo is provided by proc_namespace.ko. See also mounts, mountstats and the mount_namespaces(7) man page.

Excerpt from the proc(5) man page:

/proc/[pid]/mountinfo (since Linux 2.6.26)

 This file contains information about mounts in the
 process's mount namespace (see mount_namespaces(7)).  It
 supplies various information (e.g., propagation state,
 root of mount for bind mounts, identifier for each mount
 and its parent) that is missing from the (older)
 /proc/[pid]/mounts file, and fixes various other problems
 with that file (e.g., nonextensibility, failure to
 distinguish per-mount versus per-superblock options).

 The file contains lines of the form:

 36 35 98:0 /mnt1 /mnt2 rw,noatime master:1 - ext3 /dev/root rw,errors=continue
 (1)(2)(3)   (4)   (5)      (6)      (7)   (8) (9)   (10)   (11)

 The numbers in parentheses are labels for the descriptions
 below:

 (1)  mount ID: a unique ID for the mount (may be reused
      after umount(2)).

 (2)  parent ID: the ID of the parent mount (or of self for
      the root of this mount namespace's mount tree).

      If a new mount is stacked on top of a previous
      existing mount (so that it hides the existing mount)
      at pathname P, then the parent of the new mount is
      the previous mount at that location.  Thus, when
      looking at all the mounts stacked at a particular
      location, the top-most mount is the one that is not
      the parent of any other mount at the same location.
      (Note, however, that this top-most mount will be
      accessible only if the longest path subprefix of P
      that is a mount point is not itself hidden by a
      stacked mount.)

      If the parent mount lies outside the process's root
      directory (see chroot(2)), the ID shown here won't
      have a corresponding record in mountinfo whose mount
      ID (field 1) matches this parent mount ID (because
      mounts that lie outside the process's root directory
      are not shown in mountinfo).  As a special case of
      this point, the process's root mount may have a
      parent mount (for the initramfs filesystem) that lies
      outside the process's root directory, and an entry
      for that mount will not appear in mountinfo.

 (3)  major:minor: the value of st_dev for files on this
      filesystem (see stat(2)).

 (4)  root: the pathname of the directory in the filesystem
      which forms the root of this mount.

 (5)  mount point: the pathname of the mount point relative
      to the process's root directory.

 (6)  mount options: per-mount options (see mount(2)).

 (7)  optional fields: zero or more fields of the form
      "tag[:value]"; see below.

 (8)  separator: the end of the optional fields is marked
      by a single hyphen.

 (9)  filesystem type: the filesystem type in the form
      "type[.subtype]".

 (10) mount source: filesystem-specific information or
      "none".

 (11) super options: per-superblock options (see mount(2)).

 Currently, the possible optional fields are shared,
 master, propagate_from, and unbindable.  See
 mount_namespaces(7) for a description of these fields.
 Parsers should ignore all unrecognized optional fields.

 For more information on mount propagation see:
 Documentation/filesystems/sharedsubtree.txt in the Linux
 kernel source tree.

Examples

7530 fw 7.50 example:

root@fritz1:/var/mod/root# cat /proc/self/mountinfo

15 0 31:5 / / ro,relatime - squashfs /dev/root ro
16 15 0:6 / /dev rw,relatime - devtmpfs devtmpfs rw,size=113456k,nr_inodes=28364,mode=755
17 15 0:4 / /proc rw,relatime - proc proc rw
18 15 0:15 / /var rw,relatime - tmpfs tmpfs rw
19 15 0:16 / /sys rw,relatime - sysfs sysfs rw
20 16 0:13 / /dev/pts rw,relatime - devpts devpts rw,mode=600
21 19 0:11 / /sys/kernel/security rw,relatime - securityfs securityfs rw
22 19 0:17 / /sys/fs/pstore rw,relatime - pstore pstore rw
23 19 0:7 / /sys/kernel/debug rw,relatime - debugfs none rw
24 18 0:18 / /var/media/ftp rw,relatime - ubifs /dev/ubi0_3 rw,sync
25 24 8:2 / /var/media/ftp/LOG1-1 rw,relatime - ext4 /dev/sda2 rw,stripe=4,data=ordered
26 24 8:1 / /var/media/ftp/FRITZ1 rw,relatime - ext4 /dev/sda1 rw,stripe=8191,data=ordered
27 24 0:19 / /var/media/ftp/Onlinespeicher rw,nosuid,nodev,relatime - fuse https://sd2dav.1und1.de rw,user_id=0,group_id=100,allow_other,max_read=69632

Dependencies

Daily updated index of all dependencies of this object. Last update: GMT.
A ** in the Mod column marks info from Supportdata2 probes, which will always stay incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the Object occurs, not the Relation.

Relation Typ Object Mod Firmware Info Origin
0 dependencies for this object

Model-Matrix

Daily updated index of the presence, path and size of this object for each model. Last update: 2024-03-29 05:31 GMT.
Showing all models using this object. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom) label in the Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list comes from Supportdata2 probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata2 file or just a disabled feature.

Help Supportdata2

The data in this article is incomplete since it was manually collected using the Supportdata2 project.

Unlike the Supportdata-Probes which have been collected for years Supportdata2 is brand new and only has a few probes.
If you have access to a shell then please help to extend the Supportdata2 collection to improve this data.

It's easy and it's done in minutes. Please send created data as an Email attachment to the address listed here. Thanks!

SMW-Browser

Information is currently being retrieved from the backend.
 

Synonyms

Showing 1 related property.

m