All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: Roman Mamedov <rm@romanrm.ru>
Cc: "Fajar A. Nugraha" <list@fajar.net>,
	"linux-btrfs" <linux-btrfs@vger.kernel.org>,
	Mike Fleetwood <mike.fleetwood@googlemail.com>,
	Suman C <schakrava@gmail.com>
Subject: Re: lvm volume like support
Date: Wed, 27 Feb 2013 09:42:02 +0100	[thread overview]
Message-ID: <201302270942.03347.Martin@lichtvoll.de> (raw)
In-Reply-To: <20130227100558.37d86d82@natsu>

Am Mittwoch, 27. Februar 2013 schrieb Roman Mamedov:
> On Wed, 27 Feb 2013 13:23:23 +1100
> 
> "Fajar A. Nugraha" <list@fajar.net> wrote:
> > Not to mention the hassle in accessing the data if it resides on a 
> > partition inside the file (e.g. you need losetup + kpartx to access it,
> > and you must remember to do the reverse when you're finished with it).
> >
> > 
> >
> > In zfsonlinux it's very easy to do so since a zvol is treated pretty
> > much like a disk, and whenever there's a partition inside a zvol, a
> > coressponding device noed is also created automatically.
> 
> So I'd say what you (we) need is a generic Linux kernel framework that
> would allow treating any regular file pretty much like a disk. Not some
> filesystem-specific block device emulation kludge.
> 
> Btw some years ago there was a patchset adding proper automatic partition
> support to 'loop'; but it seems like that went nowhere, and I have no
> idea why something this useful did not end up being added into the
> mainline kernel.

Are you sure about the partition support? I thought something related to 
loop partition support has gone into some not so recent kernel.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2013-02-27  8:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 23:35 lvm volume like support Suman C
2013-02-26  0:59 ` Mike Fleetwood
2013-02-26  1:46   ` Fajar A. Nugraha
2013-02-26  5:35     ` Suman C
2013-02-26  5:48       ` Remco Hosman - Yerf-IT
2013-02-26  5:57       ` Roman Mamedov
2013-02-26  6:25         ` Suman C
2013-02-26  6:28           ` Remco Hosman - Yerf IT
2013-02-26  6:37             ` Alex Elsayed
2013-02-26  7:08             ` Dave Chinner
2013-04-19 18:13           ` Andy Grover
2013-02-26 10:30     ` Martin Steigerwald
2013-02-27  2:23       ` Fajar A. Nugraha
2013-02-27  4:05         ` Roman Mamedov
2013-02-27  8:42           ` Martin Steigerwald [this message]
2013-02-27  9:17             ` Roman Mamedov
2013-02-27  8:50           ` Alex Elsayed
2013-02-27  9:57             ` Alex Elsayed
2013-02-27 10:12               ` Alex Elsayed
2013-04-08 12:01                 ` David Sterba
2013-04-11 12:29                   ` David Sterba
2013-03-02  6:24               ` Marcus Sorensen

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=201302270942.03347.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list@fajar.net \
    --cc=mike.fleetwood@googlemail.com \
    --cc=rm@romanrm.ru \
    --cc=schakrava@gmail.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 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.