From: Ming Zhang <mingz@ele.uri.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: RE: [linux-lvm] Problem doing basic LVM functions
Date: Wed, 17 May 2006 12:35:46 -0400 [thread overview]
Message-ID: <1147883746.6409.132.camel@localhost.localdomain> (raw)
In-Reply-To: <446b46dd.77df48cd.41ae.27b8@mx.gmail.com>
blind guess, lvm sometime do block device scan and search for metadata,
u happen to have nbd module available or compiled in kernel. so if you
set a skip list for all u nbd devices, or disable the nbd in u kernel, u
might be able to solve this.
but nbd code should check if nbdX is configured or not.
ming
On Wed, 2006-05-17 at 11:52 -0400, Ricardo Sanchez wrote:
> Toby
>
> Thanks for the reply. I am not using nbd nodes...the kernel started throwing
> out those messages I have never worked with nbd nodes. How can I destroy the
> nbd nodes? I just want to start all over again but can't. Every time I try
> to do lvm functions, it hangs on those messages.
>
> Thanks
>
> Ricardo
>
> -----Original Message-----
> From: linux-lvm-bounces@redhat.com [mailto:linux-lvm-bounces@redhat.com] On
> Behalf Of tkb9@adelphia.net
> Sent: Wednesday, May 17, 2006 10:19 AM
> To: LVM general discussion and development
> Subject: Re: [linux-lvm] Problem doing basic LVM functions
>
> ---- Ricardo Sanchez <sanchez.ricardo@gmail.com> wrote:
> > I created a basic volume group named "uservg" and added two PVs to it
> > successfully.
> >
> > After doing this, I deleted the partitions to the disks...
> > Every time I try to do a vgscan or vgremove it gives the following output:
> >
> > nbd0: Attempted send on closed socket
> > end_request: I/O Error, dev nbd0, sector 0
> > printk: 7 messages suppressed.
> > Buffer I/O Error on device nbd0, logical block 0
> > Buffer I/O Error on device nbd0, logical block 1
> > Buffer I/O Error on device nbd0, logical block 2
> > nbd0: Attempted send on closed socket
> > /dev/nb0: read failed after 0 of 4096 at 0: Input/output error
> > /dev/nb0: read failed after 0 of 4096 at 2199022141440: Input/output
> error
> > /dev/nb0: read failed after 0 of 4096 at 0: Input/output error
> > /dev/nb1: read failed after 0 of 4096 at 2199022141440: Input/output
> error
>
> Are you trying to use nbd nodes in LVM?
>
> I had the same problem using nbd & LVM. I first had to destroy & recreate
> the nbd nodes. I put each nbd node into a single disk md, & used the md
> nodes in my pv & vg.
>
> Been working fine that way for several months now, although running locate
> to find a file would crash the system, so I removed the slocate rpm.
>
> -Toby
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2006-05-17 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 14:19 [linux-lvm] Problem doing basic LVM functions tkb9
2006-05-17 15:52 ` Ricardo Sanchez
2006-05-17 16:35 ` Ming Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-17 16:53 tkb9
2006-05-16 22:39 Ricardo Sanchez
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=1147883746.6409.132.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--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).