01:25.24 | *** join/#fredlug IrishW0lf (n=william@70-41-145-17.cust.wildblue.net) |
01:26.39 | IrishW0lf | hello all |
01:43.07 | *** join/#fredlug IrishW0lf (n=william@70-41-145-17.cust.wildblue.net) |
02:11.18 | plarsen | hey IrishW0lf |
02:11.42 | IrishW0lf | hey plarsem |
02:12.08 | IrishW0lf | thats plarsen |
02:12.45 | IrishW0lf | how are you doing |
02:12.47 | plarsen | <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.53 | jsmith | Let me guess... your current hard drive has a label of VolGroup00, and the disk you want to mount has the same label |
02:15.04 | plarsen | jsmith: 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.22 | jsmith | Interesting |
02:16.06 | plarsen | None of the other mounted volumes/disk have a label :( |
02:17.10 | plarsen | grrrrr |
02:17.18 | plarsen | mount: LABEL=/u01 duplicate - not mounted |
02:17.43 | plarsen | where does linux cache the labels? |
02:19.08 | stickster | e2label |
02:19.24 | plarsen | yeah but no other partition returns that label |
02:19.26 | stickster | /sbin/e2label, that is |
02:19.52 | plarsen | So it must see it somewhere else. I have it suspected for looking at the raw partition behind the LVM |
02:20.33 | stickster | You can check through /proc/partitions and use that as a feed for e2label |
02:22.39 | plarsen | well, done that (through fstab) and same result. No other mountpoint/partition has that label |
02:23.06 | plarsen | YAY! mount -v shows the conflict. |
02:23.20 | plarsen | And it's an internal problem. The same mount point exists twice |
02:23.27 | plarsen | through /dev/dm and /dev/mapper |
02:23.45 | stickster | You have both? |
02:23.52 | stickster | That's kind of... special :-) |
02:23.54 | plarsen | yep, they both respond |
02:23.57 | plarsen | yep!! |
02:24.00 | plarsen | didn't ask for it. |
02:24.06 | plarsen | Pure RHES4 32bit install |
02:25.43 | plarsen | Got an idea of how to "manage" that? |
02:27.34 | stickster | I don't know yet whether you want to... how'd this happen to start with? |
02:28.34 | plarsen | stickster: 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.37 | stickster | It's fun to start yanking around underlying substrata, but if you can just change the sheets, that's always better |
02:28.42 | plarsen | I can solve it by not using the label |
02:28.58 | plarsen | agree |
02:29.09 | plarsen | I'm trying to figure out why the dm_mod gets loaded |
02:29.25 | stickster | I think working _with_ the mapper might be a better idea, i.e. use the device /dev/<volname>/<lvname> |
02:29.36 | stickster | s/volname/volgroupname/ |
02:29.48 | plarsen | That's how I do it myself. I don't use the dm |
02:30.05 | plarsen | I only saw the dm devices in /proc/partitions |
02:30.20 | plarsen | And I see it in error reports from Oracle complaining it doesn't know how to handle dm devices ;) |
02:30.27 | stickster | dm_mod is a requirement for lvm, yes? |
02:30.49 | plarsen | don't know ... |
02:31.06 | stickster | s/, yes\?// |
02:31.22 | plarsen | "major number of the device mapper" ... so yes, it's related. |
02:31.24 | stickster | Oops, infobot doesn't grok real REs |
02:31.42 | stickster | infobot, you suck |
02:31.51 | infobot | no, *you* suck! |
02:31.51 | plarsen | hehe |
02:32.12 | plarsen | infobot is a bit slow responding |
02:42.03 | *** join/#fredlug IrishW0lf_afk (n=william@70-41-145-17.cust.wildblue.net) |
03:06.50 | IrishW0lf | wow, i seem to be having lag problems again |
03:07.04 | stickster | You and infobot, apparently |
03:07.29 | IrishW0lf | lol, i guess so |
03:10.35 | IrishW0lf | stickster: 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.51 | stickster | And? |
03:12.43 | IrishW0lf | started 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.10 | IrishW0lf | this am, found keyboard unresponsive |
03:13.39 | IrishW0lf | wondering if ps2 connector or keyboard might be bad |
03:14.06 | stickster | 104 F is perfectly acceptable, so hmmm |
03:14.15 | IrishW0lf | are those temps manageble or running hot |
03:14.41 | stickster | no, 40-ish C is just fine |
03:15.13 | stickster | If you're not seeing a steady climb, but stable temps, that's probably not an issue |
03:15.27 | IrishW0lf | ok |
03:17.25 | IrishW0lf | do you think the ps2 keyboard connector might be going bad? |
03:18.46 | IrishW0lf | i guess i could try either a serial or usb connection to test (i have both types on hand) |
03:22.21 | IrishW0lf | bbl |
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.52 | IrishW0lf | plarsen: did you get your mounting problem fixed? |
04:03.50 | plarsen | well ... yes, sorta. I dropped my "wish" of using labels ;) |
04:03.58 | plarsen | brb |
04:04.27 | IrishW0lf | ok, well what's in a label anyway? |
04:04.39 | IrishW0lf | me too, brb |
04:11.56 | plarsen | labels sorta have the community split. Some see (saw) it as the second comming, others as something the devil created. |
04:12.21 | plarsen | It does make it possible to remove the risk of mounting the wrong volume on the wrong mount-point. |
04:12.48 | plarsen | It also makes restoring easier, because you can restore to a new partition without having to change your fstab etc. for mounting. |
04:32.43 | IrishW0lf | so you label each vol (partition) as you would a HD rather than using hda, hdb, etc |
04:33.21 | IrishW0lf | or am i confusing volume with something else |
04:33.27 | plarsen | yep - instead of writing /dev/sda1 you write LABEL=<label> |
04:33.44 | plarsen | volume/partition is the same thing in this case. It's where the filesystem is written. |
04:33.55 | IrishW0lf | ok |
04:34.41 | IrishW0lf | is label an alias then |
04:34.57 | plarsen | yes; but it has to be an identifier more than an alias (unique) |
04:36.48 | IrishW0lf | so when i mount /home/data (refering to sda1), data is the label for that volume |
04:38.31 | plarsen | no |
04:38.40 | plarsen | The label isn' tpart of your file structure. |
04:39.04 | plarsen | it's an "identifier" on the file system that linux reads as it scans partitions/volumes etc. |
04:39.10 | IrishW0lf | now you have me confused |
04:39.26 | plarsen | entry in fstab might look like: |
04:39.39 | plarsen | LABEL=/boot /dev/sda1 ext2 ............. |
04:39.41 | plarsen | wups |
04:39.47 | plarsen | LABEL=/boot /boot ext2 ............. |
04:39.49 | plarsen | like that |
04:40.06 | plarsen | it simply stands in place where you would put the actual path to the device. |
04:40.56 | IrishW0lf | does it always have that designation ie. LABEL= |
04:42.11 | plarsen | if you want to use the volume label, yes. Simply the syntax |
04:42.21 | plarsen | the name of the label in the above example is /boot |
04:42.32 | plarsen | It's customary that you name the volume after it's mountpoint |
04:45.52 | IrishW0lf | so like proc /proc proc defults in fstab it would be LABEL=/home/Data /home/ |
04:46.18 | IrishW0lf | that is /home/Data ext3 |
04:47.20 | plarsen | proc 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.33 | plarsen | Remember, labels is something you set; it's not set/given by the system. |
04:47.44 | plarsen | Sorta 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.38 | IrishW0lf | how is a label of /home/Data useful as opposed to just indicating the mount point of the device |
04:49.23 | IrishW0lf | if the dev is mounted at the same point at startup |
04:50.03 | plarsen | it'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.27 | plarsen | With LVM it's kinda superfisial, other than it makes it harder to make mount mixups. |
04:52.53 | IrishW0lf | alright i can see your point, i'll have to ponder it a bit before it sinks in <smile> |
04:56.34 | IrishW0lf | so 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.06 | IrishW0lf | and then if i switch HD's i just relabel the new HD and don't have to change the entry in fstab |
05:02.39 | IrishW0lf | brb |
05:09.54 | IrishW0lf | i'm bakc |
05:09.56 | IrishW0lf | back |
05:23.10 | plarsen | k |
05:30.35 | *** part/#fredlug quigleymd_afk (n=quigley@c-71-62-143-171.hsd1.va.comcast.net) |
05:43.23 | IrishW0lf | well 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.52 | stickster_work | IrishW0lf_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.31 | stickster_work | The 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.06 | IrishW0lf_afk | stickster_work: ok, btw switching keyboards seems to have taken care of my disconnect problem everything is still functional this am |
13:42.11 | stickster_work | Excellent |
13:42.57 | IrishW0lf_afk | still using the ps2 port, so it must have been the keyboard connector |
13:43.35 | IrishW0lf_afk | it did seem a tad loose |
13:44.08 | IrishW0lf_afk | later |
13:45.16 | *** join/#fredlug jsmith (n=jsmith@h460562e8.area3.spcsdns.net) |
13:46.02 | stickster_work | See 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.28 | plarsen | wow - I'm awake and asleep at the same time. Wonder if I'm sleep walking or something. |
19:15.13 | IrishW0lf_afk | plarsen: 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.21 | jsmith | http://beta.zooomr.com/photos/33360@Z01/717163 |
22:19.38 | jsmith | Anybody know why they named a state park after her? |
23:11.22 | stickster | http://www.state.va.us/dcr/parks/hungrymo.htm |
23:15.01 | plarsen_sleep | jsmith: Did you know Asterix is in "Linux Journal" this month?? |
23:15.10 | plarsen_sleep | Asterisk |
23:15.11 | plarsen_sleep | Sorry |
23:15.12 | plarsen_sleep | lol |
23:15.29 | plarsen_sleep | Can't help messing up with my childhood cartoon hero |
23:15.38 | jsmith | plarsen_sleep: It's in almost every Linux Journal lately ;-) |
23:16.00 | jsmith | But no, my subscription to Linux Journal must have run out, as I haven't received the magazine for several months |
23:16.04 | plarsen | well, seems to be this month's theme |
23:16.32 | jsmith | w00t! |
23:24.23 | plarsen | Well, I would have thought they would have consulted with you guys ?? ohh well. Hope you enjoy the reading. |
23:25.32 | jsmith | Naw... they don't talk to people who actually write Asterisk docs... |
23:25.42 | jsmith | They just wait for people to submit articles |
23:26.12 | plarsen | I meant the people who wrote the article of course ... well, their loss I guess. |
23:26.46 | jsmith | Yeah... I'll have to grab myself a copy and figure out who wrote the articles |
23:27.06 | jsmith | Gotta run... |