From: Heinz Mauelshagen <mauelsha@ez-darmstadt.telekom.de>
To: buytenh@dsv.nl
Cc: mge@ts1.ez-darmstadt.telekom.de, linux-lvm@msede.com
Subject: Re: [linux-lvm] loopback support?
Date: Mon, 12 Jul 1999 13:09:59 METDST [thread overview]
Message-ID: <199907121110.AA02186@mailgate1b.telekom.de> (raw)
In-Reply-To: <000501beca08$afa30c40$0102010a@adminstation.sgymsdam.nl>; from "Lennert Buytenhek" at Jul 9, 99 2:43 pm
Hi Lennert,
Support comes these days with upcoming LVM 0.7.
Cheers,
Heinz
> Hi all,
>
> I know this question has been asked before (Mar 16),
> but are there patches for making lvm work over the
> loopback device? I need to do some testing of my
> ext2 resizer on 2gig+ filesystems. All my partitions
> together (including the DOS ones*) might just have
> enough space free for this. I=B4ve tried some patching
> lvm before, but I believe the lvm code thinks that p=B4s
> in a device name are special in some way
> (/dev/loo=B4p=B40 **).
>
> Thanks in advance,
>
> Lennert Buytenhek
> <buytenh@dsv.nl>
>
> * Yes, I know, and flames go to /dev/null. I have parents
> and I can=B4t do much about it :-). And I=B4m getting tired of
> this needing to defend myself.
>
> ** Is this related to the c0s0p0t0x0y0z0 stuff that devfs
> is so fond of?
>
>
>
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Systemmanagement C/S T-Nova
Entwicklungszentrum Darmstadt
Heinz Mauelshagen Otto-Roehm-Strasse 71c
Senior Systems Engineer Postfach 10 05 41
64205 Darmstadt
mge@ez-darmstadt.telekom.de Germany
+49 6151 886-425
FAX-386
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~1999-07-12 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-09 12:43 [linux-lvm] loopback support? Lennert Buytenhek
1999-07-12 11:09 ` Heinz Mauelshagen [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=199907121110.AA02186@mailgate1b.telekom.de \
--to=mauelsha@ez-darmstadt.telekom.de \
--cc=buytenh@dsv.nl \
--cc=linux-lvm@msede.com \
--cc=mge@ts1.ez-darmstadt.telekom.de \
/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).