I'm trying to use autofs to mount a directory structure. I have a directory with sub directories in it and all of them mounted on their respective filesystems
When I try to mount them on a remote server using autofs, I can access /dbname and list all its contents how ever if i go to /dbname/processing/data which is different filesystem i do not see any of its contents.
hello all,
I have a problem that just seem to show up. I was using autofs to mount home directory. It was working for about two week and now is just tsop working. I rebooted the erver and still not working. I can manually mount the directory but unable to mount via autofs. From the client I... (0 Replies)
Hi Guys,
Autofs works fine on AIX 5.2, but the same thing is not getting mounted automatically on AIX 5.3..
Is there ant difference for autofs confiiguration between 5.2 and 5.3
Thanks & Regards
Manu (0 Replies)
Hi Friends,
I am trying to configure autofs on rhel5.3 64bit to automount the nfs shares. It was working fine when i configured it first. After some days i can see its not working.
i can see the below sepcified error on the log file.
automount: rmdir_path: lstat of /NFS/test failed... (2 Replies)
I am trying to automount one of my NFS share to my client machine but it is not mounting
here is the scenario :
My server machine ip : 192.168.1.100
My client machine ip is : 192.168.1.102
on client machine i have configured the /etc/auto.master file :
/share(My mount point) ... (0 Replies)
I am running CentOS 6.3 as a VM on a host which has the same installation. I configured my NFS server and I am guessing it works. I say guessing because I can mount the desired folder with mount command on my client machine. So, when I run:
mount -t nfs -o vers=3 vm2.domain.com:/nethome /nethit... (7 Replies)
This is unfortunately for a Tru64 5.1 PK4 system.
I have Autofs running and it seems to read and mount the NIS maps, however, on a couple of maps, eventhough is says (rw), the user home directory of /home is (ro). See cut and paste Below. This prevents the automounting of Users home... (4 Replies)
Hi all,
Please help! After my solaris 10 is rebooted, I found my autofs seems not mounting the file systems.
I restart autofs service :
#svcadm -v restart svc:/system/filesystem/autofs:default
Action restart set for svc:/system/filesystem/autofs:default.
But still... (1 Reply)
Hi all,
I'm having trouble getting autofs working on a new install of Scientific Linux 7.2.
I have the files /etc/auto.master, /etc/auto/homes and /etc/auto.misc and /auto.direct setup, and they are copies of files on a working SL 6 machine. I can include the contents of the files at the end... (0 Replies)
Discussion started by: HuntWilliamR
0 Replies
LEARN ABOUT NETBSD
dm
DM(4) BSD Kernel Interfaces Manual DM(4)NAME
dm -- Device-mapper disk driver
SYNOPSIS
pseudo-device dm
DESCRIPTION
The dm driver provides the capability of creating one or more virtual disks based on the target mapping.
This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con-
figuration file, and how to partition disks. This driver is used by the Linux lvm2tools to create and manage lvm in NetBSD.
Currently, the linear, zero, and error targets are implemented. Each component partition should be offset at least 2 sectors from the begin-
ning of the component disk. This avoids potential conflicts between the component disk's disklabel and dm's disklabel. In i386 it is offset
by 65 sectors, where 63 sectors are the initial boot sectors and 2 sectors are used for the disklabel which is set to be read-only.
In order to compile in support for dm, you must add a line similar to the following to your kernel configuration file:
pseudo-device dm #device-mapper disk device
dm may create linear mapped devices, zero, and error block devices. Zero and error block devices are used mostly for testing. Linear
devices are used to create virtual disks with linearly mapped virtual blocks to blocks on real disk. dm Device-mapper devices are controlled
through the /dev/mapper/control device. For controlling this device ioctl(2) calls are used. For the implementation of the communication
channel, the proplib(3) library is used. The protocol channel is defined as a proplib dictionary with needed values. For more details, look
at sys/dev/dm/netbsd-dm.h. Before any device can be used, every device-mapper disk device must be initialized. For initialization one line
must be passed to the kernel driver in the form of a proplib dictionary. Every device can have more than one table active. An example for
such a line is:
0 10240 linear /dev/wd1a 384
dm The first parameter is the start sector for the table defined with this line, the second is the length in sectors which is described with
this table. The third parameter is the target name. All other parts of this line depend on the chosen target. dm For the linear target,
there are two additional parameters: The first parameter describes the disk device to which the device-mapper disk is mapped. The second
parameter is the offset on this disk from the start of the disk/partition.
SEE ALSO config(1), proplib(3), MAKEDEV(8), dmsetup(8), fsck(8), lvm(8), mount(8), newfs(8)HISTORY
The device-mapper disk driver first appeared in NetBSD 6.0.
AUTHORS
Adam Hamsik <haad@NetBSD.org> implemented the device-mapper driver for NetBSD.
Brett Lymn <blymn@NetBSD.org>,
Reinoud Zandijk <reinoud@NetBSD.org>, and
Bill Stouder-Studenmund <wrstuden@NetBSD.org> provided guidance and answered questions about the NetBSD implementation.
BUGS
This driver is still work-in-progress--there can be bugs.
BSD August 30, 2008 BSD