*SOLVED* Re: [NTLUG:Discuss] syslog message ReiserFS: dm-3 <--what's dm-3??
Richard Geoffrion
ntlug at rain4us.net
Tue Jul 26 14:41:09 CDT 2005
well for those following..and who care... here's the deal.
My slackware install didn't come with 'devmap-name' oh no.. that'd be
too easy. So I found the multitools homepage (
http://christophe.varoqui.free.fr/wiki/wakka.php?wiki=Home ) and
downloaded a version that matched the requirements I had to offer. (I
am not running the latest 2.6 kernel so I opted for an older version of
multitools that didn't require it)
I was then able to compile and install the devmap-name utility.
I edited my /etc/udev/rules.d/udev.rules file and commented out the line
that caused the dm[s] to be ignored and uncommented out the line that
called the devmap-name utility. ( I added a symlink to devmap-name
where the slackware version of the udev.rules script expected to see it.)
This is the snippet from what my udev.rules file now looks like..and
some of the output from the logs..
--- from udev.rules---
# dm devices (ignore them)
# *remmed - I WANT them to be created!* KERNEL="dm-[0-9]*", NAME=""
# create a symlink named after the device map name
# note devmap_name comes with extras/multipath
KERNEL="dm-[0-9]*", PROGRAM="/etc/udev/scripts/devmap_name %M %m",
NAME="%k", SYMLINK="%c"
KERNEL="device-mapper", NAME="mapper/control"
---------
---some of the entries from /var/log/messages--
Jul 26 14:10:26 gwibkp kernel: ReiserFS: dm-0: found reiserfs format
"3.6" with standard journal
Jul 26 14:10:26 gwibkp udev[22263]: configured rule in
'/etc/udev/rules.d/udev.rules' at line 41 applied, added symlink '%c'
Jul 26 14:10:26 gwibkp udev[22263]: configured rule in
'/etc/udev/rules.d/udev.rules' at line 41 applied, 'dm-0' becomes '%k'
Jul 26 14:10:26 gwibkp udev[22263]: creating device node '/dev/dm-0'
----
---and now for a lookup---
# ls -l /dev/dm-0
brw-r----- 1 root root 253, 0 2005-07-26 14:10 /dev/dm-0
# devmap_name 253 0 ; echo
duck-offline
----
Which is the name of the LV! YAY! PHEW..
--
/dev/rtcg
More information about the Discuss
mailing list