Mount: error No space left on device

I’m getting the a.m message when trying to mount a 630 MB magneto-optical
disk. Mounting of a 230 MB disk works ok. The same problem is for both an
formatted disk as well as a disk partitioned by fdisk.
Drive: Fujitsu MCR2320SS-S, 2.3 GB SCSI
Adapter: Adaptec CHIM
driver: Fsys.aha8scsi 4.25G

Any ideas, how to tackle the problem. Actually the drive seems to report
itself as a type 0 (Direct Access) not 7 (Optical) drive.
I have also two hard drives and a CD drirve, all EIDE, which are mounting
correctly at the boot time.

Juho Joensuu (juhodotjoensuu at dlcdotfi)

Juho Joensuu wrote:

I’m getting the a.m message when trying to mount a 630 MB magneto-optical
disk. Mounting of a 230 MB disk works ok. The same problem is for both an
formatted disk as well as a disk partitioned by fdisk.
Drive: Fujitsu MCR2320SS-S, 2.3 GB SCSI
Adapter: Adaptec CHIM
driver: Fsys.aha8scsi 4.25G
Any ideas, how to tackle the problem. Actually the drive seems to report
itself as a type 0 (Direct Access) not 7 (Optical) drive.
I have also two hard drives and a CD drirve, all EIDE, which are mounting
correctly at the boot time.

Two suggestions. First is, given the number of non-512-byte-sector
devices you have on your system, you may be running out of deblocking
buffers. Try increasing this with “Fsys.aha8scsi fsys -B 16”. Second,
you don’t provide the “sin ver” for Fsys itself, but some versions had
problems mounting partition tables from non-512-byte sector MO devices
(check your MO for the size, you may have a mix of 512 and 2k ones?).
Try upgrading to at least Fsys 4.24W.

Thanks for the suggestions. I was also myself thinking about that -B option.
According to the given formula the default value 8 should be enough
(2*(2048/512)) and even giving the -B 16 (or 32) didn’t help. And as I
said, reading and writing 230 MB disks works well.
The Fsys version is 4.24Y, I have installed the patch G and also other
patches found in the download area.
How I could find out the sector size of the media. Based on the error
message
“No space left on device
disk /dev/mo0.0 has 1241488 sectors”
the sector size is 1 k.
Another interesting thing is that if I’m executing “scsi_util /dev/mo0.0
scan”, it’s also showing the information of the EIDE devices ( /dev/hd0.0,
/dev/hd1.0 and /dev/cd0.0 ).
So, still in trouble.
Juho
“John Garvey” <jgarvey@qnx.com> wrote in message
news:du1pq9$8av$1@inn.qnx.com

Juho Joensuu wrote:
I’m getting the a.m message when trying to mount a 630 MB
magneto-optical
disk. Mounting of a 230 MB disk works ok. The same problem is for both
an
formatted disk as well as a disk partitioned by fdisk.
Drive: Fujitsu MCR2320SS-S, 2.3 GB SCSI
Adapter: Adaptec CHIM
driver: Fsys.aha8scsi 4.25G
Any ideas, how to tackle the problem. Actually the drive seems to report
itself as a type 0 (Direct Access) not 7 (Optical) drive.
I have also two hard drives and a CD drirve, all EIDE, which are
mounting
correctly at the boot time.

Two suggestions. First is, given the number of non-512-byte-sector
devices you have on your system, you may be running out of deblocking
buffers. Try increasing this with “Fsys.aha8scsi fsys -B 16”. Second,
you don’t provide the “sin ver” for Fsys itself, but some versions had
problems mounting partition tables from non-512-byte sector MO devices
(check your MO for the size, you may have a mix of 512 and 2k ones?).
Try upgrading to at least Fsys 4.24W.

Sorry, calculating wrong. Because the media is 640 MB the sector size then
must be 512. Fdisk is showing 64H 32S 606C = 606 Mbytes.
“Juho Joensuu” <juho.joensuu@dlc.fi> wrote in message
news:du3mtk$ih1$1@inn.qnx.com

Thanks for the suggestions. I was also myself thinking about that -B
option.
According to the given formula the default value 8 should be enough
(2*(2048/512)) and even giving the -B 16 (or 32) didn’t help. And as I
said, reading and writing 230 MB disks works well.
The Fsys version is 4.24Y, I have installed the patch G and also other
patches found in the download area.
How I could find out the sector size of the media. Based on the error
message
“No space left on device
disk /dev/mo0.0 has 1241488 sectors”
the sector size is 1 k.
Another interesting thing is that if I’m executing “scsi_util /dev/mo0.0
scan”, it’s also showing the information of the EIDE devices ( /dev/hd0.0,
/dev/hd1.0 and /dev/cd0.0 ).
So, still in trouble.
Juho
“John Garvey” <> jgarvey@qnx.com> > wrote in message
news:du1pq9$8av$> 1@inn.qnx.com> …
Juho Joensuu wrote:
I’m getting the a.m message when trying to mount a 630 MB
magneto-optical
disk. Mounting of a 230 MB disk works ok. The same problem is for both
an
formatted disk as well as a disk partitioned by fdisk.
Drive: Fujitsu MCR2320SS-S, 2.3 GB SCSI
Adapter: Adaptec CHIM
driver: Fsys.aha8scsi 4.25G
Any ideas, how to tackle the problem. Actually the drive seems to
report
itself as a type 0 (Direct Access) not 7 (Optical) drive.
I have also two hard drives and a CD drirve, all EIDE, which are
mounting
correctly at the boot time.

Two suggestions. First is, given the number of non-512-byte-sector
devices you have on your system, you may be running out of deblocking
buffers. Try increasing this with “Fsys.aha8scsi fsys -B 16”. Second,
you don’t provide the “sin ver” for Fsys itself, but some versions had
problems mounting partition tables from non-512-byte sector MO devices
(check your MO for the size, you may have a mix of 512 and 2k ones?).
Try upgrading to at least Fsys 4.24W.

Still digging deeper.
Mounting works well, if I take the alternate boot based on 4.25 patch level
E. Versions in the boot image are
Proc 4.25L
Fsys 4.24V
Fsys.eide 4.25A
Second EIDE driver is started in sysinit.1 file as well as the SCSI driver.
Versions for those drivers are
Fsys.eide 4.25G
Fsys.aha8scsi 4.25G
The boot image is based on
Proc 4.25Q
Fsys 4.24Y
Fsys.eide 4.25G
The size of the boot image is 499712
and that of the alternate boot 495616
Both are based on the standard install build file,

“Juho Joensuu” <juho.joensuu@dlc.fi> wrote in message
news:du3nau$ijj$1@inn.qnx.com

Sorry, calculating wrong. Because the media is 640 MB the sector size then
must be 512. Fdisk is showing 64H 32S 606C = 606 Mbytes.
“Juho Joensuu” <> juho.joensuu@dlc.fi> > wrote in message
news:du3mtk$ih1$> 1@inn.qnx.com> …
Thanks for the suggestions. I was also myself thinking about that -B
option.
According to the given formula the default value 8 should be enough
(2*(2048/512)) and even giving the -B 16 (or 32) didn’t help. And as I
said, reading and writing 230 MB disks works well.
The Fsys version is 4.24Y, I have installed the patch G and also other
patches found in the download area.
How I could find out the sector size of the media. Based on the error
message
“No space left on device
disk /dev/mo0.0 has 1241488 sectors”
the sector size is 1 k.
Another interesting thing is that if I’m executing “scsi_util /dev/mo0.0
scan”, it’s also showing the information of the EIDE devices (
/dev/hd0.0,
/dev/hd1.0 and /dev/cd0.0 ).
So, still in trouble.
Juho
“John Garvey” <> jgarvey@qnx.com> > wrote in message
news:du1pq9$8av$> 1@inn.qnx.com> …
Juho Joensuu wrote:
I’m getting the a.m message when trying to mount a 630 MB
magneto-optical
disk. Mounting of a 230 MB disk works ok. The same problem is for
both
an
formatted disk as well as a disk partitioned by fdisk.
Drive: Fujitsu MCR2320SS-S, 2.3 GB SCSI
Adapter: Adaptec CHIM
driver: Fsys.aha8scsi 4.25G
Any ideas, how to tackle the problem. Actually the drive seems to
report
itself as a type 0 (Direct Access) not 7 (Optical) drive.
I have also two hard drives and a CD drirve, all EIDE, which are
mounting
correctly at the boot time.

Two suggestions. First is, given the number of non-512-byte-sector
devices you have on your system, you may be running out of deblocking
buffers. Try increasing this with “Fsys.aha8scsi fsys -B 16”.
Second,
you don’t provide the “sin ver” for Fsys itself, but some versions had
problems mounting partition tables from non-512-byte sector MO devices
(check your MO for the size, you may have a mix of 512 and 2k ones?).
Try upgrading to at least Fsys 4.24W.
\

Juho Joensuu wrote:

E. Versions in the boot image are
Fsys 4.24V
The boot image is based on
Fsys 4.24Y

If the MO is non-512-byte, this does explain it as I posted
earlier, you need 4.24W to correctly handle the partition
table (unless, of course, you partitioned it under the “bad”
QNX4 version, then you will need to re-partition it under
the newer version).

How I could find out the sector size of the media.

It is typically written on the MO catridge itself, like on
the metal slide, or on the box they came in. Fsys will
always lie and map them all to 512 bytes (hence -B thing).

Thanks again,
I was inaccurate in my statement. If I boot with an older image based on
Fsys 4.24V, I can manage 230 MB, 640 MB and 1,3 GB media on 2,3 GB drive.
(Don’t have 2,3 GB media yet,) But with boot image based on 4.24Y (from
patch G, which I think is still a later version that 4.24W) I can only mount
230 MB. This the suggests that all those medias have 512 byte sector size?
The second EIDE driver is installed in sysinit.1 and is in both cases 4.25G
but the older image starts for the primary drive version 4.25A.
So it looks like Proc, Fsys, Fsys.eide and Fsys.aha8scsi are involved but
which one is the bad one?
Fujitsu doesn’t mark their drives (as I can see) and if the Fsys lies then I
really don’t know the sector size.

“John Garvey” <jgarvey@qnx.com> wrote in message
news:du4fd9$5l1$1@inn.qnx.com

Juho Joensuu wrote:
E. Versions in the boot image are
Fsys 4.24V
The boot image is based on
Fsys 4.24Y

If the MO is non-512-byte, this does explain it as I posted
earlier, you need 4.24W to correctly handle the partition
table (unless, of course, you partitioned it under the “bad”
QNX4 version, then you will need to re-partition it under
the newer version).

How I could find out the sector size of the media.

It is typically written on the MO catridge itself, like on
the metal slide, or on the box they came in. Fsys will
always lie and map them all to 512 bytes (hence -B thing).