Linux LVM users
 help / color / mirror / Atom feed
From: "Jim Pick" <jim@transvirtual.com>
To: 140957@bugs.debian.org
Cc: linux-lvm@sistina.com
Subject: [linux-lvm] [PATCH] vg_check_name.c
Date: Tue Apr 23 16:59:02 2002	[thread overview]
Message-ID: <00f401c1eb12$4df44f80$d204a8c0@pepper> (raw)

This in regards to the following bug report I filed with Debian:


http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=140957&msg=4&repeatmerged=y
es

I did some more debugging to figure out what bit me, and it turns out that
my problem was that my volume group was named just "a", and there was a new
check added to 1.1rc1 in vg_check_name.c that matched it against "ataraid"
(defined in _devdir[] in lvm_dir_cache.c).  Very confusing.  I don't think
the check was intended to work that way, so here's a patch:

Index: vg_check_name.c
===================================================================
RCS file: /data/cvs/LVM/tools/lib/vg_check_name.c,v
retrieving revision 1.7
diff -u -r1.7 vg_check_name.c
--- vg_check_name.c 2002/03/12 13:58:04 1.7
+++ vg_check_name.c 2002/04/23 21:40:15
@@ -84,7 +84,7 @@
             else
                filter = _devdir[d];

-            if ( strncmp ( vg_name, filter, strlen ( vg_name)) == 0) {
+            if ( strncmp ( vg_name, filter, strlen ( filter)) == 0) {
                ret = -LVM_EVG_CHECK_NAME;
                break;
             }

This bit me on several machines, since I used the same naming convention.
:-(

Cheers,

 - Jim

BTW, I don't believe that the Debian bug severity should have been
downgraded to just "important", as I almost lost all my data.

             reply	other threads:[~2002-04-23 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 16:59 Jim Pick [this message]
2002-04-25  5:09 ` [linux-lvm] [PATCH] vg_check_name.c Heinz J . Mauelshagen

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='00f401c1eb12$4df44f80$d204a8c0@pepper' \
    --to=jim@transvirtual.com \
    --cc=140957@bugs.debian.org \
    --cc=linux-lvm@sistina.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