From: Richard Russon <rich@flatcap.org>
To: Barubary <barubary@cox.net>
Cc: lkml <linux-kernel@vger.kernel.org>,
Anton Altaparmakov <aia21@cam.ac.uk>
Subject: Re: Change that to an NTFS bug not loopback
Date: 27 Feb 2002 00:03:20 +0000 [thread overview]
Message-ID: <1014768201.17005.25.camel@addlestones> (raw)
In-Reply-To: <000501c1bebf$80a3e460$a7eb0544@CX535256D>
In-Reply-To: <006001c1beb9$ea412690$a7eb0544@CX535256D> <3C7B7908.1040508@ellinger.de> <009c01c1bebe$41321730$a7eb0544@CX535256D> <000501c1bebf$80a3e460$a7eb0544@CX535256D>
Hi Barubary,
> I tried to mount a 20 meg ISO from an NTFS partition mounted read-only and
> it glitched. It has nothing to do with the size of the file. I would've
> checked smaller files if I had mkisofs handy, which I didn't when I tried
> it.
Reading through the thread, I've just tried everything you have.
I've used 2.4.18-rc4. I've first mounted an NTFS partition. Within
that I've mounted
1a) Another NTFS partition (from a device) 1Gb (< 2^31 bytes)
1b) Another NTFS partition (from a device) 2.2Gb (> 2^31 bytes)
2) Another NTFS partition (from a loop device) 2.2Gb (> 2^31 bytes)
3) An ISO image (from a loop device) 20Mb (< 2^31 bytes)
Please can you clarify what's going wrong. I can't seem to get the
NTFS driver to go wrong.
If I can repeat the problem, I can probably fix it.
> Now I'm afraid that it's a known bug and I've wasted your time... :(
Don't worry. If something doesn't work, someone here will want to hear
about it (and fix it).
Cheers,
FlatCap (Rich)
ntfs@flatcap.org
P.S. Anton's on holiday (current NTFS maintainer), so you've got me :-)
next prev parent reply other threads:[~2002-02-27 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 11:37 ISO9660 bug and loopback driver bug Barubary
2002-02-26 11:54 ` Jesper Juhl
2002-02-26 12:01 ` Rainer Ellinger
2002-02-26 12:08 ` Barubary
2002-02-26 12:17 ` Change that to an NTFS bug not loopback Barubary
2002-02-27 0:03 ` Richard Russon [this message]
2002-02-26 12:04 ` ISO9660 bug and loopback driver bug Alan Cox
2002-02-26 12:02 ` Barubary
2002-02-26 12:37 ` Alan Cox
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=1014768201.17005.25.camel@addlestones \
--to=rich@flatcap.org \
--cc=aia21@cam.ac.uk \
--cc=barubary@cox.net \
--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.