public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Detlev Offenbach <detlev@offenbach.fs.uunet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MO-Drive under 2.4.7 usinf vfat
Date: 22 Jul 2001 23:07:29 +0900	[thread overview]
Message-ID: <87g0bpoy5a.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <01072115265800.02284@majestix>
In-Reply-To: <01072115265800.02284@majestix>

Hi,

Detlev Offenbach <detlev@offenbach.fs.uunet.de> writes:

> Hi all,
> 
> I have just tested the new 2.4.7 kernel to see, whether it now works with a 
> MO-Drive using the vfat filesystem. Unfortunately it still doesn't. Mounting 
> a disk and writing to it is ok. However, when I try to read a file off the 
> disk, the program crashes with a Segmentation fault and I get a oops in the 
> messages file (see attachment). I tried ksymoops on this file, but either I 
> did something wrong or it couldn't analyse it.

Is the capacity of your MO disk more than 640M?
In order to clarify a problem, please send the debugging output of FAT.

---------------------- start example --------------------------------
 $ mount -t vfat /dev/sda /mnt -o debug
 $ dmesg | tail
  Type:   Optical Device                     ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 5, lun 0
sym53c875-0-<5,*>: asynchronous.
SCSI device sda: 310352 2048-byte hdwr sectors (636 MB)
sda: Write Protect is off
 sda:
MSDOS: Hardware sector size is 2048
[MS-DOS FS Rel. 12,FAT 16,check=n,conv=b,uid=0,gid=0,umask=022]
[me=0xf8,cs=8,#f=2,fs=1,fl=38,ds=77,de=512,data=85,se=0,ts=310352,ls=2048,rc=0,fc=4294967295]
Transaction block size = 2048
---------------------- end example --------------------------------

Perhaps, your MO disk will have the `ls' of a value smaller than 2048.
Logical sector size smaller than device sector size cannot be handled
with FAT of 2.4 series.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>


  parent reply	other threads:[~2001-07-22 14:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-21 13:26 MO-Drive under 2.4.7 usinf vfat Detlev Offenbach
2001-07-21 16:17 ` Steven Walter
2001-07-21 16:30   ` kgdb and/or kdb for RH7.1 Michael S. Miles
2001-07-21 19:16     ` Tigran Aivazian
2001-07-23  8:44       ` Amit S. Kale
2001-07-21 19:58     ` arjan
2001-07-22  1:58     ` Keith Owens
2001-07-22  3:09       ` Keith Owens
2001-07-22 14:07 ` OGAWA Hirofumi [this message]
2001-07-23 13:38 ` MO-Drive under 2.4.7 usinf vfat Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2001-07-21 16:15 Douglas Gilbert
2001-07-22 14:49 Douglas Gilbert
2001-07-22 17:47 ` OGAWA Hirofumi
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

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=87g0bpoy5a.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=detlev@offenbach.fs.uunet.de \
    --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