linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Stephen Childs <childss@cs.tcd.ie>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Problem with creation of dev entries on SL (RHEL) 4
Date: Thu, 18 May 2006 10:00:27 +0100	[thread overview]
Message-ID: <446C37AB.104@cs.tcd.ie> (raw)
In-Reply-To: <20060517184232.GC16774@percy.comedia.it>

Here's some snippets from the log:

activate/fs.c:176   Linking /dev/xenvg/gridmon_gridmon023__1147860249 -> 
/dev/mapper/xenvg-gridmon_gridmon023__1147860249
toollib.c:1087   Zeroing start of logical volume 
"gridmon_gridmon023__1147860249"
device/dev-cache.c:228   /dev/xenvg/gridmon_gridmon023__1147860249: Added 
to device cache
device/dev-io.c:425   Opened /dev/xenvg/gridmon_gridmon023__1147860249 RW 
O_DIRECT
device/dev-io.c:584   Wiping /dev/xenvg/gridmon_gridmon023__1147860249 at 
sector 0 length 8 sectors
device/dev-io.c:134   /dev/xenvg/gridmon_gridmon023__1147860249: block 
size is 4096 bytes
device/dev-io.c:456   Closed /dev/xenvg/gridmon_gridmon023__1147860249




metadata/metadata.c:1164   Found volume group "xenvg"
activate/dev_manager.c:1048   Getting device info for 
xenvg-gridmon_gridmon023__1147860249
ioctl/libdm-iface.c:1326   dm info 
IgMc4AcnOILtiudkjAXpuErUegVxunX66lb1awfZBR5rYYzIF64ogYnf98AcKHS0 O
mm/memlock.c:119   Unlocking memory
mm/memlock.c:138   memlock_count dec to 0
activate/fs.c:211   Removing link /dev/xenvg/gridmon_gridmon023__1147860249

The volume appears briefly in the /dev/mapper directory and then 
disappears again! How is this meant to work?

Stephen
-- 

      reply	other threads:[~2006-05-18  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 11:50 [linux-lvm] Problem with creation of dev entries on SL (RHEL) 4 Stephen Childs
2006-05-17 18:42 ` Luca Berra
2006-05-18  9:00   ` Stephen Childs [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=446C37AB.104@cs.tcd.ie \
    --to=childss@cs.tcd.ie \
    --cc=Stephen.Childs@cs.tcd.ie \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).