Re: mount command absurdly verbose?



On 11/22/2011 04:09 PM, Andras Simon wrote:
2011/11/22, Ralf Corsepius<rc040203@xxxxxxxxxx>:
On 11/22/2011 01:57 PM, Andras Simon wrote:

[...]

I use df.

Not that much better:

Real world example:

$ df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 50395844 32372316 15463528 68% /
..
tmpfs 3057628 46748 3010880 2% /run
/dev/sda3 50395844 32372316 15463528 68% /
tmpfs 3057628 46748 3010880 2% /run
...
/dev/sdb8 638902480 153233668 453214376 26% /users/user1
/dev/sdb8 638902480 153233668 453214376 26% /users/user2
/dev/sdb8 638902480 153233668 453214376 26% /users/user3
...

Hmmm. I wonder why /dev/sdb8 is mounted to 3 different places?

These are autofs-automounted local homes.

autofs mounts these home directories "on-demand", switching between
nfs-mounts and bind-mounts, depending on whether they are local or remote.

In this case, they currently are all local.

FWIW:

f14's mount displayed them this way:
# mount
..
/home/user1 on /users/user1 type none (rw,bind)
...

This reflects the actual situation and is human readable.



f16's "mount" displays them this way:
# mount
...
/dev/sdb8 on /users/user1 type ext4
(rw,relatime,seclabel,user_xattr,acl,barrier=1,data=ordered)
...

IMO, this unreadable and all wrong.

Ralf


--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


Relevant Pages

  • Re: mount() function problem !
    ... mount() attaches the filesystem specified by source (which is often a device name, ... point within a file system. ... details of the options available for each filesystem type. ... Specifies the journalling mode for file data. ...
    (comp.lang.c)
  • Re: [autofs] [RFC] Towards a Modern Autofs
    ... >entangling autofs with that work. ... >filesystem it's willing to export. ... >>map is mounted. ... The result is that some users will see mount points ...
    (Linux-Kernel)
  • Re: UFS Bug: FreeBSD 6.1/6.2/7.0: MOKB-08-11-2006, CVE-2006-5824, MOKB-03
    ... They can simply mount a filesystem with any number of SUID ... root binaries on it and have their way with the box. ... They have physical access to the machine. ...
    (FreeBSD-Security)
  • Re: Automove vs Noautomove in BPXPRMxx
    ... read/write filesystem and the executables are in a separate, ... trying to manually mount the filesystem or you have a corrupted mount ... Automove vs Noautomove in BPXPRMxx ... Are you saying you have the same data set name but 2 physically ...
    (bit.listserv.ibm-main)
  • Re: Notes on support for multiple devices for a single filesystem
    ... device is to have a mount option that contains the path to the block special ... an additional mount option when the device number is stored in the filesystem ... We can either do this in user space, or in kernel space. ...
    (Linux-Kernel)