irclog2html for #fredlug on 20070207

01:25.24*** join/#fredlug IrishW0lf (n=william@70-41-145-17.cust.wildblue.net)
01:26.39IrishW0lfhello all
01:43.07*** join/#fredlug IrishW0lf (n=william@70-41-145-17.cust.wildblue.net)
02:11.18plarsenhey IrishW0lf
02:11.42IrishW0lfhey plarsem
02:12.08IrishW0lfthats plarsen
02:12.45IrishW0lfhow are you doing
02:12.47plarsen<grumbles> is there anyone here that knows how to check for DUPLICATE disk volume labels?  I know the label of the volume I want to mount. But I need to find what/where Linux thinks there a duplicate label?
02:13.53jsmithLet me guess... your current hard drive has a label of VolGroup00, and the disk you want to mount has the same label
02:15.04plarsenjsmith: ehhh, no?? I never mount volume groups. Just logical volumes. These are two new volumes I've created. The only ones I created with labels.
02:15.22jsmithInteresting
02:16.06plarsenNone of the other mounted volumes/disk have a label :(
02:17.10plarsengrrrrr
02:17.18plarsenmount: LABEL=/u01 duplicate - not mounted
02:17.43plarsenwhere does linux cache the labels?
02:19.08stickstere2label
02:19.24plarsenyeah but no other partition returns that label
02:19.26stickster/sbin/e2label, that is
02:19.52plarsenSo it must see it somewhere else. I have it suspected for looking at the raw partition behind the LVM
02:20.33sticksterYou can check through /proc/partitions and use that as a feed for e2label
02:22.39plarsenwell, done that (through fstab) and same result. No other mountpoint/partition has that label
02:23.06plarsenYAY! mount -v shows the conflict.
02:23.20plarsenAnd it's an internal problem. The same mount point exists twice
02:23.27plarsenthrough /dev/dm and /dev/mapper
02:23.45sticksterYou have both?
02:23.52sticksterThat's kind of... special :-)
02:23.54plarsenyep, they both respond
02:23.57plarsenyep!!
02:24.00plarsendidn't ask for it.
02:24.06plarsenPure RHES4 32bit install
02:25.43plarsenGot an idea of how to "manage" that?
02:27.34sticksterI don't know yet whether you want to... how'd this happen to start with?
02:28.34plarsenstickster: hmmm - being stuborn ;)  Default RHES install, creating two logical volumes for /u01 and /u02 (oracle, yay!!) ... putting them in /etc/fstab using the LABEL=/u01 instead of a physical reference. Poof - error :)
02:28.37sticksterIt's fun to start yanking around underlying substrata, but if you can just change the sheets, that's always better
02:28.42plarsenI can solve it by not using the label
02:28.58plarsenagree
02:29.09plarsenI'm trying to figure out why the dm_mod gets loaded
02:29.25sticksterI think working _with_ the mapper might be a better idea, i.e. use the device /dev/<volname>/<lvname>
02:29.36sticksters/volname/volgroupname/
02:29.48plarsenThat's how I do it myself. I don't use the dm
02:30.05plarsenI only saw the dm devices in /proc/partitions
02:30.20plarsenAnd I see it in error reports from Oracle complaining it doesn't know how to handle dm devices ;)
02:30.27sticksterdm_mod is a requirement for lvm, yes?
02:30.49plarsendon't know ...
02:31.06sticksters/, yes\?//
02:31.22plarsen"major number of the device mapper" ... so yes, it's related.
02:31.24sticksterOops, infobot doesn't grok real REs
02:31.42sticksterinfobot, you suck
02:31.51infobotno, *you* suck!
02:31.51plarsenhehe
02:32.12plarseninfobot is a bit slow responding
02:42.03*** join/#fredlug IrishW0lf_afk (n=william@70-41-145-17.cust.wildblue.net)
03:06.50IrishW0lfwow, i seem to be having lag problems again
03:07.04sticksterYou and infobot, apparently
03:07.29IrishW0lflol, i guess so
03:10.35IrishW0lfstickster: per conversation with peter last pm concerning my problem with keyboard disconnects and major timeouts, i booted into bios setup last night and checked temps of system, cpu, and power
03:10.51sticksterAnd?
03:12.43IrishW0lfstarted at cpu=98degrees F went up to 102 deg F, system remained constant at 93 deg F, and power remained const at 104 deg F
03:13.10IrishW0lfthis am, found keyboard unresponsive
03:13.39IrishW0lfwondering if ps2 connector or keyboard might be bad
03:14.06stickster104 F is perfectly acceptable, so hmmm
03:14.15IrishW0lfare those temps manageble or running hot
03:14.41sticksterno, 40-ish C is just fine
03:15.13sticksterIf you're not seeing a steady climb, but stable temps, that's probably not an issue
03:15.27IrishW0lfok
03:17.25IrishW0lfdo you think the ps2 keyboard connector might be going bad?
03:18.46IrishW0lfi guess i could try either a serial or usb connection to test (i have both types on hand)
03:22.21IrishW0lfbbl
03:46.28*** join/#fredlug IrishW0lf (n=william@70-41-145-17.cust.wildblue.net)
04:01.10*** join/#fredlug IrishW0lf (n=william@70-41-145-17.cust.wildblue.net)
04:02.52IrishW0lfplarsen: did you get your mounting problem fixed?
04:03.50plarsenwell ... yes, sorta. I dropped my "wish" of using labels ;)
04:03.58plarsenbrb
04:04.27IrishW0lfok, well what's in a label anyway?
04:04.39IrishW0lfme too, brb
04:11.56plarsenlabels sorta have the community split. Some see (saw) it as the second comming, others as something the devil created.
04:12.21plarsenIt does make it possible to remove the risk of mounting the wrong volume on the wrong mount-point.
04:12.48plarsenIt also makes restoring easier, because you can restore to a new partition without having to change your fstab etc. for mounting.
04:32.43IrishW0lfso you label each vol (partition) as you would a HD rather than using hda, hdb, etc
04:33.21IrishW0lfor am i confusing volume with something else
04:33.27plarsenyep - instead of writing /dev/sda1 you write LABEL=<label>
04:33.44plarsenvolume/partition is the same thing in this case. It's where the filesystem is written.
04:33.55IrishW0lfok
04:34.41IrishW0lfis label an alias then
04:34.57plarsenyes; but it has to be an identifier more than an alias (unique)
04:36.48IrishW0lfso when i mount /home/data (refering to sda1), data is the label for that volume
04:38.31plarsenno
04:38.40plarsenThe label isn' tpart of your file structure.
04:39.04plarsenit's an "identifier" on the file system that linux reads as it scans partitions/volumes etc.
04:39.10IrishW0lfnow you have me confused
04:39.26plarsenentry in fstab might look like:
04:39.39plarsenLABEL=/boot  /dev/sda1 ext2 .............
04:39.41plarsenwups
04:39.47plarsenLABEL=/boot  /boot ext2 .............
04:39.49plarsenlike that
04:40.06plarsenit simply stands in place where you would put the actual path to the device.
04:40.56IrishW0lfdoes  it always have that designation ie. LABEL=
04:42.11plarsenif you want to use the volume label, yes. Simply the syntax
04:42.21plarsenthe name of the label in the above example is /boot
04:42.32plarsenIt's customary that you name the volume after it's mountpoint
04:45.52IrishW0lfso like proc /proc proc defults in fstab it would be LABEL=/home/Data   /home/
04:46.18IrishW0lfthat is /home/Data ext3
04:47.20plarsenproc is a special case; it's not based on labels. If your mountpoint is /home/Data - then you could label the filesystem that.
04:47.33plarsenRemember, labels is something you set; it's not set/given by the system.
04:47.44plarsenSorta like volume labels on FAT
04:48.04*** join/#fredlug quigleymd_afk (n=quigley@c-71-62-143-171.hsd1.va.comcast.net)
04:48.38IrishW0lfhow is a label of /home/Data useful as opposed to just indicating the mount point of the device
04:49.23IrishW0lfif the dev is mounted at the same point at startup
04:50.03plarsenit's a logical name, instead of a physical one. If you choose to move your filesystem to a new disk for instance, you keep the same label but it's "address" has change. By using labels, you don't need to update your system after a restore of the filesystem.
04:50.27plarsenWith LVM it's kinda superfisial, other than it makes it harder to make mount mixups.
04:52.53IrishW0lfalright i can see your point, i'll have to ponder it a bit before it sinks in <smile>
04:56.34IrishW0lfso  i would use that /sbin/e2label <label> to assign a label to the volume and then enter it in fstab as LABEL=<label> mountpoint filetype
04:58.06IrishW0lfand then if i switch HD's i just relabel the new HD and don't have to change the entry in fstab
05:02.39IrishW0lfbrb
05:09.54IrishW0lfi'm bakc
05:09.56IrishW0lfback
05:23.10plarsenk
05:30.35*** part/#fredlug quigleymd_afk (n=quigley@c-71-62-143-171.hsd1.va.comcast.net)
05:43.23IrishW0lfwell time to call it a night, falling asleep at the keyboard.  BTW, left system running in bios setup last night, lost connectivity to keyboard this morning.  Changed keyboards, will see if that was the problem.  not much fluctuation in temp   over night.
09:32.54*** join/#fredlug Xenophod (n=Xenophod@65.89.8.189)
13:39.52stickster_workIrishW0lf_afk: Another way to keep filesystems separated would be with the UUID= designator.  This is even safer since many Linux systems auto-label partitions during installation.  If you were examining a Linux box, you would want your examination station's /etc/fstab to either use physical partitions -- if you were using PATA drives and could guarantee their location doesn't change, or UUID= if you were using SCSI or SATA
13:41.31stickster_workThe UUID, or Universally Unique IDentifier, is basically a formatted 128-bit hash that is generated on all ext2/3 file systems and should never be duplicated from one partition to another, ever.
13:42.06IrishW0lf_afkstickster_work: ok, btw switching keyboards seems to have taken care of my disconnect problem everything is still functional this am
13:42.11stickster_workExcellent
13:42.57IrishW0lf_afkstill using the ps2 port, so it must have been the keyboard connector
13:43.35IrishW0lf_afkit did seem a tad loose
13:44.08IrishW0lf_afklater
13:45.16*** join/#fredlug jsmith (n=jsmith@h460562e8.area3.spcsdns.net)
13:46.02stickster_workSee ya IrishW0lf_afk
15:46.03*** join/#fredlug IrishW0lf_afk (n=william@70-41-145-17.cust.wildblue.net)
16:49.16*** join/#fredlug plarsen (n=plarsen@w158.z06400088.was-dc.dsl.cnc.net)
16:50.28plarsenwow - I'm awake and asleep at the same time. Wonder if I'm sleep walking or something.
19:15.13IrishW0lf_afkplarsen: it sure looks like it lol
19:38.28*** join/#fredlug IrishW0lf (n=william@70-41-145-17.cust.wildblue.net)
22:03.12*** join/#fredlug IrishW0lf (n=william@70-41-145-17.cust.wildblue.net) [NETSPLIT VICTIM]
22:06.50*** mode/#fredlug [+o stickster] by ChanServ
22:07.00*** topic/#fredlug by stickster -> FredLUG: Fredericksburg (VA) Linux Users Group -=- http://fred-lug.org/ -=- All experience levels warmly welcomed -=- Next Meeting: Tue Feb 20 2007 -=- Mailing list: http://groups.google.com/group/fredlug/
22:07.45*** mode/#fredlug [-o stickster] by stickster
22:19.21jsmithhttp://beta.zooomr.com/photos/33360@Z01/717163
22:19.38jsmithAnybody know why they named a state park after her?
23:11.22sticksterhttp://www.state.va.us/dcr/parks/hungrymo.htm
23:15.01plarsen_sleepjsmith: Did you know Asterix is in "Linux Journal" this month??
23:15.10plarsen_sleepAsterisk
23:15.11plarsen_sleepSorry
23:15.12plarsen_sleeplol
23:15.29plarsen_sleepCan't help messing up with my childhood cartoon hero
23:15.38jsmithplarsen_sleep: It's in almost every Linux Journal lately ;-)
23:16.00jsmithBut no, my subscription to Linux Journal must have run out, as I haven't received the magazine for several months
23:16.04plarsenwell, seems to be this month's theme
23:16.32jsmithw00t!
23:24.23plarsenWell, I would have thought they would have consulted with you guys ??   ohh well. Hope you enjoy the reading.
23:25.32jsmithNaw... they don't talk to people who actually write Asterisk docs...
23:25.42jsmithThey just wait for people to submit articles
23:26.12plarsenI meant the people who wrote the article of course ... well, their loss I guess.
23:26.46jsmithYeah... I'll have to grab myself a copy and figure out who wrote the articles
23:27.06jsmithGotta run...

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.