All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Carinhas <pac@fortuitous.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: Error: vbd: Segment phy
Date: Thu, 11 Nov 2004 09:04:44 -0600	[thread overview]
Message-ID: <20041111150444.GA22817@mail.fortuitous.com> (raw)
In-Reply-To: <200411102318.28163.mark.williamson@cl.cam.ac.uk>

On Wed, Nov 10, 2004 at 11:18:27PM +0000, Mark A. Williamson wrote:
> >   It's not mounted or in use anywhere. for some reason lvscan
> >   shows them all as being ACTIVE. Not sure why.
> 
> Hmmm, that's wacky.  There could be something funny going on that's confusing 
> Xend about what's mounted (maybe something doesn't parse properly...).
> 
> Could you please post the output of "mount" on the system where this fails so 
> we can try to deduce what's upsetting Xend.
 
Mark,
   I realize that the ACTIVE flag from lvscan is not relevant.
   I looked at /proc/lvm/global and it shows all unmounted volumes
   as closed:

    LVs: [AWDL  ] home                       8388608 /2048     1x open
         [AWDL  ] ksinfinity                 6291456 /1536     close
         [AWDL  ] sharedhost                20971520 /5120     close
         [AWDL  ] vserv1                     3145728 /768      close
         [AWDL  ] vserv2                     3145728 /768      close
         [AWDL  ] vserv3                     3145728 /768      close
         [AWDL  ] vserv4                     3145728 /768      close
         [AWDL  ] vserv5                     3145728 /768      close
         [AWDL  ] ksinfinity_swap             524288 /128      close
         [AWDL  ] sharedhost_swap            1048576 /256      close
         [AWDL  ] vserv1_swap                 262144 /64       close
         [AWDL  ] vserv2_swap                 262144 /64       close
         [AWDL  ] vserv3_swap                 262144 /64       close
         [AWDL  ] vserv4_swap                 262144 /64       close
         [AWDL  ] vserv5_swap                 262144 /64       close
 
 Indeed, home is the only mounted volume. Thanks for pointing
 that out.

-Phil Carinhas
--
 .--------------------------------------------------------.
 | Dr. Philip A. Carinhas       | pac(at)fortuitous.com   |
 | Fortuitous Technologies Inc. | http://fortuitous.com   |
 | Linux Networking & Security  | Tel : 1-512-351-7783    |
 `--------------------------------------------------------'


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

  parent reply	other threads:[~2004-11-11 15:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 22:05 Error: vbd: Segment phy Phil Carinhas
2004-11-10 22:18 ` Mark A. Williamson
2004-11-10 22:26   ` Phil Carinhas
2004-11-10 23:18     ` Mark A. Williamson
2004-11-10 23:27       ` Phil Carinhas
2004-11-11 15:04       ` Phil Carinhas [this message]
2004-11-11 15:20         ` Mark A. Williamson
     [not found]           ` <20041111161115.GA23136@mail.fortuitous.com>
     [not found]             ` <200411111621.37885.mark.williamson@cl.cam.ac.uk>
2004-11-11 16:29               ` Phil Carinhas

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=20041111150444.GA22817@mail.fortuitous.com \
    --to=pac@fortuitous.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.