From: Peter Samuelson <peter@cadcamlab.org>
To: Tim Riker <Tim@Rikers.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: loop device length
Date: Sun, 17 Dec 2000 04:38:45 -0600 [thread overview]
Message-ID: <20001217043845.S3199@cadcamlab.org> (raw)
In-Reply-To: <3A398E0A.A12F973E@Rikers.org>
In-Reply-To: <3A398E0A.A12F973E@Rikers.org>; from Tim@Rikers.org on Thu, Dec 14, 2000 at 08:20:42PM -0700
[Tim Riker]
> losetup allows for setting a starting offset within a file for the
> loop block device. There however is no length parameter to permit
> setting the length. Adding a length parameter would allow for
> multiple fs images in a single file (or device) and would correctly
> handle programs like resize2fs.
You don't need a length field for this, although it may be a good idea.
Filesystems know how big they are. You only need to force it at mkfs
and resize time, and in both cases you can override the tool's
knowledge.
In other words, you *can* put multiple fs images on a single piece of
backing store as long as you manage the lengths manually, which you
have to do anyway since you're keeping track of the starting offsets.
All the length parameter buys is not having to specify the same length
to losetup and mke2fs. And a little protection from shooting yourself
in the foot, but by the time you are messing with stuff like this you
had better be careful anyway.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-17 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 3:20 loop device length Tim Riker
2000-12-17 10:38 ` Peter Samuelson [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=20001217043845.S3199@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=Tim@Rikers.org \
--cc=linux-kernel@vger.kernel.org \
/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