All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Niemayer <niemayer@isg.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: mounting loop-device on a 2048 byte/sector medium fails
Date: Wed, 24 Apr 2002 11:19:26 +0200	[thread overview]
Message-ID: <3CC6789E.D99AFF8A@isg.de> (raw)
In-Reply-To: <Pine.LNX.3.96.1020423181848.31248B-100000@gatekeeper.tmr.com>

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

Bill Davidsen wrote:

> On Mon, 22 Apr 2002, Peter Niemayer wrote:
> 
> > first I thought this was some loop-AES specific issue, but now I know
> > it isn't: When I try to mount a filesystem on a loop device which
> > is in turn using a 2048 byte/sector medium (a magneto-optical drive
> > in my case), the mount fails though mkfs & fsck are happy.
> 
> I reported this some time ago as a problem with using offset mounting CDs
> with a binary prefix before the ISO image. And since it seems that the
> problem is not the offset but the sector size, the problems may be
> related.
> 
> I'll look at this over the weekend if not before. It works with 2.0 and
> 2.2, I use it regularly, and it's the main thing keeping a few of my
> machines on 2.2.

Then I've got good news for you: Jari Ruusu just sent me a patch to the
loop device that fixes the problem!

As loop-AES has a super-set of features of the original loop device,
you may download loop-AES 1.6b here:

http://sourceforge.net/project/showfiles.php?group_id=28891&release_id=84590

... and replace the loop.c-2.4.diff file in it with the attached new version.

Or wait until there's an official new loop-AES release or until the maintainer
of the original loop.c applied a similar patch.

Regards,

Peter Niemayer

[-- Attachment #2: loop.c-2.4.diff.bz2 --]
[-- Type: application/octet-stream, Size: 7771 bytes --]

[-- Attachment #3: loop.c-2.4.diff.bz2.sign --]
[-- Type: text/plain, Size: 346 bytes --]

-----BEGIN PGP MESSAGE-----
Version: 2.6.3ia
Comment: http://loop-aes.sourceforge.net/PGP-public-key.asc

iQCVAwUAPMWt8zMKg0M6Ig9RAQH/QQP9EpbDQunKEa2gzgKmJaz66QQKKc5N1HcL
Uxq9VxHScoE1eANYdvduWa0ElMXLlKezp+0eysgkc15s8PVk7CavhzOEcFo5A8Uq
SFykaCRQiPXBOqJp8bpjDdraAsvIg34pSvj01BL/oWkKHxWxqfDZmfz4+dLprsAg
ytCPFRILU7Q=
=Dhzy
-----END PGP MESSAGE-----

      reply	other threads:[~2002-04-24  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22 19:03 mounting loop-device on a 2048 byte/sector medium fails Peter Niemayer
2002-04-23 22:21 ` Bill Davidsen
2002-04-24  9:19   ` Peter Niemayer [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=3CC6789E.D99AFF8A@isg.de \
    --to=niemayer@isg.de \
    --cc=davidsen@tmr.com \
    --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 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.