Linux LVM users
 help / color / mirror / Atom feed
From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] [Bug#189650: lvcreate segfaults (possibly after renames)]
Date: Sun Apr 20 17:43:01 2003	[thread overview]
Message-ID: <20030419093127.GA1217@tykepenguin.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 15 bytes --]


-- 

patrick


[-- Attachment #2: Type: message/rfc822, Size: 4129 bytes --]

From: Alan Chandler <alan@chandlerfamily.org.uk>
To: submit@bugs.debian.org
Subject: Bug#189650: lvcreate segfaults (possibly after renames)
Date: Sat, 19 Apr 2003 09:08:52 +0100
Message-ID: <200304190908.56366.alan@chandlerfamily.org.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: lvm10
Version: 1:1.0.7-3

I have been methodically going through my system converting each filesystem to 
reiserfs.  This entails the following sort of sequence for /dev/vg/foo

lvcreate -L <size> -n newfoo vg
mkreiserfs /dev/vg/newfoo
mount /dev/vg/newfoo /mnt
rsync -aHxq /where foo mounted/ /mnt
umount /mnt
umount /where foo mounted
edit fstab to change filesystem type to reiserfs
lvremove /dev/vg/roo
lvrename vg newroo roo
mount /where foo mounted

After a while (varies, but could be when I start to reuse the PEs? ) the 
initial lvcreate seems to get to a stage where it segfaults repeatedly until 
I deactivate and reactivate the vg (vgchange -a n vg ; vgchange -a y vg).

I have done this on my (only) two systems at home (each with two vg and 
between 2 and 5 lv on each vg).  One is running sid, the other sarge.
- -- 
Alan Chandler
alan@chandlerfamily.org.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+oQQYuFHxcV2FFoIRAv/cAJ9AMwENJGSSewVbfyr9XvVkHRtsrwCfbLmM
jLMyGxR7uWB1mJP+Mo4IpO0=
=cU9e
-----END PGP SIGNATURE-----



             reply	other threads:[~2003-04-20 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-20 17:43 Patrick Caulfield [this message]
2003-04-22  3:23 ` [linux-lvm] [Bug#189650: lvcreate segfaults (possibly after renames)] 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=20030419093127.GA1217@tykepenguin.com \
    --to=caulfield@sistina.com \
    --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