I am getting old in this world.
#Since yesterday there are few problems. We couldn't access the internal servers and lab's web server yesterday due to some problems - switching hub problem, web server's configuration error, and cable problem, however, I solved that. Today, someone asked a mount problem. That seemed easy. That's was just the mount problem. I tried to fix the problem about ten minutes, but that was not just the mount problem. I found some strange messages in dmesg file as following:
[17179587.872000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com[17179588.792000] cdrom: open failed.[17179588.988000] device-mapper: dm-linear: Device lookup failed[17179588.988000] device-mapper: error adding target to table
Of course, I couldn't mount the filesystems as following:
root@gdoi2:~# mount -amount: /dev/hdb1 already mounted or /mnt/hdb1 busymount: /dev/hdb3 already mounted or /mnt/hdb3 busy
I never meet this problem before, so I did googling and I found the bad guy, it was libdevmapper1.0 init script that locked the disks. There was lots of people have the problem like me. The result is that a single disk cannot be used both for EVMS and for mounting the kernel's built-in partitions. There are three solutions to this problem. 1) Switch to using EVMS for ALL the volumes and partitions. 2) Tell EVMS to exclude any disks that contain partitions that you are going to mount using the kernel's built-in partitions. 3) Apply Base Device-Mapper Driver patch.
sysfs_devices { # "include" are the block devices found in the [sysfs_mount_dir]/block/ # directory that you want EVMS to use as disks. # # Block device names can be specified using "*", "?", and "[...]" # notations. include = [ * ] # "exclude" are the block devices found in the [sysfs_mount_dir]/block/ # directory that you don't want EVMS to use as disks. Entries here # will override any possible matches from the "include" setting. # # Block device names can be specified using "*", "?", and "[...]" # notations. exclude = [ hdb ] # "max_open_disks" is the maximum number of disks that EVMS will have # open file-descriptors for while the engine is running. The allowable # range is 1 to 1024, and the default value is 64. # max_open_disks = 64}-- hurryon 2006-07-13 13:52:06