Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Verify That the Hard Disk Did Not Mount

    Problem

    To verify that the hard disk (ad1) did not get mounted, use the following command:

    user@host> show system storage

    The following sample output was taken from a RE-333 Routing Engine.

    user@host> show system storage
    Filesystem        512-blocks       Used      Avail Capacity Mounted on
    /dev/ad0s1a           218690      60294     140902     30%  /
    devfs                     32         32          0    100%  /dev/
    /dev/vn0               20044      20044          0    100%  /packages/mnt/jbase
    devfs                     32         32          0    100%  /dev/
    /dev/vn1               51920      51920          0    100%  /packages/mnt/jkernel-6.1R1.4
    /dev/vn2               22328      22328          0    100%  /packages/mnt/jpfe-M160-6.1R1.4
    /dev/vn3                3844       3844          0    100%  /packages/mnt/jdocs-6.1R1.4
    /dev/vn4               23328      23328          0    100%  /packages/mnt/jroute-6.1R1.4
    /dev/vn5                8820       8820          0    100%  /packages/mnt/jcrypto-6.1R1.4
    mfs:139               127006      16914      99932     14%  /tmp
    /dev/ad0s1e            24234         28      22268      0%  /config
    procfs                     8          8          0    100%  /proc
    

    Solution

    The command shows that the hard disk (ad1) is not mounted. Instead, /var now exists only in the swap partition (mfs:139), so any contents saved to /var will not be saved at the next reboot.

    user@host> start shell
    user@host% ls -l /
    total 47
    -rw-r--r--  1 root  wheel  4735 Mar 31  2001 COPYRIGHT
    dr-xr-xr-x  2 root  wheel   512 Jan 20  2004 altconfig
    dr-xr-xr-x  2 root  wheel   512 Jan 20  2004 altroot
    drwxr-xr-x  2 root  wheel   512 Dec 29 12:00 bin
    dr-xr-xr-x  3 root  wheel   512 Feb  4 23:16 boot
    drwxr-xr-x  3 root  wheel   512 Feb  3 18:08 config
    dr-xr-xr-x  4 root  wheel  2084 Feb  4 23:18 dev dr-xr-xr-x  7 root  wheel  1536 Feb  4 23:19 etc
    lrwxr-xr-x  1 root  wheel    17 Dec 29 12:02 kernel -> /packages/jkernel
    dr-xr-xr-x  2 root  wheel   512 Jan 20  2004 mnt
    drwxr-xr-x  2 root  wheel   512 Feb  3 21:16 modules
    drwxr-xr-x  3 root  wheel  1536 Feb  3 21:19 packages
    dr-xr-xr-x  1 root  wheel   512 Feb  4 23:29 proc
    dr-xr-xr-x  2 root  wheel   512 Feb  3 21:15 root
    dr-xr-xr-x  3 root  wheel  1536 Feb  3 21:15 sbin
    drwxrwxrwt  3 root  wheel   512 Feb  4 23:19 tmp
    dr-xr-xr-x  8 root  wheel   512 Dec 29 12:00 usr
    lrwxr-xr-x  1 root  wheel     8 Feb  4 23:18 var -> /tmp/var
    

    The example shows that var has a symbolic link to the /tmp/var directory. It resides under the /tmp/var directory, and is mounted on the mfs partition.

    Published: 2012-08-20