From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>,
Alexander Viro <viro@math.psu.edu>
Subject: Re: MO-Drive under 2.4.7 usinf vfat
Date: 23 Jul 2001 02:47:24 +0900 [thread overview]
Message-ID: <87itgkdff7.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <3B5AE813.658ADC66@torque.net>
In-Reply-To: <3B5AE813.658ADC66@torque.net>
Hi,
Douglas Gilbert <dougg@torque.net> writes:
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:
> > Is the capacity of your MO disk more than 640M?
>
> No, the capacity is 635600896 bytes.
[...]
>
> > Perhaps, your MO disk will have the `ls' of a value smaller
> > than 2048.
> Yes, ls=512 .
>
> > Logical sector size smaller than device sector size cannot
> > be handled with FAT of 2.4 series.
>
> Great. When will that be fixed (Jens?) ? If not, can we get
> a more civilized response than the current oops?
The cause of this problem is me, and I think that it is the bug.
How should this problem be solved? I think that it is either of the
following.
1) logical sector size smaller than device sector size isn't
supported. (and output the message)
2) read a file data via block buffer (like FAT of 2.2 series).
3) other (drivers/block/loop.c?)
Please comment.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2001-07-22 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-22 14:49 MO-Drive under 2.4.7 usinf vfat Douglas Gilbert
2001-07-22 17:47 ` OGAWA Hirofumi [this message]
2001-07-24 8:33 ` Jens Axboe
2001-07-24 17:00 ` Alan Cox
2001-07-24 17:50 ` OGAWA Hirofumi
2001-07-25 6:35 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2001-07-21 16:15 Douglas Gilbert
2001-07-21 13:26 Detlev Offenbach
2001-07-21 16:17 ` Steven Walter
2001-07-22 14:07 ` OGAWA Hirofumi
2001-07-23 13:38 ` Pavel Machek
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=87itgkdff7.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=axboe@suse.de \
--cc=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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